--- ag0ny <[EMAIL PROTECTED]> wrote:
> On Fri, 14 Jul 2000, �iogo Sperb Schneider wrote:
>
> How could you avoid programs to access memory areas
> that don't belong to
> them if your MMU is implemented in software? How
> could you stop user
> programs to overwrite the MMU code and make it work
> as the user want?
I thought the kernel used to control the
communication between software and hardware. It could
be implemented with semaphores.
> Low-level kernel routines, such as the MMU and
> low-level scheduler code is
> written in assembler, even in your beloved Linux.
Not according to the documentation. By now only LILO
still uses non-"C" code according to the docs.
> But that's not the
> problem, because most members of this list have
> mastered ASM programming
> in the MSX. The problem is that you can't do it in
> software.
Applications have access to what the kernel give
access to, thus, you get the picture.
=====
______________________________________________
�iogo Sperb Schneider - [EMAIL PROTECTED]
"When I say Van Halen I mean David Lee Roth!!"
@ http://www.geocities.com/enthusiast78
__________________________________________________
Do You Yahoo!?
Get Yahoo! Mail � Free email you can access from anywhere!
http://mail.yahoo.com/
****
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
****
