- 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
ZFS chapter. Some ZFS terms were translated into german where appropriate,
but most of them (vdev, pool states and such) were left to make it easier
to relate to the ZFS outputs of FreeBSD.
Obtained from: The FreeBSD German Documentation Project
- 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)
- WITH_ and WITHOUT_ are outdated
- make.conf is the wrong place for modern systems (which should be using
poudriere)
- only reference package installation. Ports users can use the port name and
the normal ports documentation
The compiz fusion article previously duplicated portions of the handbook
in an effort to be complete. In addition, there was no reference from
the handbook so it was often forgotten.
By moving the article into the handbook, the article can be simplified,
text removed, and cross references can be added.
In addition, adding nice effects is a common enough task and isn't too
technical that it could be combined with the handbook.
As a part of the migration, reduce the focus on requiring an nVidia
driver.
There are a few places in the source tree where we list supported
architectures. Point people to a single place since we never remember
to update all the lists
version of PDF but would render more naturally when using Droid Sans
Fallback.
Note that we didn't used Noto Sans CJK because the current release
version of FOP does not support it well. We will need to revisit this
at a later time when FOP is updated.
- 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 seems unlikely that users new to FreeBSD will want to do any of
- use a floppy
- use DOS
and even using a tape drive and printing aren't common first tasks
remove this section
If I understand correctly the build broke because the non-english articles
import from the english version of fbsd-from-scratch.
Remove the translated articles for the articles I removed in English
- move perks into a question rather than its own section
- stop directing people to email me directly and instead direct people
to email the liasion alias
- 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
- use pkg instead of directly installing from ports
- reduce references to old versions of gcc, and make the article more
future-proof
- now that we either have a modern version of gcc or clang in base / as
the package building compiler, the impact of binary perf is no longer
relevant.
really, this article should either move into the handbook or be removed.
- remove mail-loopback question. The answer directly quotes the sendmail FAQ,
and we don't need to be a secondary source for one-of-many sendmail specific
questions.
