On Fri, 14 Jul 2000 18:08:41 -0700 (PDT), "ğiogo" Sperb Schneider wrote:
> I thought the kernel used to control the
>communication between software and hardware. It could
>be implemented with semaphores.
Well, if you think on "write on memory" as a task that
the program needs to ask the Kernel to do, yes, it's possible,
but I think it will have the slowest system of all time... (-:
Besides, it'll be almost impossible to program ... (-: Several
reasons.
> Not according to the documentation. By now only LILO
>still uses non-"C" code according to the docs.
If the docs say that, the docs are wrong. Lots of the Kernel
code is ASM code... simply there is no other way to do a lot
of things.
> Applications have access to what the kernel give
>access to, thus, you get the picture.
You are missing the fact MEMORY doesn't work
like a normal peripheral. Once a program runs,
it can replace the interrupt routine and "oh,
goodbye my multitask"... or even worse, the
program can overwrite some piece of the kernel
and "damn it!", the system hangs.
Did you ever programmed using ASM "language"?
----- AbraçOS/2, Daniel Caetano ([EMAIL PROTECTED])
/| | | |\
\| ___ |/ OS/2 Sites: http://www.quasarbbs.com/daniel/
\/ ----- \/
http://www.geocities.com/SiliconValley/8752/os2hp/os2index.html
| | MSX Sites: http://www.fudeba.cjb.net/
-- -- Drawings: http://www.djgallery.tsx.org/
...Programar e' a arte de organizar zeros e uns de forma que eles produzam trabalho
util!
****
MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED]
and put "unsubscribe msx [EMAIL PROTECTED]" (without the quotes) in
the body (not the subject) of the message.
Problems? contact [EMAIL PROTECTED]
More information on MSX can be found in the following places:
The MSX faq: http://www.faq.msxnet.org/
The MSX newsgroup: comp.sys.msx
The MSX IRC channel: #MSX on Undernet
****
