cpio reading multivolume floppy archives - say it ain't so

cpio reading multivolume floppy archives - say it ain't so

Post by k.. » Fri, 11 Nov 1994 17:00:17



What are you supposed to do when reading a multivolume cpio archive from
floppies, you get to the end of a volume and cpio prompts for the name
of the next device to read from?

If I just type in the device name of the floppy drive, cpio just
re-reads the floppy that's already in the drive since it never ejected
it.

I found I had to use a separate shell to explicitly eject the floppy.
Then, after I insert the next floppy and type the device name in answer
to cpio's prompt, cpio keeps complaining that it can't access the device
(errno=0), until I do something like run "eject -d" in another shell.

It can't be this lame, can it? I've RTFM and if the answer is there, I
missed it completely. This in on Sparc SunOS 5.3.

---


--


 
 
 

1. select() says there's data, read() says there isn't


Well, lots of people tell him that this means EOF and the other end
has gone away
BUT
I had a problem with Sun where a select says that there is data, a
read gets a zero return, a second select says there is data again
(perhaps later on!) and a read then gets real data.

So I only counted the other end dead after several consecutive zero
read returns.

2. parrallel port zip drive 100 megabytes

3. ``No more processes...''

4. S10 floppy ain't drivin' - except w/WABI - and now WABI died!

5. Problem compiling 99.p9

6. applixware: say it ain't so...

7. Linux Frequently Asked Questions with Answers (Part 6 of 6)

8. Say it ain't so...

9. applixware: say it ain't so...

10. IBM takeover of Sun - Say it ain't so !

11. 'mount' say NO iso9660 support and 'cat /proc/filesystems' say YES!!!