On Mon, Jun 11, 2012 at 5:55 AM, Igor M Podlesny <for.poige+archlinux@gmail.com> wrote:
On 11 June 2012 11:31, Dave Reisner <d@falconindy.com> wrote: […]
but rather with the rest of userspace's expectations. There's little we can do in initscripts to combat the fact that recent versions of udev _require_ devtmpfs for proper operation. There's little we can do to
I don't think that stating aloud of assumptions in initscripts would hurt someone. Even if the only thing it could do is emitting a few warning and then even pause booting — at least it gives (gave) hints.
The point is that I realised that the warnings are redundant. A missing devtmpfs will print an error when we trie to mount it (before this warning would have been printed). If /usr is not mounted we won't ever get this far in the bootprocess anyway, so the warning would never be printed. The "transition period" has admittedly been short, but not because we chose it. We started printing the warnings when we realised that tha hard requirements would change in the future. Now that the hard requirements have changed (udev was updated and /lib moved to /usr/lib) the warnings are of no use any more (as explained above). This reminds me: a warning that I'd like to ADD is to warn when HARDWARECLOCK in rc.conf and the third line in /var/lib/hwclock/adjtime are out of sync. This is causing some subtle bugs. Cheers, Tom