Utah OSKit v.20020317 -- static libraries

[VaultZero]

I came across this project a couple of years ago and was quite impressed by it. Not necessarily everyone's cup of tea, but a very
cool idea nevertheless.

I have come to the decision that (for now) I will provide the static libraries for the latest (AFAIK) version of this project, 20020317...

The primary reason I'm doing this is to perhaps make it easier for those who might still be interested in this but have difficulty building it. I bashed my head against the wall for weeks trying to figure it out and then finally gave up on it for a while... then I thought I'd give good old Debian 2.1 a whirl. Installed it on an old machine, got GCC 2.95.2.3/binutils 2.9.1 all set up and ready to go, and then built the whole thing. I can't vouch for how well all of it works with more modern toolchains, because I haven't tried it out that much... I'd be interested to see how well it actually does work, if at all... so comments and feedback are welcome.

It's unfortunately very very outdated by now, and could have gone so much further, but it may still be of use to some; take it or leave it - your choice, obviously.

Hope somebody finds this useful, but if you don't want/need it then don't bother.

http://zeus.murasama.net/devrec.html

use tar -jvzf to decompress/unpack. Should come out to right about 50 megabytes of .o and .a files.

/* tar -xvjf , sorry... */

source code can be found here:

http://www.cs.utah.edu/flux/oskit/

[KotuxGuy]

Cool. I tried to build OSKit a while ago, and had to get GCC 2.95.
Although, most people here don't really use OSKit(NIH?), and don't seem to look to kindly on other people using it.

Usually, they say it's because they we do this(OSDeving) to learn, but I say if you just want your own OS to toy with it, go ahead and use OSKit!

[pcmattman]

OSKit basically takes all the fun out of operating system development.

What you effectively get is a *nix-style OS that you can write applications for. Why not just go out and make a Linux distribution or something? It's basically the same...

[VaultZero]

As I said, take it or leave it. I share a fairly similar viewpoint as far as the development process goes; it's much more of a meaningful and complete experience when you're not being spoon-fed (it can also make one want to pull one's hair out at times...).

Personally, I'm not using it at this point, and probably never will... just wanted to make it available in a convenient form for those who might be curious about/interested in it.

[osdnlo]

What's strange is that you would go through so much trouble to assemble it all and not use it yourself. Why would you do that? And, why did you post it here? The forum is a place where you come to get into arguments with people you can't see. The wiki is where we post things about OS Development.

[earlz]

OSKit basically takes all the fun out of operating system development.

What you effectively get is a *nix-style OS that you can write applications for. Why not just go out and make a Linux distribution or something? It's basically the same...

I'd say Minix would be better at that cause it's so minimalistic.

But yea, I find the fun part to be the early stages. Eventually though, the OSKit does provide useful things for drivers and network connectivity, which I would say it more difficult to do right.. (and less fun for me)

What's strange is that you would go through so much trouble to assemble it all and not use it yourself. Why would you do that? And, why did you post it here? The forum is a place where you come to get into arguments with people you can't see. The wiki is where we post things about OS Development.

Congratulations on adding absolutely nothing to this conversation.