Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!spool.mu.edu!snorkelwacker.mit.edu!bloom-beacon!eru!kth.se!cyklop.nada.kth.se!news From: d88-jwa@byse.nada.kth.se (Jon W{tte) Newsgroups: comp.sys.mac.programmer Subject: Re: Mac vs. A/UX floppies (was: raw read/write floppies) Message-ID: Date: 21 Mar 91 15:04:14 GMT Article-I.D.: byse.D88-JWA.91Mar21160412 References: <69144@brunix.UUCP> <40389@cup.portal.com> Sender: news@nada.kth.se (Mr News) Organization: Royal Institute of Technology, Stockholm, Sweden Lines: 27 In-reply-to: MacUserLabs@cup.portal.com's message of 20 Mar 91 20:52:08 GMT In article <> MacUserLabs@cup.portal.com (Stephan - Somogyi) writes: tar floppies (or cpio, or just plan _files_) to be used from A/UX. I don't understand why you want this. A/UX 2.0.x reads Mac floppies just fine. I am able to copy unix files onto such a floppy and read them on a Mac. Or am I missing something here? Yes, you don't account for my un-grasp of your language :-) What I meant was that cpio -> disk from A/UX to MacOS would be nice (if you could read it back...) The other way would gain too, since you wouldn't have to worry about changing creators to avoid corruption of compressed files. Archival of larger-than-a- disk files would be snappier too. And you wouldn't have to go through finder or fire up the mac envmt. :-) Happy hacking, h+@nada.kth.se Jon W{tte -- "The IM-IV file manager chapter documents zillions of calls, all of which seem to do almost the same thing and none of which seem to do what I want them to do." -- Juri Munkki in comp.sys.mac.programmer