I did updates today on one machine. It seems to have included a new version of udev, I'm guessing udev-197-r3. I saw no warning messages however upon reboot the machine won't boot completely complainign that I don't have tmpfs in my kernel. A quick Google on another machine shows an ebuild with edits within the last few hours, but I don't know if this is what's really on the machine. http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/sys-fs/udev/udev-197-r2.ebuild?view=markup Specifically # required kernel options 102 CONFIG_CHECK="~DEVTMPFS" 103 ERROR_DEVTMPFS="DEVTMPFS is not set in this kernel. Udev will not run." If this warning appeared I didn't see it and it didn't (apparently) stop the machine from installing the new version. I rebooted, because it was udev and I sort of have to, and now that box is hosed. Maybe I got caught by some timing issue on a mirror and an older ebuild, or maybe I missed the message. I don't know. Reproducible: Always Steps to Reproduce: 1. emerge -DuN @world 2. 3. Actual Results: crash, bang, Expected Results: Should have booted, or should have stopped me from installing without the proper kernel options. Can't provide emerge --info as the machine doesn't boot. Will post more info if appropriate after the machine is back up. Likely this is just me.
OK, easy enough to fix with SystemRescueCD. Built a new kernel with CONFIG_DEVTMPFS=y and it booted fine. If the intention was to not install udev-197 without CONFIG_DEVTMPFS set it didn't work. If the intention was that I'd see the message then in the middle of other things then I didn't and that's my problem. Cheers
CONFIG_CHECK="~DEVTMPFS" has been in place since udev-180, which has been in the tree since Feb 2012. It CANNOT be made fatal: - there are systems where the kernel configuration is NOT available to check. - it's required at runtime, not at build time, you need to be able to build udev on a system without it. williamh: I would suggest a news item about making sure the kernel options are set.
(In reply to comment #2) > CONFIG_CHECK="~DEVTMPFS" has been in place since udev-180, which has been in > the tree since Feb 2012. > > It CANNOT be made fatal: > - there are systems where the kernel configuration is NOT available to check. > - it's required at runtime, not at build time, you need to be able to build > udev on a system without it. > > williamh: > I would suggest a news item about making sure the kernel options are set. We discussed about news item and decided it wasn't required. We can't force people to read and when they don't, they don't get to file bugs. *** This bug has been marked as a duplicate of bug 408947 ***
(In reply to comment #2) > CONFIG_CHECK="~DEVTMPFS" has been in place since udev-180, which has been in > the tree since Feb 2012. > > It CANNOT be made fatal: I_KNOW_WHAT_I_AM_DOING?
(In reply to comment #3) > (In reply to comment #2) > > CONFIG_CHECK="~DEVTMPFS" has been in place since udev-180, which has been in > > the tree since Feb 2012. I'm not going to argue with any decision you guys take. However I run basically stable machines and I don't think I ever saw udev-180. Stable seems to have gone from 171-r9 to today's 197-r3 release (according to what's in my packages directory) so the 180 rev wasn't something stable users like me saw coming. Again, I'm totally cool with any decision you take on this matter.
*** Bug 453186 has been marked as a duplicate of this bug. ***
