linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: SCSI Patches - mostly on/off-line stuff
Date: Fri, 19 Jan 2001 02:08:52 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-97987015612854@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-97925037703688@msgid-missing>

I see what you're thinking.  No, I mostly see these
distinctions as relating to code paths the kernel 
has to deal with; ideally, users don't see "pending".

We need that stuff to behave well (it took a while
for USB to do so, and the networking code is still
rolling in such changes) before we should expose it
to users.  IMO.


----- Original Message ----- 
From: Miles Lane <miles@megapathdsl.net>
To: David Brownell <david-b@pacbell.net>
Cc: <linux-scsi@vger.kernel.org>; <linux-hotplug-devel@lists.sourceforge.net>
Sent: Thursday, January 18, 2001 3:25 PM
Subject: Re: SCSI Patches - mostly on/off-line stuff


> David Brownell wrote:
> > 
> > Well, now that I think of it ... this may be a good way to capture
> > the two different kinds of "remove".  Think of "remove" as breaking
> > a binding between device and driver, and these scenarios:
> > 
> >     - One "remove" is done by removing the hardware.  That
> >       can't really be reversed ... gotta clean up any messy
> >       device and "higher level" state, errors all around.
> > 
> >     - Another is done by sysadmin request.  Hardware still
> >       there, driver still there ... but they're not bound.
> >       (Maybe it's install-new-driver time, say, or to make
> >       sure hardware removal won't cause trouble.)
> > 
> > In that latter case there's a lot of flexibility.  Why are you
> > thinking a "remove" might want to get undone?
> 
> Would you clarify how you envision a user working with a
> pending remove?  Is it an implementation where a long
> period of time might pass before the the device is actually
> removed?
> 
> Could something like this happen?
> 
> - I start compiling XFree86 on a removable device and tell
>   the system to unmount the media and remove the device
>   when the compile is complete, a "pending remove" is set.
> 
> - During the compile, I realize that I want to make some
>   additional source modifications, so I want to cancel the
>   device removal and continue accessing the device.
> 
> I may be misunderstanding the sequence of events and how 
> that might impact a user.
> 
> Miles


_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  parent reply	other threads:[~2001-01-19  2:08 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-11 21:56 SCSI Patches - mostly on/off-line stuff Douglas Gilbert
2001-01-11 22:43 ` Oliver.Neukum
2001-01-17 20:32 ` David Brownell
2001-01-18  0:08 ` Douglas Gilbert
2001-01-18  9:03 ` Oliver Neukum
2001-01-18  9:25 ` Miles Lane
2001-01-18 15:37 ` Eric Youngdale
2001-01-18 16:20 ` Venkatesh Ramamurthy
2001-01-18 16:49 ` Prasenjit Sarkar
2001-01-18 16:50 ` Venkatesh Ramamurthy
2001-01-18 17:03 ` Venkatesh Ramamurthy
2001-01-18 18:14 ` David Brownell
2001-01-18 19:12 ` Oliver Neukum
2001-01-18 19:20 ` Prasenjit Sarkar
2001-01-18 19:45 ` Miles Lane
2001-01-18 21:08 ` Douglas Gilbert
2001-01-18 21:41 ` Miles Lane
2001-01-18 22:07 ` David Brownell
2001-01-18 22:15 ` David Brownell
2001-01-18 22:45 ` Oliver Neukum
2001-01-18 23:10 ` Oliver Neukum
2001-01-18 23:25 ` Miles Lane
2001-01-18 23:37 ` Oliver Neukum
2001-01-19  2:08 ` David Brownell [this message]
2001-01-19  2:10 ` Bob Frey
2001-01-19  2:16 ` Venkatesh Ramamurthy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-linux-hotplug-97987015612854@msgid-missing \
    --to=david-b@pacbell.net \
    --cc=linux-hotplug@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).