>Number:         13061
>Category:       bin
>Synopsis:       newbtconf munges rbootd.conf?
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    bin-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon May 28 17:58:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     matthew green
>Release:        <NetBSD-current source date>today
>Organization:
people's front against (bozotic) www (softwar foundation)
>Environment:
	
System: NetBSD fish-dances.eterna.com.au 1.5U NetBSD 1.5U (_fish_) #72: Thu Apr 26 17:45:38 EST 2001 mrg@fish-dances.eterna.com.au:/var/_fish_ i386
Architecture: i386
Machine: i386
>Description:

	newbtconf(8) tells me that:


     The following files are all moved into that directory and symbolic links
     put in their place, in /etc, pointing to /etc/etc.current/<filename>:

           /etc/defaultdomain
           /etc/fstab
           /etc/ifconfig.*
           /etc/inetd.conf
           /etc/mrouted.conf
           /etc/mygate
           /etc/myname
           /etc/netstart
           /etc/nsswitch.conf
           /etc/ntp.conf
           /etc/rbootd.conf
           /etc/rc.conf
           /etc/rc.conf.d
           /etc/resolv.conf

why is rbootd.conf part of this?  (i also notice that rc.local.conf is not
listed above.)  rbootd is a server config file for netbooting HP machines,
and isn't typically going to be run elsewise like this.  (one could argue
it should be handled, but if so, nearly every .conf file in /etc should be.)

>How-To-Repeat:
	
	ponder about this newbtconf thing, read the man page.
>Fix:
	not given.
>Release-Note:
>Audit-Trail:
>Unformatted: