flar

Flar maken:
flarcreate -S -n -L cpio bijv.
flarcreate -S -n bulldb-a020 -L cpio /mnt/bulldb-a020.flar

in het archive kijken:
flar info -l bijv.
flar info -l bulldb-a020.flar

http://www.cuddletech.com/blog/pivot/entry.php?id=245

$ flarcreate -n “Monolyth B16 Snapshot” -a “benr@cuddletech.com”
> -S -R / -x /flash /flash/Monolyth-Snapshot-`date ‘+%m-%d-%y’`.flar
So, looking at the arguments:

-n adds a description to the archive (this is displayed during installation later)
-a adds a string containing conact information
-S tells flarcreate to skip its size checks, normally it will estimate the size of the archive prior to creating it, which can take a really really long time, this argument just lets us speed up the process
-R specifies the root directory, by default its /, but I often supply it for completeness.
-x specifies a directory to exclude from the archive, supply one -x per directory to exclude (ie: -x /opt -x /export). NFS mounted filesystems are excluded by default, but again for completeness I tend to put them in there anyway.
(archivename).flar is the actual name of the output archive file. You can name it whatever you want, but typically its wise to put the hostname, archive creation date, and a .flar extention in the filename just to help identify it. The filename should be a absolute pathname, so since we’ve mounted our NFS archive repository to /flash, we’ll specify that path.