Arthur Pemberton wrote:
On 4/19/06, Kenneth Porter <shiva@xxxxxxxxxxxxxxx> wrote:
On Tuesday, April 18, 2006 11:31 AM -0700 Gordon Messmer
<yinyang@xxxxxxxxx> wrote:
For machines with a larger set of users, dump is better. It will
preserve atime *and* ctime, and will back up ACLs and attributes.
That's what I use for my office machine. The dump is to a Samba-mounted
Windows server.
I took a quick look at the docs on 'dump' it seems to say that it is
for ext3 file systems no? If so, how do you dump to smb server on
No. The dump command dumps any UNIX like file system, any file system
based on inodes. The one shipped with Linux is the GNU/Free Software
Foundation dump, which apparently can only dump ext2/ext3 file systems.
But dump has been around for a long long time.
windows, more importantly, how does it keep the ACLs? I guess i need
to readup further on dump.
It doesn't dump files, it dumps file systems. It creates a sort of
file system image. It's not like tar or cpio in this respect. Those two
commands work with files, so they must "preserve" things. With dump,
the entire file system state in respect to the specified files
gets saved.
Mike
--
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!
