|
|
comp.os.minix |
I don't like the chmem mechanism of Minix. Processes should start with If your OS is message based I would like to have arbitrarily large PS: I am very interested in this OS. I have already thought of writing j...@cs.HUT.FI (Jyrki Kuoppala) writes: On a lower level:
>In article <1991Aug25.205708.9...@klaava.Helsinki.FI>, torvalds@klaava (Linus Benedict Torvalds) writes:
>>This implies that I'll get something practical within a few months, and
>>I'd like to know what features most people would want. Any suggestions
>>are welcome, but I won't promise I'll implement them :-)
>As for the features; well, pseudo ttys, BSD sockets, user-mode
>filesystems (so I can say cat /dev/tcp/kruuna.helsinki.fi/finger),
>window size in the tty structure, system calls capable of supporting
>POSIX.1. Oh, and bsd-style long file names.
a minimal size and grow as they need to until they run out of RAM or
disk space. Paging to disk would be nice, too.
messages. They could be implemented efficiently by mapping the pages
into the receivers address space (or just passing a pointer on 68k
systems without MMU). Oh, yes, and the addressing scheme for messages
should be different than in Minix. Messages should not be sent to
process slot numbers, but to ports. That way, user processes can use
messages, too, and it is easier to add your own servers.
my own OS, but decided I wouldn't have the time to write everything from
scratch. But I guess I could find the time to help raising a baby
OS :-)
--
| _ | Peter J. Holzer | Think of it |
| |_|_) | Technical University Vienna | as evolution |
| | | | Dept. for Real-Time Systems | in action! |
| __/ | h...@vmars.tuwien.ac.at | Tony Rand |