From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] hot plugging
Date: Fri, 9 Sep 2005 14:51:06 -0400 [thread overview]
Message-ID: <ee9e417a05090911515d17b15@mail.gmail.com> (raw)
In-Reply-To: <ab45a1f8dee5240c0ed5e80350f85fc7@lsub.org>
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
next prev parent reply other threads:[~2005-09-09 18:51 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 [this message]
2005-09-09 19:02 ` Francisco Ballesteros
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=ee9e417a05090911515d17b15@mail.gmail.com \
--to=rsc@swtch.com \
--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).