Yesterday I thought "why arent there any Unices written in ASM?" - then I set off to put an int 0x80 into MenuetOS. MeOS apps could act as terminals and drivers - perhaps an X server could even live inside a MeOS window
I wrote a simple handler that told the user it was called via the message board, then made a reference to it in sys_int and wrote a little app that did int 0x80 a few times. It compiled but the only relevant debug board output told me "K : Process - forced terminate...".
Is there anything obvious I forgot to do, or is it more likely a screwup in my code?

PS: my int 80 stuff will pro'ly act like the FreeBSD syscalls. If I get anywhere I might switch to Linux or some other system compatibility depending on the results of the poll.

Hi,

I chose 'other', because i wish MenuetOS as Linux's de facto standard GUI.

x11/x* is user mode device driver.

Edit: BTW, if you still want something unixy, then see here.
http://minnie.tuhs.org/UnixTree/
http://www.cs.bell-labs.com/who/dmr/
(debian:~# sr google bell dmr)

--
PS: reason is simple,
c/asm > 1 (natural)

asm/c < 1 (unnaturalness)

For the time-being I have given up on the int 80 thing. Instead I'm making a Unix-ish API that is all filesystem based and lives in int 40. If the poll gets lotsa votes I might have a go though.

PS: My API will implement a VFS layer and slight microkernel-ness into MenuetOS. All i/o will be via the VFS layer. Apps can be killed by cd-ing to /modules and removing the app (eg: "rm systree.03" for the 4th instance of systree). I'm not sure if it is something that will be of any use added into the main distro, but hopefully it will be of some use to someone.

That old Unix link is gold! I'm gonna show off some of that 1972 Unix code to my CS teacher