Page MenuHomeFreeBSD

For video consoles, only launch a getty if the device exists.
ClosedPublic

Authored by imp on Apr 23 2018, 2:57 PM.
Tags
None
Referenced Files
Unknown Object (File)
Thu, Nov 14, 10:05 PM
Unknown Object (File)
Tue, Nov 5, 8:01 AM
Unknown Object (File)
Oct 13 2024, 5:01 AM
Unknown Object (File)
Sep 24 2024, 9:39 AM
Unknown Object (File)
Sep 24 2024, 8:49 AM
Unknown Object (File)
Sep 17 2024, 11:05 PM
Unknown Object (File)
Sep 4 2024, 4:59 PM
Unknown Object (File)
Aug 30 2024, 7:06 AM
Subscribers

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

Looks good. Have you thought about merging the files into a single, architecture-independent one?

This revision is now accepted and ready to land.Apr 23 2018, 6:16 PM

Looks good. Have you thought about merging the files into a single, architecture-independent one?

I've thought about it, but there's still enough difference that I want to give it more thought. I'm thinking a default ttys file with a per-arch override would be better since MIPS is unlikely to ever have video console support, for example. I'd like to think about it in the back of my head for a bit.

I'm pretty sure we have MIPS boards (well, BERI running in FPGA, but still) with Terasic... screen-thingys with console on them, here at Cambridge. Not sure how it's configured regarding ttys(5), though, or if it even goes through vt(4) - although it certainly looks like a text console.

This revision was automatically updated to reflect the committed changes.

I'm pretty sure we have MIPS boards (well, BERI running in FPGA, but still) with Terasic... screen-thingys with console on them, here at Cambridge. Not sure how it's configured regarding ttys(5), though, or if it even goes through vt(4) - although it certainly looks like a text console.

That's why I'm approaching this with some caution. I'll have a common file, but then allow people to override it. But I'm torn about that, since it's more an image assembly issue to change it rather than a per-arch thing, so I'll cook on it for a bit.

Perhaps have a common file (can't help but notice it seems to be the only per-arch etc/ file, so we could get rid of the whole mechanism this way), and have per-image overrides specified by release/*/WHATEVER.conf files, like the rest of per-image things?

Perhaps have a common file (can't help but notice it seems to be the only per-arch etc/ file, so we could get rid of the whole mechanism this way), and have per-image overrides specified by release/*/WHATEVER.conf files, like the rest of per-image things?

But release/*/WHATEVER.conf isn't used for mergemaster and etcupdate... so we can't just run head-long into this...