From: Xavier Bestel <xavier.bestel@free.fr>
To: Ketil Froyn <ketil-kernel@froyn.net>
Cc: "jbradford@dial.pipex.com" <jbradford@dial.pipex.com>,
Alexander Viro <viro@math.psu.edu>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
"mochel@osdl.org" <mochel@osdl.org>,
"torvalds@transmeta.com" <torvalds@transmeta.com>,
"andre@linux-ide.org" <andre@linux-ide.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [patch] IDE driver model update
Date: 08 Oct 2002 23:34:46 +0200 [thread overview]
Message-ID: <1034112887.4607.14.camel@bip> (raw)
In-Reply-To: <Pine.LNX.4.40L0.0210081627480.1519-100000@ketil.np>
Le mar 08/10/2002 à 16:31, Ketil Froyn a écrit :
> On Tue, 8 Oct 2002, jbradford@dial.pipex.com wrote:
>
> > This raises the interesting possibility of being able to refer to
> > things like removable media directly, instead of the device the media
> > is inserted in.
> >
> > The Amiga was doing this years ago. You could access floppy drives
> > as, E.G. df0:, df1:, etc, but if you formatted a volume and called it
> > foobar, you could access foobar: no matter which floppy drive you put
> > it in to.
>
> Isn't this possible in /etc/fstab already? Standard redhat-installs seem
> to put in the labels of the volume instead of referring to the device.
No comparison possible. The amiga dos would stall all read/write
requests when a device came offline (e.g. a floppy disk ejected) and
would cancel them all if the user or something else decided the medium
wouldn't be available anymore, and resumed everything when the medium
was online again (even if in a different device/drive).
That was a pretty sophisticated volume management if you ask me, one I
can only dream of happening one day in linux.
next prev parent reply other threads:[~2002-10-08 21:30 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-07 19:30 [patch] IDE driver model update Patrick Mochel
2002-10-07 19:31 ` Patrick Mochel
2002-10-07 19:31 ` Patrick Mochel
2002-10-11 23:06 ` Pavel Machek
2002-10-07 19:31 ` Patrick Mochel
2002-10-07 22:42 ` Alexander Viro
2002-10-07 22:51 ` Patrick Mochel
2002-10-07 22:58 ` Alexander Viro
2002-10-07 23:06 ` Patrick Mochel
2002-10-08 2:17 ` Alexander Viro
2002-10-08 12:21 ` Alan Cox
2002-10-08 12:24 ` Alexander Viro
2002-10-08 13:05 ` Alan Cox
2002-10-08 19:18 ` Andries Brouwer
2002-10-08 13:25 ` jbradford
2002-10-08 14:31 ` Ketil Froyn
2002-10-08 21:34 ` Xavier Bestel [this message]
2002-10-08 21:57 ` Pavel Machek
2002-10-08 15:05 ` Benjamin Herrenschmidt
2002-10-08 18:43 ` Patrick Mochel
2002-10-08 20:47 ` [RFC] embedded struct device " Alexander Viro
2002-10-08 21:29 ` Linus Torvalds
2002-10-08 21:42 ` Alexander Viro
2002-10-08 21:53 ` Kai Germaschewski
2002-10-08 21:57 ` Patrick Mochel
2002-10-08 22:51 ` Alan Cox
2002-10-08 21:54 ` Patrick Mochel
2002-10-08 22:12 ` Linus Torvalds
2002-10-08 22:48 ` Kai Germaschewski
2002-10-08 23:28 ` Linus Torvalds
2002-10-08 22:29 ` Greg KH
2002-10-08 21:30 ` Greg KH
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=1034112887.4607.14.camel@bip \
--to=xavier.bestel@free.fr \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andre@linux-ide.org \
--cc=jbradford@dial.pipex.com \
--cc=ketil-kernel@froyn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.org \
--cc=torvalds@transmeta.com \
--cc=viro@math.psu.edu \
/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