From: Linus Torvalds <torvalds@osdl.org>
To: Greg KH <greg@kroah.com>
Cc: 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, 7 Jan 2004 17:48:20 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.58.0401071746520.12602@home.osdl.org> (raw)
In-Reply-To: <20040107195032.GB823@kroah.com>
On Wed, 7 Jan 2004, Greg KH wrote:
>
> It sounds like just having the device node around will not cause the
> rescan if you access it.
Who has problems with it, and why?
When you open a partition, that will automatically open the "whole
device", and that should cause a re-scan if the device supports the "disk
change" flagging.
This definitely has worked for me. It used to be broken in really early
2.5.x, but it got fixed with the block device interface fixes.
Linus
next prev parent reply other threads:[~2004-01-08 1:48 UTC|newest]
Thread overview: 66+ 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-03 5:58 ` Greg KH
2004-01-03 8:51 ` Andrey Borzenkov
2004-01-03 12:37 ` Andries Brouwer
2004-01-03 12:42 ` Olaf Hering
2004-01-03 16:05 ` Andrey Borzenkov
2004-01-03 17:54 ` Jens Axboe
2004-01-07 9:43 ` Olaf Hering
2004-01-07 9:50 ` Jens Axboe
2004-01-07 9:56 ` Olaf Hering
2004-01-07 9:59 ` Jens Axboe
2004-01-07 10:25 ` Olaf Hering
2004-01-07 10:31 ` Jens Axboe
2004-01-07 10:47 ` Andrey Borzenkov
2004-01-07 10:54 ` Jens Axboe
2004-01-07 17:56 ` Greg KH
2004-01-30 12:59 ` Olaf Hering
2004-01-07 11:00 ` Andrey Borzenkov
2004-01-07 11:05 ` Jens Axboe
2004-01-07 11:14 ` Andrey Borzenkov
2004-01-07 11:16 ` Jens Axboe
2004-01-03 20:51 ` Greg KH
2004-01-07 18:38 ` Linus Torvalds
2004-01-07 18:57 ` Greg KH
2004-01-07 19:23 ` Mika Penttilä
2004-01-07 19:24 ` Greg KH
2004-01-07 19:31 ` Mika Penttilä
2004-01-08 1:38 ` Linus Torvalds
2004-01-07 19:31 ` Linus Torvalds
2004-01-07 19:50 ` Greg KH
2004-01-07 20:25 ` Richard Troth
2004-01-07 20:38 ` Valdis.Kletnieks
2004-01-07 23:34 ` Greg KH
2004-01-08 0:32 ` Martin J. Bligh
2004-01-08 0:41 ` Greg KH
2004-01-08 1:07 ` Martin J. Bligh
2004-01-08 1:15 ` Greg KH
2004-01-08 1:50 ` Martin J. Bligh
2004-01-08 18:34 ` Martin Schlemmer
2004-01-08 1:48 ` Linus Torvalds [this message]
2004-01-08 14:06 ` "Andrey Borzenkov"
2004-01-08 0:42 ` viro
2004-01-08 1:16 ` Greg KH
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-08 2:03 ` Linus Torvalds
2004-01-08 4:16 ` Gene Heskett
2004-01-08 4:23 ` Linus Torvalds
2004-01-08 7:45 ` Olaf Hering
2004-01-08 2:13 ` Andries Brouwer
2004-01-08 2:19 ` Linus Torvalds
2004-01-08 2:49 ` Andries Brouwer
2004-01-08 2:56 ` Linus Torvalds
2004-01-08 3:35 ` Andries Brouwer
2004-01-08 3:43 ` Linus Torvalds
2004-01-08 8:00 ` Xavier Bestel
2004-01-09 0:28 ` Robert Love
2004-01-09 0:52 ` Linus Torvalds
2004-01-09 1:16 ` Matt Mackall
2004-01-08 10:32 ` Éric Brunet
2004-01-08 5:19 Iqbal
2004-01-12 9:09 Ling, Xiaofeng
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=Pine.LNX.4.58.0401071746520.12602@home.osdl.org \
--to=torvalds@osdl.org \
--cc=arvidjaar@mail.ru \
--cc=greg@kroah.com \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--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;
as well as URLs for NNTP newsgroup(s).