in FreeBSD and should never have got in here.
Removed hard-coded /etc/rc.local.d hacks and implemented a more flexible
solution.
Added a local configuration area to sysconfig.
Add nis_ypsetflags sysconfig entry and appropriate code in rc to call
ypset if needed. Should probably automatically add `-ypsetme' to ypbind
flags if this is set.
Add comment that you should not have to edit netstart, and if you
do we would like to know about it.
The lo0 interface is now handled just like any other interface,
This makes it possible to do things to it from sysconfig.
Redo the comments in sysconfig about network_interfaces and ifconfig_${X}
to reflect the moving of lo0 to this scheme. We now have an uncommented
variable for sysintall to find and play with. (Your welcome Jordan)
Redo the way static routes are handled. Basically use the same
scheme for routes that I did for network interfaces. This allows
any number of static routes to be added from sysconfig.
Make sure we do the default route first so we stand a chance of
getting to our DNS server (if we have one) to resolve our own
IP address from $hostname.
Have netstart directly source sysconfig so that it stands on its own.
Do not source netstart in rc, run it with sh.
Rework the dangerous /etc/hostname.* so that it uses a variable with
a list of interfaces and a variable for each interface in that list.
The files /etc/hostname.* become obsolete with this change, the
information is now stored in /etc/sysconfig.
Source any /etc/start_if.${ifn} files so they can export things to
netstart (plans for future enhancements in this area.)
Obsolete /etc/defaultrouter, this is now down with $defaultrouter from
sysconfig.
1. Move all system configuration variables into /etc/sysconfig
2. Adapt other files to use it.
3. Add a host of new variables for micro-managing your system in various
ways. For 2.1, /etc/sysconfig will be machine-edited so that the user
doesn't even have to care at all about the various funny names we picked.
4. Enable dset. We won't get it debugged if we never use it, and no one
has said anything negative about it yet, so here goes!
5. Try to use one consistent style throughout.
