Okay, looking at it again, since problem still persists. Log of failing udev installation looks like this:
Setting up udev (0.140-2) ... run_command: calling: test udevadm_test: version 140 test: unrecognized option '--subsystem=net' run_command: calling: test udevadm_test: version 140 test: unrecognized option '--subsystem=net' Warning: Fake start-stop-daemon called, doing nothing Populating the new /dev filesystem temporarily mounted on /tmp/udev.IJgNHd/... Warning: Fake start-stop-daemon called, doing nothing error binding control socket, seems udevd is already running Cannot start udevd. (rc=1) dpkg: error processing udev (--configure): subprocess post-installation script returned error exit status 1 postinst calls udevd --daemon twice; trying to stop udevd with a fake start-stop-daemon that does not do anything, which fails. At Sat, 28 Mar 2009 16:25:13 +0900, Junichi Uekawa wrote: > > Hi, > > At Mon, 23 Mar 2009 00:48:14 +0100, > Marco d'Itri wrote: > > > > [1 <text/plain; us-ascii (quoted-printable)>] > > On Mar 23, Junichi Uekawa <dan...@netfort.gr.jp> wrote: > > > > > > > udev seems to want to start a daemon even when policy-rc.d says no, > > invoke-rc.d cannot be used because the daemon must be started directly > > without using the init script. > > > > > There shouldn't be another instance of udev running, so it sounds like > > Except that there is, because udevd is failing to create the > > @/org/kernel/udev/udevd abstract local domain socket which is created > > only by udevd. > > So this part puzzled me. > > And I'm now trying to reproduce this problem but debootstrap doesn't > seem to be creating sid chroot today for other reasons. > > > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org