From: Olaf Hering <olh@suse.de>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: Andrey Borzenkov <arvidjaar@mail.ru>, Greg KH <greg@kroah.com>,
linux-hotplug-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: removable media revalidation - udev vs. devfs or static /dev
Date: Sat, 3 Jan 2004 13:42:16 +0100 [thread overview]
Message-ID: <20040103124216.GA31006@suse.de> (raw)
In-Reply-To: <20040103133749.A3393@pclin040.win.tue.nl>
On Sat, Jan 03, Andries Brouwer wrote:
> On Sat, Jan 03, 2004 at 11:51:33AM +0300, Andrey Borzenkov wrote:
>
> > yes. So what - how does it help? User needs /dev/sda4. User has /dev/sda only.
> > Any attempt to refer to /dev/sda4 simply returns "No such file or directory"
>
> Things are far from perfect here, but "blockdev --rereadpt /dev/sda" helps.
Is there really no way to get a media change notification from ZIP or
JAZ drives?
--
USB is for mice, FireWire is for men!
sUse lINUX ag, nÜRNBERG
next prev parent reply other threads:[~2004-01-03 12:43 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 [this message]
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
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=20040103124216.GA31006@suse.de \
--to=olh@suse.de \
--cc=aebr@win.tue.nl \
--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).