From: "Mika Penttilä" <mika.penttila@kolumbus.fi>
To: Greg KH <greg@kroah.com>
Cc: Linus Torvalds <torvalds@osdl.org>,
Andrey Borzenkov <arvidjaar@mail.ru>,
linux-hotplug-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: removable media revalidation - udev vs. devfs or static /dev
Date: Wed, 07 Jan 2004 19:23:39 +0000 [thread overview]
Message-ID: <3FFC5CBB.5050507@kolumbus.fi> (raw)
In-Reply-To: <20040107185656.GB31827@kroah.com>
Greg KH wrote:
>On Wed, Jan 07, 2004 at 10:38:31AM -0800, Linus Torvalds wrote:
>
>
>>On Fri, 2 Jan 2004, Greg KH wrote:
>>
>>
>>>Doesn't the kernel always create the main block device for this device?
>>>If so, udev will catch that.
>>>
>>>
>>But udev should probably also create all the sub-nodes if it doesn't
>>already.
>>
>>
>
>It doesn't, as I thought we could rely on the kernel partition support.
>
>
>
>>And it really has to create _all_ of them, exactly because there's no way
>>to know ahead-of-time which of them will be available.
>>
>>Then, user space can just access "/dev/sda1" or whatever, and the act of
>>accessing it will force the re-scan.
>>
>>
>
>Hm, that would work, but what about a user program that just polls on
>the device, as the rest of this thread discusses? As removable devices
>are not the "norm" it would seem a bit of overkill to create 16
>partitions for every block device, if they need them or not.
>
>thanks,
>
>greg k-h
>
>
>
Accessing the partition would not cause the rescan (accessing the whole
disk causes.) I think devfs does/did this rescan on access.
--Mika
-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
WARNING: multiple messages have this Message-ID (diff)
From: "Mika Penttilä" <mika.penttila@kolumbus.fi>
To: Greg KH <greg@kroah.com>
Cc: Linus Torvalds <torvalds@osdl.org>,
Andrey Borzenkov <arvidjaar@mail.ru>,
linux-hotplug-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: removable media revalidation - udev vs. devfs or static /dev
Date: Wed, 07 Jan 2004 21:23:39 +0200 [thread overview]
Message-ID: <3FFC5CBB.5050507@kolumbus.fi> (raw)
In-Reply-To: <20040107185656.GB31827@kroah.com>
Greg KH wrote:
>On Wed, Jan 07, 2004 at 10:38:31AM -0800, Linus Torvalds wrote:
>
>
>>On Fri, 2 Jan 2004, Greg KH wrote:
>>
>>
>>>Doesn't the kernel always create the main block device for this device?
>>>If so, udev will catch that.
>>>
>>>
>>But udev should probably also create all the sub-nodes if it doesn't
>>already.
>>
>>
>
>It doesn't, as I thought we could rely on the kernel partition support.
>
>
>
>>And it really has to create _all_ of them, exactly because there's no way
>>to know ahead-of-time which of them will be available.
>>
>>Then, user space can just access "/dev/sda1" or whatever, and the act of
>>accessing it will force the re-scan.
>>
>>
>
>Hm, that would work, but what about a user program that just polls on
>the device, as the rest of this thread discusses? As removable devices
>are not the "norm" it would seem a bit of overkill to create 16
>partitions for every block device, if they need them or not.
>
>thanks,
>
>greg k-h
>
>
>
Accessing the partition would not cause the rescan (accessing the whole
disk causes.) I think devfs does/did this rescan on access.
--Mika
next prev parent reply other threads:[~2004-01-07 19:23 UTC|newest]
Thread overview: 131+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-01 20:33 removable media revalidation - udev vs. devfs or static /dev Andrey Borzenkov
2004-01-01 20:33 ` Andrey Borzenkov
2004-01-03 5:58 ` Greg KH
2004-01-03 5:58 ` Greg KH
2004-01-03 8:51 ` Andrey Borzenkov
2004-01-03 8:51 ` Andrey Borzenkov
2004-01-03 12:37 ` Andries Brouwer
2004-01-03 12:37 ` Andries Brouwer
2004-01-03 12:42 ` Olaf Hering
2004-01-03 12:42 ` Olaf Hering
2004-01-03 16:05 ` Andrey Borzenkov
2004-01-03 16:05 ` Andrey Borzenkov
2004-01-03 17:54 ` Jens Axboe
2004-01-03 17:54 ` Jens Axboe
2004-01-07 9:43 ` Olaf Hering
2004-01-07 9:43 ` Olaf Hering
2004-01-07 9:50 ` Jens Axboe
2004-01-07 9:50 ` Jens Axboe
2004-01-07 9:56 ` Olaf Hering
2004-01-07 9:56 ` Olaf Hering
2004-01-07 9:59 ` Jens Axboe
2004-01-07 9:59 ` Jens Axboe
2004-01-07 10:25 ` Olaf Hering
2004-01-07 10:25 ` Olaf Hering
2004-01-07 10:31 ` Jens Axboe
2004-01-07 10:31 ` Jens Axboe
2004-01-07 10:47 ` Andrey Borzenkov
2004-01-07 10:47 ` Andrey Borzenkov
2004-01-07 10:54 ` Jens Axboe
2004-01-07 10:54 ` Jens Axboe
2004-01-07 17:56 ` Greg KH
2004-01-07 17:56 ` Greg KH
2004-01-30 12:59 ` Olaf Hering
2004-01-30 12:59 ` Olaf Hering
2004-01-07 11:00 ` Andrey Borzenkov
2004-01-07 11:00 ` Andrey Borzenkov
2004-01-07 11:05 ` Jens Axboe
2004-01-07 11:05 ` Jens Axboe
2004-01-07 11:14 ` Andrey Borzenkov
2004-01-07 11:14 ` Andrey Borzenkov
2004-01-07 11:16 ` Jens Axboe
2004-01-07 11:16 ` Jens Axboe
2004-01-03 20:51 ` Greg KH
2004-01-03 20:51 ` Greg KH
2004-01-07 18:38 ` Linus Torvalds
2004-01-07 18:38 ` Linus Torvalds
2004-01-07 18:57 ` Greg KH
2004-01-07 18:57 ` Greg KH
2004-01-07 19:23 ` Mika Penttilä [this message]
2004-01-07 19:23 ` Mika Penttilä
2004-01-07 19:24 ` Greg KH
2004-01-07 19:24 ` Greg KH
2004-01-07 19:31 ` Mika Penttilä
2004-01-07 19:31 ` Mika Penttilä
2004-01-08 1:38 ` Linus Torvalds
2004-01-08 1:38 ` Linus Torvalds
2004-01-07 19:31 ` Linus Torvalds
2004-01-07 19:31 ` Linus Torvalds
2004-01-07 19:50 ` Greg KH
2004-01-07 19:50 ` Greg KH
2004-01-07 20:25 ` Richard Troth
2004-01-07 20:25 ` Richard Troth
2004-01-07 20:38 ` Valdis.Kletnieks
2004-01-07 23:34 ` Greg KH
2004-01-07 23:34 ` Greg KH
2004-01-08 0:32 ` Martin J. Bligh
2004-01-08 0:32 ` Martin J. Bligh
2004-01-08 0:41 ` Greg KH
2004-01-08 0:41 ` Greg KH
2004-01-08 1:07 ` Martin J. Bligh
2004-01-08 1:07 ` Martin J. Bligh
2004-01-08 1:15 ` Greg KH
2004-01-08 1:15 ` Greg KH
2004-01-08 1:50 ` Martin J. Bligh
2004-01-08 1:50 ` Martin J. Bligh
2004-01-08 18:34 ` Martin Schlemmer
2004-01-08 1:48 ` Linus Torvalds
2004-01-08 1:48 ` Linus Torvalds
2004-01-08 0:42 ` viro
2004-01-08 0:42 ` viro
2004-01-08 1:16 ` Greg KH
2004-01-08 1:16 ` Greg KH
2004-01-09 3:36 ` Joel Becker
2004-01-09 3:36 ` Joel Becker
2004-01-09 9:49 ` Gerd Knorr
2004-01-12 17:16 ` Joel Becker
2004-01-12 23:08 ` J.A. Magallon
2004-01-07 20:52 ` Olaf Hering
2004-01-07 20:52 ` Olaf Hering
2004-01-08 2:03 ` Linus Torvalds
2004-01-08 2:03 ` Linus Torvalds
2004-01-08 4:16 ` Gene Heskett
2004-01-08 4:16 ` Gene Heskett
2004-01-08 4:23 ` Linus Torvalds
2004-01-08 4:23 ` Linus Torvalds
2004-01-08 7:45 ` Olaf Hering
2004-01-08 7:45 ` Olaf Hering
2004-01-08 2:13 ` Andries Brouwer
2004-01-08 2:13 ` Andries Brouwer
2004-01-08 2:19 ` Linus Torvalds
2004-01-08 2:19 ` Linus Torvalds
2004-01-08 2:49 ` Andries Brouwer
2004-01-08 2:49 ` Andries Brouwer
2004-01-08 2:56 ` Linus Torvalds
2004-01-08 2:56 ` Linus Torvalds
2004-01-08 3:35 ` Andries Brouwer
2004-01-08 3:35 ` Andries Brouwer
2004-01-08 3:43 ` Linus Torvalds
2004-01-08 3:43 ` Linus Torvalds
2004-01-08 8:00 ` Xavier Bestel
2004-01-08 8:00 ` Xavier Bestel
2004-01-09 0:28 ` Robert Love
2004-01-09 0:28 ` Robert Love
2004-01-09 0:52 ` Linus Torvalds
2004-01-09 0:52 ` Linus Torvalds
2004-01-09 1:16 ` Matt Mackall
2004-01-09 1:16 ` Matt Mackall
2004-01-08 10:32 ` Éric Brunet
2004-01-08 14:06 ` "Andrey Borzenkov"
2004-01-08 14:06 ` "Andrey Borzenkov"
2004-01-12 9:09 ` Ling, Xiaofeng
2004-01-12 9:09 ` Ling, Xiaofeng
2004-03-29 15:39 ` Greg KH
2004-03-29 15:39 ` Andrey Borzenkov
2004-03-29 15:40 ` Andries Brouwer
2004-03-29 15:40 ` Olaf Hering
2004-03-29 15:40 ` Andrey Borzenkov
2004-03-29 15:40 ` Jens Axboe
2004-03-29 15:40 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2004-01-08 5:19 Iqbal
2004-01-12 13:02 Nicolas Mailhot
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=3FFC5CBB.5050507@kolumbus.fi \
--to=mika.penttila@kolumbus.fi \
--cc=arvidjaar@mail.ru \
--cc=greg@kroah.com \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.