Op 19 nov. 2011, om 19:59 heeft McClintock Matthew-B29882 het volgende geschreven:
> On Sat, Nov 19, 2011 at 8:29 AM, Otavio Salvador > <ota...@ossystems.com.br> wrote: >>> It must be online though in this case? >> >> The code you add needs to be running on target and doesn't work at >> rootfs built time. This is bad and adds more complications to >> read-only-fs support. > > This works *perfectly* with a read only fs. Each time it boots removes > the non-working serial ports. One could argue that it does NOT work > completely as expected with a writable file system. > >>>> This could be done with a specific package that could mangle the >>>> image at first boot if really need but doing it by default on oe-core >>>> seems the wrong way. >>> >>> Isn't that exactly what this is doing? >>> >>> Easy enough to add this to a separate recipe or bbapends elsewhere if >>> there is disagreement. >> >> The need to diverge from machine default is the exception and this >> could be handled on the image being built, as post rootfs hook or an >> specific package with postinst to be run at target boot to setup it, >> and not by default. > > This will not work as a post rootfs hook as I've explained before. Let > me give you a more concrete example: We have a root file stored in > flash. We use it to boot from on a system with 4 serial ports. We use > the same image again to boot several kvm instances each of which only > have 1 serial port. The kvm instances will have spurious init messages > about respawning getty. Or you could just ditch sysvinit and switch to systemd. Systemd will only spawn a getty when udev says the device is there. And even better, every getty config is a file you can delete to disable it if for some reason the kernel reports the serial port to be there and you don't want a getty. regards, Koen _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
