Subject: install/14130: install - local path checking
To: None <gnats-bugs@gnats.netbsd.org>
From: None <claude.marinier@dreo.dnd.ca>
List: netbsd-bugs
Date: 10/02/2001 12:15:28
>Number:         14130
>Category:       install
>Synopsis:       install fails on invalid local path
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    install-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Oct 02 09:16:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Claude Marinier
>Release:        NetBSD 1.5.2
>Organization:
Claude Marinier, Information Technology Group    claude.marinier@dreo.dnd.ca 
Defence Research Establishment Ottawa (DREO)    (613) 998-4901  FAX 998-2675
3701 Carling Avenue, Ottawa, Ontario  K1A 0Z4         http://www.dreo.dnd.ca
>Environment:

System: System: NetBSD leviathan 1.5.2 NetBSD 1.5.2 (DREO) #0: Thu Jan 18 15:26:11 EST 2001 marinier@leviathan:/usr/src/sys/arch/i386/compile/DREO i386

System Installation script from the boot1.fs and boot2.fs floppy disks.

>Description:

During an upgrade from NetBSD 1.5 to 1.5.2, I incorrectly specified the path
to the sets. I left out the initial slash in the path to the local directory,
as follows.

	mnt/usr/NetBSD.152

This passed the check (if any) but the pax command failed miserably and
sysinst did not offer any means of correcting the path. The installation
aborted.

This problem is serious because the upgrade fails and recovery is non-trivial.
It has a low priority because most of us will type the path correctly.

>How-To-Repeat:

I did not attempt to repeat this since I was eager to finish the upgrade
and return to system to service. I expect that it will behave the same way
when presented with the same knid of error in the path.

>Fix:

I suspect that the check is checked in a context that allows succesful access
to the files (i.e. from root) and that the actual usage by pax is done in a
different context (some place other than root).

The fix I used was to type the path correctly. The problem is that it took
some effort to recover from the failed upgrade.

>Release-Note:
>Audit-Trail:
>Unformatted: