[src/netbsd-1-5]: src/sbin/newbtconf pull up rev 1.3:

[lukem <lukem%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/b0920ffc418d
branches:  netbsd-1-5
changeset: 489226:b0920ffc418d
user:      lukem <lukem%NetBSD.org@localhost>
date:      Wed Aug 23 12:39:43 2000 +0000

description:
pull up rev 1.3:
- add rc.conf.d to list of items to link
- update man page to reflect reality
- use mdoc macros correctly...

approved: thorpej

diffstat:

 sbin/newbtconf/newbtconf.8 |  139 +++++++++++++++++++++++++-------------------
 1 files changed, 79 insertions(+), 60 deletions(-)

diffs (265 lines):

diff -r b599c8a042aa -r b0920ffc418d sbin/newbtconf/newbtconf.8
--- a/sbin/newbtconf/newbtconf.8        Wed Aug 23 12:38:26 2000 +0000
+++ b/sbin/newbtconf/newbtconf.8        Wed Aug 23 12:39:43 2000 +0000
@@ -1,7 +1,6 @@
-.\"     $NetBSD: newbtconf.8,v 1.1.1.1 1999/10/05 11:22:43 darrenr Exp $
+.\"     $NetBSD: newbtconf.8,v 1.1.1.1.6.1 2000/08/23 12:39:43 lukem Exp $
 .\"
-.\" Copyright (c) 1999
-.\"     Darren Reed.  All rights reserved.
+.\" Copyright (c) 1999 Darren Reed.  All rights reserved.
 .\"
 .\" Redistribution and use in source and binary forms, with or without
 .\" modification, are permitted provided that the following conditions
@@ -27,8 +26,8 @@
 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 .\" SUCH DAMAGE.
 .\"
-.Dd October 3, 1999
-.Dt NEWBTCONF 1
+.Dd August 21, 2000
+.Dt NEWBTCONF 8
 .Os
 .Sh NAME
 .Nm newbtconf
@@ -43,39 +42,41 @@
 .Bl -tag -width indent
 .Nm
 is used to setup the system in such a way that the user is offered a
-selection of environments in which to boot the system up into.  The most
-obvious application being for laptops to provide a network and non-network
-environment after a successful boot into multi-user mode.
-.Ss BACKGROUND
+selection of environments in which to boot the system up into.
+The most obvious application being for laptops to provide a network
+and non-network environment after a successful boot into multi-user mode.
+.Ss Background
 .Pp
 In order to accomplish this task, the files usually associated with
 establishing the current system's running configuration are replaced with
 symbolic links which are adjusted with each boot to point to the appropriate
-file for the desired run-time environment.  This is accomplished by directing
-all of the symbolic links through a directory which itself is a symbolic
-link (
-.Pa /etc/etc.current
-), to the destination files.
+file for the desired run-time environment.
+This is accomplished by directing all of the symbolic links through a
+directory which itself is a symbolic link
+.Pa ( /etc/etc.current ) ,
+to the destination files.
 At each bootup, the selection made changes which directory
 .Pa /etc/etc.current
 points to.
 .Pp
-Though doing this and reloading
+Through doing this and reloading
 .Pa /etc/rc.conf
 in
 .Pa /etc/rc after
 the link has
 been established, the resulting run-time configuration is effectively
-controlled without the need to directly edit any files.  The default boot-up
-environment is selected by manually directing which configuration directory
+controlled without the need to directly edit any files.
+The default boot-up environment is selected by manually directing which
+configuration directory
 .Pa /etc/etc.default
-points to.  As opposed to
+points to.
+As opposed to
 .Pa /etc/etc.current
 (which is updated
 with every boot),
 .Pa /etc/etc.default
 is not automatically updated.
-.Ss GETTING STARTED
+.Ss Getting Started
 .Pp
 By default, NetBSD only has one boot-up configuration - that set in the
 file
@@ -83,32 +84,37 @@
 In order to initialize the system for operating in a
 manner which supports multiple boot configurations,
 .Nm
-must be run with the
-.B init
-option.  This will create two symbolic
+must be run with an argument of
+.Sq init .
+This will create two symbolic
 .Pa /etc/etc.current
 and
 .Pa /etc/etc.default 
 to the directory
-.Pa "/etc/etc.network".
+.Pa /etc/etc.network .
 The following files are all moved into
 that directory and symbolic links put in their place, in /etc, pointing to
-.Pa /etc/etc.current/<filename>
-:
-.Bd -literal
+.Pa /etc/etc.current/<filename> :
+.Bd -literal -offset indent
+/etc/defaultdomain
 /etc/fstab
-/etc/rc.conf
+/etc/ifconfig.*
+/etc/inetd.conf
 /etc/mrouted.conf
-/etc/resolv.conf
+/etc/mygate
+/etc/myname
+/etc/netstart
+/etc/nsswitch.conf
 /etc/ntp.conf
-/etc/ifconfig.*
-/etc/nsswitch.conf
 /etc/rbootd.conf
-/etc/inetd.conf
+/etc/rc.conf
+/etc/rc.conf.d
+/etc/resolv.conf
 .Ed
 .Pp
 To test that this has been performed correctly, reboot your system into
-NetBSD.  After the kernel has autoconfigured and tty flags have been set,
+NetBSD.
+After the kernel has autoconfigured and tty flags have been set,
 a prompt should appear, preceeded by the following like, looking like this:
 .Bd -literal
 [network]
@@ -116,33 +122,37 @@
 .Ed
 .Pp
 The []'s are used to indicate the default configuration, which can be
-selected by just pressing return.  If there were other configurations
-available at this stage, you would have 30 seconds to enter that name
-and press return.
-.Ss MUTILPLE CONFIGURATIONS
+selected by just pressing return.
+If there were other configurations available at this stage, you would
+have 30 seconds to enter that name and press
+.Sy RETURN .
+.Ss Multiple Configurations
 .Pp
 Once an initial configuration has been setup, we can proceed to setup further
-run time environments.  This is done by invoking
+run time environments.
+This is done by invoking
 .Nm
-with the name of the new configuration to be created.  By default, this step
+with the name of the new configuration to be created.
+By default, this step
 will use the current configuration files as the basis for this setup unless
 a second parameter is given - that of the configuration to use as the basis
-for the new one.  Upon completion, a new directory, /etc/etc.<newname>, will
-have been created, priming the directory with the appropriate files for
-editting.  For example, if we do
+for the new one.
+Upon completion, a new directory, /etc/etc.<newname>, will have been
+created, priming the directory with the appropriate files for editing.
+For example, if we do
 .Nm
 \fInonet\fP \fInetwork\fP it would create a directory named /etc/etc.nonet
 and copy all the files from
 .Pa /etc/etc.network
-into that directory.  Upon
-rebooting, we should see:
+into that directory.
+Upon rebooting, we should see:
 .Bd -literal
 [network] nonet
 Which configuration [network] ?
 .Ed
 .Pp
 To setup the system for booting into the "nonet" configuration, the files
-in /etc/etc.nonet need be editted.
+in /etc/etc.nonet need be edited.
 .Pp
 If you wanted to make "nonet" the default configuration when booting, you
 would need delete the symbolic link
@@ -155,41 +165,48 @@
 network [nonet]
 Which configuration [nonet] ?
 .Ed
-.Ss NO NETWORK
+.Ss No Network
 Assuming that we performed the above command successfully, in order to
 successfully configure NetBSD to not configure interfaces (or generate no
 errors from attempting to do so), the following settings (at least) should
 be used in
-.Pa "/etc/etc.nonet/rc.conf" :
+.Pa /etc/etc.nonet/rc.conf :
 .Bd -literal
 auto_ifconfig=NO
 net_interfaces=NO
 .Ed
 .Pp
 Of course other networking services, such as NTP, routed, etc, are all
-expected to be "NO".  In general, the only settings which should be "YES"
-are syslogd and update, with perhaps cron (if your cron scripts don't
-need the network) and screenblank/wscons (if applicable).  Other actions
-such as deleting any NFS mounts from
+expected to be "NO".
+In general, the only settings which should be "YES" are syslogd and
+update, with perhaps cron (if your cron scripts don't need the network)
+and screenblank/wscons (if applicable).
+Other actions such as deleting any NFS mounts from
 .Pa /etc/etc.nonet/fstab
 would also need to be undertaken.
 .El
 .Sh FILES
 .Bl -tag -width /etc/mrouted.current -compact
 .It Pa /etc/etc.current
-Symbolic link to current config dir.
+Symbolic link to current config directory.
 .It Pa /etc/etc.default
-Symbolic link to default config dir.
-.It Pa /etc/fstab
+Symbolic link to default config directory.
+.Pp
+.It Pa /etc/defaultdomain
 These files all become symbolic links.
+.It Pa /etc/fstab
 .It Pa /etc/ifconfig.*
-.It Pa /etc/rc.conf
+.It Pa /etc/inetd.conf
 .It Pa /etc/mrouted.conf
-.It Pa /etc/resolv.conf
+.It Pa /etc/mygate
+.It Pa /etc/myname
+.It Pa /etc/netstart
+.It Pa /etc/nsswitch.conf
 .It Pa /etc/ntp.conf
 .It Pa /etc/rbootd.conf
-.It Pa /etc/ntp.conf
-.It Pa /etc/inetd.conf
+.It Pa /etc/rc.conf
+.It Pa /etc/rc.conf.d
+.It Pa /etc/resolv.conf
 .El
 .Sh SEE ALSO
 .Xr rc.conf 8 ,
@@ -197,7 +214,8 @@
 .Sh HISTORY
 The
 .Nm
-program first appeared in NetBSD-current, October 1999.
+program first appeared in
+.Nx 1.5 .
 .Sh BUGS
 .Pp
 It presently does not display a count down timer whilst waiting for input
@@ -205,8 +223,9 @@
 is first pressed.
 .Pp
 The management of the overall collection of multiple configurations is much
-more manual than it ought to be.  A general system configuration tool needs
-to be written to ease their management.
+more manual than it ought to be.
+A general system configuration tool needs to be written to ease their
+management.
 .Sh AUTHORS
 This shell script was written by Darren Reed <darrenr%netbsd.org@localhost> with
 initial input from Matthew Green <mrg%netbsd.org@localhost> on how to approach this