Page 1 of 1

yaOSp 0.0.1

Posted: Fri Jan 23, 2009 10:06 am
by giszo
Hi!

I'm proud to announce that the planned features for the first version of the OS I'm writing with one of my friends are complete and now I released the first version, 0.0.1. I'd appreciate if you could test it and some feedback would be welcome also. All you need is an emulator or a rewritable CD. You can grab the ISO file from here. Note that we can not take any responsibility for any possible damage caused when tested on a real machine.

A few word about the OS. You have only one option in GRUB, so it's not hard to decide which kernel to boot. After hitting enter in GRUB the kernel will start to boot. During boot you'll see scrolling lines on the screen and after a little time it will (hopefully) stop. If the text is not ended with a line starting with "Panic" than the system is usable. :) You have 6 virtual terminals to work on. In the first 5 terminals 1-1 instance of the yaosp shell is started and waiting for your commands. The last terminal is used to display the kernel log. You can switch easily between terminals with F1 .. F6 keys. It is also possible to scroll up/down the terminals with the Page Up and Page Down keys.

At the moment the OS has a very limited range of commands you can use in the shell. These are the following: cd, pwd, ls, cat, date, lspci, ps, stat, sysinfo.

The minimum system requirements are
  • Intel Pentium (or better) CPU
  • At least 8Mb of memory
  • PS/2 keyboard
  • CD-ROM drive
Good luck and thanks for testing it :)

giszo

Re: yaOSp 0.0.1

Posted: Fri Jan 23, 2009 10:58 am
by BacioiuC
Hey there giszo i just downloaded a copy and booted it up using VirtualBox but i cannot give you any feedback. Everything went great until it tried to execute shell #4. It did not "cough" up a panic anywhere. I wonder if this happened to others.
Good luck with your OS.

Re: yaOSp 0.0.1

Posted: Fri Jan 23, 2009 11:08 am
by giszo
BacioiuC wrote:Hey there giszo i just downloaded a copy and booted it up using VirtualBox but i cannot give you any feedback. Everything went great until it tried to execute shell #4. It did not "cough" up a panic anywhere. I wonder if this happened to others.
Good luck with your OS.
Was there any problem when it tried to execute shell #4 or the boot logs are just stopped then? If the second case happened you can switch to one of the shells by pressing F1, F2, ... F5 (depends on which shell you want).

Maybe this is a bit confusing that the kernel log is left there instead of switching to a terminal where you can use the shell.

Re: yaOSp 0.0.1

Posted: Fri Jan 23, 2009 11:17 am
by BacioiuC
TBH a screenshot can, hopefully, explain things better then i can(newb here):
Image

Re: yaOSp 0.0.1

Posted: Fri Jan 23, 2009 11:20 am
by giszo
BacioiuC wrote:TBH a screenshot can, hopefully, explain things better then i can(newb here):
Image
Did you try to switch to the first terminal by pressing F1?

Re: yaOSp 0.0.1

Posted: Fri Jan 23, 2009 11:24 am
by BacioiuC
Nop i didn't press anything. I was just waiting for it to finish booting so i can play around in it and give some feedback. And yes i tried it again, pressed f1 to f6 and nothing happened. Same line, same error.

Re: yaOSp 0.0.1

Posted: Fri Jan 23, 2009 11:27 am
by giszo
BacioiuC wrote:Nop i didn't press anything. I was just waiting for it to finish booting so i can play around in it and give some feedback. And yes i tried it again, pressed f1 to f6 and nothing happened. Same line, same error.
It's strange because it works fine for me under VirtualBox. :shock:

Re: yaOSp 0.0.1

Posted: Fri Jan 23, 2009 11:30 am
by clange
Hi giszo

I just tested briefly in Bochs and VMware server 1. This is my notes.

- A help command would be nice (and easy to implement)
- 'date' gives weird output in VMware (Thu Sunday -1828776841 08:22:10 1970, should be around Fri Jan 23 18:00:00 2009)
- when typing ahead the shell mixes its own output and echoing of input. I type 'cd dir [enter] ls' and the shell echoes 'ls' before printing the prompt and them immediately executes ls printing (argh, I attach a screen shot to show it instead :D ) This happened in Bochs - on real hardware it would probably not be noticable. Image

I could not crash your system (I only tried for a few minutes but there are not that many things to "attack" yet).

Good luck

clange

Re: yaOSp 0.0.1

Posted: Fri Jan 23, 2009 11:33 am
by clange
Just tested if it runs in my Virtual Box and it does. From the screen shot (from BacioiuC) it seems like all the shells has started - 0-4 => the 5 shells.

clange

Re: yaOSp 0.0.1

Posted: Fri Jan 23, 2009 11:37 am
by giszo
clange wrote:Hi giszo

I just tested briefly in Bochs and VMware server 1. This is my notes.

- A help command would be nice (and easy to implement)
- 'date' gives weird output in VMware (Thu Sunday -1828776841 08:22:10 1970, should be around Fri Jan 23 18:00:00 2009)
- when typing ahead the shell mixes its own output and echoing of input. I type 'cd dir [enter] ls' and the shell echoes 'ls' before printing the prompt and them immediately executes ls printing (argh, I attach a screen shot to show it instead :D ) This happened in Bochs - on real hardware it would probably not be noticable.

I could not crash your system (I only tried for a few minutes but there are not that many things to "attack" yet).

Good luck

clange
Thanks for your reply.

The help command is a good idea, it will be included in the next version.
The cd+ls+typing problem is a known problem/bug, so at least I know where to start fixing it ;)
The date issue is a bit strange, I tested the OS on a few emulators (Bochs, QEMU, VirtualBox and VMware workstation) and on a few real machines as well but never seen that kind of problem. I'll look into it, thanks for pointing it out! :)

Re: yaOSp 0.0.1

Posted: Fri Jan 23, 2009 11:53 am
by clange
I just tested the 'date' thing again. It didn't work - but after rebooting your OS it worked correct. I also tried to cross check it to see what date my own OS reports (and it is wrong in VMware but correct in Bochs !!!)

It is weird ;)

clange

Re: yaOSp 0.0.1

Posted: Fri Mar 06, 2009 12:36 pm
by csko
Half of the 64-bit integer was uninitialized and that caused this time handling problem, this is fixed in the next version, which we are releasing today.