Before trying to implement this, I was wondering if anyone would find it useful for the ability to remove CraftOS off of any computer (like a rm craftos or something). What I mean by this is that every computer still comes preloaded with craftos, but you can remove it from each individual computer without modifying the jar file or using a resource pack. This could be useful when developing a computercraft os (more than just GUI for CraftOS). It possibly could be similar, but different to OpenComputers where you can install the different OSes, but with this CraftOS would be installed by default.

I honestly don't see the point. It is easy enough using the startup file to start your own custom OS and then shutdown when that shuts down, so why remove the OS entirely when it is basically just a command line?

@KnightMiner: The only real use I can see is the ability to escape the shell and the rednet coroutine. Though this can be done with a TLCO, so there isn't much benefit.

I don't think being able to delete the rom folder makes much sense. If we're going for the ability to have a "bare bones" system, I rather like @apemanzilla's suggestion of custom ROM via crafting, allowing one to "swap out" the rom folder through crafting a computer with a disk.

So maybe I could try to add either a ROM flashing API, or a ROM flashing block (insert disk the with the ROM on one side, computer on other)?

I don't think OpenComputers should be used as the standard for what ComputerCraft should be. I'm also unsure why you give yourself "thumbs up" on all your comments, it's not fooling anyone.

maybe extract the craftos part from bios.lua into rom/boot and write something in bios.lua to execute boot or, if it doesn't exist, rom/boot

I don't think this is a good idea. We already have a startup.lua which you can use to customise your environment completely.

@CrazedProgrammer But doing it in startup means overwriting everything, while splitting it up means doing it in a less hacky way. It‘s a philosophic thing.