OSDev.org

I'm going with googlecode's motto "Release early, release often"
Anyway, I know that there aren't many new visible features, but there are many changes internally (thats how OSdev goes! )
And please note that this is a kernel.

[Floppy] http://seakernel.googlecode.com/files/floppy_b1.img
[Source]http://seakernel.googlecode.com/files/trunk.zip
http://code.google.com/p/seakernel

• Device Management integrated
  Fixed some bugs
  Tasking is good, better signaling (it runs them when the task runs, not when they are signaled)
  Configuration system is better

Anyway, my test requests are.....Please test the configuration system (make config) and will it work in other places other than Qemu?

Please proofread the readme...
Notes:
To run programs, type a period and then a program name (e.g. '.ls'). Valid commands are:
.init Loads another shell (the shell is a separate executable)
.ls Lists all files in the root FS
.sync Runs a sync system call (does nothing yet)
.gr Switches Graphics modes and draws a rectangle (and halts the system)
.atam Loads a hard Drive module
die Exits The Shell (and resets the system)

-JL

Looks good - .ls doesn't list the contents of directories though, or at least it didn't list /dev's contents.

I like the build system however, very cool and colourful.

I got a random page fault, I didn't actually type anything at the time so can't tell you why:

Thanks
Does make config work?

Directories and file handles are on the list for Beta 2.

The pagefault seems to occur when I run my kernel, and then minimize qemu or do something else. As soon as I switch back it pagefaults.
When I keep Qemu focused for as long as one hour it's fine...

-JL

Yeah, I did switch focus just before it happened.

Make config works fine. Very good stuff.

Your floppy image managed to crash WinImage *again*.

Shell has same bugs, all the gravy.
How should I use the "make config" thing? Typing just "make config" does do nothing.

Release early, release often... release in hurry? There seems no big difference between 0.02 and 0.01, the shell is the same version, etc. In other words, your kernel is a crap for now. And you can have paging, multitasking, 64 bit long mode (i know its 32bit), who cares, you need to show off the practical functions of your OS.

Wasn't worth even downloading.

inflater wrote:Your floppy image managed to crash WinImage *again*.

Shell has same bugs, all the gravy.
How should I use the "make config" thing? Typing just "make config" does do nothing.

Release early, release often... release in hurry? There seems no big difference between 0.02 and 0.01, the shell is the same version, etc. In other words, your kernel is a crap for now. And you can have paging, multitasking, 64 bit long mode (i know its 32bit), who cares, you need to show off the practical functions of your OS.

Wasn't worth even downloading.

How's your OS doing at the moment inflater?

If you've got nothing nice to say... GTFO.

inflater wrote:Your floppy image managed to crash WinImage *again*.

Maybe try using something ELSE? Like VFD?

Shell has same bugs, all the gravy.
How should I use the "make config" thing? Typing just "make config" does do nothing.

It's called a makefile? The program is "make", and it "makes" the config target? I would've assumed you knew that.

Release early, release often... release in hurry? There seems no big difference between 0.02 and 0.01, the shell is the same version, etc.

No visible difference, but I'd say there's a lot of changes behind the scenes.

In other words, your kernel is a crap for now. And you can have paging, multitasking, 64 bit long mode (i know its 32bit), who cares, you need to show off the practical functions of your OS.

Wasn't worth even downloading.

No comment.

EDIT: Didn't have time to test when I posted, but I'll try it out in several emulators for you when I get home, and post my findings here .

Your floppy image managed to crash WinImage *again*

Um....as I said before, the program must be at fault, as it mounts fine on several other programs. It uses ext2, by the way.

Shell has same bugs, all the gravy.

Like....? The hi-res is optional now (in make config) and I fixed the backspace bug. What else?

How should I use the "make config" thing? Typing just "make config" does do nothing

This isn't to be typed in the OS, but this is part of the build system. The 'conf' program might only work on Linux though.

There seems no big difference between 0.02 and 0.01, the shell is the same version, etc.

See the changelog and my first post. The differences are not visual! If you think that visual changes cause different versions, then you have no ability to tell me that my kernel is crap, see below. And the shell is the same version because it will be until 0.1. I see no reason to change my simple shell that works for my current needs.

you need to show off the practical functions of your OS.

Thanks, sensei. [/sarcasm]

your kernel is a crap for now

Have you any basis at all for this? And yes, is yours any better?
I spent a lot of time on this, and.......thanks for the uplifting encouraging comment.

Wasn't worth even downloading.

Depends on your opinion. I love downloading OS's and testing them.

However, I do accept your criticism and will add more 'real' features in the future. I just don't see any reason to now.

Does anybody know why it might pagefault when Qemu gets unfocused and re-focused?

-JL

As you can see, I'm not the type who says all the time "oh yes really nice, good work". I'm being honest all the time and I like criticism on both sides .

pcmattman wrote:No visible difference, but I'd say there's a lot of changes behind the scenes.

That's right, but to make it at best, you need to show off everything your OS has. For example: let's say you have many GUI drawing functions, but you use only 1/4 of them... you got the point.

pcmattman wrote:Maybe try using something ELSE?

