site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com On 16 May 2007, at 22:39, Jordan K. Hubbard wrote: On May 16, 2007, at 10:44 AM, Dan Shoop wrote: Cheers, Graham. _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... As we all know FUSE is a project to implement ad-hoc filesystems in user space. Ad-hoc filesystems are, by nature, not readily suitable for production. Hence my comment. Furthermore if the filesystem was production quality it would most likely be implemented within the system, not a user application. User based applications don't lend themselves well as production services. That's a rather broad categorization to make and, as such, not really supportable. There are many instances where putting a filesystem in user space is a good idea: BTW [to the list, not necessarily to JKH] - check out the HURD, where almost any problem can be fixed by recompiling and restarting some user-land process. There's a kernel-space module for e2fs, but that just brings the system up to a point where it can launch the userspace e2fs translator and get on with some real work ;-) On a PPC Mac, it'd be easy to imagine a scenario where the system only relies on the Open Firmware HFS+ reader until it's loaded a userspace HFS+ translator. This email sent to site_archiver@lists.apple.com