Package: module-init-tools Version: 3.3-pre4-2 Severity: normal Our system suffered some filesystem corruption recently, and ended up with some named pipes in the /etc/modprobe.d directory. This completely prevented our system from booting. Modprobe tried to read all files in that directory whenever it ran, and it hung trying to open the named pipe; as a result it could not load any modules, so the system hung during boot. Unsurprisingly, it took us a long time to figure out what was going on and get it repaired.
I can't think of a reason to put a named pipe in /etc/modprobe.d, and a quick check that all configuration files are regular files would have saved us a lot of headache. I hope you'll consider making such a change to the Debian version of modprobe. Thanks! ----Scott. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-6-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages module-init-tools depends on: ii libc6 2.3.6.ds1-13etch7 GNU C Library: Shared libraries ii lsb-base 3.1-23.2etch1 Linux Standard Base 3.1 init scrip module-init-tools recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
