Package: udev Version: 168-1 Followup-For: Bug #624469 retitle 624469 Fails to start: failed to bind control socket (address in use) thanks
I've just checked, and if I boot the system with init=/bin/sh and then manually run the first two rcS.d scripts (mountkernfs and udev), udev starts just fine. But if I let the system boot normally, udev fails to start, complaining that it can't bind the control socket (address in use). Any chance this represents a conflict with udev from the initramfs? In case it matters, this system uses LVM-on-crypto for the root filesystem and swap. That might change something about the boot process which triggers this problem. - Josh Triplett -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38-2-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages udev depends on: ii debconf [debconf-2.0] 1.5.39 Debian configuration management sy ii libc6 2.11.2-11 Embedded GNU C Library: Shared lib ii libselinux1 2.0.98-1+b1 SELinux runtime shared libraries ii libudev0 168-1 libudev shared library ii libusb-0.1-4 2:0.1.12-17 userspace USB programming library ii lsb-base 3.2-27 Linux Standard Base 3.2 init scrip ii util-linux 2.17.2-9.1 Miscellaneous system utilities Versions of packages udev recommends: ii pciutils 1:3.1.7-9 Linux PCI Utilities ii usbutils 1:001-1 Linux USB utilities udev suggests no packages. -- debconf information excluded -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
