| 1 |
On Thursday 10 February 2011 06:31:12 Dale wrote: |
| 2 |
> Neil Bothwick wrote: |
| 3 |
> > On Thu, 10 Feb 2011 12:00:24 +0200, Petri Rosenström wrote: |
| 4 |
> >> If you use vi(m) you don't have to type too much neither. Just use |
| 5 |
> >> |
| 6 |
> >> :r!blkid /dev/sda in vi(m) and you have the UUID, with some |
| 7 |
> >> :additional |
| 8 |
> >> |
| 9 |
> >> information, but the rest is just vi(m) magic. |
| 10 |
> > |
| 11 |
> > None of which makes fstab any more readable. UUIDs are the worst option |
| 12 |
> > in this respect, although they do allow disks to be moved around. |
| 13 |
> > Filesystem labels are the best option for readability and not only do |
| 14 |
> > they allow disks to be moved but also individual filesystems. |
| 15 |
> |
| 16 |
> When I switched mine, I looked into the UUID option but never could |
| 17 |
> figure out how to tell which is what. I have /boot, /, /home, /portage |
| 18 |
> and /var but how do you get it to tell you the number for say /home? Of |
| 19 |
> all the stuff I read, I never did find that. |
| 20 |
> |
| 21 |
> I agree tho, using the plain labels are easier to understand. Even I |
| 22 |
> got that right. ;-) |
| 23 |
> |
| 24 |
> Dale |
| 25 |
> |
| 26 |
> :-) :-) |
| 27 |
|
| 28 |
Dale, |
| 29 |
|
| 30 |
Thanks to the email from Petri Rosenström earlier, I finally figured it out. |
| 31 |
If you know the current /dev/.... for it, use: |
| 32 |
blkid /dev/.... |
| 33 |
That will give you the UUID :) |
| 34 |
|
| 35 |
-- |
| 36 |
Joost |
Archives