I just installed 2008.1 in separate part. from
my 2008.0
My problem is I have all my backups on /mnt/backup on
my 2008.0
I went into mcc and local disks and found my
part. for /mnt/backup which did not have a mount point
defined.
I gave it /mnt/backup which it was before and it is in
/etc/fstab but it is empty.
I booted into 2008.0 and looked in /mnt/backup
and my files are there.PHEW....Scared me....
What do I need to do to see them while
running 2008.1 ?

Another little funny thing...in 2008.0 fstab the part.
start like this dev/hdd dev/sda ,etc.
In 2008.1 they have weird names like uudef....
whats that all about ?
Tia,Dale

On Saturday 19 July 2008 00:05, someone identifying as *Dale* wrote
in /alt.os.linux.mandriva:/

> I just installed 2008.1 in separate part. from
> my 2008.0
> My problem is I have all my backups on /mnt/backup on
> my 2008.0
> I went into mcc and local disks and found my
> part. for /mnt/backup which did not have a mount point
> defined.
> I gave it /mnt/backup which it was before and it is in
> /etc/fstab but it is empty.
> I booted into 2008.0 and looked in /mnt/backup
> and my files are there.PHEW....Scared me....
> What do I need to do to see them while
> running 2008.1 ?

Make sure that the word *auto* is listed in the comma-separated field with
the mount options for this filesystem.

> Another little funny thing...in 2008.0 fstab the part.
> start like this dev/hdd dev/sda ,etc.
> In 2008.1 they have weird names like uudef....
> whats that all about ?

Those are UUIDs, unique identifier codes assigned to each filesystem when it
is created. It's an analog to using labels instead of device names, so
that the proper filesystem will always be mounted on the proper mountpoint,
even after deleting or recreating partitions.

