Hi,

there's a first time for everything; so I thought it might be a good idea to give you people early access to some of the changes we're currently making to the hsfs filesystem driver, even before all of this pops up in a coming opensolaris.org code drop. I haven't seen anyone try this as a general request yet, but here we go.

I've put a unified diff of sourcecode changes to hsfs that implement the Joliet and ISO9660:1999 (v2) extensions, and make the hsfs filesystem module unloadable, at:

        http://cr.grommit.com/~frankho/

If you wish to look at the codechanges, the webrev/ subdirectory contains pretty-ized diffs nicely viewable via your webbrowser of choice.

Thanks to Joerg Schilling for most of this code. We are aware of one bug that exists in this code (a filename length validation issue), so this is not yet final until we've got the fix for that. But if you wish to have your go with Joliet/IOS9660-v2, try the above. If you wish to comment on it, have a go - I'd be delighted :)

We're planning to do the same (make review webrevs and udiffs available via cr.grommit.com, before the actual integration) for all future changes to the HSFS and PCFS filesystems as we do them within Sun. And yes, there is more to come. As far as HSFS goes, we want code for multi-extent (files larger than 4GB), for hardlink support, and others, and PCFS is in sore need of some significant overhaul. It's only fair to give early access.

As said, to a degree this is an experiment, trying to find out the best way to make this work, release early release often. Sorry if you feel like I'm cluttering your mailboxes.


Thanks to anyone who has a look, or better a try !

Frank Hofmann


==========================================================================
No good can come from selling your freedom, not for all gold of the world,
for the value of this heavenly gift exceeds that of any fortune on earth.
==========================================================================
_______________________________________________
ufs-discuss mailing list
[email protected]

Reply via email to