[rhelv6-beta-list] My first experiences with RHEL6 beta

[John McNulty]

Ever wish you could unsend an email, seconds after you send it ... Doh!

[john at dsv03-pv1 ~]$ sudo udevadm info --query=all --name=/dev/md0 | grep
UUID
E: MD_UUID=274ea8e2:0bd22aab:ab863ea6:f42c03cb
E: ID_FS_UUID=cae1fd8f-acfd-4e46-bd96-8c893c07b54b            <---- HERE !!!
E: ID_FS_UUID_ENC=cae1fd8f-acfd-4e46-bd96-8c893c07b54b

John


On 16 June 2010 19:35, John McNulty <johnmcn1 at googlemail.com> wrote:

> On 16 June 2010 15:47, Bryan J. Smith <b.j.smith at ieee.org> wrote:
> >
> > Not entirely true.  In fact, that -- among other assumptions presented
> > here -- are not at all, even for a single hard drive.  That's why all,
> > new versions of major distros have changed to UUID and other references,
> > and _away_ from legacy, fixed devices.
>
> Yes I noticed this and I'm not sure I like it.  For example on a test rhel6
> build I have a UUID for /boot
>
> [john at dsv03-pv1 ~]$ grep UUID /etc/fstab
> UUID=cae1fd8f-acfd-4e46-bd96-8c893c07b54b /boot                   ext3
>  defaults        1 2
>
>
> But where is it getting this from?  It's not the UUID for the filesystem or
> (in my case) the md raid device underneath. e.g.
>
> [john at dsv03-pv1 ~]$ sudo udevadm info --query=all --name=/dev/sda1 | grep
> UUID
> E: ID_FS_UUID=274ea8e2-0bd2-2aab-ab86-3ea6f42c03cb
> E: ID_FS_UUID_ENC=274ea8e2-0bd2-2aab-ab86-3ea6f42c03cb
> E: MD_UUID=274ea8e2:0bd22aab:ab863ea6:f42c03cb
> E: MD_DEV_UUID=117ed612:97cea2cd:2d80c66d:52ade163
>
> John
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/rhelv6-beta-list/attachments/20100616/316503c9/attachment.htm>