Newsgroups: comp.unix.sysv386
Path: utzoo!utgpu!watserv1!watdragon!lion!azakinthinos
From: azakinthinos@lion.uwaterloo.ca (Aris Zakinthinos)
Subject: Re: WARNING : Deinstall in SCO UNIX DANGEROUS!
Message-ID: <1991Mar11.163159.14640@watdragon.waterloo.edu>
Sender: daemon@watdragon.waterloo.edu (Owner of Many System Processes)
Organization: University of Waterloo
References: <9113@lkbreth.foretune.co.jp> <357@n4hgf.Mt-Park.GA.US> <1991Mar10.174722.20568@NCoast.ORG>
Distribution: na
Date: Mon, 11 Mar 1991 16:31:59 GMT
Lines: 29

In article <1991Mar10.174722.20568@NCoast.ORG> allbery@ncoast.ORG (Brandon S. Allbery KB8JRR) writes:
>As quoted from <357@n4hgf.Mt-Park.GA.US> by wht@n4hgf.Mt-Park.GA.US (Warren Tucker):
>+---------------
>| In article <9113@lkbreth.foretune.co.jp> trebor@lkbreth.foretune.co.jp (Robert J Woodhead) writes:
>| >However, I did find it disturbing that doing a partial install of the
>| >SCO development system partially DEINSTALLS the extended utilties of the
>| >OS.  In order to get things to work, you must then re-install the utilities.
>| >
>| >Did anyone at SCO ever bother to test their install/deinstall scripts?
>| 
>| I haven't experienced the problems you discuss, but there are some
>| warnings in the release notes about certain deinstalls. None of them
>| spoke of /usr going away in toto.
>+---------------
>
>I did the same deinstall Robert spoke of (removing the DOS and OS/2 cross-
>development stuff) under 2.3.1 and /usr didn't vanish.  We'll see what happens
>when 2.3.2 gets here.  (I found out why it's taking so long, at least....)
>

A friend of mine did the same deinstall and everything seemed to work fine.
Then we did a fsck (we had some wired problems) and low and behold nearly
the whole #%$@&# file system was screwed.  I can't exactly blame the
deinstall but that was the only major thing that has happened to cause
any type of file system failure.

------------------------------------------------------------------------------
Aris Zakinthinos
uunet!watmath!lion!azakinthinos