first defined in ${SGMLROOT}/html/catalog and ${SGML_ROOT}/iso8879/catalog.
By setting the SGML_CATALOG_FILES in the order suggested until now, we end
up with a value of SGML_CATALOG_FILES like (wrapped to keep the length of
the lines reasonable):
/usr/doc/en_US.ISO8859-1/share/sgml/catalog:/usr/doc/share/sgml/catalog:\
/usr/local/share/sgml/docbook/4.1/catalog:/usr/local/share/sgml/html/catalog:\
/usr/local/share/sgml/iso8879/catalog:/usr/local/share/sgml/jade/catalog
This means that when `dbcent.mod' refers to entities like %ISOamsa; they
are not known already (because they are defined in catalog files later in
the search path, not loaded by nsgmls yet). This results in errors like:
nsgmls:/usr/local/share/sgml/docbook/4.1/dbcent.mod:54:0:E: \
cannot open "/usr/local/share/sgml/docbook/4.1/iso-amsa.gml" \
(No such file or directory)
By rearranging the order of the catalog files a bit, we can convince nsgmls
to load the `html' and `iso8879' public entities first, and make it
possible to use nsgmls to validate DocBook SGML documents too (instead of
HTML only).
PR: docs/48980
Submitted by: Martin Karlsson <mk-freebsd@bredband.net>
at this time there is no loader.conf variable in defaults/loader.conf in 6,
note that.
Remove some old cruft and reword near sentence to keep flow going smoothly.
Two spaces between the end of a sentence and the beginning of a new sentence.
PR: 86733
Submitted by: Josh Paetzel (patch rewritten by me)
Using utilities like k5init is no longer required, that naming convention was
dropped in 5.X.
Remove some 4.X-5.X warning cruft.
Effectively closes PR: 34401 and 97409 (literally built world to investigate)
adjust tunnel settings without specifying the interface
first.
PR: docs/105000
Submitted by: dawnshade <h-k at mail dot ru>
Pointyhat: remko (me, previous commit was my mistake).
stronger, as suggested by dougb@, but do so in the right context.
I.e., don't fire all the requirements at once in the last section,
but tell each of them where the current topic is most appropriate.
Polish some wording and markup.
${name}, PROVIDE, and rc.conf var prefix.
- Distinguish flags from options when telling why -foo
doesn't belong in $command_args. ${name}_flags can
contain both dashed options and arguments, so saying
"flags" when I mean options was confusing.
Suggested by: dougb
- Be more concise and clear on the requirement of /bin/sh;
the former details weren't really interesting.
- Link to the rc.d section of Porter's Handbook.
- Mention /etc/network.subr.
Suggested by: dougb
* Replace first Windows occurence with trademarked entity
* Add trademark info for Microsoft Windows and Symantec Ghost.
* Replace "FreeBSD" with &os; and "ports collection" with &ports;,
to keep the capitalization consistent. Also introduce an &os.ports;
entity, which expands to "FreeBSD Ports Collection", to uniformly
refer to the Ports
* Add <emphasis>, <application> and <quote> tags here and there
* Use manpage entities, instead of <literal> for FreeBSD
command-line utility references
* Various minor grammar and syntax nits
'need' twice in the same sentence.
o Replace <literal> tags with <emphasis> for `tag', `port' and
`package' (they are really used as FreeBSD-specific terms, not as
<literal> text here).
o Expand a paragraph with inline URIs, which result in pretty awkward
line breaks in PDF/PS output, to a <variablelist>. This separates
the URIs from the running text, and looks slightly prettier in print
output.
Xorg is the default X server since 5.3 and there is always
docs.freebsd.org available for users who are interested in
configuration of XFree86
Approved by: keramida (mentor), trhodes (mentor)
