3 ms·

link to source?

jacquesm 14y ago
http://ww.com/task.cc.txt http://ww.com/task.cc.txt It's a 32 bit QnX clone, this is the kernel. The project is not buildable since the original scaffolding (djgpp) is going to be pretty hard to come by. I probably could still put together a bunch of images to get it to boot if I spend a month on it but I don't see any point in doing so. Still, it was a fun project and I learned an awful lot doing it.
- adamnemecek 14y ago
  With all due respect I'm not sure that that is a fair comparison. Your OS seems to be pretty barebones (I'm not sure if what you posted is all of it but it does not even seem to have a file system). SparrowOS is some 130KLOC and has a lot of shit going on for it. Here is the breakdown http://www.sparrowos.com/Wb/Accts/TS/Wb2/LineCnt.html#l711 http://www.sparrowos.com/Wb/Accts/TS/Wb2/LineCnt.html#l711. But note that not all of it is code (for example the bible). EDIT: It seems that QnX is a microkernel hence the lack of FS. But it's not really a fair comparison regardless.
  - deleted 14y ago
    [deleted]
  - jacquesm 14y ago
    This is just the kernel, the OS has a filesystem, networking, graphics, GUI (both basic elements and a window manager), does multi-user multi tasking. It is the largest project I ever worked on, but as I wrote it does not currently build so there is not much point in releasing the source in its entirety. I just posted the kernel code as proof that I did indeed write an OS. I won't make a comparison between SparrowOS and what I put together but I think that if such a comparison where to be made I'd first have to put in a lot of time to get it serviceable again and I have other things to do. The filesystem was a port of the Minix FS, the networking stack was a full TCP/IP stack adapted from freebsd to work as a stand-alone process. The GUI/WM were written from scratch. It relied heavily on DJGPP for the bootstrapping of the development process and at some point became self-hosting. The one tricky part which I really have no idea on how to solve today was that for the bootstrap it used a mixed mode program written in borland C to get the initial configuration and the first few processes loaded into ram before starting up the OS proper. All of this would have to be updated and repaired before you could get a working OS out of it. So with all due respect I think that it was a pretty fair comparison.
    - adamnemecek 14y ago
      Yeah, I was not sure if that was all of it or not. Just release it, even if it does not build. If you figure out how to build it at some point, good, but if not, it's better for it to be released than not released even if it does not build.
      - jacquesm 14y ago
        I'll think about it. Releasing code like that is not a trivial thing and I don't want to end up having to maintain it or to become a focal point for a bunch of attention.

link to source?

http://ww.com/task.cc.txt http://ww.com/task.cc.txt It's a 32 bit QnX clone, this is the kernel. The project is not buildable since the original scaffolding (djgpp) is going to be pretty hard to come by. I probably could still put together a bunch of images to get it to boot if I spend a month on it but I don't see any point in doing so. Still, it was a fun project and I learned an awful lot doing it.

adamnemecek 14y ago
With all due respect I'm not sure that that is a fair comparison. Your OS seems to be pretty barebones (I'm not sure if what you posted is all of it but it does not even seem to have a file system). SparrowOS is some 130KLOC and has a lot of shit going on for it. Here is the breakdown http://www.sparrowos.com/Wb/Accts/TS/Wb2/LineCnt.html#l711 http://www.sparrowos.com/Wb/Accts/TS/Wb2/LineCnt.html#l711. But note that not all of it is code (for example the bible). EDIT: It seems that QnX is a microkernel hence the lack of FS. But it's not really a fair comparison regardless.
- deleted 14y ago
  [deleted]
- jacquesm 14y ago
  This is just the kernel, the OS has a filesystem, networking, graphics, GUI (both basic elements and a window manager), does multi-user multi tasking. It is the largest project I ever worked on, but as I wrote it does not currently build so there is not much point in releasing the source in its entirety. I just posted the kernel code as proof that I did indeed write an OS. I won't make a comparison between SparrowOS and what I put together but I think that if such a comparison where to be made I'd first have to put in a lot of time to get it serviceable again and I have other things to do. The filesystem was a port of the Minix FS, the networking stack was a full TCP/IP stack adapted from freebsd to work as a stand-alone process. The GUI/WM were written from scratch. It relied heavily on DJGPP for the bootstrapping of the development process and at some point became self-hosting. The one tricky part which I really have no idea on how to solve today was that for the bootstrap it used a mixed mode program written in borland C to get the initial configuration and the first few processes loaded into ram before starting up the OS proper. All of this would have to be updated and repaired before you could get a working OS out of it. So with all due respect I think that it was a pretty fair comparison.
  - adamnemecek 14y ago
    Yeah, I was not sure if that was all of it or not. Just release it, even if it does not build. If you figure out how to build it at some point, good, but if not, it's better for it to be released than not released even if it does not build.
    - jacquesm 14y ago
      I'll think about it. Releasing code like that is not a trivial thing and I don't want to end up having to maintain it or to become a focal point for a bunch of attention.