Return to BSD News archive
Path: sserve!manuel!munnari.oz.au!spool.mu.edu!caen!kuhub.cc.ukans.edu!ccsvax.sfasu.edu!menudo.uh.edu!sugar!taronga!peter
From: peter@taronga.com (Peter da Silva)
Newsgroups: comp.unix.bsd
Subject: Re: TAR to multiple floppies
Message-ID: <Q8WGPIJ@taronga.com>
Date: 29 Jun 92 12:37:26 GMT
Article-I.D.: taronga.Q8WGPIJ
References: <memo.494376@cix.compulink.co.uk> <V7VG9K7@taronga.com> <1992Jun28.151916.8744@hemlock.cray.com>
Organization: Taronga Park BBS
Lines: 27
In article <1992Jun28.151916.8744@hemlock.cray.com> overby@cray.com (Glen Overby) writes:
>In article <V7VG9K7@taronga.com> peter@taronga.com (Peter da Silva) writes:
>>Another possibility is to write a wrapper for tar/cpio/whatever that
>>chops the job up into appropriately-sized chunks. I have one for CPIO
>Andy Tanenbaum wrote something like this for Minix
> vol [-u] size device
>It splits up stdin onto multiple disks or joins them together on stdout.
>Works with "anything".
Ah, that's the backwards of my program. My program calls cpio repeatedly
with just enough files to fill a floppy (approximately: there's some slop
when it can't find enough small files). It doesn't do anything supersmart
about big files in inconvenient places (I was in a hurry, it's one of those
Just In Time backups), but I'll polish it up and try to make it smarter
about filling knapsacks (and handling links).
>The problem: what do you do when disk 3 of a 20-part disk set goes bad?
Insert disk 4. Sinch each disk is a separate archive that's not a problem.
--
`-_-'
Have you hugged your wolf today? 'U`
Peter da Silva, Taronga Park BBS, Houston, TX +1 713 568 0480/1032