Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!uwm.edu!math.ohio-state.edu!howland.reston.ans.net!EU.net!Germany.EU.net!Bonn.Germany.EU.net!tools!ws From: ws@tools.de (Wolfgang Solfrank) Newsgroups: comp.os.386bsd.development Subject: Re: is there a 'complete' version of ISOFS ? Date: 30 May 94 17:34:04 Organization: TooLs GmbH, Bonn, Germany Lines: 26 Message-ID: <WS.94May30173404@kurt.tools.de> References: <BRIAN.94May29100947@sun1.claremont.com> NNTP-Posting-Host: kurt.tools.de In-reply-to: brian@sun1.claremont.com's message of Sun, 29 May 1994 14:09:47 GMT What version of ISOFS are you speaking about? The version that is included in NetBSD has had these Rock Ridge features for quite some time now. You are correct though that there are still some features missing, ISO9660 features (like interleaved files, multi-extent files, multi-volume CDs, etc.) as well as Rock Ridge extensions (like device number mapping or the features defined in the new Rock Ridge draft), not to speak of support for other extensions (like XA attributes, Mac file attributes, Plan 9 extensions etc.). I'm working on a new version (when time permits) that will support some more of these features, but time is a bit scarce right now... BTW, does anyone have a good description of the VFS layer in BSD? Especially the interworking between the *bmap and the *strategy funtions. From code inspection it looks like the *bmap routine isn't called (extenally) during the normal usage of accessing a local file. Only access to the file via NFS or through some special mechanism like the vn device seems to use this routine, but then it seems to expect proper behaviour (to some spec that I can only guess). So I would be very thankful if anyone can provide me with said spec. -- ws@TooLs.DE (Wolfgang Solfrank, TooLs GmbH) +49-228-985800