From: Martin Wilck <Martin.Wilck@fujitsu-siemens.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] GUID filesystem+device identification ?
Date: Fri, 18 May 2001 16:50:44 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590693005620@msgid-missing> (raw)
Hi all,
Has anybody yet thought about the possibility to use
a mechanism like devfs for identifying devices and file systems
by their GUID? This would be a major improvement over Linux's current
approach of identifying devices, particularly disk drives.
In principle, it would be possible to change controllers and
disks arbitrarily and still maintain a valid file system in which
all devices and sub-file systems would be identified by ther GUIDs
(think of the device in fstab specified by GUID instead of /dev/sda3
or whatever).
I think something like this could well coexist with devfs in its current
implementation, e.g. by a collection of softlinks , something like
/dev/guid/disk/[DISK_GUID]->/dev/scsi/host1/bus0/target2/lun0
/dev/guid/partitions/[PARTITION_GUID]->(you guess).
where these links would be auto-generated when a driver encounters
a disk and and the partition table is analyzed.
Links for other devices could of course also exist in /dev/guid,
although I think disks and parttions give most benefit.
The approach above would allow entries like
/dev/[PARTITION_GUID] /usr ext2 defaults 2 1
in fstab, so no need to change fstab if controllers or disks
are added/removed in a system.
Unlike the "filesystem label" approach, this would work with any
filesystem type, and even for entire disks and other devices.
Is anybody working on something like this, or does it even exist
already?
If no, what is your opinion on its usefulness?
Regards,
Martin
--
Martin Wilck <Martin.Wilck@fujitsu-siemens.com>
FSC EP PS DS1, Paderborn Tel. +49 5251 8 15113
next reply other threads:[~2001-05-18 16:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-18 16:50 Martin Wilck [this message]
2001-05-18 16:59 ` [Linux-ia64] GUID filesystem+device identification ? Christoph Hellwig
2001-05-18 17:17 ` Martin Wilck
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=marc-linux-ia64-105590693005620@msgid-missing \
--to=martin.wilck@fujitsu-siemens.com \
--cc=linux-ia64@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