Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).

×
Software

+ - BSD Stackable Filesystem Series I

Submitted by
jasonrfink00
jasonrfink00 writes "Nice beginning article of a promising BSD series: The nullfs filesystem is a passthrough filesystem. When nullfs is mounted it — literally copies the filesystem transaction. If a file is deleted, nullfs simply transmits the information down to the lower filesystem. Conversely, if a file is created, it does the same and tacks on all of the data needed for the filesystem underneath. Why is that a good thing? Where did nullfs come from and why?. What else, if anything, is it good for? The series focuses on where nullfs comes from, how it can be leveraged, a code walk and a skeloten implementation (nearly a blind copy). link."

IF I HAD A MINE SHAFT, I don't think I would just abandon it. There's got to be a better way. -- Jack Handley, The New Mexican, 1988.

Working...