[moving to hotplug list ...]
On Wed, Jan 26, 2005 at 06:23:16PM -0500, Mukker, Atul wrote:
> Or more likely, by placing our agent in /etc/dev.d directory. Unfortunately,
> there seems be not a consensus here as well. On system has "default" and
> "net" directories and other has "block", "input",
I sent this a few days ago and thought somone might be able to shed some light ?
have a i posted to the wrong list?
thanx
--Chris
- Forwarded message from [EMAIL PROTECTED] -
Date: Fri, 21 Jan 2005 00:48:22 +1030
From: [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
Subject: 2.6.1
James,
It appears there is a missing class_device_del.
The comments for transport_remove_device indicate
that transport_remove_classdev should call it
(which the attached patch does), but the comment in
attribute_container_remove_device:
If you want a
* two phase release: remove from visibility a
> > > I could try to improve the highmem situation / sg-handling. Or do you
> > > plan to do it, Jamie?
> >
> > It's on my list of things to do, but I doubt I'll have any time to do
> > anything about in the next few months. So if you have the time and
> > desire please go ahead! I'll can test any
James,
Here is a patch to update a few bugs in the 3ware driver for
5/6/7/8000 controllers.
-Adam
diff -Naur linux-2.6.11-rc2-mm1/drivers/scsi/3w-.c linux-2.6.11-rc2-mm2/driv
ers/scsi/3w-.c
--- linux-2.6.11-rc2-mm1/drivers/scsi/3w-.c 2004-12-24 13:35:28.0 -0
800
+++ linux-2.6
*** please cc: replies in email as i'm not subscribed to the list. ***
I'm using usb and 1394 to hotplug various devices (dvd-rw, drives, etc).
kernel 2.6.9.
To unplug, I use the procedure:
unmount device (if it's mounted)
sync
echo "scsi remove-single-device 0 0 0" > /proc/scsi/scsi
then i cat
>
> And what do you mean "different implementations for /sbin/hotplug"?
> What distros do not use the standard "linux-hotplug" type
> scripts, or if not the scripts, the same functionality?
You are right, even though distributions (I checked Red Hat and SuSE) have
different /sbin/hotplug scripts
Simply pulling two FC cables from a host and re-cabling incorrectly
(think a switch of two HBA cables) or a surprise reconfiguration of a
storage system target could lead to a situation where the potential for
data corruption is ripe. While it may not be reasonably possible to
prevent data corrupt
> Thanks for the suggestion. After more exploration, looks like different
> distribution have different implementations for /sbin/hotplug. This may
> aggravate the issue for applications. For now, we will stick with a wait and
> watch after bus scan :-(
What do you mean? Just use the /etc/dev.d n
Newer kernels also have kobject_uevent, which lets any application use
netlink to look for hotplug events.
-Brian
Mukker, Atul wrote:
Thanks for the suggestion. After more exploration, looks like different
distribution have different implementations for /sbin/hotplug. This may
aggravate the issue
10 matches
Mail list logo
