OSDev.org

Yes, as berkus said, adding basic versioning to a filesystem is not hard. You really just have to make space in your directory entries for a few more bytes of dedicated version information. My little Bang!FS filesystem that I created has versioning support. So, no, not revolutionary. But it's a heck of a lot smarter than the idiotic way that "make" tries to misuse file modification times to figure versioning.

(And the easy way to handle the rm question is: as each new version of the file is created, the old version gets mv'ed off into a "history" directory tree. If the final file gets rm'ed, then it's gone and you have to recover from the history directory if you want it back.)

earlz wrote:but it could render you with a filesystem(involving links and such) that is readable from other systems not aware of versioning.

How could they read it at all w/o having a driver for it? Surely anyone who takes the time to write the driver would also implement support for the fs's core feature.

TylerAnon wrote:

earlz wrote:but it could render you with a filesystem(involving links and such) that is readable from other systems not aware of versioning.

How could they read it at all w/o having a driver for it? Surely anyone who takes the time to write the driver would also implement support for the fs's core feature.

earlz was talking about implementing versioning on top of an already-existing FS (like ext2). Versioning wouldn't be a "core feature" there, but merely an add-on.

attempting to port Ruby 1.9.2 VM to bare-metal. any suggestions on which libc to use (small, and easy to convert to bare-metal) ?

Necropost ftw?

Checkout EFI