From: Joost Roeleveld <joost@antarean.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Disk Labels in Handbook
Date: Thu, 10 Feb 2011 13:53:18 +0100 [thread overview]
Message-ID: <20110210125615.9722B27CA@data.antarean.org> (raw)
In-Reply-To: <4D53DE01.8090708@gmail.com>
On Thursday 10 February 2011 06:45:53 Dale wrote:
> Joost Roeleveld wrote:
> > On Thursday 10 February 2011 06:31:12 Dale wrote:
> >> Neil Bothwick wrote:
> >>> On Thu, 10 Feb 2011 12:00:24 +0200, Petri Rosenström wrote:
> >>>> If you use vi(m) you don't have to type too much neither. Just use
> >>>>
> >>>> :r!blkid /dev/sda in vi(m) and you have the UUID, with some
> >>>> :additional
> >>>>
> >>>> information, but the rest is just vi(m) magic.
> >>>
> >>> None of which makes fstab any more readable. UUIDs are the worst
> >>> option
> >>> in this respect, although they do allow disks to be moved around.
> >>> Filesystem labels are the best option for readability and not only
> >>> do
> >>> they allow disks to be moved but also individual filesystems.
> >>
> >> When I switched mine, I looked into the UUID option but never could
> >> figure out how to tell which is what. I have /boot, /, /home,
> >> /portage
> >> and /var but how do you get it to tell you the number for say /home?
> >> Of
> >> all the stuff I read, I never did find that.
> >>
> >> I agree tho, using the plain labels are easier to understand. Even I
> >> got that right. ;-)
> >>
> >> Dale
> >>
> >> :-) :-)
> >
> > Dale,
> >
> > Thanks to the email from Petri Rosenström earlier, I finally figured it
> > out. If you know the current /dev/.... for it, use:
> > blkid /dev/....
> > That will give you the UUID :)
> >
> > --
> > Joost
>
> Kewl !! That works. Wonder if I should try this way out. See if I can
> mess this up. o_O
>
> Dale
>
> :-) :-)
In your case, yes and yes :)
Just make sure you got a backup so you can go back to the way it works now ;)
--
Joost
next prev parent reply other threads:[~2011-02-10 12:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 13:51 [gentoo-user] Disk Labels in Handbook James
2011-02-09 14:16 ` Dale
2011-02-09 14:27 ` Mark Knecht
2011-02-09 20:58 ` Alan McKinnon
2011-02-10 10:00 ` Petri Rosenström
[not found] ` <20110210120055.6e7288c2@digimed.co.uk>
2011-02-10 12:31 ` Dale
2011-02-10 12:39 ` Joost Roeleveld
2011-02-10 12:45 ` Dale
2011-02-10 12:53 ` Joost Roeleveld [this message]
2011-02-10 12:56 ` Neil Bothwick
2011-02-10 13:14 ` Dale
2011-02-10 15:39 ` Stroller
2011-02-09 16:16 ` Jarry
2011-02-09 18:41 ` [gentoo-user] Re: Bug#354229 " James
2011-02-09 20:08 ` [gentoo-user] " Neil Bothwick
2011-02-10 15:17 ` [gentoo-user] " James
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=20110210125615.9722B27CA@data.antarean.org \
--to=joost@antarean.org \
--cc=gentoo-user@lists.gentoo.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