- combine the 'how to contribute' doc and the 'contributing to ports' doc.
- modernize the 'contributing to ports' doc
- use &os;
- prefer poudriere to tinderbox
Reviewed by: crees, bapt, mat
No objections from: bdrewery, gavin, wblock
- remove article about releng packages
- we no longer produce multi-cd releases
- CVS is not our VCS system
- we havn't releaseed with xfree86 is years
- section 1 about the 'ports cluster' is now entirely untrue and
been disclaimed by portmgr
Discussed with: peter, bdrewery, Daniel O'Connor
- references mostly outdated hardware
- doesn't use modern technologies (IPMI, nmdm, bhyve)
- the SUN hardware peculiarities are not useful anymore
- there are other better references on crimping custom serial cables
- MAKEDEV is no a thing anymore
there might be room for a modern version of this article in the handbook
but there is little that is salvageable from this article.
Discussed with: bcr, xmj, sbruno, cem
- using a custom gcc should be done within poudriere
- there is a framework for choosing a ports compiler anyways
- this article is incomplete w.r.t. modern gcc verisons
- encouraging people to add global options like `mssse3` is dangerous
- the original reason to use a custom gcc is gone (our old gcc was
outdated)
- comparing 'Linux' vs 'FreeBSD' is comparing apples and fruit: one is
just the kernel and the other is a specific distribution.
- the license 'debate' is well covered elsewhere
- it still references CVS
- comparing the development style of '300 committers' vs 'going through
the maintainer' is a straw man and doesn't reflect how Linux works (or
how BSD works)
- the supported platforms list is old and incorrect
- the "Extensible Frameworks" section belongs elsewhere
- the 'security' section is a feature list, not a comparison and is
missing important features
etc.
Discussed with: mjg
- it references sysinstall, which is gone
- the scripts used to install the system use pkg_add not pkg
- and are rotted in other ways
- the limitations of sysinstall have been somewhat mitigated by
bsdinstall (which can install into a new directory)
- it warns of outdated stuff (acroread8 doesn't exist anymore)
- package building takes place on runnning system and not on poudriere
- many of the packages referenced don't exist or are vastly changed
- it incorrectly installs the base system
- and more
Discussed with: jmg, Daniel O'Connor, bjk
- laptops do not come with PCMCIA anymore
- laptops don't come with modems anymore
- APM is dead
- ACPI power management is in the handbook
- pccard is dead
Discussed with: jmg
The article references a number of old aspects include, but not limited to pkg_*, incorrect package names on the CDROM, and books or links which no longer exist.
Finally, there is not much unique to MH on FreeBSD and we do not host tutorials for all software.
Discussed with: jmg
reasonable to maintain the reference, use the archived docs.
5-roadmap
checkpoint
dialup-firewall
diskless-x
euro
formatting-media
hats (content moved to htdocs/internal)
multi-os
storage-devices
vinum
zip-drive
All of these articles can be found here:
http://docs.freebsd.org/doc/9.0-RELEASE/usr/share/doc/freebsd/en_US.ISO8859-1/articles/
No objection from: doc@, www@
"Build Your Own FreeBSD update Server"
and attach it to the build.
A freebsd-update server allows a system administrator to update a number
of servers from a local mirror of the Project's update servers.
It also allows creation and fast distribution of local patches.
For additional information, contact Jason Helfman, the article's author.
PR: docs/139095
Submitted by: Jason Helfman <jhelfman@experts-exchange.com>
Earlier reviews: keramida, gabor, pgj, trhodes
Recent reviews: cperciva, ryusuke, gjb
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
I intend this article to be the first thing that new FreeBSD users
encounter when looking for information about mailing lists (i.e. I intend
to replace most links in our existing web pages to the 'How to get the
best results from freebsd-questions' article to this one instead; and
to have that article referenced from this one). That will happen shortly
(not yet).
Much of the text is indeed recycled from that article (thanks to Grog
for permission to do so), but some, including the bikeshed meta-info,
is my own. I have also generalized his article to apply to any mailing
list (not just FreeBSD-specific, although there is new text that touches
on that as well).
I have no doubt that there are rough edges in this article (both
stylistically and formatting). Please let me know. NB: it has
been tested locally with a make in the articles/ directory.
PR: docs/64934
Discussed with: ceri, grog, a few others.
this only affects the corresponding Japanese Makefile; all the others
either have already fixed this problem, or the entry is missing (not yet
translated).
PR: docs/64931
Approved by: ceri (mentor)
