On Thu, 1 January 2009 16:23:00 +0200, Benny Halevy wrote: > > Personally, I'm not sure if maintaining that intimate knowledge in a > user space program is an ideal model with respect to keeping both > in sync, avoiding code duplication, and dealing with upgrade issues > (e.g. upgrading the kernel and not the user space utils) None of those problems actually matter, because you will have them anyway. If your filesystem is any good, someone will reimplement it for Windows, Grub, UBoot, Solaris or some other system. And even if it isn't any good, you still need to stay compatible with your own implementation from last year. Ok, maybe code duplication is a valid concern. But that will hardly outweigh the arguments in favor of a userland mkfs. The only exception I am aware of is jffs2, where a newly erased flash happens to be a valid (empty) filesystem. And even there you can view flash_eraseall as a trivial mkfs program. ;) Jörn -- It's just what we asked for, but not what we want! -- anonymous -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
