Return to BSD News archive
Newsgroups: comp.unix.bsd
Path: sserve!manuel.anu.edu.au!munnari.oz.au!metro!socs.uts.edu.au!syzygy!raz
From: raz@socs.uts.edu.au (The Inimitable Raz)
Subject: Re: [386bsd] cp something to /bin/cp and cp core dumps; bug or feature?
Message-ID: <raz.724317502@syzygy>
Sender: news@socs.uts.edu.au
Organization: Computing Sciences, Uni of Technology, Sydney.
References: <Byn6uL.2oM@ra.nrl.navy.mil> <1992Dec2.185331.57@unislc.uucp> <1fjcsuINN2vf@hrd769.brooks.af.mil> <VIXIE.92Dec5145556@cognition.pa.dec.com>
Date: 14 Dec 92 07:18:22 GMT
Lines: 21
vixie@pa.dec.com (Paul A Vixie) writes:
>Paged "Virtual Memory", as BSD implements it, means that programs are
>brought into memory in itty bitty pieces called "pages", and various
>lies are told that make the program believe that its text and its data
>and its stack are all contiguous in memory even though most of it could
>be missing and what's there could be in random order in the real RAM.
[Excellent description of paged virtal memory deleted.]
As I understood it however, writing to an executable was supported by
virtue of unlinking it FIRST, thus leaving it floating in limbo till
the process(es) using the pages were terminated. Is this not the case?
--
Bye for now.
- Raz
raz@socs.uts.edu.au (Roland Turner) (OH) 61 2 319 5700