>Hi Hilmar,
>
>Maybe this will help:
>
>http://www.linuxchix.org/pipermail/techtalk/2000-December/006029.html
>
>The following options are supported by dump:
>
>################################################
>dump [-0123456789ackMnqSu] [-A file] [-B records] [-b blocksize] [-d density] [-e inode numbers] [-E file] [-f file] [-F script] [-h level] [-I nr errors] [-j compression level] [-L label] [-Q file] [-s feet] [-T date] [-z compression level] files-to-dump dump [-W | -w]
>#################################################
>
>######################################################
>-0-9 Dump levels. A level 0, full backup, guarantees
> the entire file system is copied (but see also the -h
>option below). A level number above 0, incremental backup, tells dump to copy all files new or modified since the last dump of a lower level. The default level is 9.
>#####################################################

Thanks. Is "dump" a standard command in Linux? I suppose it will generate a list of files, right?

>For more information you might check the man pages on
>tar and cpio

Sure, I will.

>Aside from the dump, tar, and cpio commands, there are many UINX and Linux backup front end backup programs that can perform backup even in mixed environment like a network with Mac, Windows, Unix and Linux. Some backup programs are very expensive in large mixed networks. Linux supports over 30 file systems, many of which may not use an archive bit.
>
>From what I've read, Linux and Unix does not use a archive bit, but can achieve the same result using professional software to perform backups where the backup software write a catelogue of each backup.

Well, I am sure there are other ways to do it. It is just that I got accustomed to the idea of using an archive bit <g>.