I'm trying to use the version of tar on tomsrtbt to backup then restore a system. I'd like to use GNU tar for the backups (it's compare option looks very nice) but I can't get that to work with tomsrtbt restore. I use: tar -clf /dev/st0 . from the root partition for the backup. That works OK. I uses mke2fs from tomsrtbt to re-initialize my /boot and / partitions, then use: -tar xlf /dev/st0 Note: your man page is ambigious on use of -l option; usage summary and description of the option disagree on whether it can be used on create or extract. This results in a segmentation fault near the end of the restore. Here's my second disk (the one I use test with) according to fdisk: dev start end blocks Id system /dev/hdb1 1 33 265041 82 Linux swap /dev/hdb2 34 1108 8634937+ f Win95 Ext (LBA) /dev/hdb5 34 35 16033+ 83 Linux (my /boot partition) /dev/hdb6 35 1108 8618841 83 Linux (my / partition) Here's what I did to test tomsrtbt tar, all commands from tomsrtbt disk: Create Linux system on /dev/hdb Boot tomsrtbt diskette, version 1.7.185 # create backup mkdir /test mount -t ext2 /dev/hdb6 /test mount -t ext2 /dev/hdb5 /test/boot cd /test (verified boot and / have what they should with ls) tar -clf /dev/st0 . # nuke what I just backed up and initialize partitions umount /test/boot cd / umount /test mke2fs /dev/hdb5; mke2fs /dev/hdb6 e2fsck /dev/hdb5; e2fsck /dev/hdb6 # restore tape mount -t ext2 /dev/hdb6 /test cd test mkdir boot mount -t ext2 /dev/hdb5 /test/boot tar -xlf /dev/st0 Segmentation fault This fails consistently, it is reproducable. What do you think? Too many inodes? (but backup worked.) Disk too big? I have problems with tomsrtbt cpio, but would like to see if I can get tar working before getting into that. Regards Kerry [EMAIL PROTECTED]
