Subject: install/12769: clarify the upgrade notes for when the sets are on /usr
To: None <gnats-bugs@gnats.netbsd.org>
From: None <smb@research.att.com>
List: netbsd-bugs
Date: 04/27/2001 17:33:05
>Number:         12769
>Category:       install
>Synopsis:       clarify the upgrade notes for when the sets are on /usr
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    install-manager
>State:          open
>Class:          doc-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Apr 27 14:33:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Steven M. Bellovin
>Release:        1.5.1 beta
>Organization:
AT&T Labs Research
>Environment:
	
System: NetBSD berkshire.research.att.com 1.5.1_BETA NetBSD 1.5.1_BETA (BERKSHIRE) #0: Fri Apr 20 09:18:32 EDT 2001 smb@berkshire.research.att.com:/usr/src/sys/arch/i386/compile/BERKSHIRE i386


>Description:
	The documentation is sorely lacking on how to specify the
	path to a directory containing the upgrade sets, if they reside
	on what was (and will be) /usr.  Is /usr mounted or unmounted?
	If mounted, under what name?  I suggest giving a simple example,
	with actual before/after path names.  (I suspect that the same
	might be true of /, since during the upgrade you're running
	from a ramdisk.)

	It would be a good idea, while you're at it, to fix sysinst
	to back out /etc versus /etc.old when the user requests an abort
	during an upgrade.  I had to do that manually, after each of the
	many failed tries.

>How-To-Repeat:
	Try to upgrade a machine with the binary sets on the /usr partition...
>Fix:
	I never did figure it out -- I simply untarred the sets by
	hand, taking special care with etc.  But I'm extremely
	experienced as a Unix user/administrator, and reasonably
	familiar with NetBSD.
>Release-Note:
>Audit-Trail:
>Unformatted: