From: Francisco Ballesteros <nemo@lsub.org>
To: Russ Cox <rsc@swtch.com>,
Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] hot plugging
Date: Fri, 9 Sep 2005 21:02:46 +0200 [thread overview]
Message-ID: <600308d605090912024fee9947@mail.gmail.com> (raw)
In-Reply-To: <ee9e417a05090911515d17b15@mail.gmail.com>
Of course, the drivers (and its framework) must admit
you to plug in/out the hw without crashing the system :-)
And you have to handle dependencies between them.
On 9/9/05, Russ Cox <rsc@swtch.com> wrote:
> I think that these are two different issues. No matter what
> the right way is to present the ever-changing hardware to
> the user, there is plenty of restructuring to do just to track
> the ever changing hardware at the hardware level itself.
>
> Russ
>
prev parent reply other threads:[~2005-09-09 19:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-09 18:48 Fco. J. Ballesteros
2005-09-09 18:51 ` Russ Cox
2005-09-09 19:02 ` Francisco Ballesteros [this message]
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=600308d605090912024fee9947@mail.gmail.com \
--to=nemo@lsub.org \
--cc=9fans@cse.psu.edu \
--cc=rsc@swtch.com \
/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).