a plan for a filesystem

I’ve been thinking and poking at AROS a lot this week, so I have heaps to write about but haven’t had time. I’ll try to find more time today to get it all down. Here’s the first installment.

Recently AROS has obtained a new installer, but its still hamstrung by the fact that we don’t really have a proper filesystem to install AROS onto. We currently have three filesystem options:

So, what to do? We can fix the bugs and stablise the filesystems. We could implement support for SFS in GRUB. We could add extended attributes to FAT, either by making our own incompatible extensions or by using “magic” files. Ultimately though, we’re left maintaining our own filesystems. As disks become larger and larger and new innovations in filesystem design appear, we’re going to be left behind. We’re not filesystem designers. We don’t have enough people to commit resources to it. The best thing we can do in this situation is to steal something :)

I propose taking ext2/ext3(/ext4). Literally taking it - ripping it from the Linux kernel and porting it. Here’s why:

I’ve done enough research to know that this can work. I have no immediate plans to implement it, but it’ll be something I look at eventually. Of course, if you want to work on it I’m quite happy to help out.