Your message dated Mon, 16 Jul 2007 18:49:37 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: hotplug
Version: 0.0.20040329-15
Severity: normal
In my new-built system, there is SCSI controller with separately
loadable module. Its SCSI disks are physical volumes for LVM. But LVM
startup script runs before hotplug, so the SCSI module is not loaded
at that time. It does not see physical volumes therefore. One
workaround it to restart LVM startup script once more after hotplug.
Another is to put necessary module names in /etc/modules since
modutils|module-init-tools scripts run before LVM.
So I think hotplug and LVM maintainers should negotiate their order on
startup.
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.8.1
Locale: LANG=uk_UA.UTF-8, LC_CTYPE=uk_UA.UTF-8
Versions of packages hotplug depends on:
ii debconf 1.4.34 Debian configuration management sy
ii grep 2.5.1.ds1-3 GNU grep, egrep and fgrep
ii module-init-tools 3.1-pre5-6 tools for managing Linux kernel mo
ii procps 1:3.2.3-1 The /proc file system utilities
-- debconf information:
hotplug/ignore_pci_class_display: true
hotplug/net_agent_policy: hotplug
* hotplug/static_module_list:
* hotplug/usbd_enable: true
* hotplug/usb_keyboard:
hotplug/x11_usbmice_hack: false
--- End Message ---
--- Begin Message ---
This package has been removed from Debian unstable. I'm therefore
closing this bug report. The package has been removed because it
has been superseded by udev. It's quite unlikely that your bug still
exists in udev, but if it does, please let me know.
--
Martin Michlmayr
http://www.cyrius.com/
--- End Message ---
