Re: What does your OS look like? (Screen Shots..)
Posted: Sun Aug 04, 2013 1:11 am
Took me a while, but I finally have a semi-working bash:
https://github.com/dbittman/seakernel
-JL
OSDev.org
The Place to Start for Operating System Developers
http://f.osdev.org/
What does your OS look like? (Screen Shots..)
Page 96 of 262
Re: What does your OS look like? (Screen Shots..)
Posted: Mon Aug 05, 2013 8:43 pm
Been making some major progress on my kernel in the past few months! x86_64 kernel (also 32bit, so yay multiplatform [sorta]), 64 bit modules, 64 bit user-space executables, SMP... Today was the first time I was able to load up a 64 bit program and have it not segfault. Hey, even nano and gcc work in 64 bit mode!
https://github.com/dbittman/seakernel
-JL
https://github.com/dbittman/seakernel
-JL
Re: What does your OS look like? (Screen Shots..)
Posted: Wed Aug 07, 2013 2:48 pm
Here is my "window" manager - I'm avoiding the desktop metaphor, instead I'm going for an Emacs approach. I'm aiming for a highly-productive system that wastes no screen space.
The screen is made up of frames. Each frame in a non-overlapping area of the screen that shows a 'buffer'. Frames can be recursively split horizontally or vertically, and can be resized arbitrarily by dragging the borders with the mouse.
Buffers are surfaces that a process can draw to. A process may have several buffers. You can choose which buffer is shown in which frame.
Buffers are exposed to an emulated (not a true hardware accelerated) OpenGL ES 2.0 context - so far, performance is wonderful (the CPU is not as weak as many people believe). As an optimisation, full screen buffers bypass the composting, and render directly to the screen.
Working with OpenGL ES 2.0 is pretty nasty if all you want to do is text rendering or add some buttons, so I am going to develop a simple GUI API on top of it.
For example purposes, I'm just filling in the buffers with solid colours:
The code for the program that draws this is:
Notice the BufferTypes.GL - at some point in the future, I may add a BufferTypes.Pixel that allows you to draw per-pixel instead of creating an OpenGL context.
I have done much more complicated rendering, which I will present after I have worked on finalising the process architecture.
The screen is made up of frames. Each frame in a non-overlapping area of the screen that shows a 'buffer'. Frames can be recursively split horizontally or vertically, and can be resized arbitrarily by dragging the borders with the mouse.
Buffers are surfaces that a process can draw to. A process may have several buffers. You can choose which buffer is shown in which frame.
Buffers are exposed to an emulated (not a true hardware accelerated) OpenGL ES 2.0 context - so far, performance is wonderful (the CPU is not as weak as many people believe). As an optimisation, full screen buffers bypass the composting, and render directly to the screen.
Working with OpenGL ES 2.0 is pretty nasty if all you want to do is text rendering or add some buttons, so I am going to develop a simple GUI API on top of it.
For example purposes, I'm just filling in the buffers with solid colours:
- shovel1.jpg (7.55 KiB) Viewed 7807 times
Code: Select all
function main(param)
local buffer = Buffer.create("Test Buffer", BufferTypes.GL);
buffer.onDraw = function ()
-- clear buffer to yellow
GL.glClearColor(1.0, 1.0, 0.0, 1.0);
GL.glClear(gl.GL_COLOR_BUFFER_BIT);
end;
end
I have done much more complicated rendering, which I will present after I have worked on finalising the process architecture.
Re: What does your OS look like? (Screen Shots..)
Posted: Thu Aug 08, 2013 9:47 pm
Oh! That looks fantastic -- what's that font you're using?klange wrote:Took me a while, but I finally have a semi-working bash:
Re: What does your OS look like? (Screen Shots..)
Posted: Thu Aug 08, 2013 9:57 pm
Terminal font is Deja Vu Sans Mono, interface font is Deja Vu Sans / Deja Vu Sans Bold.requimrar wrote:Oh! That looks fantastic -- what's that font you're using?
Re: What does your OS look like? (Screen Shots..)
Posted: Thu Aug 15, 2013 1:12 pm
BareMetal OS supports VESA modes now.
Re: What does your OS look like? (Screen Shots..)
Posted: Sun Aug 18, 2013 10:03 pm
In the last few days I've finally managed to teach my kernel how to run it's first userspace process:
The last line is printed by a syscall called from userspace. I know, it's not very impressive, but I'm very proud I got it to work. But now I have to get back to debugging my kernel because there's an easy way to crash it: Just let it start a userspace program that is bigger than one page.
The last line is printed by a syscall called from userspace. I know, it's not very impressive, but I'm very proud I got it to work. But now I have to get back to debugging my kernel because there's an easy way to crash it: Just let it start a userspace program that is bigger than one page.
Re: What does your OS look like? (Screen Shots..)
Posted: Tue Aug 20, 2013 3:04 am
Hello 
here are some recent screenshots of my hobby OS, Quafios.
Hope you like it
here are some recent screenshots of my hobby OS, Quafios.- Quafios boot screen:
- Interactive Quafios
:
- The text editor:
- Blue screen of death
(credit: inspired by skelix):
Hope you like it
Re: What does your OS look like? (Screen Shots..)
Posted: Tue Aug 20, 2013 11:34 pm
”とある”見ました。君は日本人ですか。私いまは日本語を勉強しますよ。klange wrote:
Re: What does your OS look like? (Screen Shots..)
Posted: Thu Aug 22, 2013 12:29 am
僕は日本人じゃないけど、日本で大学へ通いました。nbdd0121 wrote:”とある”見ました。君は日本人ですか。私いまは日本語を勉強しますよ。
Re: What does your OS look like? (Screen Shots..)
Posted: Thu Aug 22, 2013 3:40 am
i just put some video on youtube (i hope it's ok to post videos) i can't do screenshot in text mode anyway
http://www.youtube.com/watch?v=YyAy187LAFc <= boot from floppy in text mode
http://www.youtube.com/watch?v=aY-wofkzWrY <= boot from cd rom in graphic mode
the image to boot from floppy and cdrom are identical, they both use usb tablet or joystick or mouse or any hid device as input for the cursor, there can be two cursor at once because there is one for each type, so can have one cursor for the joystick and one for the mouse
http://www.youtube.com/watch?v=YyAy187LAFc <= boot from floppy in text mode
http://www.youtube.com/watch?v=aY-wofkzWrY <= boot from cd rom in graphic mode
the image to boot from floppy and cdrom are identical, they both use usb tablet or joystick or mouse or any hid device as input for the cursor, there can be two cursor at once because there is one for each type, so can have one cursor for the joystick and one for the mouse
Re: What does your OS look like? (Screen Shots..)
Posted: Mon Aug 26, 2013 2:35 pm
A small screenshot of my OS.
The program to left is a monitor program which communicates to the OS in order to obtain data about the operating system. To the right is Putty which communicates in a normal command console fashion.
HelloWorld in this case was made to crash deliberately in order to show a program crash.
EDIT: now I see that something is wrong with the register dump as the values makes no sense, got to investigate.
The program to left is a monitor program which communicates to the OS in order to obtain data about the operating system. To the right is Putty which communicates in a normal command console fashion.
HelloWorld in this case was made to crash deliberately in order to show a program crash.
EDIT: now I see that something is wrong with the register dump as the values makes no sense, got to investigate.
Kolibrios once again
Posted: Mon Sep 02, 2013 1:43 pm
Worked on KolibriOS's console today, nyan cat telnet looks pretty good now, hooray!
Re: What does your OS look like? (Screen Shots..)
Posted: Mon Sep 09, 2013 6:49 am
I drew a triangle using brasenham's algorithm and SSE in vesa
Re: What does your OS look like? (Screen Shots..)
Posted: Thu Sep 12, 2013 6:53 am
https://www.youtube.com/watch?v=GKRjEm63DVg
Old work. Using ASM could be messy, so I now hardly could understand my own coding. That's why I'm now rewriting all my codes but well organized and exhaustively commented. When I rewrite that specific piece code, the user interface could look different.
Old work. Using ASM could be messy, so I now hardly could understand my own coding. That's why I'm now rewriting all my codes but well organized and exhaustively commented. When I rewrite that specific piece code, the user interface could look different.