>Number:         29064
>Category:       install
>Synopsis:       CD package install damages installed OS
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    install-manager
>State:          open
>Class:          doc-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Jan 24 18:29:00 +0000 2005
>Originator:     Robert Skegg
>Release:        2.0
>Organization:
>Environment:
n/a
>Description:
Your documentation (lack of) and naming conventions on CD iso files is confusing! Here's what happened to me: I have a new i386 machine I put NetBSD 1.6 on, then found that package dependencies were so broken that I could not install most anything else. I asked around about that problem and was advised to move on to 2.0. So I got the two 2.0 iso files, made CDs and ran i386cd, update existing OS. This worked fine. I got a working 2.0 system, user accounts intact, X11 still worked ok. Then I tried to install the packages from the i386pkg CD. I selected obvious install packages all - I have a modern machine, lots of HD space, and having the packages to hand should make build faster than ftp. HOWEVER this was a disaster! It appears that this process also over-writes existing good configured OS files with default ones! I am left with a machine that will boot to single user only, and a big puzzle as to what files have been messed-up by this process. I do NOT expect an install pack
 ages option to damage an existing good OS!  I expect it to put the packages in /usr/pkgsrc/...  Period.
>How-To-Repeat:
Simply insert the i386pkg CD and select install packages.

>Fix:
Repair: Dont know - still scratching head about what got damaged.. probably have to recover stuff from /var/backups/... but I'm not sure if that will fix everything.

Fix: Change the sysinstall menu  on the i386pkg CD to say either:

Install packages (kills OS!!!!)

or take out ALL the stuff that damages the OS, and simply install the packages.  Tell the user to use the i386cd to install/update the os.