>Number:         4634
>Category:       bin
>Synopsis:       config gives EEXIST instead of EPERM
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    bin-bug-people (Utility Bug People)
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Wed Dec  3 22:20:12 1997
>Last-Modified:
>Originator:     
>Organization:
	
>Release:        1.3_ALPHA
>Environment:
	
System: NetBSD rfhpc8135 1.3_ALPHA NetBSD 1.3_ALPHA (RFHPC8135) #1: Thu Nov 27 08:37:09 MET 1997 feyrer@rfhpc8135:/tmp_mnt/jabberwocky/usr/cvs/src/sys/arch/i386/compile/RFHPC8135 i386


>Description:

config gives a confusing error message, when it doesn't have permission
to write to the .../compile/FOO directory:

rfhpc8135% config RFHPC8135 
config: symlink(machine -> ../../../../arch/i386/include): File exists
config: symlink(i386 -> machine): File exists

Problem here is, ../../compile/RFHPC8135 (and it's contents) are owned by root
from a previous build, and this it can't write the new files (as normal
user).

Instead of giving the above error, it would be ok to just say it can't 
(first) unlink the old symlink, and it would be quite clear (to me)
what's going on.


>How-To-Repeat:
	make a GENERIC kernel as root
	log in as normal user
	cd .../conf
	config GENERIC
	experience the above error and wonder if config's broken or something

>Fix:
	Unknown.
>Audit-Trail:
>Unformatted: