the most clear deficiency of ntfs can be seen when you are copying (either reading OR writing) large volumes of source code or small files... ext4 is like 100x or more faster at reading and writing small files, it's completely out to lunch how bad windows ntfs is and then you have the issue of the bad implementations for linux, which no coincidence due to the design of the structure also are bad at large numbers of small files (and no amount of tuning the block size makes a stick of difference)
Yeah copying this windows disk from a mounted ntfs partion on linux to another ntfs partition I made using linux took like 15 minutes. The windows disk didnt even boot in the end. I don't know why windows doesn't make it easier for people with Macs to make windows install disks. Or linux. Making a windows install disk is like a chicken and egg problem that requires windows.
it can be done on linux using woeusb it's complicated because it's gotta be either ntfs and uefi, or exfat and MBR my advice is to try ventoy
Woeusb seems promising Ventoy also seems promising. Will get back to it this weekend and get it done
yeah, ventoy is super handy
Ventoy ended up being the winner! Thanks so much!
it makes it so much easier
Yeah im going to devote this usb stick to it now. No more reimaging the drive
Ventoy is awesome! I think I'm going to try Endeavor next 😮
That’s just an Arch based OS? Why is it good?
Well its supposed to be more better than Qubes as far as hardware compatability and UI goes. But you can still get the same containerization and security guarantees fairly easy, so I am told anyway. I've never run arch before and this seems like the perfect way to start.
I’m currently looking for a flavor of Debian which is more updated (like Ubuntu) but doesn’t use snaps The containerization of apps sounds interesting
yeah snaps are a pain i would absolutely be into something like that too but dont know anything outside vanilla Debian
ironically, snaps are containerization, but the problem of permission to access files is the actual problem android has a permission you have to enable for any app you want to read the base system disk... snaps don't seem to have that working right, and it should just be default on with the app config folder in the expected location... you'll have fun discovering it's the same problem more generally i don't like it, i prefer to install apps on the base system about the only app that i think has a real security need to do it is browsers, so actually what would make more sense is to install everything else normally but dumb shit with dumpster fire capacity to run arbitrary code should be in containers if it can't run arbitrary code it's literally not a vulnerable system, assuming it doesn't have stack smashing or other buffer overflow vulnerabilities... for the most part, boost, and most languages have plugged that one up anyway it's really just the "it can run arbitrary code" problem... it would be solved if the execution engine itself was containerised but what about when you want to download files to the rest of the filesystem? that again requires a permission the real elephant in the room about containerizing apps is literally the web browser engine
also, don't try to mess with changing the filesystem, there is voodoo in there... best to move partitions around or copy them across (ie, make one big enough to fit then use DD to dump it onto the partition windows does tolerate being moved about, but not simple copies, the filesystem holds magic sauce