> Rusty.Carruth wrote:
>> First, if you are not using 'tar' or 'cpio' or other program which
>> correctly handles 'character (and block) special files' you will sooner
>> or later find yourself copying much more than you should (think pipes
>> and other character or block special files
rsync. While rsync will not handle hard links in the optimal way by default,
how many people actually have hard links on their filesystems these days?
Also, char and block devices would only be found in /dev in just about any
case I can think of, and backing up /dev seems a bit like a waste of time
since udev manages it.
From: Michael Havens
> Yep,.... the advice to chown the file got lost in the shuffle
Yes, this is why it's important to read the whole message and understand it
when you're talking about semi-complicated technical things.
> however after I did that I click it and 'run in terminal'. then a shell
> opens and it says "building file list" and then something flashes
> across the screen and the terminal closes itself.
This probably means there's some sort of error happening. So, open a konsole
or gnome-terminal and run the backup script inside that terminal, which will
allow you to see what the error is. This is pretty basic, and I thought you
had done it already.
>> If you need to restore from the backup disk, just mount it. The
>> command for doing that is in the script ("mount /mnt/backup").
> as for restoring the backup isn't there a way to retrieve one file?
If you mount a disk on /mnt/backup , then rsync your ~ to /mnt/backup/bmike/ ,
that means that /mnt/backup/bmike/ will contain an exact copy of your ~. This
means that finding 1 file under /mnt/backup/bmike/ and copying it to
/home/bmike/ should be a very simple and easy thing.