Home | Notifications | New Note | Local | Federated | Search | Logout

Note Detail

Reply to @brettm@swarm.coiloptic.org
natalie[ee]@0x6e6174@mastodon.catgirl.cloud (2026-07-25 09:30:33)
@brettm bweh. bsds don't have good btrfs support though, no?

do you think there to be there much reason to not just use zfs anyways (I assume there to be ai commits (disclosed or otherwise) in plenty of kernel code by now unfortunately) and just pin zfs to a specific version later if they deploy more substantial amounts of slop?

Not having to reformat my drive if I later install a non-linux kernel is something I care about
---Reply---
💙🩷💜 Brett [he/him/any]@brettm@swarm.coiloptic.org (2026-07-25 09:54:13)
afaik:
only freebsd has support for xfs
no bsd has support for btrfs
only filesystem everyone has in common and has both read and write capability is msdos(fat)

note: just because both freebsd and linux both support btrfs does not necessarily mean you can plug and play a hard drive - underlying driver may format drive differently on physical sectors (or on pseudo sectors if there is a controller chip on the drive pretending to be the disk then doing different things behind the scenes). eg when i format usb stick msdos FAT32, if I format using openbsd then windows and linux can both read it, it i format using linux or windows, the other OS does not always recognise it. You can however send backups to linux xfs from freebsd fs and vice versa. That is the main reason they share the code, so it interoperates.

Then msdos has other problems, it cannot store files over some size (4GB?), it cannot store files that have unicode like Chinese characters in filename, it cannot store files whose name is too long.

In summary I would completely avoid sharing filesystem between different drives. Just have another computer if you want to try a different OS and avoid needless pain, and avoid the chance of your whole filesystem being corrupted. Use ssh to share the files.

Thanks for coming to my Ted Talk :p

CC: @0x6e6174@catgirl.cloud