4 ms·
It’s probably mostly done out of carefulness. I’d do the same if I were to write my own implementation of a file system. Bugs and mistakes in the code are alre
by codetrotter 3y ago
It’s probably mostly done out of carefulness. I’d do the same if I were to write my own implementation of a file system.
Bugs and mistakes in the code are already not great when implementing the read part. But if you mess up the writing well now you’re gonna cause corruption of existing data. No one likes that :)
Better to stick to just reading for a long while, and weed out most of the bugs and getting an even deeper understanding of the filesystem, before starting the implementation of anything that will modify the data.
- nineteen999 3y ago> I’d do the same if I were to write my own implementation of a file system. Exactly. I have my own ext2 driver for a couple of hobby OS projects where the read side is extremely stable, but as the write side involves inode allocation, block/bitmap allocation etc. I don't turn it on on outside of testing since I know it's going to destroy the disk images until I "get it right".