Re: [tlug] Intro to Linux System Calls

[Godwin Stewart <gstewart@example.com>]

And Thus Spake Josh Glover <jmglov@example.com> (on Sun, 23 Feb 2003
09:10:08 -0500):

> *gulp* Hey, this page supposed to make my brain look big to people who
> don't understand Intel architecture! ;)

LOL :)

> I mean: "the system call software interrupt is thrown, and vectored
> through to the sys_call() handler by entry 0x80 in the IDT."
> 
> Is that a better way of putting it?

It's much more accurate from a technical point of view. If you want to leave
out the gory details of protected mode interrupt vectoring, you could just
say "the system call software interrupt number 0x80 is throuwn".

> Thanks, I will make that wording change. :)

Good :)

As a famous British leader said (tongue in cheek) a few decades ago:
"this is the kind of language up with which I shall not put!"

> Well, I hope to add to it. If you or anyone else feels like writing some
> high- quality stuff for the FAQ, I would love to include it. (And don't
> worry, I will give you credit and everything! ;)

How about outlining the differences between real mode and protected mode,
and then the differences between 286 PM and 386 PM so as to show up the huge
advantage of Linux over anything DOS-like? Furthermore, a good understanding
of PM and its priority levels will explain why you can't just dump userland
data into kernel space without taking a few detours.

-- 
G. Stewart   --   gstewart@example.com -- gstewart@example.com
Registered Linux user #284683

GnuPG key  : BA3D01C6 (pgp.mit.edu)
Fingerprint: C3DF C686 6572 6E59 E3E4  0F40 2B9A 2218 BA3D 01C6
---------------------------------------------------------------
Artificial intelligence is nothing compared to the
power of human idiocy.

Attachment: pgp00087.pgp
Description: PGP signature