OSDev.org

My (old) screenshots are up on my project's sourceforge page: http://sourceforge.net/projects/mattise...

There really isn't all that much that has changed (apart from fixing stuff) since they were taken so they remain.

Here is a pic of my SecOS
JouleOS is retired due to all of the design problems it has with multitasking
and well, I just lost intrest in the rewrite of it

Actually, my OS just got a new feature, so I guess it's worth posting a new screenshot. Yes, you can actually read that device from a normal program.

Don't pay attention to the inode numbers. They are internal, and the only useful thing a userspace program can expect to do with them is compare "device+inode" pair between different files to see if they are the same or different. My "minicmd" program prints them simply because I needed the info for debuggin at some point...

mystran wrote:

inflater wrote: It is not a fake, by the way

Can we have the floppy image?

You don't seem to read my whole message though:

Well, THIS is expected at PortixOS 0.5 or 0.6:

Stay tuned for version 0.5 !
(Latest version: 0.4 pre-II, next version: 0.4 full)

inflater

MessiahAndrw wrote:This thread should be a sticky we can constantly add to.

Well I might as well joing the uber-fun. I'd really like to post my screenshot of Bash running on my OS, but I lost it and it doesn't run atm (writing my ATA and EXT2 drivers is taking a while, and I decided to totally rewrite my entire syscall and IPC interface and as you know it takes a lot longer to rework an interface than a module...)

Right then here we go

Jimix after boot, running my super-mini shell. keys F1-F4 change tty from tty1-tty3,/dev/console. All of this is running in user mode by the way - four processes running: /init, /udev, /tty, /shell.



The boot sequence into tty mode is currently far too fast for me to screenshot so I stuck it in serial mode (default kernel output is directed to a serial port instead of the monitor) and put it in debug mode (There are three levels, debug, verbose and spam). Debug mode is essentially an strace.



OK, then we have JTED (Jimix test execution daemon), my automated testing software. It's still in development and can currently run automated builds and (just about) train tests interactively. It's what I use to exorcise (deliberate spelling) the evil web-dev in me!

Home page:


A listing of all the builds/tests in one 'batch run'. The 'auxiliary builds' are programs that tests may use but don't live in the source tree, such as memory consistency checkers or the all-important 'hello world' app.


Finally an in-depth view of a build, to show it actually does stuff


If you're wondering what the 'speaker' in shiny colours is there for - each batch is assigned not only an ID but a random word as well - helps with remembering which one's which. I learned that trick from my work

Sorry for spamming with images...

Sorry for spamming? That's exactly what this thread is for.

Not that interesting features yet. Rather just detection at the moment.
I'm trying to boot the second cpu but it crashes(both qemu and my laptop) when I try to do so

Wow some really nice OS , I like them all but bontanu thats a really good gui you have

Well, here's what mine used to look like, before I started again from scratch in C++:


The current version just prints a few lines of text at the moment. But it does have a really nice boot splash:


-Stephen

Mmm, a bit late to join in but oh well!



That's the latest screenshot of my OS showing off the filesystem code (with RamFS as the root filesystem) and some other stuff like uname.

There's some older screenies here, too: http://exclaim.tuxtalk.org/?q=screenshots

My OS with multitasking
the Unknown command line is it's attempt to run a program that grub loaded as a module the 'a' is the output from a successful program.

Hi,

Here's some pictures of my current code - it's just boot code at the moment (rewriting).

The first picture is BCOS booting directly from ROM in Bochs:



I like seeing RAM from 0x000C0000 to 0x007FFFFF


The second picture is BCOS booting on a real machine (via. network). This was done as a headless boot, with the OS's output captured by a terminal emulator running on Windows:




Cheers,

Brendan

Brendan wrote: The second picture is BCOS booting on a real machine (via. network). This was done as a headless boot, with the OS's output captured by a terminal emulator running on Windows:

Why no colors in this one? TeraTerm can do vt100 just fine.

Hooray! people are posting screenshots again... lol..

Some really cool additions, really nice!