Writing custom operating system
Aside from that, go crazy, be creative! For a definite reference for what's available in an init script, check the kernel.
It looks for a file system with address set via computer. Starting with OpenComputers 1. This works because component. To get a proxy, use the component.
There are a few libraries documented on the wiki that are in fact part of OpenOS, so when you're implementing your own operation system, those won't be at your disposal.
The user script is now in control. For several reasons the proxy system is provided via the machine itself, so you can still use that. If no working init. Otherwise that BIOS is run.
If it succeeds, that's it. Most notably that includes the io , package and filesystem libraries. When a computer is powered on, that script is loaded and run. You can either write that down manually, or get the list of components using component. If that fails the computer crashes. While this makes it slightly more annoying to set up computers, it opens up a lot more possibilities for people that want to write their own OSes; which is what this article is all about!
That means you cannot just write component. If it fails, it iterates over all present file systems, performing step 2 again until it succeeds. For example, to get the first best redstone component, you can do the following: On that file system it tries to load and execute a Lua script from a file named init. Signals must be processed using computer.
You'll also want to take care of setting up attached components during your OS ' boot routine, such as binding GPUs to screens. It expects the address of the component to wrap.