> Your dump is just a regular file sitting on a hard drive with a file > system that's already mounted. If you created an on-disk ISO image of > that file, you'd have to mount the file system of that ISO image to read > the file. If you burned the ISO image to a CD, you'd mount the CD's > file system to read it. Either way, the file remains just a file, and > is read using restore(8). > > I'll offer a guess that you're confusing things with tar(1) (which is > often used for backups) and the recent changes. From the manpage: > > This implementation can extract from tar, pax, cpio, zip, jar, ar, > and ISO 9660 cdrom images and can create tar, pax, cpio, ar, and > shar archives. > > The above means you can now do nifty things like 'tar xvf mybackup.iso', > and if you've configured a pre-processor for less(1), even niftier > things like: > > less backup.tar.gz > less backup.zip > less backup.iso > > It's also possible you might be thinking of file system snapshots (which > can be mounted). Check the Handbook for details. >
All I really want to do is take my dump file and see the "files" inside it, and do things with those files such as copy or md5sum (not edit). And I don't even know which tool do use to accomplish that. For example, if I took a dump 0 of /usr (which I did), I would like to see the "file" /usr/home/nlandys/.zshrc inside the dump, and then actually see (read) this file and/or copy it over scp or to another filesystem. _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
