Return to BSD News archive
Xref: sserve comp.os.linux.development:2017 comp.os.386bsd.development:1320 comp.os.386bsd.misc:1266 Newsgroups: comp.os.linux.development,comp.os.386bsd.development,comp.os.386bsd.misc Path: sserve!newshost.anu.edu.au!munnari.oz.au!network.ucsd.edu!swrinde!cs.utexas.edu!uwm.edu!vixen.cso.uiuc.edu!moe.ksu.ksu.edu!osuunx.ucc.okstate.edu!constellation!servalan!rmtodd From: rmtodd@servalan.servalan.com (Richard Todd) Subject: Re: Has anyone written a Mac FS or Mac FS Access utilities for Linux or 386BSD? Message-ID: <CF0L0r.75w@servalan.servalan.com> Organization: Ministry of Silly Walks References: <CEv6Co.MA1.3@cs.cmu.edu> <29o4a1$r6u@u.cc.utah.edu> <29otpb$s8a@news.u.washington.edu> <CGD.93Oct16065256@eden.CS.Berkeley.EDU> Date: Sat, 16 Oct 1993 23:53:00 GMT Lines: 53 cgd@eden.CS.Berkeley.EDU (Chris G. Demetriou) writes: >In article <29otpb$s8a@news.u.washington.edu> tzs@stein3.u.washington.edu (Tim Smith) writes: >>How about making each Mac file appear to be three unix files? Mac file >>"foo" would appear under unix as "foo" (the data fork), "foo:r" (the >>resource fork), and "foo:i" (the Finder information). >hmm. A/UX does something like: > foo data fork > %foo resource fork >and i dunno what for the finder info... Hmm. It's a bit more complicated than that on A/UX. Mac files stored on an A/UX partition (presumably with the intent of being accessed by the MacOS environment that runs under A/UX) can be in one of two formats, AppleSingle and AppleDouble. AppleSingle format has all the information for a Mac file "foo" stored in a single Unix file "foo"; the resource fork and finder info appear first, followed by the data fork. AppleDouble format has the data fork for the Mac file "foo" stored in the Unix file "foo", without any stray headers on it. The resource fork and finder info are stored in the file "%foo", as you mentioned. AppleDouble is arguably the more convenient format for dealing with from Unix-side apps. For files like .gif or other platform-independent formats, all the information a Unix app would want to deal with would be in the data fork, and hence in the Unix-side file "foo", with no Mac-specific resource fork goo cluttering the picture. If you're planning on making an HFS filesystem for NetBSD, it'd probably be best to have it present the Mac files in AppleDouble format. (Just FYI, A/UX doesn't let you mount HFS filesystems on the Unix filesystem tree; the only way to dink with HFS filesystems is through Mac apps such as Finder running under the MacOS environment of A/UX.) The specs for AppleSingle and AppleDouble format should be available somewhere, probably on ftp.apple.com. There's currently a discussion ongoing in comp.mail.mime on how to best handle including Macintosh-specific files in MIME messages, and the formats they are planning to use are AppleSingle and AppleDouble. >it'd probably be a good idea to follow the A/UX convention -- >it's a unix on the mac and i for one would like to see >the mac port of NetBSD be as A/UX compatible in terms of things >like *that* as possible... (but no, i don't want NetBSD to become >svr2... *chuckle* 8-) Agreed. Especially about it not becoming SVR2. :-) -- Richard Todd rmtodd@mailhost.ecn.uoknor.edu rmtodd@servalan.uucp New Improved Domain: rmtodd@servalan.servalan.com