Package: hotplug
Version: N/A; reported 2004-04-02
Severity: normal
This does not apply specically to the system I'm reporting from. I'm
installing a wireless card, and was horrified to find that its firmware
is expected to be someplace under /usr.
Chap 3 of FHS 2.3 begins:
Chapter 3. The Root Filesystem
Purpose
The contents of the root filesystem must be adequate to boot,
restore, recover, and/or repair the system.
To be able to perform all these functions you may equire a working
network in order to NFS-mount /usr, working USB/firewire to mount a
memory drive and so on.
This is why the kernel modules, fdisk etc are in /lib, /bin or /sbin and
why libc is in /lib and not /usr/lib.
-- System Information
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux Dolphin 2.4.18-686 #1 Sun Apr 14 11:32:47 EST 2002 i686
Locale: LANG=C, LC_CTYPE=C
Package: hotplug
Version: N/A; reported 2004-04-02
Severity: normal
This does not apply specically to the system I'm reporting from. I'm
installing a wireless card, and was horrified to find that its firmware
is expected to be someplace under /usr.
Chap 3 of FHS 2.3 begins:
Chapter 3. The Root Filesystem
Purpose
The contents of the root filesystem must be adequate to boot,
restore, recover, and/or repair the system.
To be able to perform all these functions you may equire a working
network in order to NFS-mount /usr, working USB/firewire to mount a
memory drive and so on.
If the firmware for some critical device is inaccessible, you simply www.pathname. com/fhs/ pub/fhs- 2.3.html# THEROOTFILESYST EM.
cannot perform these critical functions. See
http://
This is why the kernel modules, fdisk etc are in /lib, /bin or /sbin and
why libc is in /lib and not /usr/lib.
-- System Information
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux Dolphin 2.4.18-686 #1 Sun Apr 14 11:32:47 EST 2002 i686
Locale: LANG=C, LC_CTYPE=C