Hi All,

My limited contribution to the udev issue sounds like this:

(main source:
http://git.kernel.org/?p=linux/hotplug/udev.git;a=blob;hb=HEAD;f=README)

In my understanding there are only a couple of requirements the above
website mentions which are (possibly) not met in T2:

1) Groups and users
„The system must have the following group names resolvable at udev
startup:
disk, cdrom, floppy, tape, audio, video, lp, tty, dialout, kmem.
Especially in LDAP setups, it is required, that getgrnam() is able to resolve
these group names with only the rootfs mounted, and while no network is
available.”

In my T2 (trunk) installation the following groups are not there:
cdrom, floppy, tape, lp, dialout,

I am not sure that groups ’tape’ and ’dialout’ are
really needed, however in the above README  that is explicitely stated.

I have noticed that also group ’uucp’ and user
’vcsa’ are claimed to be missing by udev.

2)  /dev/tmp
“Very early in the boot process, the /dev/ directory should get a
'tmpfs'
filesystem mounted, which is populated from scratch by udev. Created nodes
or changed permissions will not survive a reboot, which is
intentional.”

The only item in /etc/fstab  which may seem similar is:
none  /dev/shm   tmpfs   defaults   0  0

At this point I am not sure where exactly the problem lies. My guess would
be either /dev/tmp (instead of /dev/shm) is expected by udev or /dev/shm
is created too late (-> I am also not sure what exactly “very early
[in the boot process]” menas, I deduce from the context that in any
case it should be done before udev be loaded.


The fact is that

a) udev-event several times claims /dev/tmp-x-y missing before entering
the runlevel (in my case) 3

b) some process claims during boot process, immediately before entering 
runlevel 3 missing /dev/null

I am not expert in kernel programming and in the boot process, so I can
not judge with certainty that all these facts are connected, however they
seem to be.

best regards,

helasz



----------------------------------------------------------- 
If you wish to unsubscribe from this mailing, send mail to
[email protected] with a subject of: unsubscribe t2

Reply via email to