Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!mcvax!eurifb!wietse
From: wietse@eurifb.UUCP (Wietse Venema)
Newsgroups: comp.unix.xenix
Subject: Re: cpio: Microport <-> Xenix
Message-ID: <210@eurifb.UUCP>
Date: Sun, 20-Sep-87 16:15:04 EDT
Article-I.D.: eurifb.210
Posted: Sun Sep 20 16:15:04 1987
Date-Received: Tue, 22-Sep-87 01:03:52 EDT
References: <232@puck.UUCP>
Organization: EUR/Bedrijfskunde,PObox 1738,Rotterdam,Neth.
Lines: 19
Keywords: not multi-volume
Summary: use standard unix tools

In article <232@puck.UUCP>, asp@puck.UUCP (Andy Puchrik) writes:
> I was recently moving some s/w via floppy from uport to xenix when I got
> a rude shock.  Cpio works fine (after you get the device names right) as
> long as you only use a single floppy.  Uport cpio handles multiple floppies
> fine.  Xenix cpio exits to shell after writing a full floppy or reading in
> the first of a multi-volume set.

What about reading a multi-volume set with the following Bourne-shell commands:

	while :
	do
		dd if=floppydrive bs=blocksize count=blockcount
		(echo "Mount next floppy"; read ans) >/dev/tty </dev/tty
	done | cpio [options]

Creating a multi-volume set this way is left as an exercise for the reader...

		Wietse Venema	(uucp:	...!mcvax!eutrc3!wswietse)
				(bitnet:	wswietse@heithe5)