use this.
Requested by: max, andreas
Note: This change just provides a convenient way to exercise existing
functionality. Whether `kern.securelevel' is effective in increasing
system security is another issue, and one that has been well thrashed
out in the lists.
hard coded into too many things), it's not nice to go and change /home/src
etc. This means they will be created if missing (so it shouldn't break
the releases), but won't touch them once they are changed.
Move a.out libraries to /usr/lib/aout to make space for ELF libs.
Make rtld usr /usr/lib/aout as default library path.
Make ldconfig reject /usr/lib as an a.out library path.
Fix various Makefiles for LIBDIR!=/usr/lib breakage.
This will after a make world & reboot give a system that no
longer uses /usr/lib/*, infact one could remove all the old
libraries there, they are not used anymore.
We are getting close to an ELF make world, but I'll let this
all settle for a week or two...
1646 (radacct), but RFC's 2138 and 2139 define new ports
for RADIUS and RADIUS accounting, namely 1812 and 1813
respectively. FreeBSD 2.2.6 uses the old radacct port, but
the new radius port, which is a bit silly.
PR: 6712
Reviewed by: phk
Submitted by: Nick Hilliard <nick@foobar.org>
almost certainly have to change as the FreeBSD/Alpha kernel comes
along, but for the transitionary period this is the most correct.
Obtained from: NetBSD
against the "master map" to get the list of mount point/amd map
correspondences, and using that list as command-line arguments to start
amd.
When I tried to do this with the existing /etc/rc* scripts, I found that
I couldn't do this by modifying only /etc/rc.conf: that file gets
sourced very early by /etc/rc, well before any networking functionality
is present, let alone NIS. Further, I wasn't able to figure out a way
to use various levels & types of quoting to defer evaluation of the
string to a point subsequent to NIS initialization.
As a result, I resorted to hacking /etc/rc.network -- but I did it in a
way that ought to be reasonably general, and avoid breakage for anyone
else.
PR: 6387
Reviewed by: phk
Submitted by: David Wolfskill <dhw@whistle.com>
allowed external hosts to send packets to the 127.0.0.0/8 subnet on the
firewall host.
Renumber the lo0 rules to guarantee they appear first.
PR: 6406
Submitted by: Archie Cobbs <archie@whistle.com>
as the initial generic hostname if the user didn't setup any NIC, but
failure to resolve this name results in XF86Setup not being able to
run.
Reported by: Lutz Zienert <luzi@interface-business.de>