From: Ville Herva <vherva@viasys.com>
To: "Adam J. Richter" <adam@yggdrasil.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: Future devfs plans (sorry for previous incomplete message)
Date: Mon, 26 Jul 2004 12:38:20 +0300 [thread overview]
Message-ID: <20040726093820.GL16073@viasys.com> (raw)
In-Reply-To: <200407261737.i6QHbff04878@freya.yggdrasil.com>
On Mon, Jul 26, 2004 at 10:37:41AM -0700, you [Adam J. Richter] wrote:
>
> 3. hardware that is incidentally plugged in, but which might not
> be used in the current session from boot to shutdown. With the
> increasing popularity of USB and firewire, a user might have a
> "webcam", a still digital camera, a digital video converter, a
> flash reader, a printer, a scanner and an external disk that
> happen attached to the computer's USB network, with the user
> having no intention of using any of them during the current
> session from boot to shutdown. This way, the cost of leaving
> some things plugged in for convenience is reduced.
Not only memory, but stability, too. Not all the most exotic USB drivers
etc. are stellar wrt. their stability. If the driver is not loaded unless
the device is used (as opposed to boot-time), it can make the system behave
more stable.
-- v --
v@iki.fi
next prev parent reply other threads:[~2004-07-26 9:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-26 17:37 Future devfs plans (sorry for previous incomplete message) Adam J. Richter
2004-07-26 3:34 ` Tim Connors
2004-07-26 6:24 ` Trent Lloyd
2004-07-26 6:32 ` Norberto Bensa
2004-07-26 7:11 ` Alexander E. Patrakov
2004-07-26 9:09 ` Måns Rullgård
2004-07-28 0:12 ` Trent Lloyd
2004-07-28 1:43 ` Måns Rullgård
2004-07-26 9:38 ` Ville Herva [this message]
2004-07-27 1:03 ` Matt Mackall
2004-07-28 3:16 ` Ian Kent
-- strict thread matches above, loose matches on Subject: below --
2004-07-28 4:16 Adam J. Richter
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=20040726093820.GL16073@viasys.com \
--to=vherva@viasys.com \
--cc=adam@yggdrasil.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@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