On Thu, 23 Jan 2003 14:06:36 -0700
Steven Dake <[EMAIL PROTECTED]> wrote:
>
> I cant speak about OS/X, but I have crashed windows several times
> (BSOD) while hot removing a USB SCSI CDROM.
You can crash 98 and NT by simply removing a CD without telling them...
On Fri, Jan 24, 2003 at 10:09:32AM -0800, Matthew Jacob wrote:
> > It's like when I pull the power plug because my system is totally hosed and
> > I want to start over. I know I can cause damage by doing that, but I would
> > be upset if the new system booted back to the broken state it was in wh
>
> It's like when I pull the power plug because my system is totally hosed and
> I want to start over. I know I can cause damage by doing that, but I would
> be upset if the new system booted back to the broken state it was in when I
> unplugged it.
I had this conversation with doug offlist- thi
My $.02:
The comparing of a saved device list snapshot with the current device should
be the responsibility of a user-space daemon, provided that the kernel
exposes enough information to uniquely identify the devices (like serial
numbers, or some other UID if no ser num exists).
The kernel wou
>The comparing of a saved device list snapshot with the current device
should
>be the responsibility of
>From a usability standpoint, I don't think any such comparing should be
done by anyone. When I unplug a device and then plug it in again, I want a
total reset. I'm willing to take my lump
> >>...
> >
> >
> > Could this time limit be fixed (or parameterized) known to all LLDDs?
> > This would allow one to try and avoid flooding SCSI with detach/reattach
> > events for the 'same' device.
>
> And what exactly is the "same" device? And who's keeping history
> about devices that have p
Matthew Jacob wrote:
I want:
LLDD to SCSI: device is gone
SCSI to LLDD: Ok. I'll handle from here on.
LLDD: OK. I am gone. And won't have any contact until the next device is
plugged in.
...
Could this time limit be fixed (or parameterized) known to all LLDDs?
This would allow one to try and a
On Thu, Jan 23, 2003 at 05:54:57PM -0700, Steven Dake wrote:
> >I want:
> >LLDD to SCSI: device is gone
> >SCSI to LLDD: Ok. I'll handle from here on.
> >LLDD: OK. I am gone. And won't have any contact until the next device is
> >plugged in.
> >
> >
> The downside of this approach is that the LLD
I want:
LLDD to SCSI: device is gone
SCSI to LLDD: Ok. I'll handle from here on.
LLDD: OK. I am gone. And won't have any contact until the next device is
plugged in.
The downside of this approach is that the LLDD must now be able to
detect insertions and removals when it may not be able to d
> I want:
> LLDD to SCSI: device is gone
> SCSI to LLDD: Ok. I'll handle from here on.
> LLDD: OK. I am gone. And won't have any contact until the next device is
> plugged in.
>
> The process can be somewhat more complicated, under some conditions:
> - it never fails
> - it is done within a finite,
Am Donnerstag, 23. Januar 2003 21:41 schrieb Steven Dake:
> Oliver and others,
>
> In regards to hotswap, any real operating system should be _told_ that a
> block device is going to be removed from the top. There are several
> reasons.
Users don't do what they should. It is as simple as that.
Th
Oh, well. I've pulled my camera in the middle of reads and just got the
usual whininess.
I think I was reacting to your "get what they deserve" comment. The end
goal of USB should probably *be* an alert that said "oh, dear, that
wasn't helpful- please put that memory stick back so I can finish
wr
I cant speak about OS/X, but I have crashed windows several times (BSOD)
while hot removing a USB SCSI CDROM. As you will notice, when you run
windows and attach a device, there is a program that is started that
allows you to notify the os of the removal so that it may properly
remove the devi
>
> The key is that the removal request should come from the top, not the
> bottom. If someone is stupid enough to surprise remove a device (ie:
> unplug their USB SCSI device while the device is in use by the OS), they
> get what they deserve (I/O errors, dirty OS data, queued up requests
> which
14 matches
Mail list logo
