OSDev.org

ehird wrote:SkyOS has linux code? Um, no. Just because something conforms to the UNIX specification doesn't mean it uses linux code.

Plus, SkyOS is proprietary, that would violate the GPL

Some apps are open source though

dex: What about minix? and what about Woz and the Apple I/IIs? There are plenty of people who can code a kernel/fs/userland within eight years. I'm planning (EEEK) to do this. (No, I'm not quite as naive as you think... this is a designed os, not hacked, like many here are.)

Also, last time I checked, you didn't use fasm for the DS, you used fasmarm, which is different (not self-compiling).

baileydr wrote:dex: What about minix? and what about Woz and the Apple I/IIs? There are plenty of people who can code a kernel/fs/userland within eight years. I'm planning (EEEK) to do this. (No, I'm not quite as naive as you think... this is a designed os, not hacked, like many here are.)

Also, last time I checked, you didn't use fasm for the DS, you used fasmarm, which is different (not self-compiling).

Haha, "like many here are"... I don't doubt that, I'm trying that as well, but my software is no more than a HELLO WORLD low level program at the moment. A one-person project in 8 years to become as Linux and yet better would take a true one an only Einstein of programming, not possible for almost 99.999999% of programmers.

And about hacking other OS'es, that's just a nice way of learning them while providing a help to those who want to understand it whenever possible...

I'm not envisioning linux... I'm thinking about a CLI with a basic gcc/glibc port, maybe a tcp/ip stack, drivers for my hardware.

There's quite a bit of excellent code at work here; just look at dex, menuet, mattisse, etc. I'm simply saying that many of the work that goes on here is a lot of people trying to run before they can walk; i.e. creating a gui before a memory manager or multitasking (unless a dos clone is being made or something).

baileydr wrote:dex: What about minix? and what about Woz and the Apple I/IIs? There are plenty of people who can code a kernel/fs/userland within eight years. I'm planning (EEEK) to do this. (No, I'm not quite as naive as you think... this is a designed os, not hacked, like many here are.)

Also, last time I checked, you didn't use fasm for the DS, you used fasmarm, which is different (not self-compiling).

First if it was 8 year, i would have no problem, i would be impressed, but it not 8 years, its more 3 - 4 year since a total rewrite.

As for fasmarm, see here what it is http://arm.flatassembler.net/
See the words "ARM cross-assembler add-on for FASM" its 1. a cross-compiler or in this case a cross-assembler and 2. a add on for FASM.
And that is what we were talking about.

Maybe they don't have something to call a formal memory manager, but doing such things without auditing programatically the memory usage is an unimaginable thing. They surely have to have some sort of implicit memory management for doing those things. Those are the things to document once one of us gets to successfuly find time to dissect those apps

But anyway, my words don't help anyhow, and if I can't or don't help I better limit my opinions...