...or whatever release number I'm on. I should really keep track more. Okay, from now on, I will keep track of the release numbers! Hey everyone. I'm releasing another version of my OS (this will be the third rewrite, which I started working on in December of 2009). I'm pretty sure I released an alpha version of this OS about a year ago, but much has changed since then, and with this being version 0.1, I figure that I should put up a hd image for people to try it out. I already have a large list of things I want to fix/rewrite in the code (a lot of that is usermode stuff), but I wanted to upload an image to find more bugs so that I go into version 0.2 with a good list of things to fix.
The big things: It is self-hosting! Well, sortof. I managed to compile, assemble, and link my OS inside itself, take the self-compiled kernel file, and boot it up with no problems that I can see. It has a port of the coreutils and binutile programs, so thats pretty standard. It has a port of GCC that seems to work (though its quite slow). It has a semi-working port of bash. It has a working port of python, though it doesn't have many modules installed. It has a port of e2fsprogs (so you can run fsck on the filesystem! Woo!). The kernel is a hybrid modular kernel. The drivers are: iso9660, ata+atapi, ext2, floppy, keyboard, loop devices, pci.
I have my own set of programs, such as the program to control services (bring). Kinda a weird name, I know, but I named it that so I could type "bring loop up" and that means to start the loop devices service. Theres user management and partition management (though these not well tested and isn't complete): "sparta" and "modusers". And some others...to find lists of programs, try "ls /bin /usr/bin /usr/sbin". Other programs to try: bcache (try 'sudo bcache -d -c /dev/hda1'. This will remove all caching on that device. Neat, huh? You can put it back with 'sudo bcache -c rw /dev/hda1'), lspci, lsmod, bring -l, explode (which forks 100 times and starts a small schell script for each process), die (which forks a bunch and runs explode in each process), d2 (which runs explode a bunch), and bomb (which executes a fork bomb), fsckroot -f (a wrapper program I made that fscks the root device), and 'gcc t.c -o t.o'. Also, you could check out "fortune", though be warned...some of that is nsfw.
There are two bootable images in the archive: hd.img and cd.iso. They are separate. The cd image is made to test the OS on real hardware, and has very few features or programs (beyond ls and cat). It boots to a simple shell ("??? (/)$ ") is about what is should look like. Don't report bugs from this image, unless the OS crashes or does something weird. The hd image has all the features and programs. Please read the known_bugs file before reporting any bugs. To log in, try using "bob" as the username (it has no password) or "god" (who's password is "dog"). To shut down, run "shutdown". To log out, use "exit".
Here's the link: http://microsea.googlecode.com/files/seaos01.zip
At the GRUB screen for the hd image, choose the first option. The install program doesn't work. Also, it does cache writes, so don't just close the emulator - use shutdown, or it might corrupt the filesystem. Also, to switch terminals, use ctrl+<term number>. 1-7 are login shells, 8 is a system monitor, 9 is a debug output.
I'm sure I'm forgetting something. I'll update the post if I think of something. I still really wanna call it a beta because I'm sure theres so many bugs, but whatever, I'll dive deep in to the realm of full releases.
Many thanks to all who have assisted.
-JL
SeaOS 0.1 Release + Test Request
- piranha
- Member
- Posts: 1391
- Joined: Thu Dec 21, 2006 7:42 pm
- Location: Unknown. Momentum is pretty certain, however.
- Contact:
SeaOS 0.1 Release + Test Request
SeaOS: Adding VT-x, networking, and ARM support
dbittman on IRC, @danielbittman on twitter
https://dbittman.github.io
dbittman on IRC, @danielbittman on twitter
https://dbittman.github.io
Re: SeaOS 0.1 Release + Test Request
Hi,
I've attached a image - which seemed really weird to me. I tried logging in as 'god', however it didn't work the first time. As far as I remember, I didn't type any special characters. Later trials could not reproduce the original problem, and further more, even with special characters, it works.
Other than that,
Regards,
Shikhin
I've attached a image - which seemed really weird to me. I tried logging in as 'god', however it didn't work the first time. As far as I remember, I didn't type any special characters. Later trials could not reproduce the original problem, and further more, even with special characters, it works.
Other than that,
piranha wrote: explode
Regards,
Shikhin
Re: SeaOS 0.1 Release + Test Request
Did you mistakenly append a 'space'?Shikhin wrote:I tried logging in as 'god', however it didn't work the first time. As far as I remember, I didn't type any special characters. Later trials could not reproduce the original problem, and further more, even with special characters, it works.
(That can sometimes surprise you when you are unaware. It's not even obvious)
Programming is not about using a language to solve a problem, it's about using logic to find a solution !
Re: SeaOS 0.1 Release + Test Request
Hi,
Regards,
Shikhin
As I said, I don't remember pressing anything. But on the other hand, I'm quite busy preparing for tomorrows exam, so I may have appended a 'space'. Now that you mention it, it could be a possibility.Chandra wrote:Did you mistakenly append a 'space'?
Regards,
Shikhin
- piranha
- Member
- Posts: 1391
- Joined: Thu Dec 21, 2006 7:42 pm
- Location: Unknown. Momentum is pretty certain, however.
- Contact:
Re: SeaOS 0.1 Release + Test Request
I couldn't reproduce it, but yeah you probably hit a key at some point. Theres nothing in there that clears the input buffer, so what you type is what you get.
Edit: I called the command explode cause when I ran it, it used to make the OS crash violently (like, several hundred #PF and then triple fault)
-JL
Edit: I called the command explode cause when I ran it, it used to make the OS crash violently (like, several hundred #PF and then triple fault)
-JL
SeaOS: Adding VT-x, networking, and ARM support
dbittman on IRC, @danielbittman on twitter
https://dbittman.github.io
dbittman on IRC, @danielbittman on twitter
https://dbittman.github.io
Re: SeaOS 0.1 Release + Test Request
/me is having several troubles with the keyboard.piranha wrote:I couldn't reproduce it, but yeah you probably hit a key at some point. Theres nothing in there that clears the input buffer, so what you type is what you get.
Edit: I called the command explode cause when I ran it, it used to make the OS crash violently (like, several hundred #PF and then triple fault)
-JL
Like, when I press certain keys in a certain order, the problem occurs (weird new line with weird characters, etc). Perhaps it is counted as 'unstable bash support' - so I didn't bother showing the screenshots. If it is not counted as 'unstable bash support', then I will be happy to help (tomorrow, going to sleep now).
Regards,
Shikhin
Re: SeaOS 0.1 Release + Test Request
very cool! works well, and "echoes" ..... and your sig, obviously a floyd fan
rock on, my friend. rock on.
rock on, my friend. rock on.
- Combuster
- Member
- Posts: 9301
- Joined: Wed Oct 18, 2006 3:45 am
- Libera.chat IRC: [com]buster
- Location: On the balcony, where I can actually keep 1½m distance
- Contact:
Re: SeaOS 0.1 Release + Test Request
You don't happen to have a floppy image for real hardware testing?
- piranha
- Member
- Posts: 1391
- Joined: Thu Dec 21, 2006 7:42 pm
- Location: Unknown. Momentum is pretty certain, however.
- Contact:
Re: SeaOS 0.1 Release + Test Request
I do actually, but its a little older. However, it should work. This is even less featured than the CD image, I think the only external command you can run on the floppy is "./test". It should boot to a command prompt like the CD version.
Link: http://microsea.googlecode.com/files/bootfloppy.img
-JL
Link: http://microsea.googlecode.com/files/bootfloppy.img
-JL
SeaOS: Adding VT-x, networking, and ARM support
dbittman on IRC, @danielbittman on twitter
https://dbittman.github.io
dbittman on IRC, @danielbittman on twitter
https://dbittman.github.io