Created attachment 343417 [details] Relevant Gentoo news article Section 7.b (topic Activating Required Options) does not mention that devtmpfs support is required for the current udev (197 and newer) operation. I suggest adding the relevant requirement to section 7.b. Device Drivers ---> Generic Driver Options ---> [*] Maintain a devtmpfs filesystem to mount at /dev [ ] Automount devtmpfs at /dev, after the kernel mounted the rootfs
FYI, it's documented in http://www.gentoo.org/doc/en/udev-guide.xml plus warned about when you emerge udev's ebuild.
Oh! I found it to be also in the handbook here, both amd64 and x86. I don't know when it was added, but it's there. http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=7 Next select Maintain a devtmpfs file system to mount at /dev so that critical device files are already available early in the boot process. Code Listing 2.3: Enabling devtmpfs support Device Drivers ---> Generic Driver Options ---> [*] Maintain a devtmpfs filesystem to mount at /dev
Handbooks for x86 and x64 mentioned a need to activate devtmpfs support in the kernel, because the corresponding stage3 contain udev version newer than 171. I checked the current stage3 for Sparc and it indeed contains udev-171 which works fine without the mentioned option. Hence, if there are no plans to update the Sparc stage3 to include udev newer than 171, my suggestion is irrelevant.
It's not irrelevant. I'll take the udev stabilization as a guide and update those architectures that have udev-200 stable.
Oh well, udev-197-r8 is stable for all others as well, so I guess it wont hurt for the others.
Thanks, committed
