udev-087, kernel 2.6.16-r7, baselayout-1.12.0_pre19-r2 (also occurred with baselayout-1.11.14-r8.ebuild) udevd --daemon would fail at boot time, although it would run correctly at a bash shell, with debug warnings about missing user 'tss' who owns the tpm devices according to udev rules. `useradd tss` allowed it to start at boot. where it gets strange is that I do not have tpm enabled in the kernel, nobody else has this user and they seem to do fine, and the rules file contains more user ids my system doesnt have (eg, cdrw), and yet udev doesnt care about them. on newer baselayouts with device_tarball=no this means an unbootable system.
Eh? Who's tss? What's tpm? Attach your kernel .config and relevant dmesg part and reopen then.
Created attachment 86562 [details] zcat /proc/config.z >> sysconfig
Attached config, there is no relevant part of dmesg, because no errors were logged. udevd just wouldnt start with boot. As for who tss is, beats me.. Here's the line from /etc/udev/rules.d/50-udev.rules: KERNEL=="tpm*", NAME="%k", OWNER="tss", GROUP="tss", MODE="0600" tpm* is all the trusted computing palladium stuff we all cant wait to rush out and buy.
*** This bug has been marked as a duplicate of 99564 ***
