From: Pascal Maillard <pascalmaillard@web.de>
To: Mark Hahn <hahn@physics.mcmaster.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: independence from ide master/slave
Date: Sat, 20 Mar 2004 18:40:31 +0100 [thread overview]
Message-ID: <200403201819.43220.pascalmaillard@web.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0403201109110.20406-100000@coffee.psychology.mcmaster.ca>
Hi,
thanks for your answers. I didn't know of UUIDs and user defined labels and
you're right, it is much more flexible. But, according to man fstab, it is
currently only supported by ext2 and xfs. What about the others?
One last note about the term "current hd" I used: I did not define it as the
hd where the root fs is located, but I said that it should be defined by the
kernel at startup. That is, it could be any disk. The default could have
been, for example, the root fs.
> perhaps you are thinking of the rather
> specialized case where a system has only one disk, and the root partition
> is on it.
Do you really think, that it is such a specialized case? I know that Linux is
used much more on servers than on desktop computers, but I suppose we all
hope that Linux' market share on desktops can grow further.
cö,
Pascal Maillard
Mark Hahn wrote:
> > filesystems were thought to be on /dev/hda. So I asked myself if there
> > should not be device files that point to the _current_ hard disk (which
> > should be defined at startup by the kernel) and its partitions.
>
> "current hd" has no meaning. perhaps you are thinking of the rather
> specialized case where a system has only one disk, and the root partition
> is on it. if so, you really mean "/dev/root" (which is a notional device
> that the kernel uses in /proc/mounts for instance - I don't know whether
> it has any assigned major/minor number that would let it appear in /dev.)
>
> note that RedHat has used a relatively simple mechanism called
> mount-by-label which permits the kind of cable/controller independence that
> you're asking for. it's vastly more logical than your /dev/root approach,
> and extends beyond a single disk.
>
> > This way, it wouldn't
> > matter which IDE channel a disk is connected to. What do you mean about
> > this?
>
> mount by label.
next parent reply other threads:[~2004-03-22 19:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0403201109110.20406-100000@coffee.psychology.mcmaster.ca>
2004-03-20 17:40 ` Pascal Maillard [this message]
2004-03-20 12:53 independence from ide master/slave Pascal Maillard
2004-03-20 13:31 ` Andre Tomt
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=200403201819.43220.pascalmaillard@web.de \
--to=pascalmaillard@web.de \
--cc=hahn@physics.mcmaster.ca \
--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