Your message dated Fri, 15 Apr 2011 18:52:59 +0200
with message-id <[email protected]>
and subject line Re: Bug#622893: /etc/init.d/udev should not rely on /run
unless it's actually writable
has caused the Debian Bug report #622893,
regarding /etc/init.d/udev should not rely on /run unless it's actually writable
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
622893: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622893
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: udev
Version: 167-2
Severity: important
The latest udev upgrades completely broke my system, because somebody
shipped /run (was it base-files?), but /etc/init.d/udev was run when the
root FS is still mounted read-only. As a result, it sees /run and tries
to create stuff under it and fails, aborts, and the rest of the boot
process was screwed because /dev was not populated. (I don't know why it
didn't mount tmpfs over /run, which *would* have avoided the problem.)
`\rm -rf /run` fixed the problem.
Regardless of whose fault it is that /run is broken, IMNSHO
/etc/init.d/udev should not be using it unless it's actually writable
--- not just permissions writable, but it shouldn't be used at all if
the filesystem it's on is mounted read-only, or if it can't be written
to for whatever other reason. At the very least, /etc/init.d/udev should
catch failures and fallback to /dev/.udev if /run fails for any reason
(if anything, /dev/ is at least guaranteed to be writable, since if not,
we're screwed anyway and there's no point in continuing).
I'll leave it up to the maintainer to decide what severity this bug
should be at. (I was going to file it as critical but since removing
/run fixed the problem, I'll settle with 'important').
T
--
PNP = Plug 'N' Pray
--- End Message ---
--- Begin Message ---
On Apr 15, "H. S. Teoh" <[email protected]> wrote:
> Regardless of whose fault it is that /run is broken, IMNSHO
> /etc/init.d/udev should not be using it unless it's actually writable
It does not, /run/udev/ needs to exist too and this only happens to
people who installed 167-1 after upgrading to the broken version of
base-files, so it is not a major concern.
Actually I'd rather have the system fail catastrophically than have hard
to spot bugs caused by /dev/.udev/ used first and /run/udev/ later.
--
ciao,
Marco
signature.asc
Description: Digital signature
--- End Message ---
