Justin Piszcz wrote:
On Sun, 25 Jan 2009, Bill Davidsen wrote:
Justin Piszcz wrote:
On Sun, 25 Jan 2009, Justin Piszcz wrote:
On Sun, 25 Jan 2009, Justin Piszcz wrote:
On Sun, 25 Jan 2009, Alan Cox wrote:
Easiest is to use labels. Old ide will keep hda,b,c,d constant
providing you have interfaces using the legacy IDE port mappings
(0x1f0
and 0x170). Libata doesn't do that as pretty much every
distribution had
already switched to volume labels, and the user space can do the
job far
better than the kernel - especially as the newer devices with modern
interfaces don't have the old BIOS/DOS legacy ideas any more.
Mount by label also means you can flip back and forth between the
different drivers and kernel revisions.
Alan
It comes with one :)
# xfs_admin -u /dev/sdd2
UUID = 77ae4251-631f-4656-a365-c5723f5c5da8
Will try to use this to boot; however, I'd prefer the labels over
the UUID, wish there was an easy way to set it.
Justin.
_______________________________________________
xfs mailing list
xfs@xxxxxxxxxxx
http://oss.sgi.com/mailman/listinfo/xfs
One final question, without udev, how does one determine the UUID of
a non-XFS
partition, e.g., swap?
One uses blkid. Which suggests that you can solve your name problem by
not using names and switching to UUID.
This will fix the /etc/fstab issue but not LILO/boot one, per the
earlier poster, need an initrd/etc for that.
Good point, I have not used LILO since about Slackware 8.1, or any system w/o
initrd in ages. I suppose there is a benefit to running without initrd, but I
confess that I can't remember what it is. So I don't immediately consider the
issues and limitations if you run without initrd.
Well I answered how to GET the UUID, he didn't ask me how to USE it. And I
certainly didn't think of it, even though the info was there. :-(
--
Bill Davidsen <davidsen@xxxxxxx>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
--
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
