- Reemphasise the need of full source set for 'make buildkernel'
PR: docs/75864 (inspired by)
Submitted by: Eli K. Breen <eli@gopostal.ca>
Approved by: keramida (mentor)
- Clarify that /stand does not exists in 6.0 and later, it is present on
all 5.X installation CDs (including 5.4)
PR: docs/84730 (inspired by)
Submitted by: Jimmie James <jimmiejaz@to2600.org>
Approved by: keramida (mentor)
Right For You."
This article attempts to provide an introduction to such concepts
as Releases, Branches, and STABLE vs. CURRENT, which are currently
scattered around between the FAQ, various Release Engineering documents,
and folklore on the mailing lists.
The material in the FAQ should probably be deleted and this used as
its replacement. This material does not replace any of the Release
Engineering documentation, but it does attempt to discuss how the
concepts discussed in great detail therein should influence user
decisions on which version to install. In particular, this article
attempts to inform users about the current thinking of the development
team in terms of how future releases are going to be done.
A companion article comparing e.g. 5.X vs 6.X would be useful but is
outside the scope of this commit.
This article is partially a response to the "Quality of FreeBSD" thread
on freebsd-stable in July 2005 (and its many antecedents).
Submitted for review to: core, re, secteam
Reviewed by: imp, wes, remko, simon, and others
credential argument to dev_clone event handler. Requires minor tweaks
to kernel modules that use devfs cloning in order to accept the new
argument (don't need to use it in most cases).
the mailing-lists.ent file (though it's not really an mailinglist).
Also replace the current follow up addresses by it's entity name.
Submitted by: ceri
- We currently state "Install the net/cvsup port"; let's point directly
to the package, in particular cvsup-without-gui since all commands, in
the text, used the legacy "-g"...
- Most of people do not edit the ports-supfile and directly use the -h
argument for the CVSup server, the reader should uses/knows that.
- Keep, as note, the ports-supfile edition for a "hardcoded" CVSup
server
- I kept the odd <link linkend/<xref linkend way, maybe this should be
fixed
The text should, now, be closer to what we do when it's time to CVSup
the Ports tree.
- eliminate single use of term "rcNG"
- change chapter name to mention FreeBSD 5.X and newer, not just 5.X
- kill <indexterm> rcNG
- kill mention of 5.X at the end of the chapter, it's not just 5.X
Approved by: keramida (mentor)
easiest way to start GNOME.
- Fix a few small grammar errors in the GNOME section and adds a few
small clarity tweaks.
Submitted by: adamw
PR: docs/84713
* This chapter claims to be about striping, but talks about
disk concatenation in some paragraphs. Remove all references to
concatenation, add a brief paragraph explaining what striping is and
why it provides superior I/O performance through parallel I/O to
multiple disks simultaneously.
* Do not alternate between calling striping raid0 and raid1.
Consistently refer to it as raid0, as raid1 is mirroring.
* Cleanup / reorganize the example set of commands for creating a
stripe of two ATA disks. Wrap it in a DocBook <procedure> tag with
individual <steps> to provide a title for this procedure and make the
numbered steps very clear to follow without confusing verbiage and
side tangents adding confusion.
* Expand 'redundant array of inexpensive disks' in <acronym> tag for
mouseover on first use of HTML output.
* Remove some poorly worded, confusing, and contradictory sentences
and paragraphs.
