9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Ronald G Minnich <rminnich@lanl.gov>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] detaching devices in kernel
Date: Fri,  4 Oct 2002 12:38:41 -0600	[thread overview]
Message-ID: <Pine.LNX.4.33.0210041237570.8559-100000@xed.acl.lanl.gov> (raw)
In-Reply-To: <369b4bf86b28f222780348113b23861a@plan9.bell-labs.com>

On Fri, 4 Oct 2002 presotto@plan9.bell-labs.com wrote:

> Once the device is notices, it's there forever.  The exception is
> the bitsy were we've started putting in stuff to take out pccards.
> We need to move that work everywhere, just haven't gotten around
> to it.

thanks for the clarification.

What would be the process by which a device is removed. A new function in
the interface (detach?) or some sequence of existing functions?

ron



  reply	other threads:[~2002-10-04 18:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-04 18:33 presotto
2002-10-04 18:38 ` Ronald G Minnich [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-10-04 18:47 presotto
2002-10-04 16:03 Russ Cox
2002-10-04 15:50 andrey mirtchovski

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=Pine.LNX.4.33.0210041237570.8559-100000@xed.acl.lanl.gov \
    --to=rminnich@lanl.gov \
    --cc=9fans@cse.psu.edu \
    /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).