Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!agate.berkeley.edu!cgd
From: cgd@eden.CS.Berkeley.EDU (Chris G. Demetriou)
Newsgroups: comp.os.386bsd.development
Subject: Re: File Truncation Philosophy
Date: 2 Apr 93 02:04:13
Organization: Kernel Hackers 'r' Us
Lines: 24
Message-ID: <CGD.93Apr2020413@eden.CS.Berkeley.EDU>
References: <C4tJ6C.C17@ns1.nodak.edu> <CGD.93Apr1173018@eden.CS.Berkeley.EDU>
<C4u8y2.HCM@ns1.nodak.edu> <CGD.93Apr1204906@eden.CS.Berkeley.EDU>
<1993Apr2.072443.790@cm.cf.ac.uk>
NNTP-Posting-Host: eden.cs.berkeley.edu
In-reply-to: paul@isl.cf.ac.uk's message of 2 Apr 93 07:24:42 GMT
In article <1993Apr2.072443.790@cm.cf.ac.uk> paul@isl.cf.ac.uk (Paul) writes:
=>What about users moving their own binaries around. If cp et al don't
=>work properly then aren't users (including root) just as likely to bring
=>the system down when they overwrite running binaries.
not the system, just the copied-over process will die...
=>We're not just talking about installation and init updates. You can't
=>expect novice users to know that they shouldn't copy foo.new to foo
=>while they're running foo.
if they do it, then their foo will die, and that's it.
it's the `init' updates that will kill the system...
(init will crash and die, then 386bsd panics with "init died".)
chris
--
Chris G. Demetriou cgd@cs.berkeley.edu
"386bsd as depth first search: whenever you go to fix something you
find that 3 more things are actually broken." -- Adam Glass