From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: Switching from (deprecated) IDE driver -> SATA (PATA support)
Date: Sun, 25 Jan 2009 07:28:28 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.1.10.0901250726530.10805@p34.internal.lan> (raw)
In-Reply-To: <alpine.DEB.1.10.0901250715030.10379@p34.internal.lan>
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@oss.sgi.com
> 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?
$ ls -l
total 0
lrwxrwxrwx 1 root root 9 2009-01-25 01:54 203fcd30-4e56-40e9-a8e5-93ddc8eb536a -> ../../md0
lrwxrwxrwx 1 root root 10 2009-01-25 01:54 2ef862e1-cf78-4065-a205-d1784716d633 -> ../../sdd1
lrwxrwxrwx 1 root root 10 2009-01-25 01:54 77ae4251-631f-4656-a365-c5723f5c5da8 -> ../../sdd2
p254:~# find /proc/|grep -i uuid
/proc/sys/kernel/random/uuid
p254:~# find /sys/|grep -i uuid
p254:~#
next prev parent reply other threads:[~2009-01-25 12:28 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-25 10:56 Justin Piszcz
2009-01-25 11:07 ` Alan Cox
2009-01-25 12:09 ` Justin Piszcz
2009-01-25 12:15 ` Justin Piszcz
2009-01-25 12:28 ` Justin Piszcz [this message]
2009-01-25 12:41 ` Justin Piszcz
2009-01-25 12:55 ` Switching from (deprecated) IDE driver -> SATA (PATA support) (found solution) Justin Piszcz
2009-01-25 13:08 ` Switching from (deprecated) IDE driver -> SATA (PATA support) (found solution (scratch that)) Justin Piszcz
2009-01-25 13:15 ` Michael Tokarev
2009-01-25 15:45 ` Switching from (deprecated) IDE driver -> SATA (PATA support) Eric Sandeen
[not found] ` <alpine.DEB.1.10.0901250726530.10805__44823.8515914001$1232890466$gmane$org@p34.internal.lan>
2009-01-25 21:13 ` Bill Davidsen
2009-01-25 21:14 ` Justin Piszcz
2009-01-29 23:44 ` Bill Davidsen
2009-01-26 22:02 ` Lennart Sorensen
2009-01-26 23:36 ` Sergei Shtylyov
2009-01-25 18:04 ` Mark Lord
2009-01-25 19:27 ` Bartlomiej Zolnierkiewicz
2009-01-25 21:13 ` Justin Piszcz
2009-01-25 21:39 ` Bartlomiej Zolnierkiewicz
2009-01-29 23:50 ` Bill Davidsen
2009-01-30 3:38 ` david
2009-01-30 10:21 ` Alan Cox
2009-01-30 10:11 ` Alan Cox
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=alpine.DEB.1.10.0901250726530.10805@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xfs@oss.sgi.com \
/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
all inboxes | Powered by JetHome®