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 -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
