Bug#621036: udev fails to load modules at startup: cannot create, /run/udev//root-link-rule: Read-only file system
#issue 1: udev failing during boot The bug is in the sysv init script for udev: It has set -e and if [ -d /run/ ]; then mkdir -p /run/udev/rules.d/ create_dev_root_rule /run/udev/ else This will obviously fail when /run is ro, the script will exit and as a consequence udevd is never started. This is the issue that was originally reported which breaks the system horribly and is trivial to fix in the udev init script. #issue 2: udev being restarted during runtime as /run will be writable now, it will use /run and create a subdirectory /run/udev, even if /run is not on a tmpfs yet. This doesn't really break anything but clutters /run and is more a cosmetic issue. I think Rogers' proposal in #620995 is reasonable. The udev package should keep using /dev/.udev for now (even if /run exists). As soon as we have a proper initscripts in the archive, udev can use /run and add a corresponding versioned depends. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#621036: udev fails to load modules at startup: cannot create /run/udev//root-link-rule: Read-only file system
On Wed, 6 Apr 2011, Marco d'Itri wrote: > reassign 621036 base-files > retitle 621036 base-files creates an unuseable /run, breaking udev and the > whole system > affects 621036 udev > block 620995 with 621036 620191 > thanks > > On Apr 06, Gianluigi Tiesi wrote: > > Indeed this happens because your system has /run/ but it is not > writeable. udev does not depend on /run being available, but if it > exists then it must be useable. I do not believe this to be > unreasonable. I think this bug clearly shows that it is unreasonable indeed, because currently /run exists but the package in charge of making it useable has not been modified yet. I just was told to create /run as a placeholder but certainly base-files will not be in charge of making it work. For this reason I fail to see how this breakage is supposed to be fixed in base-files (according to your reassign). Do you mean that base-files should also make /run to work? That *is* unreasonable, a lot more than udev using /run without it being ready, IMHO. So: Would it be too much difficult for udev not to use /run until it is ready? I think that would be the best solution for this, so I would ask you to reconsider this reassign that you made. (Otherwise I will simply remove /run and leave it to initscripts. I think that would be a pity, because it would be a sign of how inflexible our software is). Thanks. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#621036: udev fails to load modules at startup: cannot create /run/udev//root-link-rule: Read-only file system
reassign 621036 base-files retitle 621036 base-files creates an unuseable /run, breaking udev and the whole system affects 621036 udev block 620995 with 621036 620191 thanks On Apr 06, Gianluigi Tiesi wrote: Indeed this happens because your system has /run/ but it is not writeable. udev does not depend on /run being available, but if it exists then it must be useable. I do not believe this to be unreasonable. It was really stupid for base-files to ship a broken /run, but it is still unclear what the best solution is. > but now even downgrading (dpkg -i of 166-1) udev does not solve the problem I can't see how this could be true. -- ciao, Marco signature.asc Description: Digital signature
Bug#621036: udev fails to load modules at startup: cannot create /run/udev//root-link-rule: Read-only file system
Package: udev Version: 167-1 Severity: grave Tags: sid I've just upgraded udev from 166-1 to 167-1, but udev is not anymore able to load modules, e.g. network cards 166-1 was ok but now even downgrading (dpkg -i of 166-1) udev does not solve the problem (I've also called update-initramfs) I think it's related to base-files 6.2 that added /run I suspect the udev part in initrd should mount tmpfs on /run Regards -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (x86_64) Kernel: Linux 2.6.26-2-xen-amd64 (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
