From owner-freebsd-questions Sun Jun 13 1:47: 9 1999 Delivered-To: freebsd-questions@freebsd.org Received: from syrex.acenet.co.za (earth.acenet.co.za [196.25.170.15]) by hub.freebsd.org (Postfix) with ESMTP id 111C714DC5 for ; Sun, 13 Jun 1999 01:46:59 -0700 (PDT) (envelope-from w1@syrex.cc) Received: from europa.pcb.co.za (syrex.acenet.co.za [196.25.170.15]) by syrex.acenet.co.za (8.8.7/8.8.7) with SMTP id KAA29502 for ; Sun, 13 Jun 1999 10:52:55 +0200 Message-Id: <199906130852.KAA29502@syrex.acenet.co.za> To: freebsd-questions@freebsd.org From: w1@syrex.cc Subject: Memory and Addressing Protection Date: Sun, 13 Jun 99 08:52:56 +0000 X-Mailer: Syrex Intranets Webmail v2.0 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi there, Sorry to bug you, I'm sure you have much better things to do than to answer questions like this, but I would really appreciate any help you can offer. I write a technical e-zine that focuses largely on security in computing issues. Over the past two issues I have described how memory protection worked in primitive Operating Systems, like MS-DOS and Multics. I have covered the use of fence registers, bounds registers, segmentation, paging, and paging on top of segmentation. I would like to move on to how memory protection in more advanced and modern Operating Systems works and, amongst others, how FreeBSD Memory Protection works. My CD-ROM Drive is broken, and as a result, I can't get FreeBSD source onto my home PC to analyze it. :( Could you please give me a technical overview of how FreeBSD Memory Protection works? If you're busy, you can delay answering this message for a few weeks, but I would appreciate a reply some time this month if at all possible. Thanks a Lot, Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message