Andrew Benton wrote: > On Thu, 15 Sep 2011 21:46:08 +0100 Matthew Burgess > <matt...@linuxfromscratch.org> wrote: > >> So, based on the above, 5 is definitely something to look into I >> think. If that doesn't pan out, then I think option 2 is the next >> 'least worst'. > > Or you could set the time with a bootscript.
Only if you know which RTC-class device the system is using. :-) (It's probably required to set the time with a bootscript if you're using NTP, though I don't know for sure. AFAIK there aren't any standard uevents for "the network has been configured" that could be used as a trigger.) > Same with alsactl restore. run them after udev has finished and > everything's mounted. Why do these things have to be done by udev? Originally, they would pollute the udev database with failed events, until those events were retried. Of course, that's not relevant anymore, and even when it was, it was just a couple extra zero-byte files in a tmpfs. Upstream (at least, udev upstream) is *really* pushing hard for everyone to use something like systemd, though, where everything is event-driven. I don't think that's a good idea (except as a hint for now) for LFS, but I don't think it's too bad to go that route where it makes sense.
signature.asc
Description: OpenPGP digital signature
-- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
