OSDev.org

Sea kernel 0.01 is done!
http://code.google.com/p/seakernel/
[FLoppy] http://seakernel.googlecode.com/files/Sea0.01.img
[Source] http://seakernel.googlecode.com/files/seakernel.zip
It has:

• 1) Paging, MM
  2) Tasking
  3) INITRD and VFS support
  4) System calls, in channel 0x80
  5) Basic HD driver, floppy driver (untested)
  6) The basics of signaling
  7) Loadable modules
  8) Pipes.....?
  9) Userland! And loading programs
  10) Basic shell with commands '.ls', '.sync', and 'die'

Note: To run the commands, (except for 'die') you must add the '.' to the beginning.

To reconfigure it, run 'make config'
To compile and run in Qemu, type 'sh ./build'
See the readme for more info.

So.....test please...?

-JL

Great Job! I ran it in Qemu, it seemed very stable and the high-rez text mode is a nice touch. There were just two bugs that I noticed. The first is that you can backspace over the "Sea$" part in the shell. The second is that if I type "hello" for example, backspace over it, and type ".ls" (or any other valid command) it doesn't recognize that the command is valid.

Thanks.
Yeah, I noticed that too. Backspace-dealing-with will be implemented next version.

-JL

I tried typing .gr, which got me into a black screen with a green square, after which the system locked up.
.cd xxx works irrespectively of wether the directory exists. I got an empty directory listing, and the original after typing .cd ..
arrow buttons generate weird characters on the prompt.

and of course, the aforementioned backspace bug.

Other than that, it looks pretty good.

The reason why '.cd' does nothing is cause theres no cd program.
'.gr' was testing my graphics switching system call.
'.term' loads a simple module from the ramdisk.
If it starts with a '.' it's a separate binary.
The shell is also a separate binary.
EDIT: If a command doesn't work, try it again and type a little slower.
-JL

piranha wrote: EDIT: If a command doesn't work, try it again and type a little slower.

Sounds to me like your shell doesn't quite understand it's own language...

Yayyak wrote:

piranha wrote: EDIT: If a command doesn't work, try it again and type a little slower.

Sounds to me like your shell doesn't quite understand it's own language...

Oh, a funny guy!
My getch() function needs to be optimized.

-JL

- Trying to open the disk image results in winimage crash "abnormal program termination", writed with rawwritewin now.
- Ugly graphics mode. Eyes do hurt from such a small text.
- Floppy disk motor never stops.
- Where is the HELP command?... How should I know what parameters can be passed to your OS?

Summa summarum: a Linux "distro" programmed in a hurry

This isn't my Linux Distro, this is my kernel.
If the image won't open it's a bug in the program, as it opens/mounts fine on my computer.

-JL

Ran it once and the screen was all jumbled but the commands worked. Ran it a second time and the commands didn't work. I am using VPC2007 on Vista. Tried taking a screenie but windows is being odd for some reason.

The most recent thread for this OS is here.

But thanks, I'll look into that.
-JL