Possibly, as long as inodes are kept in sync on disk for a permanent record I'd think the major problems would be limited to race conditions from processes or threads where something opens a file and another deletes it. I don't know a good way to handle that, or a better way to handle file deletions. Journaling would help, to keep a record of changes or actions. I'd have to research more
You could write the OS.bin file directly to a usb with dd or rufus, but it probably won't work in protected mode unless usb somehow emulates an ide drive. ATA PIO would not work, it needs a proper USB stack, and ehci or xhci support, which is a lot of work. I use a SATA to USB cable to write to an ssd and boot from that, which is less convenient, but works for now.
So happy to see you.
Seems like that ref_count-- in delete file is going to cause problems later
Possibly, as long as inodes are kept in sync on disk for a permanent record I'd think the major problems would be limited to race conditions from processes or threads where something opens a file and another deletes it. I don't know a good way to handle that, or a better way to handle file deletions. Journaling would help, to keep a record of changes or actions. I'd have to research more
🔥🔥🔥🔥🔥 we need to dotfiles
git.sr.ht/~queso_fuego/dot_files
Hi, can you please tell me how to run your OS from a USB drive?
You could write the OS.bin file directly to a usb with dd or rufus, but it probably won't work in protected mode unless usb somehow emulates an ide drive. ATA PIO would not work, it needs a proper USB stack, and ehci or xhci support, which is a lot of work.
I use a SATA to USB cable to write to an ssd and boot from that, which is less convenient, but works for now.
@@QuesoFuego thanks you very much