From owner-freebsd-current Sun Mar 26 9: 2:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from cx587235-a.chnd1.az.home.com (cx587235-a.chnd1.az.home.com [24.11.88.170]) by hub.freebsd.org (Postfix) with ESMTP id 3639D37B9EF for ; Sun, 26 Mar 2000 09:02:41 -0800 (PST) (envelope-from jjreynold@home.com) Received: from whale.home-net (whale [192.168.1.2]) by cx587235-a.chnd1.az.home.com (8.9.3/8.9.3) with ESMTP id KAA23511; Sun, 26 Mar 2000 10:02:38 -0700 (MST) (envelope-from jjreynold@home.com) Received: (from jjreynold@localhost) by whale.home-net (8.9.3/8.9.3) id KAA55757; Sun, 26 Mar 2000 10:02:38 -0700 (MST) (envelope-from jjreynold@home.com) From: John Reynolds MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14558.17069.754126.394415@whale.home-net> Date: Sun, 26 Mar 2000 10:02:37 -0700 (MST) To: Julian Elischer , current@freebsd.org Subject: Re: anything more current info on UDF support/activities? In-Reply-To: References: <14558.13857.889817.169398@whale.home-net> X-Mailer: VM 6.73 under Emacs 20.6.1 Cc: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ On Sunday, March 26, Julian Elischer wrote: ] > I'm in the process of investigating UDF with the aim of > producing a UDF filesystem (possibly only read-only) > and a UDF enabled version of mkisofs (porst/sysutils) > cool! > I have all the appropriate specs and standards here and have been reading > them. I also have the linux UDF code as of a month or two back. I'd love > to see the MACOS-X UDF code but it doesn''t seem to be released in those > parts they have made public. :( > The UDF filesystem is not rocket science but the documents describing it > are in "ISO-Standardese" which means that they are almost IMPOSSIBLE to > read. EVERYTHING is defined in the least useful manner possible, and no > overall architecture is given. they just specify every single field, and > you have to piece the big picture together from about 200 pages of minute > fragments. if it was easy to read, it couldn't be called a "standard" though ;-) > (In the mean while all CDs and DVDs should also have a ISO9660 > filesystem in parallel, pointing at the same data) (for a couple of years > anyhow) (that is what the standard for DVDs say) Right ... I was originally searching for info on this topic because my wife got a CD-R from her relatives that was supposed to have billions of scanned family pictures on it. Unfortunately the person writing the CD-R used "DirectCD" from adaptec which uses UDF and packet writing, rather than burning an ISO9660 filesystem the "traditional" way. Thus, I was not able to "see" the contents under FreeBSD. It just got me curious. Your code will not go un-appreciated! Thanks for the more-up-to-date info, -Jr -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= John Reynolds Chandler Capabilities Engineering, CDS, Intel Corporation jreynold@sedona.ch.intel.com My opinions are mine, not Intel's. Running jjreynold@home.com FreeBSD 3.4-STABLE. FreeBSD: The Power to Serve. http://members.home.com/jjreynold/ Come join us!!! @ http://www.FreeBSD.org/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message