--
*Aragorn*
(registered GNU/Linux user #223157)

On Fri, 18 Jul 2008 18:05:25 -0400, Dale <dwinters6@verizon.net> wrote:

> I went into mcc and local disks and found my
> part. for /mnt/backup which did not have a mount point
> defined.
> I gave it /mnt/backup which it was before and it is in
> /etc/fstab but it is empty.

After creating the directory to be used as a mountpoint, you have
to mount the filesyste. If the entry has been added to /etc/fstab, and
doesn't have the noauto option, then it will be mounted during startup.

> In 2008.1 they have weird names like uudef....

Read "man fstab".

There are three ways you can identify a filesystem in fstab. Device, Label,
or Uniniversal Unique IDentifier. You can assign a label when the filesystem
is formatted, or after, using the appropriate command for the type of filesystem,
such as tune2fs for ext2/ext3, reiserfstune, or xfs_admin. A useful command for
finding info on a filesystem is vol_id.

For example, I have a backup filesystem on /dev/hda18.

$ /sbin/vol_id /dev/hda18
ID_FS_USAGE=filesystem
ID_FS_TYPE=xfs
ID_FS_VERSION=
ID_FS_UUID=245d306c-4800-415f-af8c-821c34a94947
ID_FS_UUID_ENC=245d306c-4800-415f-af8c-821c34a94947
ID_FS_LABEL=backup
ID_FS_LABEL_ENC=backup
ID_FS_LABEL_SAFE=backup

To identify the filesystem in /etc/fstab, I can start the line with
/dev/hda18 or LABEL=backup or UUID=245d306c-4800-415f-af8c-821c34a94947.

Because I added the noauto option, the filesystem is only mounted, when I
manually mount it. When it isn't mounted, /mnt/backup is just a directory,
which by default is on the root filesystem.

Be careful. If you try to copy files to /mnt/backup, when the filesystem
has not been mounted, you'll be copying them to the root filesystem, which
can make rebooting difficult, if it becomes full. If you copy files to
the directory, and then mount the filesystem, the files in that directory
will be hidden. The only way to access them, is to first unmount the filesystem.

Regards, Dave Hodgins

--
Change nomail.afraid.org to ody.ca to reply by email.
(nomail.afraid.org has been set up specifically for
use in usenet. Feel free to use it yourself.)

On Fri, 18 Jul 2008 18:25:33 -0400, Aragorn <aragorn@chatfactory.invalid> wrote:

> Make sure that the word *auto* is listed in the comma-separated field with
> the mount options for this filesystem.

Shouldn't that be 'Make sure the word "noauto" is not listed?

> Those are UUIDs, unique identifier codes assigned to each filesystem when it
> is created. It's an analog to using labels instead of device names, so
> that the proper filesystem will always be mounted on the proper mountpoint,
> even after deleting or recreating partitions.

I'm sure you're aware, but want to make sure it's clear, that the uuid for
a file sytem will be changed, if you format it. For example, if you use
diskdrake in 2008.1 to create and format partitions for installation of 2009.0,
it will add entries to /etc/fstab, using the uuid (if you didn't specify a label).
You then install the 2009.0, allowing it to format the filesystem(s). When
you reboot back to 2008.1, it won't find the uuids that are specified in
/etc/fstab.

In my opinion, it's better to always use device names, or labels. If you use
labels, it's up to you to ensure they are unique.

Be careful with using uuid in /etc/lilo.conf, as well.

Regards, Dave Hodgins

--
Change nomail.afraid.org to ody.ca to reply by email.
(nomail.afraid.org has been set up specifically for
use in usenet. Feel free to use it yourself.)

On Saturday 19 July 2008 00:56, someone identifying as *David W. Hodgins*
wrote in /alt.os.linux.mandriva:/

> On Fri, 18 Jul 2008 18:25:33 -0400, Aragorn <aragorn@chatfactory.invalid>
> wrote:
>
>> Make sure that the word *auto* is listed in the comma-separated field
>> with the mount options for this filesystem.
>
> Shouldn't that be 'Make sure the word "noauto" is not listed?

If the mount options include the word /defaults,/ then you are indeed
correct. However, on my own systems I don't use the /defaults/ keyword and
I rather specify each mount option individually, which makes it easier to
set up and maintain my */etc/fstab* and to make small modifications. ;-)

>> Those are UUIDs, unique identifier codes assigned to each filesystem when
>> it is created. It's an analog to using labels instead of device names,
>> so that the proper filesystem will always be mounted on the proper
>> mountpoint, even after deleting or recreating partitions.
>
> I'm sure you're aware, but want to make sure it's clear, that the uuid for
> a file sytem will be changed, if you format it.

That is correct. The UUID will be created as part of the formatting
process, which I normally do not describe as formatting because of
the /format/ command - which is a text processing utility - and so I
typically refer to this as "creating a filesystem".

And just as you would be wiping out all files on a partition with the
creation of a new filesystem, you would also be overwriting the UUID with a
new one.

> For example, if you use diskdrake in 2008.1 to create and format
> partitions for installation of 2009.0, it will add entries to /etc/fstab,
> using the uuid (if you didn't specify a label).
> You then install the 2009.0, allowing it to format the filesystem(s).
> When you reboot back to 2008.1, it won't find the uuids that are specified
> in /etc/fstab.
>
> In my opinion, it's better to always use device names, or labels.

Device names are the most easy to use, in my humble opinion, but through the
now widespread use of the /udev/ system, device names are no longer
absolute. Labels are just as easy to use, but not every filesystem gets a
label by default.

UUIDs are less easy to use because of the lengthy and cryptic looking
string, but every formatted partition will normally always have a UUID and
this UUID won't change unless you reformat the filesystem, as you described
above.

There's no general consensus anymore about which is best and which isn't,
given that all three methods have their flaws. I myself still used device
names because I'm used to it, but that does not mean that I think that it's
the best way. UUIDs are probably a better idea on a static system.

> If you use labels, it's up to you to ensure they are unique.

And that could be a problem on a very elaborate system... :-/

> Be careful with using uuid in /etc/lilo.conf, as well.

.... Or in */boot/grub/menu.lst* for that matter... ;-)


--
*Aragorn*
(registered GNU/Linux user #223157)