Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!spool.mu.edu!mips!wrdis01!gatech!prism!dali.cc.gatech.edu!ken
From: ken@dali.cc.gatech.edu (Ken Seefried iii)
Newsgroups: comp.unix.aux
Subject: Re: 2.0.1 update error
Message-ID: <27487@hydra.gatech.EDU>
Date: 27 Apr 91 07:34:24 GMT
References: <1991Apr19.191312.3785@athena.mit.edu> <1991Apr24.053159.27641@panix.uucp> <27342@hydra.gatech.EDU> <-2.++F-@smurf.sub.org>
Sender: news@prism.gatech.EDU
Reply-To: ken@dali.gatech.edu (Ken Seefried iii)
Organization: The House Of Fun
Lines: 27

In article <-2.++F-@smurf.sub.org> urlichs@smurf.sub.org (Matthias Urlichs) writes:
>
>I don't know the reason for making open demand-paged programs (and shared
>libraries) a special case where the usual Unix semantics suddenly don't
>apply, but it seems to me that it can't possibly be a very good one.

I agree with you 100%, it's not the best way to do things.  However,
it's the way it's done, and it's documented.  Bitching because it
doesn't work the way you *want* it to, as opposed to the way it really
is, is not an excuse for botching an upgrade.

>As for installing on top of a running system: Not everybody has enough free
>space (remember sash doesn't have compress, and I don't think pipes work).
>Myself, I had to pull the upgrade from another machine via NFS for exactly
>this reason. Sash can't do that either.

True, space can be a problem.   I just uncompressed the file under
older A/UX and split inc.cpio into smaller pieces for machine that had
very small root partitions.

Sorry...I'm not a super-genius, and doing this upgrade just wasn't
that hard.  On machines with root disks ranging from 86MB to 330MB.

--

	ken seefried iii	"I'll have what the gentleman 
	ken@dali.cc.gatech.edu	 on the floor is having..."