than we had before in the configuration chapter. It describes how
the system logger can be configured, the rationale behind it and
the most important field that the user should edit.
PR: docs/168305
Submitted by: Niclas Zeising (zeising daemonic se)
Reviewed by: wblock@, myself
the current state of how the things are done
- add a new paragraph covering the fact that rc.conf is read by sh(1)
PR: docs/157894
Reviewed by: gavin, simon, Niclas Zeising
More specifically:
- mentions of old versions of FreeBSD in historical context are left in tact
- remove section about KerberosIV
- remove section about SAP R/3
- remove mentions of XFree86
- only support gvinum
- update examples to 7.X or 8.X
- remove Alpha support
- add COMPAT_FREEBSD[67] kernel options
- csup(1) now only in the base system
- update (tty) device names, add warnings for 7.X
- remove MD5 from the port checksum algorithms
- update port versions (probably not all)
- add definitions for ctm-src[5-8] to mailing-lists.ent
Reviewed by: bcr, joel, remko, simon
section. We don't want any new examples of these kinds of scripts.
While I'm here, tune up the example rc.d script a bit, and tweak the text
in that section a bit for readability.
explain why `/var' or `/var/tmp' may needs a lot of disk space, and
tune the description of `/usr' to remove an instance of ``Both of
which'' that seemed to be dangling from nowhere in particular.
and unsupported 6.x releases. Tom started this process a while ago
and I'll follow up on that for the latest EoL round.
The old versions can still be found in the doc archives:
http://docs.freebsd.org/doc/
more clear that it is *required* for startup scripts. An rc.d script
without a PROVIDE keyword is not run by our rc.subr (it is skipped by
the find_local_scripts_new() shell function of rc.subr).
Inspired by: A post by Helmut Schneider, jumper99 at gmx.de,
on news:comp.unix.bsd.freebsd.misc
Message-Id: 63aggbF26iusnU1@mid.individual.net
As Alexander Leidinger has pointed out:
"glibc behaves differently based upon the value of it. It may refuse to
do anything if it doesn't understand the value. Changing the value of
osrelease is only advised in experimental situations (like in
http://wiki.freebsd.org/linux-kernel) and may result even in kernel
panics."
I've replaced a reference to `compat.linux.osrelease' with a safer
example, for setting `security.bsd.see_other_uids=0', which we already
use as a sample /etc/sysctl.conf entry anyway.
* Reword the paragraph before a set of tunables for Linux, as
it wasa bit confusing.
* Correct the name of 'kern.maxfiles' (it was 'kern.maxfile')
before, and reword the text around it to remove the need for
a possessive "'s", which would look funny after 'maxfiles'.
* Finish properly a sentence which was missing a fullstop.
Submitted by: ganbold &at; micom ˙ mng ˙ net
- Mention /boot/loader.conf when we talk about modules;
- The NDIS driver part does not belong to wireless devices section since
it can be used for other Ethernet device, so move that part to its own
section in the network device configuration page. I also updated the
previous text to match 5.5, 6.X and 7.X
Based on docs/84961 (submitted by Fredrik Lindberg
<fli+freebsd@shapeshifter.se>), docs/97229 (submitted by Gavin
Atkinson <gavin@mod3.co.uk>) and many other requests/remarks.
o Remove 4.X information, this includes notes and sections.
o Update documentation to reflect 5.X and 6.X.
o In some areas, try to make the new content version agnostic.
o Skip areas stating "5.[0-5] and later" as it's relevant - we
need a better way to handle these.
For several items, I checked the NOTES files, manual pages,
CVS history, etc.
Discussed on: -doc
A few ideas from: remko
