From: David Bryson <david@tsumego.com>
To: Erik Steffl <steffl@bigfoot.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Future devfs plans
Date: Tue, 27 Jul 2004 09:55:17 -0700 [thread overview]
Message-ID: <20040727165517.GA7727@heliosphan.in.cryptobackpack.org> (raw)
In-Reply-To: <4104AB98.8070506@bigfoot.com>
[-- Attachment #1: Type: text/plain, Size: 1669 bytes --]
On Sun, Jul 25, 2004 at 11:58:32PM -0700 or thereabouts, Erik Steffl wrote:
> >devfs allowes you to not have the driver loaded till you try to use it.
> >so udev _cannot_ do what devfs does.
> >
> >still I agree that the way kernel/hotplug/udev work is much better and
> >supporting the old style devfs works is not necessary. but please be
> >honest about the differences.
>
> which means that now iPod automatically connects to firewire (and
> looses info on random tracks, sometime some other settings), instead of
> only connecting when I try to actually access it (the device).
>
I have been using ipods with linux for about 3 years.
And I see that it says "do not disconnect" even after I have unmounted
the file system. I just disconnect it at this point and have not
had any problems.
> it looks like there is no user level (end user, not admin) control on
> when the device drivers are loaded anymore - or is there?
>
> Is there any way to load drivers on demand (obviously it's not job of
> udev but whose job it is?). What about unloading them - I unmount the
> disk and i think the iPod is disconnecred but it still says connected -
> is there any way to disconnect it (I guess similar problems arise with
> other hotplug devices)
>
This has been discussed in length on lkml many times during the
writing of udev. IIRC the argument was something like:
"we shouldn't be unloading modules because the memory taken up by a
module in memory(a few k) isn't worth writing the code to save"
I also recall there was something about end user behavior, but I don't
remember the details. Read the archives.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-07-27 16:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-26 14:45 Adam J. Richter
2004-07-26 0:00 ` Jim Gifford
2004-07-26 0:17 ` Ed Sweetman
2004-07-26 0:29 ` Lee Revell
2004-07-26 0:59 ` Lee Revell
2004-07-26 18:09 ` Adrian Bunk
2004-07-26 21:44 ` Ed Sweetman
2004-07-26 23:01 ` CaT
2004-07-27 21:24 ` Lee Revell
2004-07-27 22:35 ` Adrian Bunk
2004-07-27 22:39 ` Lee Revell
2004-07-26 0:21 ` Rafael do N. Pereira
2004-07-26 0:31 ` Ramón Rey Vicente
2004-07-26 0:35 ` Ramón Rey Vicente
2004-07-26 5:35 ` Andreas Jellinghaus
2004-07-26 6:58 ` Erik Steffl
2004-07-27 16:55 ` David Bryson [this message]
2004-07-27 18:44 ` Erik Steffl
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=20040727165517.GA7727@heliosphan.in.cryptobackpack.org \
--to=david@tsumego.com \
--cc=linux-kernel@vger.kernel.org \
--cc=steffl@bigfoot.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
all inboxes | Powered by JetHome®