FS#9739 - udev in testing doesn't respawn udevd like in previous releases
Attached to Project:
Arch Linux
Opened by Hussam Al-Tayeb (hussam) - Sunday, 02 March 2008, 13:28 GMT
Last edited by Thomas Bächler (brain0) - Friday, 19 September 2008, 07:18 GMT
Opened by Hussam Al-Tayeb (hussam) - Sunday, 02 March 2008, 13:28 GMT
Last edited by Thomas Bächler (brain0) - Friday, 19 September 2008, 07:18 GMT
|
Details
After the removal of udev_start, if I 'init s' and then
'init 5' (for whatever reason), I have to manually run
'udevd --daemon'.
This wasn't the case before as udevd was automatically respawned. I realize that there aren't many cases where 'init s' is needed. but since this worked before, it is clearly a regression. Maybe 'init 5' should check if udevd isn't running and run it in /etc/rc.multi Without udevd, certain things like gnome-volume-manage/gnome-mount/hal appear to stop working properly. |
This task depends upon
need to fix that stuff finally....
First question: should it? Should 'init s' terminate everything, or only non-critical ones?
So then 'init 5' does not rerun udev?
Second question: should not switching from S to 5 rerun rc.multi only? If this is the case, anything done in rc.sysinit should NOT be undone by 'init s'
I remember that switching runlevels 3 -> s -> 3 resulted in incorrect udev reloading and reasonless syslog reloading, so the status of the system after such switch back & forth was different.
When it goes away this bug will still remain
[darek@agnieszka ~]$ ls -l /dev/bus/usb/002/006
crw-r--r-- 1 root root 189, 133 kwi 6 23:51 006
[darek@agnieszka ~]$ sudo /etc/start_udev
Hasło:
mounting... ramfs at /dev
Creating initial udev device nodes:
Kernel >= 2.6.15 and supports uevents
udev startup is finished! - time = 4
[darek@agnieszka ~]$ ls -l /dev/bus/usb/002/006
crw-rw-r-- 1 root scanner 189, 133 kwi 6 23:54 006
Thanks you :) You may close the bug.