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
source of information regarding logging TCP packets, and it already
points to that manual page
PR: docs/144881
Submitted by: Glen Barber <glen.j.barber@gmail.com>
was modified because handbook descriptions regarding FreeBSD 5.X and 6.X
are not mainstream anymore. Fix this by collapsing the list into a single
sentence.
Discussed with: jkois (mentor)
Approved by: jkois (mentor)
PR: docs/141042
Submitted by: Glen Barber (glen dot j dot barber at gmail dot com)
- Give specific clear examples on how to load the pf module and the pflog module.
- Remove some information that is stated in the section right above.
- Update the doc to reflect that pflog is now its own module. [1]
PR: 140896 [1]
This is a rather lengthy patch, that attempts to fix several problems:
- Reduce repetition. There are several paragraphs in the original text that are repeated throughout the sections
- Markup fixes. Replace single quotes with <literal> tags, add <acronym>s and several other changes to improve markup consistency
- Convert to passive voice where possible, eliminate few first person references
- Several grammar and language fixes
- The original text implied that the same TCP packet would go back and forth between source and destination. Rephrase relevant paragraphs to clarify these are different packets
- Includes many fixes submitted in a PR [1] and a link fix submitted on -doc [2]
- Numerous other smaller changes, too many to mention here
PR: docs/131568 [1]
Submitted by: Chris Pepper <pepper@cbio.mskcc.org> [1]
Submitted by: Phillip Nordwall <Phillip.Nordwall@wwu.edu> [2]
Reviewed by: trhodes, keramida
use. Mention the changed location of a configuration file in 7.0.
PR: docs/122351, docs/121321 (related)
Submitted by: John Ferrell <jdferrell3@yahoo.com>
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/
could find) so remove it from the information, give an example on how
such a setup can be achieved.
PR: docs/113464
Submitted by: Josh Paetzel <josh at tcbug dot org>
Inspired by: Marc Silver <marcs at draenor dot org> (slightly rewritten
by me).
Left as 0/32, it would only redirect Very Weird Packets(tm), while
as 0.0.0.0/0 it will indeed process all the traffic as intended.
Submitted by: "Michael P. Soulier" <msoulier@digitaltorque.ca>
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
- Add general info about enabling PF and creating rulsets.
PR: docs/92113
Submitted by: Daniel Gerzo <danger at rulez dot sk>
Reviewed by: simon@ and ceri@
Approved by: ceri@
be any content changes involved in this commit, however, localization
teams are encouraged to catch up with this change.
Requested by: intron at intron ac
Reviewed by: Niclas Zeising <lothrandil at n00b apagnu se>
Glanced by: simon
configure the system via rc.conf. This avoids to repeat things and
allows the reader to complete the natd(8) configuration.
Based on PR: docs/81199
Submitted by: Rong-En Fan <rafan@infor.org>
- Use firewall package instead of firewall software application.
- Do not say non-stateful firewall's are "legacy" since they still
make sense in some cases.
- Move paragraph about /etc/rc.firewall to the ipfw section and don't
say it's outdates, just simple. [1]
Inspired by: den [1]
