I had built this project many years ago, and even got it to the point where it was "technically" self hosting. The architecture was as follows:
- The "kernel" is just a set of common routines for input, output and file handling.
- The file system was just an index number, corresponding to a sector on disk.
- A simple shell program had a table of strings and numbers to load a program from the disk.
- The text editor was line based, and I mean literally line based. You could only print or add one line at a time.
- I ported the hex program to assemble the files.
I got this to a point where it could assemble itself (I dont think assemble is the right word), but the process was incredibly tedious as you had to load the text file from one disk, assemble it, swap disks, and write it to the new disk. Repeat this for each file; it was per program so maybe 5-6.
It's been a while since I've had time to work on it, but I've recently changed jobs so I might get to this stage again soon.
hexer292•1h ago
I had built this project many years ago, and even got it to the point where it was "technically" self hosting. The architecture was as follows:
- The "kernel" is just a set of common routines for input, output and file handling.
- The file system was just an index number, corresponding to a sector on disk.
- A simple shell program had a table of strings and numbers to load a program from the disk.
- The text editor was line based, and I mean literally line based. You could only print or add one line at a time.
- I ported the hex program to assemble the files.
I got this to a point where it could assemble itself (I dont think assemble is the right word), but the process was incredibly tedious as you had to load the text file from one disk, assemble it, swap disks, and write it to the new disk. Repeat this for each file; it was per program so maybe 5-6.
It's been a while since I've had time to work on it, but I've recently changed jobs so I might get to this stage again soon.
P.S. - Assembly is Too High Level