Hmm... If I wouldn't used something ELSE than WinImage, I couldn't get the kernel on the floppy. Pretty logical.

piranha wrote:If you think that visual changes cause different versions, then you have no ability to tell me that my kernel is crap, see below.

I'll not go searching through your kernel/OS source code just to see what is new. (Read above.) If you aim your kernel towards people who aren't experienced at it's platform (POSIX-like), they will just gaze at it with "wtf".

piranha wrote:Thanks, sensei.

I don't speak japanese.

piranha wrote:I love downloading OS's and testing them.

Well, me too, but I'm not a broken record saying "very good, good work" all the time. It's explained above.

JamesM wrote:If you've got nothing nice to say... GTFO.

[sarcasm] Ah, these darn acronyms! Who invented them? [/sarcasm]

Regards
inflater

Hi there!

You seem to be in need of some clarification. I'm happy to provide it.

inflater wrote:As you can see, I'm not the type who says all the time "oh yes really nice, good work". I'm being honest all the time and I like criticism on both sides .

pcmattman wrote:No visible difference, but I'd say there's a lot of changes behind the scenes.

That's right, but to make it at best, you need to show off everything your OS has. For example: let's say you have many GUI drawing functions, but you use only 1/4 of them... you got the point.

Who are you to lecture someone on how to "make it best [sic]"? Internal kernel changes are just as if not more interesting to most people [here] than eye candy. In the 4 months I've been working on Pedigree I could have hacked up an x86-only OS that runs a NASM and Bash. I didn't, because I enjoy designing the internals of kernels properly, and seeing everything come together. Never judge a book by its cover.

pcmattman wrote:Maybe try using something ELSE?

Hmm... If I wouldn't used something ELSE than WinImage, I couldn't get the kernel on the floppy. Pretty logical.

No, it's not logical at all. If you don't use any tool at all, you wouldn't be able to get your kernel on the floppy. If you use a different tool (as explicitly stated by the "Else"), you would.

How about something like mtools?

(HINT: If you don't like your "logic" being torn to shreds, don't try and logic troll.)

piranha wrote:If you think that visual changes cause different versions, then you have no ability to tell me that my kernel is crap, see below.

I'll not go searching through your kernel/OS source code just to see what is new. (Read above.) If you aim your kernel towards people who aren't experienced at it's platform (POSIX-like), they will just gaze at it with "wtf".

You do know what forum this is, right? It's not a forum for laymens, it's a forum for operating system developers. The fact that he released his alpha here and not, say for example slashdot or gamedev.net, should show to you that this release is NOT aimed at people who aren't experienced. What gave you that idea in the first place?

As for POSIX - his OS isn't particularly complex and there's hardly anything posix about it, apart from the naming of the directory listing command "ls" as opposed to "dir", there isn't much to distinguish it from DOS.

piranha wrote:Thanks, sensei.

I don't speak japanese.

Sensei = master. He was being sarcastic.

piranha wrote:I love downloading OS's and testing them.

Well, me too, but I'm not a broken record saying "very good, good work" all the time. It's explained above.

You don't have to be a broken record. What you do have to do is look at what work has taken place, not just a superficial glance before you bring out the beating stick.

JamesM wrote:If you've got nothing nice to say... GTFO.

[sarcasm] Ah, these darn acronyms! Who invented them? [/sarcasm]

Regards
inflater

It means "Get the f**k out". It applies well to you in this current situation - you're not usually a troll but you really have excelled yourself in this thread.

Cheers,

James

JamesM wrote:Internal kernel changes are just as if not more interesting to most people [here] than eye candy.

You got me wrong. I don't need no eye candy in hobby operating systems, it's just like this: you e.g. comment that your OS has routines and functions for multitasking, support for PAE, SSE2, GUI functions etc., but you don't use them. [It's just a example, I'm not quoting you.]

JamesM wrote:If you use a different tool (as explicitly stated by the "Else"), you would.

Again you got me wrong (or I'm writing wrong): WinImage did crash, but I've written the image using rawwritewin. This sentence:

me wrote:Your floppy image managed to crash WinImage *again*.

wasn't meant to be sarcastic, and yes, the smiley should be there.

JamesM wrote:but you really have excelled yourself in this thread.

Excelled myself? Pardon me? For saying my opinion I should be ashamed of excelling myself? IMHO LOL.

This is why you have excelled yourself:

Trollmeister general wrote: In other words, your kernel is a crap for now. Cool And you can have paging, multitasking, 64 bit long mode (i know its 32bit), who cares, you need to show off the practical functions of your OS.

And as to the "You misunderstood me" explanations - I'm not buying them. I read and write English to a high standard and there is only one interpretation of your comments as far as I can see.

Cheers,

James

JamesM wrote:This is why you have excelled yourself: /my quote/

So? His OS is a crap, is it wrong to say it?

JamesM wrote:I'm not buying them.

Could you restrain from using your flowers of speech?

So, please explain why it's crap?

-JL

inflater wrote:Could you restrain from using your flowers of speech?

English is a language full of a colloquial phrases/slang, you have no right to tell us to stop using them.