Merged changes between LINUXDOC_2_DOCBOOK_2 and LINUXDOC_2_DOCBOOK_3

from doc/handbook.

File                 From  ->  To      Merged to files...
---------------------------------------------------------------
anoncvs.sgml         1.1   ->  1.2     cutting-edge/chapter.sgml
authors.sgml         1.128 ->  1.135   authors.ent
bibliography.sgml    1.37  ->  1.38    bibliography/chapter.sgml
contrib.sgml         1.329 ->  1.338   staff/chapter.sgml
current.sgml         1.24  ->  1.25    cutting-edge/chapter.sgml
cvsup.sgml           1.40  ->  1.41    cutting-edge/chapter.sgml
eresources.sgml      1.51  ->  1.53    eresources/chapter.sgml
firewalls.sgml       1.20  ->  1.21    security/chapter.sgml
handbook.sgml        1.95  ->  1.96    handbook.sgml
history.sgml         1.25  ->  1.27    introduction/chapter.sgml
kernelconfig.sgml    1.32  ->  1.33    kernelconfig/chapter.sgml
linuxemu.sgml        1.24  ->  1.25    linuxemu/chapter.sgml
mail.sgml[1]         1.12  ->  1.13    mail/chapter.sgml
mirrors.sgml         1.99  ->  1.101   mirrors/chapter.sgml
pgpkeys.sgml         1.28  ->  1.30    pgpkeys/chapter.sgml
porting.sgml         1.118 ->  1.124   ports/chapter.sgml
ports.sgml           1.33  ->  1.35    ports/chapter.sgml
stable.sgml          1.18  ->  1.19    cutting-edge/chapter.sgml
submitters.sgml      1.261 ->  1.277   contrib/chapter.sgml

[1] Typo fix is another typo! "wait" should be "want"
This commit is contained in:
Nik Clayton 1999-01-29 22:34:03 +00:00
parent ed01f19eb5
commit c73e1d5b63
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=4149
49 changed files with 2540 additions and 528 deletions
en/handbook
en_US.ISO8859-1
articles/contributing
books
handbook
porters-handbook
share/sgml
en_US.ISO_8859-1/books
handbook
porters-handbook

View file

@ -7,7 +7,7 @@
Please keep this list in alphabetical order by entity names.
$Id: authors.ent,v 1.4 1998-12-10 20:43:39 nik Exp $
$Id: authors.ent,v 1.5 1999-01-29 22:33:55 nik Exp $
-->
<!ENTITY a.abial "Andrzej Bialecki <email>abial@FreeBSD.ORG</email>">
@ -70,6 +70,8 @@
<!ENTITY a.dima "Dima Ruban <email>dima@FreeBSD.ORG</email>">
<!ENTITY a.dirk "Dirk Fr&ouml;mberg <email>dirk@FreeBSD.ORG</email>">
<!ENTITY a.dirkvangulik "Dirk-Willem van Gulik <email>Dirk.vanGulik@jrc.it</email>">
<!ENTITY a.dt "Dmitrij Tejblum <email>dt@FreeBSD.ORG</email>">
@ -92,8 +94,12 @@
<!ENTITY a.flathill "Seiichirou Hiraoka <email>flathill@FreeBSD.ORG</email>">
<!ENTITY a.foxfair "Howard F. Hu <email>foxfair@FreeBSD.ORG</email>">
<!ENTITY a.fsmp "Steve Passe <email>fsmp@FreeBSD.ORG</email>">
<!ENTITY a.gallatin "Andrew Gallatin <email>gallatin@FreeBSD.ORG</email>">
<!ENTITY a.gclarkii "Gary Clark II <email>gclarkii@FreeBSD.ORG</email>">
<!ENTITY a.gena "Gennady B. Sorokopud <email>gena@NetVision.net.il</email>">
@ -122,7 +128,7 @@
<!ENTITY a.helbig "Wolfgang Helbig <email>helbig@FreeBSD.ORG</email>">
<!ENTITY a.hm "Hellmuth Michaelis <email>hm@kts.org</email>">
<!ENTITY a.hm "Hellmuth Michaelis <email>hm@FreeBSD.ORG</email>">
<!ENTITY a.hoek "Tim Vanderhoek <email>hoek@FreeBSD.ORG</email>">
@ -212,6 +218,8 @@
<!ENTITY a.md "Mark Dapoz <email>md@bsc.no</email>">
<!ENTITY a.mks "Mike Spengler <email>mks@FreeBSD.ORG</email>">
<!ENTITY a.motoyuki "Motoyuki Konno <email>motoyuki@FreeBSD.ORG</email>">
<!ENTITY a.mph "Matthew Hunt <email>mph@FreeBSD.ORG</email>">
@ -224,6 +232,8 @@
<!ENTITY a.nectar "Jacques Vidrine <email>nectar@FreeBSD.ORG</email>">
<!ENTITY a.newton "Mark Newton <email>newton@FreeBSD.ORG</email>">
<!ENTITY a.nhibma "Nick Hibma <email>n_hibma@FreeBSD.ORG</email>">
<!ENTITY a.nik "Nik Clayton <email>nik@FreeBSD.ORG</email>">
@ -274,6 +284,8 @@
<!ENTITY a.sef "Sean Eric Fagan <email>sef@FreeBSD.ORG</email>">
<!ENTITY a.simokawa "Hidetoshi Shimokawa <email>simokawa@FreeBSD.ORG</email>">
<!ENTITY a.smace "Scott Mace <email>smace@FreeBSD.ORG</email>">
<!ENTITY a.smpatel "Sujal Patel <email>smpatel@FreeBSD.ORG</email>">

View file

@ -51,9 +51,16 @@
</listitem>
<listitem>
<para>FreeBSD mit Methode (in German), publiched by Computer und
Literatur Verlag/Vertrieb Hanser, 1998. ISBN 3-93211-31-0.</para>
<para>FreeBSD mit Methode (in German), published by Computer und
Literatur Verlag/Vertrieb Hanser, 1998. ISBN 3-932311-31-0.</para>
</listitem>
<listitem>
<para><ulink url="http://www.pc.mycom.co.uk/FreeBSD/install-manual.html">FreeBSD
Install and Utilization Manual</ulink> (in Japanese),
published by <ulink url="http://www.pc.mycom.co.jp/">Mainichi
Communications Inc.</ulink>.</para>
</listitem>
</itemizedlist>
@ -111,7 +118,16 @@
University</ulink> has written a <ulink
URL="http://www-wks.acs.ohio-state.edu/unix_course/unix.html">UNIX Introductory Course</ulink> which is available online in HTML and postscript format.</para>
</listitem>
<listitem>
<para><ulink url="http://www.jp.FreeBSD.ORG/">Jpman Project,
Japan FreeBSD Users Group</ulink>. <ulink
url="http://www.pc.mycom.co.jp/FreeBSD/urm.html">FreeBSD
User's Reference Manual</ulink> (Japanese translation).
<ulink url="http://www.pc.mycom.co.jp/">Mainichi
Communications Inc.</ulink>, 1998. ISBN4-8399-0088-4
P3800E.</para>
</listitem>
</itemizedlist>
@ -164,7 +180,16 @@
O'Reilly &amp; Associates, Inc., 1991. <!-- <br> --> ISBN
0-937175-75-7</para>
</listitem>
<listitem>
<para><ulink url="http://www.jp.FreeBSD.ORG/">Jpman Project,
Japan FreeBSD Users Group</ulink>. <ulink
url="http://www.pc.mycom.co.jp/FreeBSD/sam.html">FreeBSD
System Administrator's Manual</ulink> (Japanese translation).
<ulink url="http://www.pc.mycom.co.jp/">Mainichi
Communications Inc.</ulink>, 1998. ISBN4-8399-0109-0
P3300E.</para>
</listitem>
</itemizedlist>

View file

@ -993,6 +993,10 @@ box can be opened)</para>
URL="http://www.buffnet.net/">BuffNET</ulink></para>
</listitem>
<listitem>
<para><ulink url="http://www.pacificsolutions.com/">Pacific
Solutions</ulink></para>
</listitem>
</itemizedlist>
</listitem>
@ -1235,7 +1239,11 @@ box can be opened)</para>
<listitem>
<para>Anthony Yee-Hang Chan <email>yeehang@netcom.com</email></para>
</listitem>
<listitem>
<para>Anton Berezin <email>tobez@plab.ku.dk</email></para>
</listitem>
<listitem>
<para>Ari Suutari <email>ari@suutari.iki.fi</email></para>
</listitem>
@ -1279,7 +1287,11 @@ box can be opened)</para>
<listitem>
<para>Brian Clapper <email>bmc@willscreek.com</email></para>
</listitem>
<listitem>
<para>Brian F. Feldman <email>green@unixhelp.org</email></para>
</listitem>
<listitem>
<para>Brian Handy <email>handy@lambic.space.lockheed.com</email></para>
</listitem>
@ -1460,7 +1472,11 @@ box can be opened)</para>
<listitem>
<para>Dean Huxley <email>dean@fsa.ca</email></para>
</listitem>
<listitem>
<para>Dima Sivachenko <email>demon@gpad.ac.ru</email></para>
</listitem>
<listitem>
<para>Dirk Froemberg <email>dirk@hal.in-berlin.de</email></para>
</listitem>
@ -1611,14 +1627,14 @@ box can be opened)</para>
<para>Hidekazu Kuroki <email>hidekazu@cs.titech.ac.jp</email></para>
</listitem>
<listitem>
<para>Hidetoshi Shimokawa <email>simokawa@sat.t.u-tokyo.ac.jp</email></para>
</listitem>
<listitem>
<para>Hideyuki Suzuki <email>hideyuki@sat.t.u-tokyo.ac.jp</email></para>
</listitem>
<listitem>
<para>Hiroaki Sakai <email>sakai@miya.ee.kagu.sut.ac.jp</email></para>
</listitem>
<listitem>
<para>Hironori Ikura <email>hikura@kaisei.org</email></para>
</listitem>
@ -1742,7 +1758,10 @@ box can be opened)</para>
<listitem>
<para>Jim Lowe <email>james@cs.uwm.edu</email></para>
</listitem>
<listitem>
<para>Jim Mock <email>jim@phrantic.phear.net</email></para>
</listitem>
<listitem>
<para>Jim Wilson <email>wilson@moria.cygnus.com</email></para>
</listitem>
@ -1756,6 +1775,10 @@ box can be opened)</para>
<para>Joao Carlos Mendes Luis <email>jonny@coppe.ufrj.br</email></para>
</listitem>
<listitem>
<para>Joe Abley <email>jabley@clear.co.nz</email></para>
</listitem>
<listitem>
<para>Joe &ldquo;Marcus&rdquo; Clarke
<email>marcus@miami.edu</email></para>
@ -1893,7 +1916,11 @@ box can be opened)</para>
<listitem>
<para>Kostya Lukin <email>lukin@okbmei.msk.su</email></para>
</listitem>
<listitem>
<para>KUNISHIMA Takeo <email>kunishi@c.oka-pu.ac.jp</email></para>
</listitem>
<listitem>
<para>Kurt Olsen <email>kurto@tiny.mcs.usu.edu</email></para>
</listitem>
@ -1914,7 +1941,11 @@ box can be opened)</para>
<listitem>
<para>Luigi Rizzo <email>luigi@iet.unipi.it</email></para>
</listitem>
<listitem>
<para>Malte Lance <email>malte.lance@gmx.net</email></para>
</listitem>
<listitem>
<para>Makoto MATSUSHITA <email>matusita@jp.freebsd.org</email></para>
</listitem>
@ -1923,6 +1954,10 @@ box can be opened)</para>
<para>Makoto WATANABE
<email>watanabe@zlab.phys.nagoya-u.ac.jp</email></para>
</listitem>
<listitem>
<para>MANTANI Nobutaka <email>nobutaka@nobutaka.com</email></para>
</listitem>
<listitem>
<para>Manu Iyengar <email>iyengar@grunthos.pscwa.psca.com</email></para>
@ -2055,6 +2090,10 @@ box can be opened)</para>
<listitem>
<para>Motoyuki Kasahara <email>m-hasahr@sra.co.jp</email></para>
</listitem>
<listitem>
<para>Munechika Sumikawa <email>sumikawa@kame.net</email></para>
</listitem>
<listitem>
<para>Murray Stokely <email>murray@cdrom.com</email></para>
@ -2095,7 +2134,11 @@ box can be opened)</para>
<listitem>
<para>Nobuyuki Koganemaru <email>kogane@kces.koganemaru.co.jp</email></para>
</listitem>
<listitem>
<para>Norio Suzuki <email>nosuzuki@e-mail.ne.jp</email></para>
</listitem>
<listitem>
<para>Noritaka Ishizumi <email>graphite@jp.FreeBSD.ORG</email></para>
</listitem>
@ -2115,7 +2158,11 @@ box can be opened)</para>
<listitem>
<para>Oliver Oberdorf <email>oly@world.std.com</email></para>
</listitem>
<listitem>
<para>Palle Girgensohn <email>girgen@partitur.se</email></para>
</listitem>
<listitem>
<para>Paul Fox <email>pgf@foxharp.boston.ma.us</email></para>
</listitem>
@ -2256,6 +2303,10 @@ box can be opened)</para>
<para>Satoshi Taoka <email>taoka@infonets.hiroshima-u.ac.jp</email></para>
</listitem>
<listitem>
<para>Satsuki FUJISHIMA <email>k5@respo.or.jp</email></para>
</listitem>
<listitem>
<para>Scot W. Hetzel <email>hetzels@westbend.net</email></para>
</listitem>
@ -2273,10 +2324,6 @@ box can be opened)</para>
<email>tanimura@naklab.dnj.ynu.ac.jp</email></para>
</listitem>
<listitem>
<para>Seiichirou Hiraoka <email>flathill@flathill.gr.jp</email></para>
</listitem>
<listitem>
<para>Serge Babkin <email>babkin@hq.icb.chel.su</email></para>
</listitem>
@ -2351,6 +2398,10 @@ box can be opened)</para>
<para>Stuart Henderson
<email>stuart@internationalschool.co.uk</email></para>
</listitem>
<listitem>
<para>SUGIMURA Takashi <email>sugimura@jp.FreeBSD.ORG</email></para>
</listitem>
<listitem>
<para>Suzuki Yoshiaki <email>zensyo@ann.tama.kawasaki.jp</email></para>
@ -2416,6 +2467,10 @@ box can be opened)</para>
<para>Tim Wilkinson <email>tim@sarc.city.ac.uk</email></para>
</listitem>
<listitem>
<para>Tom Hukins <email>tom@eborcom.com</email></para>
</listitem>
<listitem>
<para>Tom Jobbins <email>tom@tom.tj</email></para>
</listitem>
@ -2439,7 +2494,11 @@ box can be opened)</para>
<listitem>
<para>Trefor S. <email>trefor@flevel.co.uk</email></para>
</listitem>
<listitem>
<para>Vadim Chekan <email>vadim@gc.lviv.ua</email></para>
</listitem>
<listitem>
<para>Ville Eerola <email>ve@sci.fi</email></para>
</listitem>
@ -2485,7 +2544,7 @@ box can be opened)</para>
</listitem>
<listitem>
<para>Yukihiro Nakai <email>nakai@technologist.com</email></para>
<para>Yukihiro Nakai <email>nakai@iname.com</email></para>
</listitem>
<listitem>

View file

@ -111,18 +111,19 @@
<para>Join the &a.current; and the &a.cvsall; . This is not
just a good idea, it is <emphasis>essential</emphasis>. If
you are not on the <emphasis>FreeBSD-current</emphasis>
mailing list you will not see the comments that people are
mailing list, you will not see the comments that people are
making about the current state of the system and thus will
probably end up stumbling over a lot of problems that others
have already found and solved. Even more importantly, you
will miss out on potentially critical information (e.g.
&ldquo;Yo, Everybody! Before you rebuild
<filename>/usr/src</filename>, you <emphasis>must</emphasis>
rebuild the kernel or your system will crash horribly!&rdquo;).
The <email>cvs-all</email> mailing list will allow you
will miss out on important bulletins which may be critical
to your system's continued health.</para>
<para>The <email>cvs-all</email> mailing list will allow you
to see the commit log entry for each change as it is made
along with any pertinent information on possible
side-effects. To join these lists, send mail to
side-effects.</para>
<para>To join these lists, send mail to
&a.majordomo; and specify:
<programlisting>
@ -151,7 +152,13 @@ subscribe cvs-all</programlisting>
<listitem>
<para>Use the <link linkend="cvsup">cvsup</link>
program with <ulink
URL="ftp://ftp.freebsd.org/pub/FreeBSD/FreeBSD-current/src/share/examples/cvsup/standard-supfile">this supfile</ulink>. This is the second most recommended method, since it allows you to grab the entire collection once and then only what has changed from then on. Many people run cvsup from cron and keep their sources up-to-date automatically.</para>
URL="ftp://ftp.freebsd.org/pub/FreeBSD/FreeBSD-current/src/share/examples/cvsup/standard-supfile">this supfile</ulink>. This is the second most recommended method, since it allows you to grab the entire collection once and then only what has changed from then on. Many people run cvsup from cron and keep their sources up-to-date automatically. For a fairly easy interface to this, simply type:</para>
<informalexample>
<screen>&prompt.root; <userinput>pkg_add -f ftp://ftp.freebsd.org/pub/FreeBSD/CVSup/cvsupit.tgz</userinput></screen>
</informalexample>
</listitem>
<listitem>
@ -182,18 +189,14 @@ subscribe cvs-all</programlisting>
<para>Essentially, if you need rapid on-demand access to the
source and communications bandwidth is not a consideration,
use <command>cvsup</command> or <command>ftp</command>. Otherwise, use <application>CTM</application>.</para>
</listitem>
<listitem>
<para>If you are grabbing the sources to run, and not just
look at, then grab <emphasis>all</emphasis> of current, not
just selected portions. The reason for this is that various
parts of the source depend on updates elsewhere, and trying
to compile just a subset is almost guaranteed to get you
into trouble.</para>
</listitem>
<listitem>
<para>Before compiling current, read the Makefile in
<filename>/usr/src</filename> carefully. You should at
least run a <link
@ -201,7 +204,7 @@ subscribe cvs-all</programlisting>
through as part of the upgrading process. Reading the
&a.current; will keep you up-to-date on other bootstrapping
procedures that sometimes become necessary as we move
towards the next release.</para>
towards the next release.</para>
</listitem>
<listitem>
@ -270,14 +273,25 @@ subscribe cvs-all</programlisting>
in this mailing list when they are contemplating some
controversial fix or update, giving the users a chance to
respond if they have any issues to raise concerning the
proposed change. To join this list, send mail to
&a.majordomo; and say:
proposed change.</para>
<para>The <email>cvs-all</email> mailing list will allow you
to see the commit log entry for each change as it is made
along with any pertinent information on possible
side-effects.</para>
<para>To join these lists, send mail to
&a.majordomo; and specify:
<programlisting>
subscribe freebsd-stable</programlisting> In the body of your
message. Optionally, you can also say <literal>help</literal> and Majordomo
will send you full help on how to subscribe and unsubscribe
to the various other mailing lists we support.</para>
subscribe freebsd-stable
subscribe cvs-all</programlisting>
in the
body of your message. Optionally, you can also say <literal>help</literal>
and Majordomo will send you full help on how to subscribe
and unsubscribe to the various other mailing lists we
support.</para>
</listitem>
<listitem>
@ -514,12 +528,21 @@ subscribe freebsd-stable</programlisting> In the body of your
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_3</term>
<listitem>
<para>The line of development for FreeBSD-3.x, also known as
FreeBSD-stable. Not valid for the ports collection.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_2_2</term>
<listitem>
<para>The line of development for FreeBSD-2.2.x, also known as
FreeBSD-stable. Not valid for the ports collection.</para>
2.2-stable. Not valid for the ports collection.</para>
</listitem>
</varlistentry>
@ -1365,17 +1388,25 @@ cvs-crypto</programlisting>
</note>
</listitem>
</varlistentry>
<varlistentry><term>tag=RELENG_2_2</term>
<listitem>
<para>The line of development for FreeBSD-2.2.x,
also known as FreeBSD-stable. Not valid for the
ports-* collections.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_3</term>
<listitem>
<para>The line of development for FreeBSD-3.x, also known as
FreeBSD-stable. Not valid for the ports collection.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_2_2</term>
<listitem>
<para>The line of development for FreeBSD-2.2.x, also known as
2.2-stable. Not valid for the ports collection.</para>
</listitem>
</varlistentry>
<varlistentry><term>tag=RELENG_2_1_0</term>
<listitem>

View file

@ -88,12 +88,6 @@
FreeBSD-current</entry>
</row>
<row>
<entry>freebsd-stable</entry>
<entry>Discussion concerning the use of
FreeBSD-stable</entry>
</row>
<row>
<entry>freebsd-isp</entry>
<entry>Issues for Internet Service Providers using
@ -113,8 +107,15 @@
<row>
<entry>freebsd-questions</entry>
<entry>User questions</entry>
<entry>User questions and technical support</entry>
</row>
<row>
<entry>freebsd-stable</entry>
<entry>Discussion concerning the use of
FreeBSD-stable</entry>
</row>
</tbody>
</tgroup>
</informaltable>
@ -146,7 +147,7 @@
<row>
<entry>freebsd-doc</entry>
<entry>The FreeBSD Documentation project</entry>
<entry>Creating FreeBSD related documents</entry>
</row>
<row>
@ -608,33 +609,17 @@ help
</listitem>
</varlistentry>
<varlistentry><term>FREEBSD-STABLE</term>
<listitem>
<para><emphasis>Discussions about the use of
FreeBSD-stable</emphasis></para>
<para>This is the
mailing list for users of freebsd-stable. It includes
warnings about new features coming out in -stable that
will affect the users, and instructions on steps that must
be taken to remain -stable. Anyone running &ldquo;stable&rdquo;
should subscribe to this list. This is a technical mailing
list for which strictly technical content is
expected.</para>
</listitem>
</varlistentry>
<varlistentry><term>FREEBSD-DOC</term>
<listitem>
<para><emphasis>Documentation project</emphasis></para>
<para>This mailing list is for the discussion of documentation
related issues and projects. The members of this mailing list
are collectively referred to as &ldquo;The FreeBSD
Documentation Project&rdquo;. It is an open list; feel free to
join and contribute.</para>
<para>This mailing list is for the discussion of issues and
projects related to the creation of documenation for
FreeBSD. The members of this mailing list are collectively
referred to as &ldquo;The FreeBSD Documentation
Project&rdquo;. It is an open list; feel free to join and
contribute!</para>
</listitem>
</varlistentry>
@ -855,7 +840,24 @@ help
</listitem>
</varlistentry>
<varlistentry><term>FREEBSD-USER-GROUPS</term>
<varlistentry><term>FREEBSD-STABLE</term>
<listitem>
<para><emphasis>Discussions about the use of
FreeBSD-stable</emphasis></para>
<para>This is the
mailing list for users of freebsd-stable. It includes
warnings about new features coming out in -stable that
will affect the users, and instructions on steps that must
be taken to remain -stable. Anyone running &ldquo;stable&rdquo;
should subscribe to this list. This is a technical mailing
list for which strictly technical content is
expected.</para>
</listitem>
</varlistentry>
<varlistentry><term>FREEBSD-USER-GROUPS</term>
<listitem>
<para><emphasis>User Group Coordination
@ -1045,27 +1047,52 @@ help
<listitem>
<para><ulink
URL="http://www.au.freebsd.org/FreeBSD/">http://www.au.freebsd.org/FreeBSD/</ulink> &mdash; Australia.</para>
URL="http://www.au.freebsd.org/FreeBSD/">http://www.au.freebsd.org/FreeBSD/</ulink> &mdash; Australia/1.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www2.au.freebsd.org/FreeBSD/">http://www2.au.freebsd.org/FreeBSD/</ulink> &mdash; Australia/2.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www3.au.freebsd.org/FreeBSD/">http://www3.au.freebsd.org/FreeBSD/</ulink> &mdash; Australia/3.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.br.freebsd.org/www.freebsd.org/">http://www.br.freebsd.org/www.freebsd.org/</ulink> &mdash; Brazil/1.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.br.freebsd.org/">http://www.br.freebsd.org/</ulink> &mdash; Brazil.</para>
URL="http://www.br2.freebsd.org/www.freebsd.org/">http://www.br2.freebsd.org/www.freebsd.org/</ulink> &mdash; Brazil/2.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.ca.freebsd.org/">http://www.ca.freebsd.org/</ulink> &mdash; Canada.</para>
URL="http://www3.br.freebsd.org/">http://www3.br.freebsd.org/</ulink> &mdash; Brazil/3.</para>
</listitem>
<listitem>
<para><ulink
URL="http://sunsite.mff.cuni.cz/www.freebsd.org/">http://sunsite.mff.cuni.cz/www.freebsd.org/</ulink> &mdash; Czech Republic.</para>
URL="http://www.bg.freebsd.org/">http://www.bg.freebsd.org/</ulink> &mdash; Bulgaria.</para>
</listitem>
<listitem>
<para><ulink
URL="http://sunsite.auc.dk/www.freebsd.org/">http://sunsite.auc.dk/www.freebsd.org/</ulink> &mdash; Denmark.</para>
URL="http://www.ca.freebsd.org/">http://www.ca.freebsd.org/</ulink> &mdash; Canada/1.</para>
</listitem>
<listitem>
<para><ulink
URL="http://freebsd.kawartha.com/">http://freebsd.kawartha.com/</ulink> &mdash; Canada/2.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.dk.freebsd.org/">http://www.dk.freebsd.org/</ulink> &mdash; Denmark.</para>
</listitem>
<listitem>
@ -1077,10 +1104,35 @@ help
<para><ulink
URL="http://www.fi.freebsd.org/">http://www.fi.freebsd.org/</ulink> &mdash; Finland.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.fr.freebsd.org/">http://www.fr.freebsd.org/</ulink> &mdash; France.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.de.freebsd.org/">http://www.de.freebsd.org/</ulink> &mdash; Germany/1.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.de.freebsd.org/">http://www.de.freebsd.org/</ulink> &mdash; Germany.</para>
URL="http://www1.de.freebsd.org/">http://www1.de.freebsd.org/</ulink> &mdash; Germany/2.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www2.de.freebsd.org/">http://www.de.freebsd.org/</ulink> &mdash; Germany/3.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.hu.freebsd.org/">http://www.hu.freebsd.org/</ulink> &mdash; Hungary.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.is.freebsd.org/">http://www.is.freebsd.org/</ulink> &mdash; Iceland.</para>
</listitem>
<listitem>
@ -1090,7 +1142,7 @@ help
<listitem>
<para><ulink
URL="http://www.jp.freebsd.org/">http://www.jp.freebsd.org/</ulink> &mdash; Japan.</para>
URL="http://www.jp.freebsd.org/www.freebsd.org/">http://www.jp.freebsd.org/www.freebsd.org/</ulink> &mdash; Japan.</para>
</listitem>
<listitem>
@ -1098,6 +1150,16 @@ help
URL="http://www.kr.freebsd.org/">http://www.kr.freebsd.org/</ulink> &mdash; Korea.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.lv.freebsd.org/">http://www.lv.freebsd.org/</ulink> &mdash; Latvia.</para>
</listitem>
<listitem>
<para><ulink
URL="http://rama.asiapac.net/freebsd/">http://rama.asiapac.net/freebsd/</ulink> &mdash; Malaysia.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.nl.freebsd.org/">http://www.nl.freebsd.org/</ulink> &mdash; Netherlands.</para>
@ -1105,7 +1167,67 @@ help
<listitem>
<para><ulink
URL="http://www.pt.freebsd.org/">http://www.pt.freebsd.org/</ulink> &mdash; Portugal.</para>
URL="http://www.no.freebsd.org/">http://www.no.freebsd.org/</ulink> &mdash; Norway.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.pt.freebsd.org/">http://www.pt.freebsd.org/</ulink> &mdash; Portugal/1.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www2.pt.freebsd.org/">http://www2.pt.freebsd.org/</ulink> &mdash; Portugal/2.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www3.pt.freebsd.org/">http://www3.pt.freebsd.org/</ulink> &mdash; Portugal/3.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.ro.freebsd.org/">http://www.ro.freebsd.org/</ulink> &mdash; Romania.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.ru.freebsd.org/">http://www.ru.freebsd.org/</ulink> &mdash; Russia/1.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www2.ru.freebsd.org/">http://www2.ru.freebsd.org/</ulink> &mdash; Russia/2.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www3.ru.freebsd.org/">http://www3.ru.freebsd.org/</ulink> &mdash; Russia/3.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.sk.freebsd.org/">http://www.sk.freebsd.org/</ulink> &mdash; Slovak Republic.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.si.freebsd.org/">http://www.si.freebsd.org/</ulink> &mdash; Slovenia.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.es.freebsd.org/">http://www.es.freebsd.org/</ulink> &mdash; Spain.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.za.freebsd.org/">http://www.za.freebsd.org/</ulink> &mdash; South Africa/1.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www2.za.freebsd.org/">http://www2.za.freebsd.org/</ulink> &mdash; South Africa/2.</para>
</listitem>
<listitem>
@ -1115,14 +1237,38 @@ help
<listitem>
<para><ulink
URL="http://www.tw.freebsd.org/freebsd.html">http://www.tw.freebsd.org/freebsd.html</ulink> &mdash; Taiwan.</para>
URL="http://www.tr.freebsd.org/">http://www.tr.freebsd.org/</ulink> &mdash; Turkey.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www2.ua.freebsd.org/">http://www2.ua.freebsd.org/</ulink> &mdash; Ukraine.</para>
URL="http://www.ua.freebsd.org/">http://www.ua.freebsd.org/</ulink> &mdash; Ukraine/1.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www2.ua.freebsd.org/">http://www2.ua.freebsd.org/</ulink> &mdash; Ukraine/2.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.uk.freebsd.org/">http://www.uk.freebsd.org/</ulink> &mdash; United Kingdom.</para>
</listitem>
<listitem>
<para><ulink
URL="http://freebsd.advansys.net/">http://freebsd.advansys.net/</ulink> &mdash; USA/Indiana.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www6.freebsd.org/">http://www6.freebsd.org/</ulink> &mdash; USA/Oregon.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www2freebsd.org/">http://www2.freebsd.org/</ulink> &mdash; USA/Texas.</para>
</listitem>
</itemizedlist>

View file

@ -35,13 +35,13 @@
manual is a <emphasis>work in progress</emphasis> and is the work of
many individuals. Many sections do not yet exist and some of those
that do exist need to be updated. If you are interested in helping
with this project, send email to the &a.doc; The latest version of
with this project, send email to the &a.doc;. The latest version of
this document is always available from the <ulink
URL="http://www.FreeBSD.ORG/">FreeBSD World Wide Web server</ulink>.
It may also be downloaded in <ulink url="handbook.latin1">plain
text</ulink>, <ulink url="handbook.ps">postscript</ulink> or <ulink
url="handbook-html.tar.gz">HTML</ulink> with HTTP or gzip'd from the <ulink
url="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/docs/">FreeBSD FTP server</ulink> or one of the numerous <link
url="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/doc/">FreeBSD FTP server</ulink> or one of the numerous <link
linkend="mirrors-ftp">mirror sites</link>. You may also want to
<ulink URL="http://www.FreeBSD.ORG/search.html">Search the Handbook</ulink>.</para>
</abstract>
@ -103,6 +103,7 @@ url="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/docs/">FreeBSD FTP server</ulink> or one
</book>
<!--
Local Variables:
mode: sgml
sgml-indent-data: t
sgml-omittag: nil

View file

@ -349,13 +349,17 @@
first full release (2.2.1) was released in April, 1997. Further
releases along the 2.2 branch were done in the Summer and Fall of
'97, the latest being 2.2.7 which appeared in late July of '98.
The first official 3.0 release will appear in October, 1998 and the
last release on the 2.2 branch, 2.2.8, will appear in November.</para>
<para>Long term development projects for everything from SMP to DEC
ALPHA support will continue to take place in the 3.0-current branch
and SNAPshot releases of 3.0 on CDROM (and, of course, on the net).</para>
The first official 3.0 release appeared in October, 1998 and the
last release on the 2.2 branch, 2.2.8, appeared in November,
1998.</para>
<para>The tree branched again on Jan 20, 1999. This led to
4.0-current and a 3.x-stable branch, from which 3.1 will be
released on February 15th, 1999.</para>
<para>Long term development projects will continue to take place in
the 4.0-current branch and SNAPshot releases of 4.0 on CDROM (and,
of course, on the net).</para>
</sect1>
<sect1 id="goals">

View file

@ -73,9 +73,11 @@
<note>
<para>If there is <emphasis>not</emphasis> a
<filename>/usr/src/sys</filename> directory on your system, then
the kernel source has not been been installed. Follow the
instructions for installing packages to add this package to your
system.</para>
the kernel source has not been been installed. The easiest way
to do this is by running <command>/stand/sysinstall</command> as
<username>root</username>, choosing <literal>Configure</literal>,
then <literal>Distributions</literal>, then <literal>src</literal>,
then <literal>sys</literal>.</para>
</note>
<para>Next, move to the <filename>i386/conf</filename> directory and

View file

@ -433,7 +433,7 @@ Abort</screen>
</informalexample>
<para>To help the FreeBSD kernel distinguish between a FreeBSD ELF
binary from a Linux one, use the <citerefentry>
binary from a Linux binary, use the <citerefentry>
<refentrytitle>brandelf</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry> utility.</para>

View file

@ -529,7 +529,7 @@ bigco.com. MX 10 bigco.com.
<filename>/etc/rc.conf</filename> ) 15 minutes to connect to your
host to deliver the mail to the primary MX site.</para>
<para>You might wat to use something like this as a login script.</para>
<para>You might want to use something like this as a login script.</para>
<programlisting>
#!/bin/sh

View file

@ -722,7 +722,7 @@
<listitem>
<para><ulink
URL="ftp://ftp.ua.FreeBSD.ORG/pub/FreeBSD">ftp://ftp.ua.FreeBSD.ORG/pub/FreeBSD</ulink> Contact: <email>archer@lucky.net</email>.</para>
URL="ftp://ftp.ua.FreeBSD.ORG/pub/FreeBSD">ftp://ftp.ua.FreeBSD.ORG/pub/FreeBSD</ulink> Contact: <email>freebsd-mnt@lucky.net</email>.</para>
</listitem>
</itemizedlist>
@ -1269,7 +1269,7 @@
<itemizedlist>
<listitem>
<para>cvsup2.ua.FreeBSD.ORG (maintainer <email>archer@lucky.net</email>)</para>
<para>cvsup2.ua.FreeBSD.ORG (maintainer <email>freebsd-mnt@lucky.net</email>)</para>
</listitem>
</itemizedlist>
@ -1310,6 +1310,9 @@
<para>cvsup3.FreeBSD.ORG (maintainer <email>wollman@FreeBSD.ORG</email>)</para>
</listitem>
<listitem>
<para>cvsup4.FreeBSD.ORG (maintainer <email>shmit@rcn.com</email>)</para>
</listitem>
</itemizedlist>
</listitem>

View file

@ -495,6 +495,75 @@ vvlVQ0UbcR0N2+5F6Mb5GqrXZpIesn7jFJpkQKPU
-----END PGP PUBLIC KEY BLOCK-----</programlisting>
</sect2>
</sect1>
<sect1>
<title>Developers</title>
<sect2>
<title>&a.wosch;</title>
<programlisting>
Type Bits/KeyID Date User ID
pub 1024/2B7181AD 1997/08/09 Wolfram Schneider &lt;wosch@FreeBSD.org&gt;
Fingerprint = CA 16 91 D9 75 33 F1 07 1B F0 B4 9F 3E 95 B6 09
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: 2.6.3ia
mQCNAzPs+aEAAAEEAJqqMm2I9CxWMuHDvuVO/uh0QT0az5ByOktwYLxGXQmqPG1G
Q3hVuHWYs5Vfm/ARU9CRcVHFyqGQ3LepoRhDHk+JcASHan7ptdFsz7xk1iNNEoe0
vE2rns38HIbiyQ/2OZd4XsyhFOFtExNoBuyDyNoe3HbHVBQT7TmN/mkrcYGtAAUR
tCVXb2xmcmFtIFNjaG5laWRlciA8d29zY2hARnJlZUJTRC5vcmc+iQCVAwUQNmrS
AzmN/mkrcYGtAQFQjAP8CthNueur8XDAZqC5q6NQcDs0PqqQ+raTUfQTv6Km6ykf
UzdpDlBoRC+CCyHfBfC5zo9N6mB7iV7qS1PljrdIh6VAwHxJN9iopB/x6+nsBvmy
0YSNt7eyfFrIVegCJvd4ALz5JBV8ZstznOwo8RAhDD0gX58F8nDhgWjy62JekGK0
IldvbGZyYW0gU2NobmVpZGVyIDx3b3NjaEBhcGZlbC5kZT6JARUDBRA2Z9ZcCMks
sk6wLt0BAQBICACcTiDZ/AyYWRDLXsBOK+WMRoNk3+bQZ1cdy11nwJo+taT/389M
0r5TrEJ7CogpXC2rFUExTVWldSFZd8A1YIHtrTsP7YauUH0nA7k0wUnqDRYj8YJR
eMLFvc1OQ2y+mkvxF2BzzBzh/bcYbgJdWCB1MPahSNQfkGXtp+A5PjEs8Cp4+FLu
EUFScyxsD3g5/E+0d7mirJpe3pxcf9KCmFGHM89mrTKODQR/7N8dVqa9npeXZotm
ZK8Jz+tvRKFgNiLf2XL048+IE8ZtJXDYaDzTirHdcAqJMWQuxthCdG3ta4I+w5WM
WR8JtBLfVNpyU7LN6dl0IB7O5sYhyskApmMwiQCVAwUQM+z5oTmN/mkrcYGtAQGU
gAP/cJGro/SbV+L19s/Gem26KmegUH+bfIXoh2EzyRJ7heVdybu1LrSDFApmAE7d
sMDlAA1wd2XjVWD3nIEBl6k+J7qJB4ACjKVGs414jLpdKGPHdLRYqYDj4LyQFMv6
/BpSoX1gnWp6xlC2xeWRan9ns3XZGS55UBVDvBE/B+fPoTe0JFdvbGZyYW0gU2No
bmVpZGVyIDxzY2huZWlkZXJAemliLmRlPokAlQMFEDZq0dI5jf5pK3GBrQEB38QD
/3NYyRPIejtXXq/okdDRyhWmA8cv0KG6gEupKCQKa7ep/OZTw/KxrN3ZOS8zlPod
tEn8mol+4SvY5AgSMdjQ0jTd1JdFcMKFnbJJrJ3b9IpwCqbkXy25rTUcQn9ICP47
rFKC4qR/Ucrg5YVVhQ3pVJX6XuO2XvuG7euHAQNXV3e2
=EpJQ
-----END PGP PUBLIC KEY BLOCK-----</programlisting>
</sect2>
<sect2>
<title>&a.brian;</title>
<programlisting>
Type Bits/KeyID Date User ID
pub 1024/666A7421 1997/04/30 Brian Somers &lt;brian@Awfulhak.org&gt;
Key fingerprint = 2D 91 BD C2 94 2C 46 8F 8F 09 C4 FC AD 12 3B 21
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: 2.6.3ia
mQCNAzNmogUAAAEEALdsjVsV2dzO8UU4EEo7z3nYuvB2Q6YJ8sBUYjB8/vfR5oZ9
7aEQjgY5//pXvS30rHUB9ghk4kIFSljzeMudE0K2zH5n2sxpLbBKWZRDLS7xnrDC
I3j9CNKwQBzMPs0fUT46gp96nf1X8wPiJXkDUEia/c0bRbXlLw7tvOdmanQhAAUR
tCFCcmlhbiBTb21lcnMgPGJyaWFuQGF3ZnVsaGFrLm9yZz6JAJUDBRAzbedc77Ox
BWZTbW0BAVtFA/42QelA3RBXYUtIcYGob+QsWkA1kGyBKQGPSS9coHdUVjClBRl3
UZFmZhxAODb7cBRXmpvx2ZuMrhn/MpXTMqPOJaE3FYm+5SoeArphsRU+T8XofxfL
vRHkM3JURUjIVZdAQNvxxBso8NJG5KayP0Q96Vw+3sEwFK49jt14RCJy4IkAlQMF
EDNzvb1sq+iWcxFJBQEBfZwD/R3KNFf9ype9Dea8j1YIeNZ1E3e03en1I8fMj6Em
S1/L1WfFzMnfFCxZs7JgPtkBuB3CqP8f+LOdDt6PHPqNakmI9E6fiuGfJZ3jFZYA
TXa0XKuIoxIJNKhqkpbF8ixJZFTxFwAAwVYM3+sqr4qQ8FzVc5entxjyxPFNkwJw
RWV+iQCVAwUQM2aiBQ7tvOdmanQhAQE7LgQAiN6Hz+zd8bh0nO6VizbJxWFRHPbr
QWnJXGoMYyy88DyszAXC4zRshlyGUDQdHeP/1DFCXDEu78GfDCLaJ1bm25yVR7kL
xDZaEUQEbWqxfiwuzizAjkaxrW7dBbWILwWqrYF5TXClw+oUU/oIUW4t6t+GpAO1
8PLYhSMXVYErrAA=
=EdyZ
-----END PGP PUBLIC KEY BLOCK-----</programlisting>
</sect2>
</sect1>
</chapter>
<!--

View file

@ -110,7 +110,7 @@
<para>If you look at a port skeleton (either on <ulink
URL="file://localhost/usr/ports/devel/ElectricFence">your FreeBSD
system</ulink> or <ulink
URL="ftp://ftp.freebsd.org/pub/FreeBSD/ports/devel/ElectricFence">the FTP site</ulink>) and expect to find all sorts of pointy-headed rocket science lurking there, you may be disappointed by the one or two rather unexciting-looking files and directories you find there. (We will discuss in a minute how to go about <link
URL="ftp://ftp.freebsd.org/pub/FreeBSD/ports/ports/devel/ElectricFence">the FTP site</ulink>) and expect to find all sorts of pointy-headed rocket science lurking there, you may be disappointed by the one or two rather unexciting-looking files and directories you find there. (We will discuss in a minute how to go about <link
linkend="ports-getting">Getting a port</link>).</para>
<para>&ldquo;How on earth can this do anything?&rdquo; I hear you cry. &ldquo;There
@ -243,7 +243,25 @@ install -c -o bin -g bin -m 444 /usr/ports/devel/ElectricFence/work/ElectricFenc
collection's built in search path should find the tarballs in
<filename>/cdrom/ports/distfiles/</filename> (if they exist there)
rather than downloading them over the net.</para>
<para>Another way of doing this, if you want to just use the port
skeletons on the CDROM, is to set these variables in
<filename>/etc/make.conf</filename>:</para>
<programlisting>
PORTSDIR= /cdrom/ports
DISTDIR= /tmp/distfiles
WRKDIRPREFIX= /tmp</programlisting>
<para>Substitute <literal>/tmp</literal> for any place you have enough
free space. Then, just <command>cd</command> to the appropriate
subdirectory under <filename>/cdrom/ports</filename> and type
<command>make install</command> as
usual. <makevar>WRKDIRPREFIX</makevar> will cause the port to be
build under <filename>/tmp/cdrom/ports</filename>; for instance,
<filename>games/oneko</filename> will be built under
<filename>/tmp/cdrom/ports/games/oneko</filename>.</para>
<note>
<para>There are some ports for which we cannot provide the
original source in the CDROM due to licensing limitations. In
@ -283,7 +301,7 @@ install -c -o bin -g bin -m 444 /usr/ports/devel/ElectricFence/work/ElectricFenc
&prompt.root; <userinput>ftp ftp.freebsd.org</userinput>
[log in as `ftp' and give your email address when asked for a
password. Remember to use binary (also known as image) mode!]
<prompt>&gt;</prompt> <userinput>cd /pub/FreeBSD/ports/databases</userinput>
<prompt>&gt;</prompt> <userinput>cd /pub/FreeBSD/ports/ports/databases</userinput>
<prompt>&gt;</prompt> <userinput>get gnats.tar</userinput>
[tars up the gnats skeleton for us]
<prompt>&gt;</prompt> <userinput>quit</userinput>
@ -315,7 +333,7 @@ password. Remember to use binary (also known as image) mode!]
&prompt.root; <userinput>ftp ftp.freebsd.org</userinput>
[log in as `ftp' and give your email address when asked for a
password. Remember to use binary (also known as image) mode!]
<prompt>&gt;</prompt> <userinput>cd /pub/FreeBSD/ports</userinput>
<prompt>&gt;</prompt> <userinput>cd /pub/FreeBSD/ports/ports</userinput>
<prompt>&gt;</prompt> <userinput>get databases.tar</userinput>
[tars up the databases directory for us]
<prompt>&gt;</prompt> <userinput>quit</userinput>
@ -501,7 +519,7 @@ do-install:
<para>Grab the pre-compiled package from a ftp server. The
&ldquo;master&rdquo; package collection is on FreeBSD's FTP server in
the <ulink
URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/packages/">packages
URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/packages/">packages
directory</ulink>, though check your local mirror first,
please! These are more likely to work (on the whole) than
trying to compile from source and a lot faster besides! Use
@ -759,7 +777,7 @@ do-install:
<informalexample>
<screen>&prompt.root; <userinput>cd /usr/ports/directory</userinput>
&prompt.root; <userinput>make MASTER_SITE_OVERRIDE=ftp://ftp.FreeBSD.ORG/pub/FreeBSD/distfiles/ fetch</userinput></screen>
&prompt.root; <userinput>make MASTER_SITE_OVERRIDE=ftp://ftp.FreeBSD.ORG/pub/FreeBSD/ports/distfiles/ fetch</userinput></screen>
</informalexample>
</listitem>
@ -1348,7 +1366,7 @@ lib/X11/oneko/mouse.xpm
URL <makevar>MASTER_SITES</makevar>,
which is set in the Makefile, as well as our main ftp
site at <ulink
URL="ftp://ftp.freebsd.org/pub/FreeBSD/distfiles/">ftp://ftp.freebsd.org/pub/FreeBSD/distfiles/,</ulink> where we put sanctioned distfiles as backup. It will then attempt to fetch the named distribution file with <makevar>FETCH</makevar>, assuming that the requesting site has direct access to the Internet. If that succeeds, it will save the file in <makevar>DISTDIR</makevar> for future use and proceed.</para>
URL="ftp://ftp.freebsd.org/pub/FreeBSD/ports/distfiles/">ftp://ftp.freebsd.org/pub/FreeBSD/ports/distfiles/,</ulink> where we put sanctioned distfiles as backup. It will then attempt to fetch the named distribution file with <makevar>FETCH</makevar>, assuming that the requesting site has direct access to the Internet. If that succeeds, it will save the file in <makevar>DISTDIR</makevar> for future use and proceed.</para>
</step>
<step>
@ -1398,7 +1416,7 @@ lib/X11/oneko/mouse.xpm
<step>
<para>The <maketarget>build</maketarget> target is run. This is responsible for
descending into the ports' private working directory
descending into the port's private working directory
(<makevar>WRKSRC</makevar>) and
building it. If <makevar>USE_GMAKE</makevar> is set, GNU
<command>make</command> will be used,
@ -1435,7 +1453,7 @@ lib/X11/oneko/mouse.xpm
<note>
<para>The &ldquo;main&rdquo; targets (e.g., <maketarget>extract</maketarget>, <maketarget>configure</maketarget>, etc.) do nothing more than
make sure all the stages up to that one is completed and
make sure all the stages up to that one are completed and
call the real targets or scripts, and they are not intended
to be changed. If you want to fix the extraction, fix
<maketarget>do-extract</maketarget>, but never ever
@ -1471,7 +1489,7 @@ lib/X11/oneko/mouse.xpm
<filename>public_html/</filename> directory on
<hostid>freefall</hostid>),
we can &ldquo;house&rdquo; it ourselves by putting
it on <filename>ftp://ftp.freebsd.org/pub/FreeBSD/distfiles/LOCAL_PORTS/</filename> as the last resort. Please refer to this
it on <filename>ftp://ftp.freebsd.org/pub/FreeBSD/ports/distfiles/LOCAL_PORTS/</filename> as the last resort. Please refer to this
location as <makevar>MASTER_SITE_LOCAL</makevar>. Send mail to
the &a.ports;if you are not sure what to do.</para>
@ -1488,7 +1506,7 @@ lib/X11/oneko/mouse.xpm
<para>If your port requires some additional `patches' that are
available on the Internet, fetch them too and put them in
<makevar>DISTDIR</makevar>. Do not worry if
they come from site other than where you got the main source
they come from a site other than where you got the main source
tarball, we have a way to handle these situations (see the
description of <link
linkend="porting-patchfiles">PATCHFILES</link> below).</para>
@ -1726,7 +1744,7 @@ MASTER_SITE_SUBDIR= applications</programlisting>
<para>If the patch is not relative to the top of the source tree
(i.e., <makevar>WKRSRC</makevar>) because it
contains some extra pathnames, set <makevar>PATCH_DIST_STRIP</makevar> accordingly.
For instance, if all the pathnames in the patch has an extra
For instance, if all the pathnames in the patch have an extra
<literal>foozolix-1.0/</literal> in front of the
filenames, then set
<literal>PATCH_DIST_STRIP=-p1</literal>.</para>
@ -1978,7 +1996,7 @@ BUILD_DEPENDS= /nonexistent:${PORTSDIR}/graphics/jpeg:extract</programlisting>
other way the behaviour you want can be accomplished. It will
cause the other port to be always build (and installed, by
default), and the dependency will go into the packages as
well. If this is really what you need, I recommend you to
well. If this is really what you need, I recommend you
write it as <literal>BUILD_DEPENDS</literal> and
<literal>RUN_DEPENDS</literal> instead&mdash;at least the
intention will be clear.</para>
@ -2077,7 +2095,7 @@ lib/libtvl80.so.1
<sect2>
<title>ELF support</title>
<para>Since FreeBSD is moving to ELF from 3.0-release onwards,
<para>Since FreeBSD is moving to ELF shortly after 3.0-release,
we need to convert many ports that build shared libraries
to support ELF. Complicating this task is that a 3.0
system can run as both ELF and a.out, and that there will
@ -2778,8 +2796,8 @@ diff -u -r1.15 PLIST
<sect3>
<title><filename>INSTALL</filename></title>
<para>If your port needs execute commands when the binary package is
installed with <command>pkg_add</command> you can do with via the
<para>If your port needs to execute commands when the binary package is
installed with <command>pkg_add</command> you can do this via the
<filename>pkg/INSTALL</filename> script. This script will
automatically be added to the package, and will be run twice by
<command>pkg_add</command>. The first time will as
@ -2796,7 +2814,7 @@ diff -u -r1.15 PLIST
<note>
<para>This script is not run automatically if you install the port
with <command>make install</command>. If you are depending on
it being run, you will have to explicitly call it on your port's
it being run, you will have to explicitly call it from your port's
<filename>Makefile</filename>.</para>
</note>
</sect3>
@ -2862,15 +2880,87 @@ PLIST_SUB= OCTAVE_VERSION=${OCTAVE_VERSION}</programlisting>
<maketarget>post-install</maketarget> to a file named
<makevar>TMPPLIST</makevar>.</para>
</sect3>
<sect3>
<title id="porting-pkgsubdir">Changing the names of files in the
<filename>pkg</filename> subdirectory</title>
<para>All the filenames in the <filename>pkg</filename> subdirectory
are defined using variables so you can change them in your
<filename>Makefile</filename> if need be. This is especially useful when you
are sharing the same <filename>pkg</filename> subdirectory among
several ports or have to write to one of the above files (see
<link linkend="porting-wrkdir">writing to places other than
<makevar>WRKDIR</makevar></link> for why it is a bad idea to
write directly in to the <filename>pkg</filename>
subdirectory.</para>
<para>Here is a list of variable names and their default
values.</para>
<informaltable frame="none">
<tgroup cols="2">
<thead>
<row>
<entry>Variable</entry>
<entry>Default value</entry>
</row>
</thead>
<tbody>
<row>
<entry><makevar>COMMENT</makevar></entry>
<entry><literal>${PKGDIR}/DESCR</literal></entry>
</row>
<row>
<entry><makevar>DESCR</makevar></entry>
<entry><literal>${PKGDIR}/DESCR</literal></entry>
</row>
<row>
<entry><makevar>PLIST</makevar></entry>
<entry><literal>${PKGDIR}/PLIST</literal></entry>
</row>
<row>
<entry><makevar>PKGINSTALL</makevar></entry>
<entry><literal>${PKGDIR}/PKGINSTALL</literal></entry>
</row>
<row>
<entry><makevar>PKGDEINSTALL</makevar></entry>
<entry><literal>${PKGDIR}/PKGDEINSTALL</literal></entry>
</row>
<row>
<entry><makevar>PKGREQ</makevar></entry>
<entry><literal>${PKGDIR}/REQ</literal></entry>
</row>
<row>
<entry><makevar>PKGMESSAGE</makevar></entry>
<entry><literal>${PKGDIR}/MESSAGE</literal></entry>
</row>
</tbody>
</tgroup>
</informaltable>
<para>Please change these variables rather than overriding
<makevar>PKG_ARGS</makevar>. If you change
<makevar>PKG_ARGS</makevar>, those files will not correctly be
installed in <filename>/var/db/pkg</filename> upon install from a
port.</para>
</sect3>
</sect2>
<sect2>
<title>Licensing Problems</title>
<para>Some software packages have restrictive licenses or can be
in violation to the law (PKP's patent on public key crypto, ITAR
(export of crypto software) to name just two of them). What we
can do with them vary a lot, depending on the exact wordings of
can do with them varies a lot, depending on the exact wordings of
the respective licenses.</para>
<note>
@ -3031,6 +3121,35 @@ post-install:
with all the appropriate flags. See below for an example on how
to use them.</para>
</sect3>
<sect3 id="porting-wrkdir">
<title><makevar>WRKDIR</makevar></title>
<para>Do not write anything to files outside
<makevar>WRKDIR</makevar>. <makevar>WRKDIR</makevar> is the only
place that is guaranteed to be writable during the port build (see
<link linkend="ports-cd">compiling ports from CDROM</link> for an
example of building ports from a read-only tree). If you need to
modigy some file in <makevar>PKGDIR</makevar>, do so by <link
linkend="porting-pkgsubdir">redefining a variable</link>, not by
writing over it.</para>
</sect3>
<sect3>
<title><makevar>WRKDIRPREFIX</makevar></title>
<para>Make sure your port honors
<makevar>WRKDIRPREFIX</makevar>. Most ports don't have to worry
about this. In particular, if you are referring to a
<makevar>WRKDIR</makevar> of another port, note that the correct
location is
<filename><makevar>WRKDIRPREFIX</makevar><makevar>PORTSDIR</makevar>/<replaceable>subdir</replaceable>/<replaceable>name</replaceable>/work</filename> not <filename><makevar>PORTSDIR</makevar>/<replaceable>subdir</replaceable>/<replaceable>name</replaceable>/work</filename> or <filename><makevar>.CURDIR</makevar>/../../<replaceable>subdir</replaceable>/<replaceable>name</replaceable>/work</filename> or some such.</para>
<para>Also, if you are defining <makevar>WRKDIR</makevar> yourself,
make sure you prepend
<literal>&dollar;{WKRDIRPREFIX}&dollar;{.CURDIR}</literal> in the
front.</para>
</sect3>
<sect3 id="porting-versions">
<title>Differentiating operating systems and OS versions</title>
@ -3055,7 +3174,7 @@ post-install:
#endif</programlisting>
<para>to the proper place in the <filename>.c</filename> file. We
believe that every system that defines these to symbols has
believe that every system that defines these two symbols has
<filename>sys/param.h</filename>. If you find a system that
doesn't, we would like to know. Please send mail to the
&a.ports;.</para>
@ -3094,7 +3213,7 @@ post-install:
<para>The value of the <literal>BSD</literal> macro is
<literal>199506</literal> for the 4.4BSD-Lite2 code base. This is
stated for informational purposes only. It should not be used to
distinguish between version of FreeBSD based only on 4.4-Lite vs.
distinguish between versions of FreeBSD based only on 4.4-Lite vs.
versions that have merged in changes from 4.4-Lite2. The
<literal>__FreeBSD__</literal> macro should be used
instead.</para>
@ -3315,6 +3434,26 @@ post-install:
<entry>3.0-current after 3.0-RELEASE</entry>
<entry>300006</entry>
</row>
<row>
<entry>3.0-stable after 3/4 branch</entry>
<entry>300007</entry>
</row>
<row>
<entry>3.1-RELEASE</entry>
<entry>310000</entry>
</row>
<row>
<entry>3.1-stable after 3.1-RELEASE</entry>
<entry>310001</entry>
</row>
<row>
<entry>4.0-current after 3/4 branch</entry>
<entry>400000</entry>
</row>
</tbody>
</tgroup>
</informaltable>
@ -3649,8 +3788,8 @@ post-install:
<filename>info</filename> (documentation for info browser)
or <filename>share</filename> (architecture independent
files). See man <citerefentry><refentrytitle>hier</refentrytitle><manvolnum>7</manvolnum></citerefentry> for
details, the rule governing <filename>/usr</filename> pretty
much applies to <filename>/usr/local</filename> too. The
details, the rules governing <filename>/usr</filename> pretty
much apply to <filename>/usr/local</filename> too. The
exception are ports dealing with USENET &ldquo;news&rdquo;. They may use
<filename><makevar>PREFIX</makevar>/news</filename> as a destination for
their files.</para>
@ -4125,6 +4264,11 @@ pre-install:
</thead>
<tbody>
<row>
<entry><filename>afterstep*</filename></entry>
<entry>Ports to support AfterStep window manager</entry>
</row>
<row>
<entry><filename>archivers</filename></entry>
<entry>Archiving tools.</entry>
@ -4290,18 +4434,18 @@ pre-install:
<entry>Ports from the OffiX suite.</entry>
</row>
<row>
<entry><filename>palm</filename></entry>
<entry>Software support for the 3Com Palm(tm) series.</entry>
</row>
<row>
<entry><filename>perl5*</filename></entry>
<entry>Ports that require perl version 5 to run.</entry>
</row>
<row>
<entry><filename>pilot*</filename></entry>
<entry>Software to use with the 3Com PalmPilot.</entry>
</row>
<row>
<entry><filename>plan9</filename></entry>
<entry><filename>plan9*</filename></entry>
<entry>Various programs from Plan9.</entry>
</row>
@ -4387,6 +4531,12 @@ pre-install:
<entry>Vietnamese language support.</entry>
</row>
<row>
<entry><filename>windowmaker*</filename></entry>
<entry>Ports to support the WindowMaker window
manager</entry>
</row>
<row>
<entry><filename>www</filename></entry>
<entry>Software related to the World Wide Web. HTML language

View file

@ -1439,6 +1439,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
as any combination of ranges and/or individual types
separated by commas. Commonly used ICMP types are:
<literal>0</literal> echo reply (ping reply),
<literal>3</literal> destination unreachable,
<literal>5</literal> redirect, <literal>8</literal> echo request (ping request), and
<literal>11</literal> time exceeded (used to
indicate TTL expiration as with

View file

@ -216,10 +216,18 @@
<para>&a.lars;</para>
</listitem>
<listitem>
<para>&.dirk;</para>
</listitem>
<listitem>
<para>&a.billf;</para>
</listitem>
<listitem>
<para>&a.gallatin;</para>
</listitem>
<listitem>
<para>&a.tg;</para>
</listitem>
@ -275,7 +283,11 @@
<listitem>
<para>&a.flathill;</para>
</listitem>
<listitem>
<para>&a.foxfair;</para>
</listitem>
<listitem>
<para>&a.hosokawa;</para>
</listitem>
@ -359,7 +371,11 @@
<listitem>
<para>&a.ken;</para>
</listitem>
<listitem>
<para>&a.hm;</para>
</listitem>
<listitem>
<para>&a.tedm;</para>
</listitem>
@ -380,6 +396,10 @@
<para>&a.alex;</para>
</listitem>
<listitem>
<para>&a.newton;</para>
</listitem>
<listitem>
<para>&a.rnordier;</para>
</listitem>
@ -479,7 +499,11 @@
<listitem>
<para>&a.jseger;</para>
</listitem>
<listitem>
<para>&a.simokawa;</para>
</listitem>
<listitem>
<para>&a.vanilla;</para>
</listitem>
@ -495,7 +519,11 @@
<listitem>
<para>&a.brian;</para>
</listitem>
<listitem>
<para>&a.mks;</para>
</listitem>
<listitem>
<para>&a.stark;</para>
</listitem>
@ -604,7 +632,7 @@
</listitem>
</varlistentry>
<varlistentry><term>Gallery and Commercial Editor</term>
<varlistentry><term>Gallery Editor</term>
<listitem>
<para>&a.nsj;</para>
@ -613,7 +641,23 @@
</listitem>
</varlistentry>
<varlistentry>
<term>Commercial Editor</term>
<listitem>
<para>&a.mbarkah;</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Web Changes Editor</term>
<listitem>
<para>&a.mbarkah;</para>
</listitem>
</varlistentry>
<varlistentry><term>Style Police &amp; Art Director</term>
<listitem>

View file

@ -993,6 +993,10 @@ box can be opened)</para>
URL="http://www.buffnet.net/">BuffNET</ulink></para>
</listitem>
<listitem>
<para><ulink url="http://www.pacificsolutions.com/">Pacific
Solutions</ulink></para>
</listitem>
</itemizedlist>
</listitem>
@ -1235,7 +1239,11 @@ box can be opened)</para>
<listitem>
<para>Anthony Yee-Hang Chan <email>yeehang@netcom.com</email></para>
</listitem>
<listitem>
<para>Anton Berezin <email>tobez@plab.ku.dk</email></para>
</listitem>
<listitem>
<para>Ari Suutari <email>ari@suutari.iki.fi</email></para>
</listitem>
@ -1279,7 +1287,11 @@ box can be opened)</para>
<listitem>
<para>Brian Clapper <email>bmc@willscreek.com</email></para>
</listitem>
<listitem>
<para>Brian F. Feldman <email>green@unixhelp.org</email></para>
</listitem>
<listitem>
<para>Brian Handy <email>handy@lambic.space.lockheed.com</email></para>
</listitem>
@ -1460,7 +1472,11 @@ box can be opened)</para>
<listitem>
<para>Dean Huxley <email>dean@fsa.ca</email></para>
</listitem>
<listitem>
<para>Dima Sivachenko <email>demon@gpad.ac.ru</email></para>
</listitem>
<listitem>
<para>Dirk Froemberg <email>dirk@hal.in-berlin.de</email></para>
</listitem>
@ -1611,14 +1627,14 @@ box can be opened)</para>
<para>Hidekazu Kuroki <email>hidekazu@cs.titech.ac.jp</email></para>
</listitem>
<listitem>
<para>Hidetoshi Shimokawa <email>simokawa@sat.t.u-tokyo.ac.jp</email></para>
</listitem>
<listitem>
<para>Hideyuki Suzuki <email>hideyuki@sat.t.u-tokyo.ac.jp</email></para>
</listitem>
<listitem>
<para>Hiroaki Sakai <email>sakai@miya.ee.kagu.sut.ac.jp</email></para>
</listitem>
<listitem>
<para>Hironori Ikura <email>hikura@kaisei.org</email></para>
</listitem>
@ -1742,7 +1758,10 @@ box can be opened)</para>
<listitem>
<para>Jim Lowe <email>james@cs.uwm.edu</email></para>
</listitem>
<listitem>
<para>Jim Mock <email>jim@phrantic.phear.net</email></para>
</listitem>
<listitem>
<para>Jim Wilson <email>wilson@moria.cygnus.com</email></para>
</listitem>
@ -1756,6 +1775,10 @@ box can be opened)</para>
<para>Joao Carlos Mendes Luis <email>jonny@coppe.ufrj.br</email></para>
</listitem>
<listitem>
<para>Joe Abley <email>jabley@clear.co.nz</email></para>
</listitem>
<listitem>
<para>Joe &ldquo;Marcus&rdquo; Clarke
<email>marcus@miami.edu</email></para>
@ -1893,7 +1916,11 @@ box can be opened)</para>
<listitem>
<para>Kostya Lukin <email>lukin@okbmei.msk.su</email></para>
</listitem>
<listitem>
<para>KUNISHIMA Takeo <email>kunishi@c.oka-pu.ac.jp</email></para>
</listitem>
<listitem>
<para>Kurt Olsen <email>kurto@tiny.mcs.usu.edu</email></para>
</listitem>
@ -1914,7 +1941,11 @@ box can be opened)</para>
<listitem>
<para>Luigi Rizzo <email>luigi@iet.unipi.it</email></para>
</listitem>
<listitem>
<para>Malte Lance <email>malte.lance@gmx.net</email></para>
</listitem>
<listitem>
<para>Makoto MATSUSHITA <email>matusita@jp.freebsd.org</email></para>
</listitem>
@ -1923,6 +1954,10 @@ box can be opened)</para>
<para>Makoto WATANABE
<email>watanabe@zlab.phys.nagoya-u.ac.jp</email></para>
</listitem>
<listitem>
<para>MANTANI Nobutaka <email>nobutaka@nobutaka.com</email></para>
</listitem>
<listitem>
<para>Manu Iyengar <email>iyengar@grunthos.pscwa.psca.com</email></para>
@ -2055,6 +2090,10 @@ box can be opened)</para>
<listitem>
<para>Motoyuki Kasahara <email>m-hasahr@sra.co.jp</email></para>
</listitem>
<listitem>
<para>Munechika Sumikawa <email>sumikawa@kame.net</email></para>
</listitem>
<listitem>
<para>Murray Stokely <email>murray@cdrom.com</email></para>
@ -2095,7 +2134,11 @@ box can be opened)</para>
<listitem>
<para>Nobuyuki Koganemaru <email>kogane@kces.koganemaru.co.jp</email></para>
</listitem>
<listitem>
<para>Norio Suzuki <email>nosuzuki@e-mail.ne.jp</email></para>
</listitem>
<listitem>
<para>Noritaka Ishizumi <email>graphite@jp.FreeBSD.ORG</email></para>
</listitem>
@ -2115,7 +2158,11 @@ box can be opened)</para>
<listitem>
<para>Oliver Oberdorf <email>oly@world.std.com</email></para>
</listitem>
<listitem>
<para>Palle Girgensohn <email>girgen@partitur.se</email></para>
</listitem>
<listitem>
<para>Paul Fox <email>pgf@foxharp.boston.ma.us</email></para>
</listitem>
@ -2256,6 +2303,10 @@ box can be opened)</para>
<para>Satoshi Taoka <email>taoka@infonets.hiroshima-u.ac.jp</email></para>
</listitem>
<listitem>
<para>Satsuki FUJISHIMA <email>k5@respo.or.jp</email></para>
</listitem>
<listitem>
<para>Scot W. Hetzel <email>hetzels@westbend.net</email></para>
</listitem>
@ -2273,10 +2324,6 @@ box can be opened)</para>
<email>tanimura@naklab.dnj.ynu.ac.jp</email></para>
</listitem>
<listitem>
<para>Seiichirou Hiraoka <email>flathill@flathill.gr.jp</email></para>
</listitem>
<listitem>
<para>Serge Babkin <email>babkin@hq.icb.chel.su</email></para>
</listitem>
@ -2351,6 +2398,10 @@ box can be opened)</para>
<para>Stuart Henderson
<email>stuart@internationalschool.co.uk</email></para>
</listitem>
<listitem>
<para>SUGIMURA Takashi <email>sugimura@jp.FreeBSD.ORG</email></para>
</listitem>
<listitem>
<para>Suzuki Yoshiaki <email>zensyo@ann.tama.kawasaki.jp</email></para>
@ -2416,6 +2467,10 @@ box can be opened)</para>
<para>Tim Wilkinson <email>tim@sarc.city.ac.uk</email></para>
</listitem>
<listitem>
<para>Tom Hukins <email>tom@eborcom.com</email></para>
</listitem>
<listitem>
<para>Tom Jobbins <email>tom@tom.tj</email></para>
</listitem>
@ -2439,7 +2494,11 @@ box can be opened)</para>
<listitem>
<para>Trefor S. <email>trefor@flevel.co.uk</email></para>
</listitem>
<listitem>
<para>Vadim Chekan <email>vadim@gc.lviv.ua</email></para>
</listitem>
<listitem>
<para>Ville Eerola <email>ve@sci.fi</email></para>
</listitem>
@ -2485,7 +2544,7 @@ box can be opened)</para>
</listitem>
<listitem>
<para>Yukihiro Nakai <email>nakai@technologist.com</email></para>
<para>Yukihiro Nakai <email>nakai@iname.com</email></para>
</listitem>
<listitem>

View file

@ -7,7 +7,7 @@
Please keep this list in alphabetical order by entity names.
$Id: authors.ent,v 1.4 1998-12-10 20:43:39 nik Exp $
$Id: authors.ent,v 1.5 1999-01-29 22:33:55 nik Exp $
-->
<!ENTITY a.abial "Andrzej Bialecki <email>abial@FreeBSD.ORG</email>">
@ -70,6 +70,8 @@
<!ENTITY a.dima "Dima Ruban <email>dima@FreeBSD.ORG</email>">
<!ENTITY a.dirk "Dirk Fr&ouml;mberg <email>dirk@FreeBSD.ORG</email>">
<!ENTITY a.dirkvangulik "Dirk-Willem van Gulik <email>Dirk.vanGulik@jrc.it</email>">
<!ENTITY a.dt "Dmitrij Tejblum <email>dt@FreeBSD.ORG</email>">
@ -92,8 +94,12 @@
<!ENTITY a.flathill "Seiichirou Hiraoka <email>flathill@FreeBSD.ORG</email>">
<!ENTITY a.foxfair "Howard F. Hu <email>foxfair@FreeBSD.ORG</email>">
<!ENTITY a.fsmp "Steve Passe <email>fsmp@FreeBSD.ORG</email>">
<!ENTITY a.gallatin "Andrew Gallatin <email>gallatin@FreeBSD.ORG</email>">
<!ENTITY a.gclarkii "Gary Clark II <email>gclarkii@FreeBSD.ORG</email>">
<!ENTITY a.gena "Gennady B. Sorokopud <email>gena@NetVision.net.il</email>">
@ -122,7 +128,7 @@
<!ENTITY a.helbig "Wolfgang Helbig <email>helbig@FreeBSD.ORG</email>">
<!ENTITY a.hm "Hellmuth Michaelis <email>hm@kts.org</email>">
<!ENTITY a.hm "Hellmuth Michaelis <email>hm@FreeBSD.ORG</email>">
<!ENTITY a.hoek "Tim Vanderhoek <email>hoek@FreeBSD.ORG</email>">
@ -212,6 +218,8 @@
<!ENTITY a.md "Mark Dapoz <email>md@bsc.no</email>">
<!ENTITY a.mks "Mike Spengler <email>mks@FreeBSD.ORG</email>">
<!ENTITY a.motoyuki "Motoyuki Konno <email>motoyuki@FreeBSD.ORG</email>">
<!ENTITY a.mph "Matthew Hunt <email>mph@FreeBSD.ORG</email>">
@ -224,6 +232,8 @@
<!ENTITY a.nectar "Jacques Vidrine <email>nectar@FreeBSD.ORG</email>">
<!ENTITY a.newton "Mark Newton <email>newton@FreeBSD.ORG</email>">
<!ENTITY a.nhibma "Nick Hibma <email>n_hibma@FreeBSD.ORG</email>">
<!ENTITY a.nik "Nik Clayton <email>nik@FreeBSD.ORG</email>">
@ -274,6 +284,8 @@
<!ENTITY a.sef "Sean Eric Fagan <email>sef@FreeBSD.ORG</email>">
<!ENTITY a.simokawa "Hidetoshi Shimokawa <email>simokawa@FreeBSD.ORG</email>">
<!ENTITY a.smace "Scott Mace <email>smace@FreeBSD.ORG</email>">
<!ENTITY a.smpatel "Sujal Patel <email>smpatel@FreeBSD.ORG</email>">

View file

@ -51,9 +51,16 @@
</listitem>
<listitem>
<para>FreeBSD mit Methode (in German), publiched by Computer und
Literatur Verlag/Vertrieb Hanser, 1998. ISBN 3-93211-31-0.</para>
<para>FreeBSD mit Methode (in German), published by Computer und
Literatur Verlag/Vertrieb Hanser, 1998. ISBN 3-932311-31-0.</para>
</listitem>
<listitem>
<para><ulink url="http://www.pc.mycom.co.uk/FreeBSD/install-manual.html">FreeBSD
Install and Utilization Manual</ulink> (in Japanese),
published by <ulink url="http://www.pc.mycom.co.jp/">Mainichi
Communications Inc.</ulink>.</para>
</listitem>
</itemizedlist>
@ -111,7 +118,16 @@
University</ulink> has written a <ulink
URL="http://www-wks.acs.ohio-state.edu/unix_course/unix.html">UNIX Introductory Course</ulink> which is available online in HTML and postscript format.</para>
</listitem>
<listitem>
<para><ulink url="http://www.jp.FreeBSD.ORG/">Jpman Project,
Japan FreeBSD Users Group</ulink>. <ulink
url="http://www.pc.mycom.co.jp/FreeBSD/urm.html">FreeBSD
User's Reference Manual</ulink> (Japanese translation).
<ulink url="http://www.pc.mycom.co.jp/">Mainichi
Communications Inc.</ulink>, 1998. ISBN4-8399-0088-4
P3800E.</para>
</listitem>
</itemizedlist>
@ -164,7 +180,16 @@
O'Reilly &amp; Associates, Inc., 1991. <!-- <br> --> ISBN
0-937175-75-7</para>
</listitem>
<listitem>
<para><ulink url="http://www.jp.FreeBSD.ORG/">Jpman Project,
Japan FreeBSD Users Group</ulink>. <ulink
url="http://www.pc.mycom.co.jp/FreeBSD/sam.html">FreeBSD
System Administrator's Manual</ulink> (Japanese translation).
<ulink url="http://www.pc.mycom.co.jp/">Mainichi
Communications Inc.</ulink>, 1998. ISBN4-8399-0109-0
P3300E.</para>
</listitem>
</itemizedlist>

View file

@ -35,13 +35,13 @@
manual is a <emphasis>work in progress</emphasis> and is the work of
many individuals. Many sections do not yet exist and some of those
that do exist need to be updated. If you are interested in helping
with this project, send email to the &a.doc; The latest version of
with this project, send email to the &a.doc;. The latest version of
this document is always available from the <ulink
URL="http://www.FreeBSD.ORG/">FreeBSD World Wide Web server</ulink>.
It may also be downloaded in <ulink url="handbook.latin1">plain
text</ulink>, <ulink url="handbook.ps">postscript</ulink> or <ulink
url="handbook-html.tar.gz">HTML</ulink> with HTTP or gzip'd from the <ulink
url="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/docs/">FreeBSD FTP server</ulink> or one of the numerous <link
url="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/doc/">FreeBSD FTP server</ulink> or one of the numerous <link
linkend="mirrors-ftp">mirror sites</link>. You may also want to
<ulink URL="http://www.FreeBSD.ORG/search.html">Search the Handbook</ulink>.</para>
</abstract>
@ -103,6 +103,7 @@ url="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/docs/">FreeBSD FTP server</ulink> or one
</book>
<!--
Local Variables:
mode: sgml
sgml-indent-data: t
sgml-omittag: nil

View file

@ -993,6 +993,10 @@ box can be opened)</para>
URL="http://www.buffnet.net/">BuffNET</ulink></para>
</listitem>
<listitem>
<para><ulink url="http://www.pacificsolutions.com/">Pacific
Solutions</ulink></para>
</listitem>
</itemizedlist>
</listitem>
@ -1235,7 +1239,11 @@ box can be opened)</para>
<listitem>
<para>Anthony Yee-Hang Chan <email>yeehang@netcom.com</email></para>
</listitem>
<listitem>
<para>Anton Berezin <email>tobez@plab.ku.dk</email></para>
</listitem>
<listitem>
<para>Ari Suutari <email>ari@suutari.iki.fi</email></para>
</listitem>
@ -1279,7 +1287,11 @@ box can be opened)</para>
<listitem>
<para>Brian Clapper <email>bmc@willscreek.com</email></para>
</listitem>
<listitem>
<para>Brian F. Feldman <email>green@unixhelp.org</email></para>
</listitem>
<listitem>
<para>Brian Handy <email>handy@lambic.space.lockheed.com</email></para>
</listitem>
@ -1460,7 +1472,11 @@ box can be opened)</para>
<listitem>
<para>Dean Huxley <email>dean@fsa.ca</email></para>
</listitem>
<listitem>
<para>Dima Sivachenko <email>demon@gpad.ac.ru</email></para>
</listitem>
<listitem>
<para>Dirk Froemberg <email>dirk@hal.in-berlin.de</email></para>
</listitem>
@ -1611,14 +1627,14 @@ box can be opened)</para>
<para>Hidekazu Kuroki <email>hidekazu@cs.titech.ac.jp</email></para>
</listitem>
<listitem>
<para>Hidetoshi Shimokawa <email>simokawa@sat.t.u-tokyo.ac.jp</email></para>
</listitem>
<listitem>
<para>Hideyuki Suzuki <email>hideyuki@sat.t.u-tokyo.ac.jp</email></para>
</listitem>
<listitem>
<para>Hiroaki Sakai <email>sakai@miya.ee.kagu.sut.ac.jp</email></para>
</listitem>
<listitem>
<para>Hironori Ikura <email>hikura@kaisei.org</email></para>
</listitem>
@ -1742,7 +1758,10 @@ box can be opened)</para>
<listitem>
<para>Jim Lowe <email>james@cs.uwm.edu</email></para>
</listitem>
<listitem>
<para>Jim Mock <email>jim@phrantic.phear.net</email></para>
</listitem>
<listitem>
<para>Jim Wilson <email>wilson@moria.cygnus.com</email></para>
</listitem>
@ -1756,6 +1775,10 @@ box can be opened)</para>
<para>Joao Carlos Mendes Luis <email>jonny@coppe.ufrj.br</email></para>
</listitem>
<listitem>
<para>Joe Abley <email>jabley@clear.co.nz</email></para>
</listitem>
<listitem>
<para>Joe &ldquo;Marcus&rdquo; Clarke
<email>marcus@miami.edu</email></para>
@ -1893,7 +1916,11 @@ box can be opened)</para>
<listitem>
<para>Kostya Lukin <email>lukin@okbmei.msk.su</email></para>
</listitem>
<listitem>
<para>KUNISHIMA Takeo <email>kunishi@c.oka-pu.ac.jp</email></para>
</listitem>
<listitem>
<para>Kurt Olsen <email>kurto@tiny.mcs.usu.edu</email></para>
</listitem>
@ -1914,7 +1941,11 @@ box can be opened)</para>
<listitem>
<para>Luigi Rizzo <email>luigi@iet.unipi.it</email></para>
</listitem>
<listitem>
<para>Malte Lance <email>malte.lance@gmx.net</email></para>
</listitem>
<listitem>
<para>Makoto MATSUSHITA <email>matusita@jp.freebsd.org</email></para>
</listitem>
@ -1923,6 +1954,10 @@ box can be opened)</para>
<para>Makoto WATANABE
<email>watanabe@zlab.phys.nagoya-u.ac.jp</email></para>
</listitem>
<listitem>
<para>MANTANI Nobutaka <email>nobutaka@nobutaka.com</email></para>
</listitem>
<listitem>
<para>Manu Iyengar <email>iyengar@grunthos.pscwa.psca.com</email></para>
@ -2055,6 +2090,10 @@ box can be opened)</para>
<listitem>
<para>Motoyuki Kasahara <email>m-hasahr@sra.co.jp</email></para>
</listitem>
<listitem>
<para>Munechika Sumikawa <email>sumikawa@kame.net</email></para>
</listitem>
<listitem>
<para>Murray Stokely <email>murray@cdrom.com</email></para>
@ -2095,7 +2134,11 @@ box can be opened)</para>
<listitem>
<para>Nobuyuki Koganemaru <email>kogane@kces.koganemaru.co.jp</email></para>
</listitem>
<listitem>
<para>Norio Suzuki <email>nosuzuki@e-mail.ne.jp</email></para>
</listitem>
<listitem>
<para>Noritaka Ishizumi <email>graphite@jp.FreeBSD.ORG</email></para>
</listitem>
@ -2115,7 +2158,11 @@ box can be opened)</para>
<listitem>
<para>Oliver Oberdorf <email>oly@world.std.com</email></para>
</listitem>
<listitem>
<para>Palle Girgensohn <email>girgen@partitur.se</email></para>
</listitem>
<listitem>
<para>Paul Fox <email>pgf@foxharp.boston.ma.us</email></para>
</listitem>
@ -2256,6 +2303,10 @@ box can be opened)</para>
<para>Satoshi Taoka <email>taoka@infonets.hiroshima-u.ac.jp</email></para>
</listitem>
<listitem>
<para>Satsuki FUJISHIMA <email>k5@respo.or.jp</email></para>
</listitem>
<listitem>
<para>Scot W. Hetzel <email>hetzels@westbend.net</email></para>
</listitem>
@ -2273,10 +2324,6 @@ box can be opened)</para>
<email>tanimura@naklab.dnj.ynu.ac.jp</email></para>
</listitem>
<listitem>
<para>Seiichirou Hiraoka <email>flathill@flathill.gr.jp</email></para>
</listitem>
<listitem>
<para>Serge Babkin <email>babkin@hq.icb.chel.su</email></para>
</listitem>
@ -2351,6 +2398,10 @@ box can be opened)</para>
<para>Stuart Henderson
<email>stuart@internationalschool.co.uk</email></para>
</listitem>
<listitem>
<para>SUGIMURA Takashi <email>sugimura@jp.FreeBSD.ORG</email></para>
</listitem>
<listitem>
<para>Suzuki Yoshiaki <email>zensyo@ann.tama.kawasaki.jp</email></para>
@ -2416,6 +2467,10 @@ box can be opened)</para>
<para>Tim Wilkinson <email>tim@sarc.city.ac.uk</email></para>
</listitem>
<listitem>
<para>Tom Hukins <email>tom@eborcom.com</email></para>
</listitem>
<listitem>
<para>Tom Jobbins <email>tom@tom.tj</email></para>
</listitem>
@ -2439,7 +2494,11 @@ box can be opened)</para>
<listitem>
<para>Trefor S. <email>trefor@flevel.co.uk</email></para>
</listitem>
<listitem>
<para>Vadim Chekan <email>vadim@gc.lviv.ua</email></para>
</listitem>
<listitem>
<para>Ville Eerola <email>ve@sci.fi</email></para>
</listitem>
@ -2485,7 +2544,7 @@ box can be opened)</para>
</listitem>
<listitem>
<para>Yukihiro Nakai <email>nakai@technologist.com</email></para>
<para>Yukihiro Nakai <email>nakai@iname.com</email></para>
</listitem>
<listitem>

View file

@ -111,18 +111,19 @@
<para>Join the &a.current; and the &a.cvsall; . This is not
just a good idea, it is <emphasis>essential</emphasis>. If
you are not on the <emphasis>FreeBSD-current</emphasis>
mailing list you will not see the comments that people are
mailing list, you will not see the comments that people are
making about the current state of the system and thus will
probably end up stumbling over a lot of problems that others
have already found and solved. Even more importantly, you
will miss out on potentially critical information (e.g.
&ldquo;Yo, Everybody! Before you rebuild
<filename>/usr/src</filename>, you <emphasis>must</emphasis>
rebuild the kernel or your system will crash horribly!&rdquo;).
The <email>cvs-all</email> mailing list will allow you
will miss out on important bulletins which may be critical
to your system's continued health.</para>
<para>The <email>cvs-all</email> mailing list will allow you
to see the commit log entry for each change as it is made
along with any pertinent information on possible
side-effects. To join these lists, send mail to
side-effects.</para>
<para>To join these lists, send mail to
&a.majordomo; and specify:
<programlisting>
@ -151,7 +152,13 @@ subscribe cvs-all</programlisting>
<listitem>
<para>Use the <link linkend="cvsup">cvsup</link>
program with <ulink
URL="ftp://ftp.freebsd.org/pub/FreeBSD/FreeBSD-current/src/share/examples/cvsup/standard-supfile">this supfile</ulink>. This is the second most recommended method, since it allows you to grab the entire collection once and then only what has changed from then on. Many people run cvsup from cron and keep their sources up-to-date automatically.</para>
URL="ftp://ftp.freebsd.org/pub/FreeBSD/FreeBSD-current/src/share/examples/cvsup/standard-supfile">this supfile</ulink>. This is the second most recommended method, since it allows you to grab the entire collection once and then only what has changed from then on. Many people run cvsup from cron and keep their sources up-to-date automatically. For a fairly easy interface to this, simply type:</para>
<informalexample>
<screen>&prompt.root; <userinput>pkg_add -f ftp://ftp.freebsd.org/pub/FreeBSD/CVSup/cvsupit.tgz</userinput></screen>
</informalexample>
</listitem>
<listitem>
@ -182,18 +189,14 @@ subscribe cvs-all</programlisting>
<para>Essentially, if you need rapid on-demand access to the
source and communications bandwidth is not a consideration,
use <command>cvsup</command> or <command>ftp</command>. Otherwise, use <application>CTM</application>.</para>
</listitem>
<listitem>
<para>If you are grabbing the sources to run, and not just
look at, then grab <emphasis>all</emphasis> of current, not
just selected portions. The reason for this is that various
parts of the source depend on updates elsewhere, and trying
to compile just a subset is almost guaranteed to get you
into trouble.</para>
</listitem>
<listitem>
<para>Before compiling current, read the Makefile in
<filename>/usr/src</filename> carefully. You should at
least run a <link
@ -201,7 +204,7 @@ subscribe cvs-all</programlisting>
through as part of the upgrading process. Reading the
&a.current; will keep you up-to-date on other bootstrapping
procedures that sometimes become necessary as we move
towards the next release.</para>
towards the next release.</para>
</listitem>
<listitem>
@ -270,14 +273,25 @@ subscribe cvs-all</programlisting>
in this mailing list when they are contemplating some
controversial fix or update, giving the users a chance to
respond if they have any issues to raise concerning the
proposed change. To join this list, send mail to
&a.majordomo; and say:
proposed change.</para>
<para>The <email>cvs-all</email> mailing list will allow you
to see the commit log entry for each change as it is made
along with any pertinent information on possible
side-effects.</para>
<para>To join these lists, send mail to
&a.majordomo; and specify:
<programlisting>
subscribe freebsd-stable</programlisting> In the body of your
message. Optionally, you can also say <literal>help</literal> and Majordomo
will send you full help on how to subscribe and unsubscribe
to the various other mailing lists we support.</para>
subscribe freebsd-stable
subscribe cvs-all</programlisting>
in the
body of your message. Optionally, you can also say <literal>help</literal>
and Majordomo will send you full help on how to subscribe
and unsubscribe to the various other mailing lists we
support.</para>
</listitem>
<listitem>
@ -514,12 +528,21 @@ subscribe freebsd-stable</programlisting> In the body of your
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_3</term>
<listitem>
<para>The line of development for FreeBSD-3.x, also known as
FreeBSD-stable. Not valid for the ports collection.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_2_2</term>
<listitem>
<para>The line of development for FreeBSD-2.2.x, also known as
FreeBSD-stable. Not valid for the ports collection.</para>
2.2-stable. Not valid for the ports collection.</para>
</listitem>
</varlistentry>
@ -1365,17 +1388,25 @@ cvs-crypto</programlisting>
</note>
</listitem>
</varlistentry>
<varlistentry><term>tag=RELENG_2_2</term>
<listitem>
<para>The line of development for FreeBSD-2.2.x,
also known as FreeBSD-stable. Not valid for the
ports-* collections.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_3</term>
<listitem>
<para>The line of development for FreeBSD-3.x, also known as
FreeBSD-stable. Not valid for the ports collection.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_2_2</term>
<listitem>
<para>The line of development for FreeBSD-2.2.x, also known as
2.2-stable. Not valid for the ports collection.</para>
</listitem>
</varlistentry>
<varlistentry><term>tag=RELENG_2_1_0</term>
<listitem>

View file

@ -88,12 +88,6 @@
FreeBSD-current</entry>
</row>
<row>
<entry>freebsd-stable</entry>
<entry>Discussion concerning the use of
FreeBSD-stable</entry>
</row>
<row>
<entry>freebsd-isp</entry>
<entry>Issues for Internet Service Providers using
@ -113,8 +107,15 @@
<row>
<entry>freebsd-questions</entry>
<entry>User questions</entry>
<entry>User questions and technical support</entry>
</row>
<row>
<entry>freebsd-stable</entry>
<entry>Discussion concerning the use of
FreeBSD-stable</entry>
</row>
</tbody>
</tgroup>
</informaltable>
@ -146,7 +147,7 @@
<row>
<entry>freebsd-doc</entry>
<entry>The FreeBSD Documentation project</entry>
<entry>Creating FreeBSD related documents</entry>
</row>
<row>
@ -608,33 +609,17 @@ help
</listitem>
</varlistentry>
<varlistentry><term>FREEBSD-STABLE</term>
<listitem>
<para><emphasis>Discussions about the use of
FreeBSD-stable</emphasis></para>
<para>This is the
mailing list for users of freebsd-stable. It includes
warnings about new features coming out in -stable that
will affect the users, and instructions on steps that must
be taken to remain -stable. Anyone running &ldquo;stable&rdquo;
should subscribe to this list. This is a technical mailing
list for which strictly technical content is
expected.</para>
</listitem>
</varlistentry>
<varlistentry><term>FREEBSD-DOC</term>
<listitem>
<para><emphasis>Documentation project</emphasis></para>
<para>This mailing list is for the discussion of documentation
related issues and projects. The members of this mailing list
are collectively referred to as &ldquo;The FreeBSD
Documentation Project&rdquo;. It is an open list; feel free to
join and contribute.</para>
<para>This mailing list is for the discussion of issues and
projects related to the creation of documenation for
FreeBSD. The members of this mailing list are collectively
referred to as &ldquo;The FreeBSD Documentation
Project&rdquo;. It is an open list; feel free to join and
contribute!</para>
</listitem>
</varlistentry>
@ -855,7 +840,24 @@ help
</listitem>
</varlistentry>
<varlistentry><term>FREEBSD-USER-GROUPS</term>
<varlistentry><term>FREEBSD-STABLE</term>
<listitem>
<para><emphasis>Discussions about the use of
FreeBSD-stable</emphasis></para>
<para>This is the
mailing list for users of freebsd-stable. It includes
warnings about new features coming out in -stable that
will affect the users, and instructions on steps that must
be taken to remain -stable. Anyone running &ldquo;stable&rdquo;
should subscribe to this list. This is a technical mailing
list for which strictly technical content is
expected.</para>
</listitem>
</varlistentry>
<varlistentry><term>FREEBSD-USER-GROUPS</term>
<listitem>
<para><emphasis>User Group Coordination
@ -1045,27 +1047,52 @@ help
<listitem>
<para><ulink
URL="http://www.au.freebsd.org/FreeBSD/">http://www.au.freebsd.org/FreeBSD/</ulink> &mdash; Australia.</para>
URL="http://www.au.freebsd.org/FreeBSD/">http://www.au.freebsd.org/FreeBSD/</ulink> &mdash; Australia/1.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www2.au.freebsd.org/FreeBSD/">http://www2.au.freebsd.org/FreeBSD/</ulink> &mdash; Australia/2.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www3.au.freebsd.org/FreeBSD/">http://www3.au.freebsd.org/FreeBSD/</ulink> &mdash; Australia/3.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.br.freebsd.org/www.freebsd.org/">http://www.br.freebsd.org/www.freebsd.org/</ulink> &mdash; Brazil/1.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.br.freebsd.org/">http://www.br.freebsd.org/</ulink> &mdash; Brazil.</para>
URL="http://www.br2.freebsd.org/www.freebsd.org/">http://www.br2.freebsd.org/www.freebsd.org/</ulink> &mdash; Brazil/2.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.ca.freebsd.org/">http://www.ca.freebsd.org/</ulink> &mdash; Canada.</para>
URL="http://www3.br.freebsd.org/">http://www3.br.freebsd.org/</ulink> &mdash; Brazil/3.</para>
</listitem>
<listitem>
<para><ulink
URL="http://sunsite.mff.cuni.cz/www.freebsd.org/">http://sunsite.mff.cuni.cz/www.freebsd.org/</ulink> &mdash; Czech Republic.</para>
URL="http://www.bg.freebsd.org/">http://www.bg.freebsd.org/</ulink> &mdash; Bulgaria.</para>
</listitem>
<listitem>
<para><ulink
URL="http://sunsite.auc.dk/www.freebsd.org/">http://sunsite.auc.dk/www.freebsd.org/</ulink> &mdash; Denmark.</para>
URL="http://www.ca.freebsd.org/">http://www.ca.freebsd.org/</ulink> &mdash; Canada/1.</para>
</listitem>
<listitem>
<para><ulink
URL="http://freebsd.kawartha.com/">http://freebsd.kawartha.com/</ulink> &mdash; Canada/2.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.dk.freebsd.org/">http://www.dk.freebsd.org/</ulink> &mdash; Denmark.</para>
</listitem>
<listitem>
@ -1077,10 +1104,35 @@ help
<para><ulink
URL="http://www.fi.freebsd.org/">http://www.fi.freebsd.org/</ulink> &mdash; Finland.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.fr.freebsd.org/">http://www.fr.freebsd.org/</ulink> &mdash; France.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.de.freebsd.org/">http://www.de.freebsd.org/</ulink> &mdash; Germany/1.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.de.freebsd.org/">http://www.de.freebsd.org/</ulink> &mdash; Germany.</para>
URL="http://www1.de.freebsd.org/">http://www1.de.freebsd.org/</ulink> &mdash; Germany/2.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www2.de.freebsd.org/">http://www.de.freebsd.org/</ulink> &mdash; Germany/3.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.hu.freebsd.org/">http://www.hu.freebsd.org/</ulink> &mdash; Hungary.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.is.freebsd.org/">http://www.is.freebsd.org/</ulink> &mdash; Iceland.</para>
</listitem>
<listitem>
@ -1090,7 +1142,7 @@ help
<listitem>
<para><ulink
URL="http://www.jp.freebsd.org/">http://www.jp.freebsd.org/</ulink> &mdash; Japan.</para>
URL="http://www.jp.freebsd.org/www.freebsd.org/">http://www.jp.freebsd.org/www.freebsd.org/</ulink> &mdash; Japan.</para>
</listitem>
<listitem>
@ -1098,6 +1150,16 @@ help
URL="http://www.kr.freebsd.org/">http://www.kr.freebsd.org/</ulink> &mdash; Korea.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.lv.freebsd.org/">http://www.lv.freebsd.org/</ulink> &mdash; Latvia.</para>
</listitem>
<listitem>
<para><ulink
URL="http://rama.asiapac.net/freebsd/">http://rama.asiapac.net/freebsd/</ulink> &mdash; Malaysia.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.nl.freebsd.org/">http://www.nl.freebsd.org/</ulink> &mdash; Netherlands.</para>
@ -1105,7 +1167,67 @@ help
<listitem>
<para><ulink
URL="http://www.pt.freebsd.org/">http://www.pt.freebsd.org/</ulink> &mdash; Portugal.</para>
URL="http://www.no.freebsd.org/">http://www.no.freebsd.org/</ulink> &mdash; Norway.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.pt.freebsd.org/">http://www.pt.freebsd.org/</ulink> &mdash; Portugal/1.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www2.pt.freebsd.org/">http://www2.pt.freebsd.org/</ulink> &mdash; Portugal/2.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www3.pt.freebsd.org/">http://www3.pt.freebsd.org/</ulink> &mdash; Portugal/3.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.ro.freebsd.org/">http://www.ro.freebsd.org/</ulink> &mdash; Romania.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.ru.freebsd.org/">http://www.ru.freebsd.org/</ulink> &mdash; Russia/1.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www2.ru.freebsd.org/">http://www2.ru.freebsd.org/</ulink> &mdash; Russia/2.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www3.ru.freebsd.org/">http://www3.ru.freebsd.org/</ulink> &mdash; Russia/3.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.sk.freebsd.org/">http://www.sk.freebsd.org/</ulink> &mdash; Slovak Republic.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.si.freebsd.org/">http://www.si.freebsd.org/</ulink> &mdash; Slovenia.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.es.freebsd.org/">http://www.es.freebsd.org/</ulink> &mdash; Spain.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.za.freebsd.org/">http://www.za.freebsd.org/</ulink> &mdash; South Africa/1.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www2.za.freebsd.org/">http://www2.za.freebsd.org/</ulink> &mdash; South Africa/2.</para>
</listitem>
<listitem>
@ -1115,14 +1237,38 @@ help
<listitem>
<para><ulink
URL="http://www.tw.freebsd.org/freebsd.html">http://www.tw.freebsd.org/freebsd.html</ulink> &mdash; Taiwan.</para>
URL="http://www.tr.freebsd.org/">http://www.tr.freebsd.org/</ulink> &mdash; Turkey.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www2.ua.freebsd.org/">http://www2.ua.freebsd.org/</ulink> &mdash; Ukraine.</para>
URL="http://www.ua.freebsd.org/">http://www.ua.freebsd.org/</ulink> &mdash; Ukraine/1.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www2.ua.freebsd.org/">http://www2.ua.freebsd.org/</ulink> &mdash; Ukraine/2.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.uk.freebsd.org/">http://www.uk.freebsd.org/</ulink> &mdash; United Kingdom.</para>
</listitem>
<listitem>
<para><ulink
URL="http://freebsd.advansys.net/">http://freebsd.advansys.net/</ulink> &mdash; USA/Indiana.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www6.freebsd.org/">http://www6.freebsd.org/</ulink> &mdash; USA/Oregon.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www2freebsd.org/">http://www2.freebsd.org/</ulink> &mdash; USA/Texas.</para>
</listitem>
</itemizedlist>

View file

@ -349,13 +349,17 @@
first full release (2.2.1) was released in April, 1997. Further
releases along the 2.2 branch were done in the Summer and Fall of
'97, the latest being 2.2.7 which appeared in late July of '98.
The first official 3.0 release will appear in October, 1998 and the
last release on the 2.2 branch, 2.2.8, will appear in November.</para>
<para>Long term development projects for everything from SMP to DEC
ALPHA support will continue to take place in the 3.0-current branch
and SNAPshot releases of 3.0 on CDROM (and, of course, on the net).</para>
The first official 3.0 release appeared in October, 1998 and the
last release on the 2.2 branch, 2.2.8, appeared in November,
1998.</para>
<para>The tree branched again on Jan 20, 1999. This led to
4.0-current and a 3.x-stable branch, from which 3.1 will be
released on February 15th, 1999.</para>
<para>Long term development projects will continue to take place in
the 4.0-current branch and SNAPshot releases of 4.0 on CDROM (and,
of course, on the net).</para>
</sect1>
<sect1 id="goals">

View file

@ -73,9 +73,11 @@
<note>
<para>If there is <emphasis>not</emphasis> a
<filename>/usr/src/sys</filename> directory on your system, then
the kernel source has not been been installed. Follow the
instructions for installing packages to add this package to your
system.</para>
the kernel source has not been been installed. The easiest way
to do this is by running <command>/stand/sysinstall</command> as
<username>root</username>, choosing <literal>Configure</literal>,
then <literal>Distributions</literal>, then <literal>src</literal>,
then <literal>sys</literal>.</para>
</note>
<para>Next, move to the <filename>i386/conf</filename> directory and

View file

@ -433,7 +433,7 @@ Abort</screen>
</informalexample>
<para>To help the FreeBSD kernel distinguish between a FreeBSD ELF
binary from a Linux one, use the <citerefentry>
binary from a Linux binary, use the <citerefentry>
<refentrytitle>brandelf</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry> utility.</para>

View file

@ -529,7 +529,7 @@ bigco.com. MX 10 bigco.com.
<filename>/etc/rc.conf</filename> ) 15 minutes to connect to your
host to deliver the mail to the primary MX site.</para>
<para>You might wat to use something like this as a login script.</para>
<para>You might want to use something like this as a login script.</para>
<programlisting>
#!/bin/sh

View file

@ -722,7 +722,7 @@
<listitem>
<para><ulink
URL="ftp://ftp.ua.FreeBSD.ORG/pub/FreeBSD">ftp://ftp.ua.FreeBSD.ORG/pub/FreeBSD</ulink> Contact: <email>archer@lucky.net</email>.</para>
URL="ftp://ftp.ua.FreeBSD.ORG/pub/FreeBSD">ftp://ftp.ua.FreeBSD.ORG/pub/FreeBSD</ulink> Contact: <email>freebsd-mnt@lucky.net</email>.</para>
</listitem>
</itemizedlist>
@ -1269,7 +1269,7 @@
<itemizedlist>
<listitem>
<para>cvsup2.ua.FreeBSD.ORG (maintainer <email>archer@lucky.net</email>)</para>
<para>cvsup2.ua.FreeBSD.ORG (maintainer <email>freebsd-mnt@lucky.net</email>)</para>
</listitem>
</itemizedlist>
@ -1310,6 +1310,9 @@
<para>cvsup3.FreeBSD.ORG (maintainer <email>wollman@FreeBSD.ORG</email>)</para>
</listitem>
<listitem>
<para>cvsup4.FreeBSD.ORG (maintainer <email>shmit@rcn.com</email>)</para>
</listitem>
</itemizedlist>
</listitem>

View file

@ -495,6 +495,75 @@ vvlVQ0UbcR0N2+5F6Mb5GqrXZpIesn7jFJpkQKPU
-----END PGP PUBLIC KEY BLOCK-----</programlisting>
</sect2>
</sect1>
<sect1>
<title>Developers</title>
<sect2>
<title>&a.wosch;</title>
<programlisting>
Type Bits/KeyID Date User ID
pub 1024/2B7181AD 1997/08/09 Wolfram Schneider &lt;wosch@FreeBSD.org&gt;
Fingerprint = CA 16 91 D9 75 33 F1 07 1B F0 B4 9F 3E 95 B6 09
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: 2.6.3ia
mQCNAzPs+aEAAAEEAJqqMm2I9CxWMuHDvuVO/uh0QT0az5ByOktwYLxGXQmqPG1G
Q3hVuHWYs5Vfm/ARU9CRcVHFyqGQ3LepoRhDHk+JcASHan7ptdFsz7xk1iNNEoe0
vE2rns38HIbiyQ/2OZd4XsyhFOFtExNoBuyDyNoe3HbHVBQT7TmN/mkrcYGtAAUR
tCVXb2xmcmFtIFNjaG5laWRlciA8d29zY2hARnJlZUJTRC5vcmc+iQCVAwUQNmrS
AzmN/mkrcYGtAQFQjAP8CthNueur8XDAZqC5q6NQcDs0PqqQ+raTUfQTv6Km6ykf
UzdpDlBoRC+CCyHfBfC5zo9N6mB7iV7qS1PljrdIh6VAwHxJN9iopB/x6+nsBvmy
0YSNt7eyfFrIVegCJvd4ALz5JBV8ZstznOwo8RAhDD0gX58F8nDhgWjy62JekGK0
IldvbGZyYW0gU2NobmVpZGVyIDx3b3NjaEBhcGZlbC5kZT6JARUDBRA2Z9ZcCMks
sk6wLt0BAQBICACcTiDZ/AyYWRDLXsBOK+WMRoNk3+bQZ1cdy11nwJo+taT/389M
0r5TrEJ7CogpXC2rFUExTVWldSFZd8A1YIHtrTsP7YauUH0nA7k0wUnqDRYj8YJR
eMLFvc1OQ2y+mkvxF2BzzBzh/bcYbgJdWCB1MPahSNQfkGXtp+A5PjEs8Cp4+FLu
EUFScyxsD3g5/E+0d7mirJpe3pxcf9KCmFGHM89mrTKODQR/7N8dVqa9npeXZotm
ZK8Jz+tvRKFgNiLf2XL048+IE8ZtJXDYaDzTirHdcAqJMWQuxthCdG3ta4I+w5WM
WR8JtBLfVNpyU7LN6dl0IB7O5sYhyskApmMwiQCVAwUQM+z5oTmN/mkrcYGtAQGU
gAP/cJGro/SbV+L19s/Gem26KmegUH+bfIXoh2EzyRJ7heVdybu1LrSDFApmAE7d
sMDlAA1wd2XjVWD3nIEBl6k+J7qJB4ACjKVGs414jLpdKGPHdLRYqYDj4LyQFMv6
/BpSoX1gnWp6xlC2xeWRan9ns3XZGS55UBVDvBE/B+fPoTe0JFdvbGZyYW0gU2No
bmVpZGVyIDxzY2huZWlkZXJAemliLmRlPokAlQMFEDZq0dI5jf5pK3GBrQEB38QD
/3NYyRPIejtXXq/okdDRyhWmA8cv0KG6gEupKCQKa7ep/OZTw/KxrN3ZOS8zlPod
tEn8mol+4SvY5AgSMdjQ0jTd1JdFcMKFnbJJrJ3b9IpwCqbkXy25rTUcQn9ICP47
rFKC4qR/Ucrg5YVVhQ3pVJX6XuO2XvuG7euHAQNXV3e2
=EpJQ
-----END PGP PUBLIC KEY BLOCK-----</programlisting>
</sect2>
<sect2>
<title>&a.brian;</title>
<programlisting>
Type Bits/KeyID Date User ID
pub 1024/666A7421 1997/04/30 Brian Somers &lt;brian@Awfulhak.org&gt;
Key fingerprint = 2D 91 BD C2 94 2C 46 8F 8F 09 C4 FC AD 12 3B 21
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: 2.6.3ia
mQCNAzNmogUAAAEEALdsjVsV2dzO8UU4EEo7z3nYuvB2Q6YJ8sBUYjB8/vfR5oZ9
7aEQjgY5//pXvS30rHUB9ghk4kIFSljzeMudE0K2zH5n2sxpLbBKWZRDLS7xnrDC
I3j9CNKwQBzMPs0fUT46gp96nf1X8wPiJXkDUEia/c0bRbXlLw7tvOdmanQhAAUR
tCFCcmlhbiBTb21lcnMgPGJyaWFuQGF3ZnVsaGFrLm9yZz6JAJUDBRAzbedc77Ox
BWZTbW0BAVtFA/42QelA3RBXYUtIcYGob+QsWkA1kGyBKQGPSS9coHdUVjClBRl3
UZFmZhxAODb7cBRXmpvx2ZuMrhn/MpXTMqPOJaE3FYm+5SoeArphsRU+T8XofxfL
vRHkM3JURUjIVZdAQNvxxBso8NJG5KayP0Q96Vw+3sEwFK49jt14RCJy4IkAlQMF
EDNzvb1sq+iWcxFJBQEBfZwD/R3KNFf9ype9Dea8j1YIeNZ1E3e03en1I8fMj6Em
S1/L1WfFzMnfFCxZs7JgPtkBuB3CqP8f+LOdDt6PHPqNakmI9E6fiuGfJZ3jFZYA
TXa0XKuIoxIJNKhqkpbF8ixJZFTxFwAAwVYM3+sqr4qQ8FzVc5entxjyxPFNkwJw
RWV+iQCVAwUQM2aiBQ7tvOdmanQhAQE7LgQAiN6Hz+zd8bh0nO6VizbJxWFRHPbr
QWnJXGoMYyy88DyszAXC4zRshlyGUDQdHeP/1DFCXDEu78GfDCLaJ1bm25yVR7kL
xDZaEUQEbWqxfiwuzizAjkaxrW7dBbWILwWqrYF5TXClw+oUU/oIUW4t6t+GpAO1
8PLYhSMXVYErrAA=
=EdyZ
-----END PGP PUBLIC KEY BLOCK-----</programlisting>
</sect2>
</sect1>
</chapter>
<!--

View file

@ -110,7 +110,7 @@
<para>If you look at a port skeleton (either on <ulink
URL="file://localhost/usr/ports/devel/ElectricFence">your FreeBSD
system</ulink> or <ulink
URL="ftp://ftp.freebsd.org/pub/FreeBSD/ports/devel/ElectricFence">the FTP site</ulink>) and expect to find all sorts of pointy-headed rocket science lurking there, you may be disappointed by the one or two rather unexciting-looking files and directories you find there. (We will discuss in a minute how to go about <link
URL="ftp://ftp.freebsd.org/pub/FreeBSD/ports/ports/devel/ElectricFence">the FTP site</ulink>) and expect to find all sorts of pointy-headed rocket science lurking there, you may be disappointed by the one or two rather unexciting-looking files and directories you find there. (We will discuss in a minute how to go about <link
linkend="ports-getting">Getting a port</link>).</para>
<para>&ldquo;How on earth can this do anything?&rdquo; I hear you cry. &ldquo;There
@ -243,7 +243,25 @@ install -c -o bin -g bin -m 444 /usr/ports/devel/ElectricFence/work/ElectricFenc
collection's built in search path should find the tarballs in
<filename>/cdrom/ports/distfiles/</filename> (if they exist there)
rather than downloading them over the net.</para>
<para>Another way of doing this, if you want to just use the port
skeletons on the CDROM, is to set these variables in
<filename>/etc/make.conf</filename>:</para>
<programlisting>
PORTSDIR= /cdrom/ports
DISTDIR= /tmp/distfiles
WRKDIRPREFIX= /tmp</programlisting>
<para>Substitute <literal>/tmp</literal> for any place you have enough
free space. Then, just <command>cd</command> to the appropriate
subdirectory under <filename>/cdrom/ports</filename> and type
<command>make install</command> as
usual. <makevar>WRKDIRPREFIX</makevar> will cause the port to be
build under <filename>/tmp/cdrom/ports</filename>; for instance,
<filename>games/oneko</filename> will be built under
<filename>/tmp/cdrom/ports/games/oneko</filename>.</para>
<note>
<para>There are some ports for which we cannot provide the
original source in the CDROM due to licensing limitations. In
@ -283,7 +301,7 @@ install -c -o bin -g bin -m 444 /usr/ports/devel/ElectricFence/work/ElectricFenc
&prompt.root; <userinput>ftp ftp.freebsd.org</userinput>
[log in as `ftp' and give your email address when asked for a
password. Remember to use binary (also known as image) mode!]
<prompt>&gt;</prompt> <userinput>cd /pub/FreeBSD/ports/databases</userinput>
<prompt>&gt;</prompt> <userinput>cd /pub/FreeBSD/ports/ports/databases</userinput>
<prompt>&gt;</prompt> <userinput>get gnats.tar</userinput>
[tars up the gnats skeleton for us]
<prompt>&gt;</prompt> <userinput>quit</userinput>
@ -315,7 +333,7 @@ password. Remember to use binary (also known as image) mode!]
&prompt.root; <userinput>ftp ftp.freebsd.org</userinput>
[log in as `ftp' and give your email address when asked for a
password. Remember to use binary (also known as image) mode!]
<prompt>&gt;</prompt> <userinput>cd /pub/FreeBSD/ports</userinput>
<prompt>&gt;</prompt> <userinput>cd /pub/FreeBSD/ports/ports</userinput>
<prompt>&gt;</prompt> <userinput>get databases.tar</userinput>
[tars up the databases directory for us]
<prompt>&gt;</prompt> <userinput>quit</userinput>
@ -501,7 +519,7 @@ do-install:
<para>Grab the pre-compiled package from a ftp server. The
&ldquo;master&rdquo; package collection is on FreeBSD's FTP server in
the <ulink
URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/packages/">packages
URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/packages/">packages
directory</ulink>, though check your local mirror first,
please! These are more likely to work (on the whole) than
trying to compile from source and a lot faster besides! Use
@ -759,7 +777,7 @@ do-install:
<informalexample>
<screen>&prompt.root; <userinput>cd /usr/ports/directory</userinput>
&prompt.root; <userinput>make MASTER_SITE_OVERRIDE=ftp://ftp.FreeBSD.ORG/pub/FreeBSD/distfiles/ fetch</userinput></screen>
&prompt.root; <userinput>make MASTER_SITE_OVERRIDE=ftp://ftp.FreeBSD.ORG/pub/FreeBSD/ports/distfiles/ fetch</userinput></screen>
</informalexample>
</listitem>
@ -1348,7 +1366,7 @@ lib/X11/oneko/mouse.xpm
URL <makevar>MASTER_SITES</makevar>,
which is set in the Makefile, as well as our main ftp
site at <ulink
URL="ftp://ftp.freebsd.org/pub/FreeBSD/distfiles/">ftp://ftp.freebsd.org/pub/FreeBSD/distfiles/,</ulink> where we put sanctioned distfiles as backup. It will then attempt to fetch the named distribution file with <makevar>FETCH</makevar>, assuming that the requesting site has direct access to the Internet. If that succeeds, it will save the file in <makevar>DISTDIR</makevar> for future use and proceed.</para>
URL="ftp://ftp.freebsd.org/pub/FreeBSD/ports/distfiles/">ftp://ftp.freebsd.org/pub/FreeBSD/ports/distfiles/,</ulink> where we put sanctioned distfiles as backup. It will then attempt to fetch the named distribution file with <makevar>FETCH</makevar>, assuming that the requesting site has direct access to the Internet. If that succeeds, it will save the file in <makevar>DISTDIR</makevar> for future use and proceed.</para>
</step>
<step>
@ -1398,7 +1416,7 @@ lib/X11/oneko/mouse.xpm
<step>
<para>The <maketarget>build</maketarget> target is run. This is responsible for
descending into the ports' private working directory
descending into the port's private working directory
(<makevar>WRKSRC</makevar>) and
building it. If <makevar>USE_GMAKE</makevar> is set, GNU
<command>make</command> will be used,
@ -1435,7 +1453,7 @@ lib/X11/oneko/mouse.xpm
<note>
<para>The &ldquo;main&rdquo; targets (e.g., <maketarget>extract</maketarget>, <maketarget>configure</maketarget>, etc.) do nothing more than
make sure all the stages up to that one is completed and
make sure all the stages up to that one are completed and
call the real targets or scripts, and they are not intended
to be changed. If you want to fix the extraction, fix
<maketarget>do-extract</maketarget>, but never ever
@ -1471,7 +1489,7 @@ lib/X11/oneko/mouse.xpm
<filename>public_html/</filename> directory on
<hostid>freefall</hostid>),
we can &ldquo;house&rdquo; it ourselves by putting
it on <filename>ftp://ftp.freebsd.org/pub/FreeBSD/distfiles/LOCAL_PORTS/</filename> as the last resort. Please refer to this
it on <filename>ftp://ftp.freebsd.org/pub/FreeBSD/ports/distfiles/LOCAL_PORTS/</filename> as the last resort. Please refer to this
location as <makevar>MASTER_SITE_LOCAL</makevar>. Send mail to
the &a.ports;if you are not sure what to do.</para>
@ -1488,7 +1506,7 @@ lib/X11/oneko/mouse.xpm
<para>If your port requires some additional `patches' that are
available on the Internet, fetch them too and put them in
<makevar>DISTDIR</makevar>. Do not worry if
they come from site other than where you got the main source
they come from a site other than where you got the main source
tarball, we have a way to handle these situations (see the
description of <link
linkend="porting-patchfiles">PATCHFILES</link> below).</para>
@ -1726,7 +1744,7 @@ MASTER_SITE_SUBDIR= applications</programlisting>
<para>If the patch is not relative to the top of the source tree
(i.e., <makevar>WKRSRC</makevar>) because it
contains some extra pathnames, set <makevar>PATCH_DIST_STRIP</makevar> accordingly.
For instance, if all the pathnames in the patch has an extra
For instance, if all the pathnames in the patch have an extra
<literal>foozolix-1.0/</literal> in front of the
filenames, then set
<literal>PATCH_DIST_STRIP=-p1</literal>.</para>
@ -1978,7 +1996,7 @@ BUILD_DEPENDS= /nonexistent:${PORTSDIR}/graphics/jpeg:extract</programlisting>
other way the behaviour you want can be accomplished. It will
cause the other port to be always build (and installed, by
default), and the dependency will go into the packages as
well. If this is really what you need, I recommend you to
well. If this is really what you need, I recommend you
write it as <literal>BUILD_DEPENDS</literal> and
<literal>RUN_DEPENDS</literal> instead&mdash;at least the
intention will be clear.</para>
@ -2077,7 +2095,7 @@ lib/libtvl80.so.1
<sect2>
<title>ELF support</title>
<para>Since FreeBSD is moving to ELF from 3.0-release onwards,
<para>Since FreeBSD is moving to ELF shortly after 3.0-release,
we need to convert many ports that build shared libraries
to support ELF. Complicating this task is that a 3.0
system can run as both ELF and a.out, and that there will
@ -2778,8 +2796,8 @@ diff -u -r1.15 PLIST
<sect3>
<title><filename>INSTALL</filename></title>
<para>If your port needs execute commands when the binary package is
installed with <command>pkg_add</command> you can do with via the
<para>If your port needs to execute commands when the binary package is
installed with <command>pkg_add</command> you can do this via the
<filename>pkg/INSTALL</filename> script. This script will
automatically be added to the package, and will be run twice by
<command>pkg_add</command>. The first time will as
@ -2796,7 +2814,7 @@ diff -u -r1.15 PLIST
<note>
<para>This script is not run automatically if you install the port
with <command>make install</command>. If you are depending on
it being run, you will have to explicitly call it on your port's
it being run, you will have to explicitly call it from your port's
<filename>Makefile</filename>.</para>
</note>
</sect3>
@ -2862,15 +2880,87 @@ PLIST_SUB= OCTAVE_VERSION=${OCTAVE_VERSION}</programlisting>
<maketarget>post-install</maketarget> to a file named
<makevar>TMPPLIST</makevar>.</para>
</sect3>
<sect3>
<title id="porting-pkgsubdir">Changing the names of files in the
<filename>pkg</filename> subdirectory</title>
<para>All the filenames in the <filename>pkg</filename> subdirectory
are defined using variables so you can change them in your
<filename>Makefile</filename> if need be. This is especially useful when you
are sharing the same <filename>pkg</filename> subdirectory among
several ports or have to write to one of the above files (see
<link linkend="porting-wrkdir">writing to places other than
<makevar>WRKDIR</makevar></link> for why it is a bad idea to
write directly in to the <filename>pkg</filename>
subdirectory.</para>
<para>Here is a list of variable names and their default
values.</para>
<informaltable frame="none">
<tgroup cols="2">
<thead>
<row>
<entry>Variable</entry>
<entry>Default value</entry>
</row>
</thead>
<tbody>
<row>
<entry><makevar>COMMENT</makevar></entry>
<entry><literal>${PKGDIR}/DESCR</literal></entry>
</row>
<row>
<entry><makevar>DESCR</makevar></entry>
<entry><literal>${PKGDIR}/DESCR</literal></entry>
</row>
<row>
<entry><makevar>PLIST</makevar></entry>
<entry><literal>${PKGDIR}/PLIST</literal></entry>
</row>
<row>
<entry><makevar>PKGINSTALL</makevar></entry>
<entry><literal>${PKGDIR}/PKGINSTALL</literal></entry>
</row>
<row>
<entry><makevar>PKGDEINSTALL</makevar></entry>
<entry><literal>${PKGDIR}/PKGDEINSTALL</literal></entry>
</row>
<row>
<entry><makevar>PKGREQ</makevar></entry>
<entry><literal>${PKGDIR}/REQ</literal></entry>
</row>
<row>
<entry><makevar>PKGMESSAGE</makevar></entry>
<entry><literal>${PKGDIR}/MESSAGE</literal></entry>
</row>
</tbody>
</tgroup>
</informaltable>
<para>Please change these variables rather than overriding
<makevar>PKG_ARGS</makevar>. If you change
<makevar>PKG_ARGS</makevar>, those files will not correctly be
installed in <filename>/var/db/pkg</filename> upon install from a
port.</para>
</sect3>
</sect2>
<sect2>
<title>Licensing Problems</title>
<para>Some software packages have restrictive licenses or can be
in violation to the law (PKP's patent on public key crypto, ITAR
(export of crypto software) to name just two of them). What we
can do with them vary a lot, depending on the exact wordings of
can do with them varies a lot, depending on the exact wordings of
the respective licenses.</para>
<note>
@ -3031,6 +3121,35 @@ post-install:
with all the appropriate flags. See below for an example on how
to use them.</para>
</sect3>
<sect3 id="porting-wrkdir">
<title><makevar>WRKDIR</makevar></title>
<para>Do not write anything to files outside
<makevar>WRKDIR</makevar>. <makevar>WRKDIR</makevar> is the only
place that is guaranteed to be writable during the port build (see
<link linkend="ports-cd">compiling ports from CDROM</link> for an
example of building ports from a read-only tree). If you need to
modigy some file in <makevar>PKGDIR</makevar>, do so by <link
linkend="porting-pkgsubdir">redefining a variable</link>, not by
writing over it.</para>
</sect3>
<sect3>
<title><makevar>WRKDIRPREFIX</makevar></title>
<para>Make sure your port honors
<makevar>WRKDIRPREFIX</makevar>. Most ports don't have to worry
about this. In particular, if you are referring to a
<makevar>WRKDIR</makevar> of another port, note that the correct
location is
<filename><makevar>WRKDIRPREFIX</makevar><makevar>PORTSDIR</makevar>/<replaceable>subdir</replaceable>/<replaceable>name</replaceable>/work</filename> not <filename><makevar>PORTSDIR</makevar>/<replaceable>subdir</replaceable>/<replaceable>name</replaceable>/work</filename> or <filename><makevar>.CURDIR</makevar>/../../<replaceable>subdir</replaceable>/<replaceable>name</replaceable>/work</filename> or some such.</para>
<para>Also, if you are defining <makevar>WRKDIR</makevar> yourself,
make sure you prepend
<literal>&dollar;{WKRDIRPREFIX}&dollar;{.CURDIR}</literal> in the
front.</para>
</sect3>
<sect3 id="porting-versions">
<title>Differentiating operating systems and OS versions</title>
@ -3055,7 +3174,7 @@ post-install:
#endif</programlisting>
<para>to the proper place in the <filename>.c</filename> file. We
believe that every system that defines these to symbols has
believe that every system that defines these two symbols has
<filename>sys/param.h</filename>. If you find a system that
doesn't, we would like to know. Please send mail to the
&a.ports;.</para>
@ -3094,7 +3213,7 @@ post-install:
<para>The value of the <literal>BSD</literal> macro is
<literal>199506</literal> for the 4.4BSD-Lite2 code base. This is
stated for informational purposes only. It should not be used to
distinguish between version of FreeBSD based only on 4.4-Lite vs.
distinguish between versions of FreeBSD based only on 4.4-Lite vs.
versions that have merged in changes from 4.4-Lite2. The
<literal>__FreeBSD__</literal> macro should be used
instead.</para>
@ -3315,6 +3434,26 @@ post-install:
<entry>3.0-current after 3.0-RELEASE</entry>
<entry>300006</entry>
</row>
<row>
<entry>3.0-stable after 3/4 branch</entry>
<entry>300007</entry>
</row>
<row>
<entry>3.1-RELEASE</entry>
<entry>310000</entry>
</row>
<row>
<entry>3.1-stable after 3.1-RELEASE</entry>
<entry>310001</entry>
</row>
<row>
<entry>4.0-current after 3/4 branch</entry>
<entry>400000</entry>
</row>
</tbody>
</tgroup>
</informaltable>
@ -3649,8 +3788,8 @@ post-install:
<filename>info</filename> (documentation for info browser)
or <filename>share</filename> (architecture independent
files). See man <citerefentry><refentrytitle>hier</refentrytitle><manvolnum>7</manvolnum></citerefentry> for
details, the rule governing <filename>/usr</filename> pretty
much applies to <filename>/usr/local</filename> too. The
details, the rules governing <filename>/usr</filename> pretty
much apply to <filename>/usr/local</filename> too. The
exception are ports dealing with USENET &ldquo;news&rdquo;. They may use
<filename><makevar>PREFIX</makevar>/news</filename> as a destination for
their files.</para>
@ -4125,6 +4264,11 @@ pre-install:
</thead>
<tbody>
<row>
<entry><filename>afterstep*</filename></entry>
<entry>Ports to support AfterStep window manager</entry>
</row>
<row>
<entry><filename>archivers</filename></entry>
<entry>Archiving tools.</entry>
@ -4290,18 +4434,18 @@ pre-install:
<entry>Ports from the OffiX suite.</entry>
</row>
<row>
<entry><filename>palm</filename></entry>
<entry>Software support for the 3Com Palm(tm) series.</entry>
</row>
<row>
<entry><filename>perl5*</filename></entry>
<entry>Ports that require perl version 5 to run.</entry>
</row>
<row>
<entry><filename>pilot*</filename></entry>
<entry>Software to use with the 3Com PalmPilot.</entry>
</row>
<row>
<entry><filename>plan9</filename></entry>
<entry><filename>plan9*</filename></entry>
<entry>Various programs from Plan9.</entry>
</row>
@ -4387,6 +4531,12 @@ pre-install:
<entry>Vietnamese language support.</entry>
</row>
<row>
<entry><filename>windowmaker*</filename></entry>
<entry>Ports to support the WindowMaker window
manager</entry>
</row>
<row>
<entry><filename>www</filename></entry>
<entry>Software related to the World Wide Web. HTML language

View file

@ -1439,6 +1439,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
as any combination of ranges and/or individual types
separated by commas. Commonly used ICMP types are:
<literal>0</literal> echo reply (ping reply),
<literal>3</literal> destination unreachable,
<literal>5</literal> redirect, <literal>8</literal> echo request (ping request), and
<literal>11</literal> time exceeded (used to
indicate TTL expiration as with

View file

@ -216,10 +216,18 @@
<para>&a.lars;</para>
</listitem>
<listitem>
<para>&.dirk;</para>
</listitem>
<listitem>
<para>&a.billf;</para>
</listitem>
<listitem>
<para>&a.gallatin;</para>
</listitem>
<listitem>
<para>&a.tg;</para>
</listitem>
@ -275,7 +283,11 @@
<listitem>
<para>&a.flathill;</para>
</listitem>
<listitem>
<para>&a.foxfair;</para>
</listitem>
<listitem>
<para>&a.hosokawa;</para>
</listitem>
@ -359,7 +371,11 @@
<listitem>
<para>&a.ken;</para>
</listitem>
<listitem>
<para>&a.hm;</para>
</listitem>
<listitem>
<para>&a.tedm;</para>
</listitem>
@ -380,6 +396,10 @@
<para>&a.alex;</para>
</listitem>
<listitem>
<para>&a.newton;</para>
</listitem>
<listitem>
<para>&a.rnordier;</para>
</listitem>
@ -479,7 +499,11 @@
<listitem>
<para>&a.jseger;</para>
</listitem>
<listitem>
<para>&a.simokawa;</para>
</listitem>
<listitem>
<para>&a.vanilla;</para>
</listitem>
@ -495,7 +519,11 @@
<listitem>
<para>&a.brian;</para>
</listitem>
<listitem>
<para>&a.mks;</para>
</listitem>
<listitem>
<para>&a.stark;</para>
</listitem>
@ -604,7 +632,7 @@
</listitem>
</varlistentry>
<varlistentry><term>Gallery and Commercial Editor</term>
<varlistentry><term>Gallery Editor</term>
<listitem>
<para>&a.nsj;</para>
@ -613,7 +641,23 @@
</listitem>
</varlistentry>
<varlistentry>
<term>Commercial Editor</term>
<listitem>
<para>&a.mbarkah;</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Web Changes Editor</term>
<listitem>
<para>&a.mbarkah;</para>
</listitem>
</varlistentry>
<varlistentry><term>Style Police &amp; Art Director</term>
<listitem>

View file

@ -110,7 +110,7 @@
<para>If you look at a port skeleton (either on <ulink
URL="file://localhost/usr/ports/devel/ElectricFence">your FreeBSD
system</ulink> or <ulink
URL="ftp://ftp.freebsd.org/pub/FreeBSD/ports/devel/ElectricFence">the FTP site</ulink>) and expect to find all sorts of pointy-headed rocket science lurking there, you may be disappointed by the one or two rather unexciting-looking files and directories you find there. (We will discuss in a minute how to go about <link
URL="ftp://ftp.freebsd.org/pub/FreeBSD/ports/ports/devel/ElectricFence">the FTP site</ulink>) and expect to find all sorts of pointy-headed rocket science lurking there, you may be disappointed by the one or two rather unexciting-looking files and directories you find there. (We will discuss in a minute how to go about <link
linkend="ports-getting">Getting a port</link>).</para>
<para>&ldquo;How on earth can this do anything?&rdquo; I hear you cry. &ldquo;There
@ -243,7 +243,25 @@ install -c -o bin -g bin -m 444 /usr/ports/devel/ElectricFence/work/ElectricFenc
collection's built in search path should find the tarballs in
<filename>/cdrom/ports/distfiles/</filename> (if they exist there)
rather than downloading them over the net.</para>
<para>Another way of doing this, if you want to just use the port
skeletons on the CDROM, is to set these variables in
<filename>/etc/make.conf</filename>:</para>
<programlisting>
PORTSDIR= /cdrom/ports
DISTDIR= /tmp/distfiles
WRKDIRPREFIX= /tmp</programlisting>
<para>Substitute <literal>/tmp</literal> for any place you have enough
free space. Then, just <command>cd</command> to the appropriate
subdirectory under <filename>/cdrom/ports</filename> and type
<command>make install</command> as
usual. <makevar>WRKDIRPREFIX</makevar> will cause the port to be
build under <filename>/tmp/cdrom/ports</filename>; for instance,
<filename>games/oneko</filename> will be built under
<filename>/tmp/cdrom/ports/games/oneko</filename>.</para>
<note>
<para>There are some ports for which we cannot provide the
original source in the CDROM due to licensing limitations. In
@ -283,7 +301,7 @@ install -c -o bin -g bin -m 444 /usr/ports/devel/ElectricFence/work/ElectricFenc
&prompt.root; <userinput>ftp ftp.freebsd.org</userinput>
[log in as `ftp' and give your email address when asked for a
password. Remember to use binary (also known as image) mode!]
<prompt>&gt;</prompt> <userinput>cd /pub/FreeBSD/ports/databases</userinput>
<prompt>&gt;</prompt> <userinput>cd /pub/FreeBSD/ports/ports/databases</userinput>
<prompt>&gt;</prompt> <userinput>get gnats.tar</userinput>
[tars up the gnats skeleton for us]
<prompt>&gt;</prompt> <userinput>quit</userinput>
@ -315,7 +333,7 @@ password. Remember to use binary (also known as image) mode!]
&prompt.root; <userinput>ftp ftp.freebsd.org</userinput>
[log in as `ftp' and give your email address when asked for a
password. Remember to use binary (also known as image) mode!]
<prompt>&gt;</prompt> <userinput>cd /pub/FreeBSD/ports</userinput>
<prompt>&gt;</prompt> <userinput>cd /pub/FreeBSD/ports/ports</userinput>
<prompt>&gt;</prompt> <userinput>get databases.tar</userinput>
[tars up the databases directory for us]
<prompt>&gt;</prompt> <userinput>quit</userinput>
@ -501,7 +519,7 @@ do-install:
<para>Grab the pre-compiled package from a ftp server. The
&ldquo;master&rdquo; package collection is on FreeBSD's FTP server in
the <ulink
URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/packages/">packages
URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/packages/">packages
directory</ulink>, though check your local mirror first,
please! These are more likely to work (on the whole) than
trying to compile from source and a lot faster besides! Use
@ -759,7 +777,7 @@ do-install:
<informalexample>
<screen>&prompt.root; <userinput>cd /usr/ports/directory</userinput>
&prompt.root; <userinput>make MASTER_SITE_OVERRIDE=ftp://ftp.FreeBSD.ORG/pub/FreeBSD/distfiles/ fetch</userinput></screen>
&prompt.root; <userinput>make MASTER_SITE_OVERRIDE=ftp://ftp.FreeBSD.ORG/pub/FreeBSD/ports/distfiles/ fetch</userinput></screen>
</informalexample>
</listitem>
@ -1348,7 +1366,7 @@ lib/X11/oneko/mouse.xpm
URL <makevar>MASTER_SITES</makevar>,
which is set in the Makefile, as well as our main ftp
site at <ulink
URL="ftp://ftp.freebsd.org/pub/FreeBSD/distfiles/">ftp://ftp.freebsd.org/pub/FreeBSD/distfiles/,</ulink> where we put sanctioned distfiles as backup. It will then attempt to fetch the named distribution file with <makevar>FETCH</makevar>, assuming that the requesting site has direct access to the Internet. If that succeeds, it will save the file in <makevar>DISTDIR</makevar> for future use and proceed.</para>
URL="ftp://ftp.freebsd.org/pub/FreeBSD/ports/distfiles/">ftp://ftp.freebsd.org/pub/FreeBSD/ports/distfiles/,</ulink> where we put sanctioned distfiles as backup. It will then attempt to fetch the named distribution file with <makevar>FETCH</makevar>, assuming that the requesting site has direct access to the Internet. If that succeeds, it will save the file in <makevar>DISTDIR</makevar> for future use and proceed.</para>
</step>
<step>
@ -1398,7 +1416,7 @@ lib/X11/oneko/mouse.xpm
<step>
<para>The <maketarget>build</maketarget> target is run. This is responsible for
descending into the ports' private working directory
descending into the port's private working directory
(<makevar>WRKSRC</makevar>) and
building it. If <makevar>USE_GMAKE</makevar> is set, GNU
<command>make</command> will be used,
@ -1435,7 +1453,7 @@ lib/X11/oneko/mouse.xpm
<note>
<para>The &ldquo;main&rdquo; targets (e.g., <maketarget>extract</maketarget>, <maketarget>configure</maketarget>, etc.) do nothing more than
make sure all the stages up to that one is completed and
make sure all the stages up to that one are completed and
call the real targets or scripts, and they are not intended
to be changed. If you want to fix the extraction, fix
<maketarget>do-extract</maketarget>, but never ever
@ -1471,7 +1489,7 @@ lib/X11/oneko/mouse.xpm
<filename>public_html/</filename> directory on
<hostid>freefall</hostid>),
we can &ldquo;house&rdquo; it ourselves by putting
it on <filename>ftp://ftp.freebsd.org/pub/FreeBSD/distfiles/LOCAL_PORTS/</filename> as the last resort. Please refer to this
it on <filename>ftp://ftp.freebsd.org/pub/FreeBSD/ports/distfiles/LOCAL_PORTS/</filename> as the last resort. Please refer to this
location as <makevar>MASTER_SITE_LOCAL</makevar>. Send mail to
the &a.ports;if you are not sure what to do.</para>
@ -1488,7 +1506,7 @@ lib/X11/oneko/mouse.xpm
<para>If your port requires some additional `patches' that are
available on the Internet, fetch them too and put them in
<makevar>DISTDIR</makevar>. Do not worry if
they come from site other than where you got the main source
they come from a site other than where you got the main source
tarball, we have a way to handle these situations (see the
description of <link
linkend="porting-patchfiles">PATCHFILES</link> below).</para>
@ -1726,7 +1744,7 @@ MASTER_SITE_SUBDIR= applications</programlisting>
<para>If the patch is not relative to the top of the source tree
(i.e., <makevar>WKRSRC</makevar>) because it
contains some extra pathnames, set <makevar>PATCH_DIST_STRIP</makevar> accordingly.
For instance, if all the pathnames in the patch has an extra
For instance, if all the pathnames in the patch have an extra
<literal>foozolix-1.0/</literal> in front of the
filenames, then set
<literal>PATCH_DIST_STRIP=-p1</literal>.</para>
@ -1978,7 +1996,7 @@ BUILD_DEPENDS= /nonexistent:${PORTSDIR}/graphics/jpeg:extract</programlisting>
other way the behaviour you want can be accomplished. It will
cause the other port to be always build (and installed, by
default), and the dependency will go into the packages as
well. If this is really what you need, I recommend you to
well. If this is really what you need, I recommend you
write it as <literal>BUILD_DEPENDS</literal> and
<literal>RUN_DEPENDS</literal> instead&mdash;at least the
intention will be clear.</para>
@ -2077,7 +2095,7 @@ lib/libtvl80.so.1
<sect2>
<title>ELF support</title>
<para>Since FreeBSD is moving to ELF from 3.0-release onwards,
<para>Since FreeBSD is moving to ELF shortly after 3.0-release,
we need to convert many ports that build shared libraries
to support ELF. Complicating this task is that a 3.0
system can run as both ELF and a.out, and that there will
@ -2778,8 +2796,8 @@ diff -u -r1.15 PLIST
<sect3>
<title><filename>INSTALL</filename></title>
<para>If your port needs execute commands when the binary package is
installed with <command>pkg_add</command> you can do with via the
<para>If your port needs to execute commands when the binary package is
installed with <command>pkg_add</command> you can do this via the
<filename>pkg/INSTALL</filename> script. This script will
automatically be added to the package, and will be run twice by
<command>pkg_add</command>. The first time will as
@ -2796,7 +2814,7 @@ diff -u -r1.15 PLIST
<note>
<para>This script is not run automatically if you install the port
with <command>make install</command>. If you are depending on
it being run, you will have to explicitly call it on your port's
it being run, you will have to explicitly call it from your port's
<filename>Makefile</filename>.</para>
</note>
</sect3>
@ -2862,15 +2880,87 @@ PLIST_SUB= OCTAVE_VERSION=${OCTAVE_VERSION}</programlisting>
<maketarget>post-install</maketarget> to a file named
<makevar>TMPPLIST</makevar>.</para>
</sect3>
<sect3>
<title id="porting-pkgsubdir">Changing the names of files in the
<filename>pkg</filename> subdirectory</title>
<para>All the filenames in the <filename>pkg</filename> subdirectory
are defined using variables so you can change them in your
<filename>Makefile</filename> if need be. This is especially useful when you
are sharing the same <filename>pkg</filename> subdirectory among
several ports or have to write to one of the above files (see
<link linkend="porting-wrkdir">writing to places other than
<makevar>WRKDIR</makevar></link> for why it is a bad idea to
write directly in to the <filename>pkg</filename>
subdirectory.</para>
<para>Here is a list of variable names and their default
values.</para>
<informaltable frame="none">
<tgroup cols="2">
<thead>
<row>
<entry>Variable</entry>
<entry>Default value</entry>
</row>
</thead>
<tbody>
<row>
<entry><makevar>COMMENT</makevar></entry>
<entry><literal>${PKGDIR}/DESCR</literal></entry>
</row>
<row>
<entry><makevar>DESCR</makevar></entry>
<entry><literal>${PKGDIR}/DESCR</literal></entry>
</row>
<row>
<entry><makevar>PLIST</makevar></entry>
<entry><literal>${PKGDIR}/PLIST</literal></entry>
</row>
<row>
<entry><makevar>PKGINSTALL</makevar></entry>
<entry><literal>${PKGDIR}/PKGINSTALL</literal></entry>
</row>
<row>
<entry><makevar>PKGDEINSTALL</makevar></entry>
<entry><literal>${PKGDIR}/PKGDEINSTALL</literal></entry>
</row>
<row>
<entry><makevar>PKGREQ</makevar></entry>
<entry><literal>${PKGDIR}/REQ</literal></entry>
</row>
<row>
<entry><makevar>PKGMESSAGE</makevar></entry>
<entry><literal>${PKGDIR}/MESSAGE</literal></entry>
</row>
</tbody>
</tgroup>
</informaltable>
<para>Please change these variables rather than overriding
<makevar>PKG_ARGS</makevar>. If you change
<makevar>PKG_ARGS</makevar>, those files will not correctly be
installed in <filename>/var/db/pkg</filename> upon install from a
port.</para>
</sect3>
</sect2>
<sect2>
<title>Licensing Problems</title>
<para>Some software packages have restrictive licenses or can be
in violation to the law (PKP's patent on public key crypto, ITAR
(export of crypto software) to name just two of them). What we
can do with them vary a lot, depending on the exact wordings of
can do with them varies a lot, depending on the exact wordings of
the respective licenses.</para>
<note>
@ -3031,6 +3121,35 @@ post-install:
with all the appropriate flags. See below for an example on how
to use them.</para>
</sect3>
<sect3 id="porting-wrkdir">
<title><makevar>WRKDIR</makevar></title>
<para>Do not write anything to files outside
<makevar>WRKDIR</makevar>. <makevar>WRKDIR</makevar> is the only
place that is guaranteed to be writable during the port build (see
<link linkend="ports-cd">compiling ports from CDROM</link> for an
example of building ports from a read-only tree). If you need to
modigy some file in <makevar>PKGDIR</makevar>, do so by <link
linkend="porting-pkgsubdir">redefining a variable</link>, not by
writing over it.</para>
</sect3>
<sect3>
<title><makevar>WRKDIRPREFIX</makevar></title>
<para>Make sure your port honors
<makevar>WRKDIRPREFIX</makevar>. Most ports don't have to worry
about this. In particular, if you are referring to a
<makevar>WRKDIR</makevar> of another port, note that the correct
location is
<filename><makevar>WRKDIRPREFIX</makevar><makevar>PORTSDIR</makevar>/<replaceable>subdir</replaceable>/<replaceable>name</replaceable>/work</filename> not <filename><makevar>PORTSDIR</makevar>/<replaceable>subdir</replaceable>/<replaceable>name</replaceable>/work</filename> or <filename><makevar>.CURDIR</makevar>/../../<replaceable>subdir</replaceable>/<replaceable>name</replaceable>/work</filename> or some such.</para>
<para>Also, if you are defining <makevar>WRKDIR</makevar> yourself,
make sure you prepend
<literal>&dollar;{WKRDIRPREFIX}&dollar;{.CURDIR}</literal> in the
front.</para>
</sect3>
<sect3 id="porting-versions">
<title>Differentiating operating systems and OS versions</title>
@ -3055,7 +3174,7 @@ post-install:
#endif</programlisting>
<para>to the proper place in the <filename>.c</filename> file. We
believe that every system that defines these to symbols has
believe that every system that defines these two symbols has
<filename>sys/param.h</filename>. If you find a system that
doesn't, we would like to know. Please send mail to the
&a.ports;.</para>
@ -3094,7 +3213,7 @@ post-install:
<para>The value of the <literal>BSD</literal> macro is
<literal>199506</literal> for the 4.4BSD-Lite2 code base. This is
stated for informational purposes only. It should not be used to
distinguish between version of FreeBSD based only on 4.4-Lite vs.
distinguish between versions of FreeBSD based only on 4.4-Lite vs.
versions that have merged in changes from 4.4-Lite2. The
<literal>__FreeBSD__</literal> macro should be used
instead.</para>
@ -3315,6 +3434,26 @@ post-install:
<entry>3.0-current after 3.0-RELEASE</entry>
<entry>300006</entry>
</row>
<row>
<entry>3.0-stable after 3/4 branch</entry>
<entry>300007</entry>
</row>
<row>
<entry>3.1-RELEASE</entry>
<entry>310000</entry>
</row>
<row>
<entry>3.1-stable after 3.1-RELEASE</entry>
<entry>310001</entry>
</row>
<row>
<entry>4.0-current after 3/4 branch</entry>
<entry>400000</entry>
</row>
</tbody>
</tgroup>
</informaltable>
@ -3649,8 +3788,8 @@ post-install:
<filename>info</filename> (documentation for info browser)
or <filename>share</filename> (architecture independent
files). See man <citerefentry><refentrytitle>hier</refentrytitle><manvolnum>7</manvolnum></citerefentry> for
details, the rule governing <filename>/usr</filename> pretty
much applies to <filename>/usr/local</filename> too. The
details, the rules governing <filename>/usr</filename> pretty
much apply to <filename>/usr/local</filename> too. The
exception are ports dealing with USENET &ldquo;news&rdquo;. They may use
<filename><makevar>PREFIX</makevar>/news</filename> as a destination for
their files.</para>
@ -4125,6 +4264,11 @@ pre-install:
</thead>
<tbody>
<row>
<entry><filename>afterstep*</filename></entry>
<entry>Ports to support AfterStep window manager</entry>
</row>
<row>
<entry><filename>archivers</filename></entry>
<entry>Archiving tools.</entry>
@ -4290,18 +4434,18 @@ pre-install:
<entry>Ports from the OffiX suite.</entry>
</row>
<row>
<entry><filename>palm</filename></entry>
<entry>Software support for the 3Com Palm(tm) series.</entry>
</row>
<row>
<entry><filename>perl5*</filename></entry>
<entry>Ports that require perl version 5 to run.</entry>
</row>
<row>
<entry><filename>pilot*</filename></entry>
<entry>Software to use with the 3Com PalmPilot.</entry>
</row>
<row>
<entry><filename>plan9</filename></entry>
<entry><filename>plan9*</filename></entry>
<entry>Various programs from Plan9.</entry>
</row>
@ -4387,6 +4531,12 @@ pre-install:
<entry>Vietnamese language support.</entry>
</row>
<row>
<entry><filename>windowmaker*</filename></entry>
<entry>Ports to support the WindowMaker window
manager</entry>
</row>
<row>
<entry><filename>www</filename></entry>
<entry>Software related to the World Wide Web. HTML language

View file

@ -7,7 +7,7 @@
Please keep this list in alphabetical order by entity names.
$Id: authors.ent,v 1.4 1998-12-10 20:43:39 nik Exp $
$Id: authors.ent,v 1.5 1999-01-29 22:33:55 nik Exp $
-->
<!ENTITY a.abial "Andrzej Bialecki <email>abial@FreeBSD.ORG</email>">
@ -70,6 +70,8 @@
<!ENTITY a.dima "Dima Ruban <email>dima@FreeBSD.ORG</email>">
<!ENTITY a.dirk "Dirk Fr&ouml;mberg <email>dirk@FreeBSD.ORG</email>">
<!ENTITY a.dirkvangulik "Dirk-Willem van Gulik <email>Dirk.vanGulik@jrc.it</email>">
<!ENTITY a.dt "Dmitrij Tejblum <email>dt@FreeBSD.ORG</email>">
@ -92,8 +94,12 @@
<!ENTITY a.flathill "Seiichirou Hiraoka <email>flathill@FreeBSD.ORG</email>">
<!ENTITY a.foxfair "Howard F. Hu <email>foxfair@FreeBSD.ORG</email>">
<!ENTITY a.fsmp "Steve Passe <email>fsmp@FreeBSD.ORG</email>">
<!ENTITY a.gallatin "Andrew Gallatin <email>gallatin@FreeBSD.ORG</email>">
<!ENTITY a.gclarkii "Gary Clark II <email>gclarkii@FreeBSD.ORG</email>">
<!ENTITY a.gena "Gennady B. Sorokopud <email>gena@NetVision.net.il</email>">
@ -122,7 +128,7 @@
<!ENTITY a.helbig "Wolfgang Helbig <email>helbig@FreeBSD.ORG</email>">
<!ENTITY a.hm "Hellmuth Michaelis <email>hm@kts.org</email>">
<!ENTITY a.hm "Hellmuth Michaelis <email>hm@FreeBSD.ORG</email>">
<!ENTITY a.hoek "Tim Vanderhoek <email>hoek@FreeBSD.ORG</email>">
@ -212,6 +218,8 @@
<!ENTITY a.md "Mark Dapoz <email>md@bsc.no</email>">
<!ENTITY a.mks "Mike Spengler <email>mks@FreeBSD.ORG</email>">
<!ENTITY a.motoyuki "Motoyuki Konno <email>motoyuki@FreeBSD.ORG</email>">
<!ENTITY a.mph "Matthew Hunt <email>mph@FreeBSD.ORG</email>">
@ -224,6 +232,8 @@
<!ENTITY a.nectar "Jacques Vidrine <email>nectar@FreeBSD.ORG</email>">
<!ENTITY a.newton "Mark Newton <email>newton@FreeBSD.ORG</email>">
<!ENTITY a.nhibma "Nick Hibma <email>n_hibma@FreeBSD.ORG</email>">
<!ENTITY a.nik "Nik Clayton <email>nik@FreeBSD.ORG</email>">
@ -274,6 +284,8 @@
<!ENTITY a.sef "Sean Eric Fagan <email>sef@FreeBSD.ORG</email>">
<!ENTITY a.simokawa "Hidetoshi Shimokawa <email>simokawa@FreeBSD.ORG</email>">
<!ENTITY a.smace "Scott Mace <email>smace@FreeBSD.ORG</email>">
<!ENTITY a.smpatel "Sujal Patel <email>smpatel@FreeBSD.ORG</email>">

View file

@ -7,7 +7,7 @@
Please keep this list in alphabetical order by entity names.
$Id: authors.ent,v 1.4 1998-12-10 20:43:39 nik Exp $
$Id: authors.ent,v 1.5 1999-01-29 22:33:55 nik Exp $
-->
<!ENTITY a.abial "Andrzej Bialecki <email>abial@FreeBSD.ORG</email>">
@ -70,6 +70,8 @@
<!ENTITY a.dima "Dima Ruban <email>dima@FreeBSD.ORG</email>">
<!ENTITY a.dirk "Dirk Fr&ouml;mberg <email>dirk@FreeBSD.ORG</email>">
<!ENTITY a.dirkvangulik "Dirk-Willem van Gulik <email>Dirk.vanGulik@jrc.it</email>">
<!ENTITY a.dt "Dmitrij Tejblum <email>dt@FreeBSD.ORG</email>">
@ -92,8 +94,12 @@
<!ENTITY a.flathill "Seiichirou Hiraoka <email>flathill@FreeBSD.ORG</email>">
<!ENTITY a.foxfair "Howard F. Hu <email>foxfair@FreeBSD.ORG</email>">
<!ENTITY a.fsmp "Steve Passe <email>fsmp@FreeBSD.ORG</email>">
<!ENTITY a.gallatin "Andrew Gallatin <email>gallatin@FreeBSD.ORG</email>">
<!ENTITY a.gclarkii "Gary Clark II <email>gclarkii@FreeBSD.ORG</email>">
<!ENTITY a.gena "Gennady B. Sorokopud <email>gena@NetVision.net.il</email>">
@ -122,7 +128,7 @@
<!ENTITY a.helbig "Wolfgang Helbig <email>helbig@FreeBSD.ORG</email>">
<!ENTITY a.hm "Hellmuth Michaelis <email>hm@kts.org</email>">
<!ENTITY a.hm "Hellmuth Michaelis <email>hm@FreeBSD.ORG</email>">
<!ENTITY a.hoek "Tim Vanderhoek <email>hoek@FreeBSD.ORG</email>">
@ -212,6 +218,8 @@
<!ENTITY a.md "Mark Dapoz <email>md@bsc.no</email>">
<!ENTITY a.mks "Mike Spengler <email>mks@FreeBSD.ORG</email>">
<!ENTITY a.motoyuki "Motoyuki Konno <email>motoyuki@FreeBSD.ORG</email>">
<!ENTITY a.mph "Matthew Hunt <email>mph@FreeBSD.ORG</email>">
@ -224,6 +232,8 @@
<!ENTITY a.nectar "Jacques Vidrine <email>nectar@FreeBSD.ORG</email>">
<!ENTITY a.newton "Mark Newton <email>newton@FreeBSD.ORG</email>">
<!ENTITY a.nhibma "Nick Hibma <email>n_hibma@FreeBSD.ORG</email>">
<!ENTITY a.nik "Nik Clayton <email>nik@FreeBSD.ORG</email>">
@ -274,6 +284,8 @@
<!ENTITY a.sef "Sean Eric Fagan <email>sef@FreeBSD.ORG</email>">
<!ENTITY a.simokawa "Hidetoshi Shimokawa <email>simokawa@FreeBSD.ORG</email>">
<!ENTITY a.smace "Scott Mace <email>smace@FreeBSD.ORG</email>">
<!ENTITY a.smpatel "Sujal Patel <email>smpatel@FreeBSD.ORG</email>">

View file

@ -51,9 +51,16 @@
</listitem>
<listitem>
<para>FreeBSD mit Methode (in German), publiched by Computer und
Literatur Verlag/Vertrieb Hanser, 1998. ISBN 3-93211-31-0.</para>
<para>FreeBSD mit Methode (in German), published by Computer und
Literatur Verlag/Vertrieb Hanser, 1998. ISBN 3-932311-31-0.</para>
</listitem>
<listitem>
<para><ulink url="http://www.pc.mycom.co.uk/FreeBSD/install-manual.html">FreeBSD
Install and Utilization Manual</ulink> (in Japanese),
published by <ulink url="http://www.pc.mycom.co.jp/">Mainichi
Communications Inc.</ulink>.</para>
</listitem>
</itemizedlist>
@ -111,7 +118,16 @@
University</ulink> has written a <ulink
URL="http://www-wks.acs.ohio-state.edu/unix_course/unix.html">UNIX Introductory Course</ulink> which is available online in HTML and postscript format.</para>
</listitem>
<listitem>
<para><ulink url="http://www.jp.FreeBSD.ORG/">Jpman Project,
Japan FreeBSD Users Group</ulink>. <ulink
url="http://www.pc.mycom.co.jp/FreeBSD/urm.html">FreeBSD
User's Reference Manual</ulink> (Japanese translation).
<ulink url="http://www.pc.mycom.co.jp/">Mainichi
Communications Inc.</ulink>, 1998. ISBN4-8399-0088-4
P3800E.</para>
</listitem>
</itemizedlist>
@ -164,7 +180,16 @@
O'Reilly &amp; Associates, Inc., 1991. <!-- <br> --> ISBN
0-937175-75-7</para>
</listitem>
<listitem>
<para><ulink url="http://www.jp.FreeBSD.ORG/">Jpman Project,
Japan FreeBSD Users Group</ulink>. <ulink
url="http://www.pc.mycom.co.jp/FreeBSD/sam.html">FreeBSD
System Administrator's Manual</ulink> (Japanese translation).
<ulink url="http://www.pc.mycom.co.jp/">Mainichi
Communications Inc.</ulink>, 1998. ISBN4-8399-0109-0
P3300E.</para>
</listitem>
</itemizedlist>

View file

@ -35,13 +35,13 @@
manual is a <emphasis>work in progress</emphasis> and is the work of
many individuals. Many sections do not yet exist and some of those
that do exist need to be updated. If you are interested in helping
with this project, send email to the &a.doc; The latest version of
with this project, send email to the &a.doc;. The latest version of
this document is always available from the <ulink
URL="http://www.FreeBSD.ORG/">FreeBSD World Wide Web server</ulink>.
It may also be downloaded in <ulink url="handbook.latin1">plain
text</ulink>, <ulink url="handbook.ps">postscript</ulink> or <ulink
url="handbook-html.tar.gz">HTML</ulink> with HTTP or gzip'd from the <ulink
url="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/docs/">FreeBSD FTP server</ulink> or one of the numerous <link
url="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/doc/">FreeBSD FTP server</ulink> or one of the numerous <link
linkend="mirrors-ftp">mirror sites</link>. You may also want to
<ulink URL="http://www.FreeBSD.ORG/search.html">Search the Handbook</ulink>.</para>
</abstract>
@ -103,6 +103,7 @@ url="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/docs/">FreeBSD FTP server</ulink> or one
</book>
<!--
Local Variables:
mode: sgml
sgml-indent-data: t
sgml-omittag: nil

View file

@ -993,6 +993,10 @@ box can be opened)</para>
URL="http://www.buffnet.net/">BuffNET</ulink></para>
</listitem>
<listitem>
<para><ulink url="http://www.pacificsolutions.com/">Pacific
Solutions</ulink></para>
</listitem>
</itemizedlist>
</listitem>
@ -1235,7 +1239,11 @@ box can be opened)</para>
<listitem>
<para>Anthony Yee-Hang Chan <email>yeehang@netcom.com</email></para>
</listitem>
<listitem>
<para>Anton Berezin <email>tobez@plab.ku.dk</email></para>
</listitem>
<listitem>
<para>Ari Suutari <email>ari@suutari.iki.fi</email></para>
</listitem>
@ -1279,7 +1287,11 @@ box can be opened)</para>
<listitem>
<para>Brian Clapper <email>bmc@willscreek.com</email></para>
</listitem>
<listitem>
<para>Brian F. Feldman <email>green@unixhelp.org</email></para>
</listitem>
<listitem>
<para>Brian Handy <email>handy@lambic.space.lockheed.com</email></para>
</listitem>
@ -1460,7 +1472,11 @@ box can be opened)</para>
<listitem>
<para>Dean Huxley <email>dean@fsa.ca</email></para>
</listitem>
<listitem>
<para>Dima Sivachenko <email>demon@gpad.ac.ru</email></para>
</listitem>
<listitem>
<para>Dirk Froemberg <email>dirk@hal.in-berlin.de</email></para>
</listitem>
@ -1611,14 +1627,14 @@ box can be opened)</para>
<para>Hidekazu Kuroki <email>hidekazu@cs.titech.ac.jp</email></para>
</listitem>
<listitem>
<para>Hidetoshi Shimokawa <email>simokawa@sat.t.u-tokyo.ac.jp</email></para>
</listitem>
<listitem>
<para>Hideyuki Suzuki <email>hideyuki@sat.t.u-tokyo.ac.jp</email></para>
</listitem>
<listitem>
<para>Hiroaki Sakai <email>sakai@miya.ee.kagu.sut.ac.jp</email></para>
</listitem>
<listitem>
<para>Hironori Ikura <email>hikura@kaisei.org</email></para>
</listitem>
@ -1742,7 +1758,10 @@ box can be opened)</para>
<listitem>
<para>Jim Lowe <email>james@cs.uwm.edu</email></para>
</listitem>
<listitem>
<para>Jim Mock <email>jim@phrantic.phear.net</email></para>
</listitem>
<listitem>
<para>Jim Wilson <email>wilson@moria.cygnus.com</email></para>
</listitem>
@ -1756,6 +1775,10 @@ box can be opened)</para>
<para>Joao Carlos Mendes Luis <email>jonny@coppe.ufrj.br</email></para>
</listitem>
<listitem>
<para>Joe Abley <email>jabley@clear.co.nz</email></para>
</listitem>
<listitem>
<para>Joe &ldquo;Marcus&rdquo; Clarke
<email>marcus@miami.edu</email></para>
@ -1893,7 +1916,11 @@ box can be opened)</para>
<listitem>
<para>Kostya Lukin <email>lukin@okbmei.msk.su</email></para>
</listitem>
<listitem>
<para>KUNISHIMA Takeo <email>kunishi@c.oka-pu.ac.jp</email></para>
</listitem>
<listitem>
<para>Kurt Olsen <email>kurto@tiny.mcs.usu.edu</email></para>
</listitem>
@ -1914,7 +1941,11 @@ box can be opened)</para>
<listitem>
<para>Luigi Rizzo <email>luigi@iet.unipi.it</email></para>
</listitem>
<listitem>
<para>Malte Lance <email>malte.lance@gmx.net</email></para>
</listitem>
<listitem>
<para>Makoto MATSUSHITA <email>matusita@jp.freebsd.org</email></para>
</listitem>
@ -1923,6 +1954,10 @@ box can be opened)</para>
<para>Makoto WATANABE
<email>watanabe@zlab.phys.nagoya-u.ac.jp</email></para>
</listitem>
<listitem>
<para>MANTANI Nobutaka <email>nobutaka@nobutaka.com</email></para>
</listitem>
<listitem>
<para>Manu Iyengar <email>iyengar@grunthos.pscwa.psca.com</email></para>
@ -2055,6 +2090,10 @@ box can be opened)</para>
<listitem>
<para>Motoyuki Kasahara <email>m-hasahr@sra.co.jp</email></para>
</listitem>
<listitem>
<para>Munechika Sumikawa <email>sumikawa@kame.net</email></para>
</listitem>
<listitem>
<para>Murray Stokely <email>murray@cdrom.com</email></para>
@ -2095,7 +2134,11 @@ box can be opened)</para>
<listitem>
<para>Nobuyuki Koganemaru <email>kogane@kces.koganemaru.co.jp</email></para>
</listitem>
<listitem>
<para>Norio Suzuki <email>nosuzuki@e-mail.ne.jp</email></para>
</listitem>
<listitem>
<para>Noritaka Ishizumi <email>graphite@jp.FreeBSD.ORG</email></para>
</listitem>
@ -2115,7 +2158,11 @@ box can be opened)</para>
<listitem>
<para>Oliver Oberdorf <email>oly@world.std.com</email></para>
</listitem>
<listitem>
<para>Palle Girgensohn <email>girgen@partitur.se</email></para>
</listitem>
<listitem>
<para>Paul Fox <email>pgf@foxharp.boston.ma.us</email></para>
</listitem>
@ -2256,6 +2303,10 @@ box can be opened)</para>
<para>Satoshi Taoka <email>taoka@infonets.hiroshima-u.ac.jp</email></para>
</listitem>
<listitem>
<para>Satsuki FUJISHIMA <email>k5@respo.or.jp</email></para>
</listitem>
<listitem>
<para>Scot W. Hetzel <email>hetzels@westbend.net</email></para>
</listitem>
@ -2273,10 +2324,6 @@ box can be opened)</para>
<email>tanimura@naklab.dnj.ynu.ac.jp</email></para>
</listitem>
<listitem>
<para>Seiichirou Hiraoka <email>flathill@flathill.gr.jp</email></para>
</listitem>
<listitem>
<para>Serge Babkin <email>babkin@hq.icb.chel.su</email></para>
</listitem>
@ -2351,6 +2398,10 @@ box can be opened)</para>
<para>Stuart Henderson
<email>stuart@internationalschool.co.uk</email></para>
</listitem>
<listitem>
<para>SUGIMURA Takashi <email>sugimura@jp.FreeBSD.ORG</email></para>
</listitem>
<listitem>
<para>Suzuki Yoshiaki <email>zensyo@ann.tama.kawasaki.jp</email></para>
@ -2416,6 +2467,10 @@ box can be opened)</para>
<para>Tim Wilkinson <email>tim@sarc.city.ac.uk</email></para>
</listitem>
<listitem>
<para>Tom Hukins <email>tom@eborcom.com</email></para>
</listitem>
<listitem>
<para>Tom Jobbins <email>tom@tom.tj</email></para>
</listitem>
@ -2439,7 +2494,11 @@ box can be opened)</para>
<listitem>
<para>Trefor S. <email>trefor@flevel.co.uk</email></para>
</listitem>
<listitem>
<para>Vadim Chekan <email>vadim@gc.lviv.ua</email></para>
</listitem>
<listitem>
<para>Ville Eerola <email>ve@sci.fi</email></para>
</listitem>
@ -2485,7 +2544,7 @@ box can be opened)</para>
</listitem>
<listitem>
<para>Yukihiro Nakai <email>nakai@technologist.com</email></para>
<para>Yukihiro Nakai <email>nakai@iname.com</email></para>
</listitem>
<listitem>

View file

@ -111,18 +111,19 @@
<para>Join the &a.current; and the &a.cvsall; . This is not
just a good idea, it is <emphasis>essential</emphasis>. If
you are not on the <emphasis>FreeBSD-current</emphasis>
mailing list you will not see the comments that people are
mailing list, you will not see the comments that people are
making about the current state of the system and thus will
probably end up stumbling over a lot of problems that others
have already found and solved. Even more importantly, you
will miss out on potentially critical information (e.g.
&ldquo;Yo, Everybody! Before you rebuild
<filename>/usr/src</filename>, you <emphasis>must</emphasis>
rebuild the kernel or your system will crash horribly!&rdquo;).
The <email>cvs-all</email> mailing list will allow you
will miss out on important bulletins which may be critical
to your system's continued health.</para>
<para>The <email>cvs-all</email> mailing list will allow you
to see the commit log entry for each change as it is made
along with any pertinent information on possible
side-effects. To join these lists, send mail to
side-effects.</para>
<para>To join these lists, send mail to
&a.majordomo; and specify:
<programlisting>
@ -151,7 +152,13 @@ subscribe cvs-all</programlisting>
<listitem>
<para>Use the <link linkend="cvsup">cvsup</link>
program with <ulink
URL="ftp://ftp.freebsd.org/pub/FreeBSD/FreeBSD-current/src/share/examples/cvsup/standard-supfile">this supfile</ulink>. This is the second most recommended method, since it allows you to grab the entire collection once and then only what has changed from then on. Many people run cvsup from cron and keep their sources up-to-date automatically.</para>
URL="ftp://ftp.freebsd.org/pub/FreeBSD/FreeBSD-current/src/share/examples/cvsup/standard-supfile">this supfile</ulink>. This is the second most recommended method, since it allows you to grab the entire collection once and then only what has changed from then on. Many people run cvsup from cron and keep their sources up-to-date automatically. For a fairly easy interface to this, simply type:</para>
<informalexample>
<screen>&prompt.root; <userinput>pkg_add -f ftp://ftp.freebsd.org/pub/FreeBSD/CVSup/cvsupit.tgz</userinput></screen>
</informalexample>
</listitem>
<listitem>
@ -182,18 +189,14 @@ subscribe cvs-all</programlisting>
<para>Essentially, if you need rapid on-demand access to the
source and communications bandwidth is not a consideration,
use <command>cvsup</command> or <command>ftp</command>. Otherwise, use <application>CTM</application>.</para>
</listitem>
<listitem>
<para>If you are grabbing the sources to run, and not just
look at, then grab <emphasis>all</emphasis> of current, not
just selected portions. The reason for this is that various
parts of the source depend on updates elsewhere, and trying
to compile just a subset is almost guaranteed to get you
into trouble.</para>
</listitem>
<listitem>
<para>Before compiling current, read the Makefile in
<filename>/usr/src</filename> carefully. You should at
least run a <link
@ -201,7 +204,7 @@ subscribe cvs-all</programlisting>
through as part of the upgrading process. Reading the
&a.current; will keep you up-to-date on other bootstrapping
procedures that sometimes become necessary as we move
towards the next release.</para>
towards the next release.</para>
</listitem>
<listitem>
@ -270,14 +273,25 @@ subscribe cvs-all</programlisting>
in this mailing list when they are contemplating some
controversial fix or update, giving the users a chance to
respond if they have any issues to raise concerning the
proposed change. To join this list, send mail to
&a.majordomo; and say:
proposed change.</para>
<para>The <email>cvs-all</email> mailing list will allow you
to see the commit log entry for each change as it is made
along with any pertinent information on possible
side-effects.</para>
<para>To join these lists, send mail to
&a.majordomo; and specify:
<programlisting>
subscribe freebsd-stable</programlisting> In the body of your
message. Optionally, you can also say <literal>help</literal> and Majordomo
will send you full help on how to subscribe and unsubscribe
to the various other mailing lists we support.</para>
subscribe freebsd-stable
subscribe cvs-all</programlisting>
in the
body of your message. Optionally, you can also say <literal>help</literal>
and Majordomo will send you full help on how to subscribe
and unsubscribe to the various other mailing lists we
support.</para>
</listitem>
<listitem>
@ -514,12 +528,21 @@ subscribe freebsd-stable</programlisting> In the body of your
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_3</term>
<listitem>
<para>The line of development for FreeBSD-3.x, also known as
FreeBSD-stable. Not valid for the ports collection.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_2_2</term>
<listitem>
<para>The line of development for FreeBSD-2.2.x, also known as
FreeBSD-stable. Not valid for the ports collection.</para>
2.2-stable. Not valid for the ports collection.</para>
</listitem>
</varlistentry>
@ -1365,17 +1388,25 @@ cvs-crypto</programlisting>
</note>
</listitem>
</varlistentry>
<varlistentry><term>tag=RELENG_2_2</term>
<listitem>
<para>The line of development for FreeBSD-2.2.x,
also known as FreeBSD-stable. Not valid for the
ports-* collections.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_3</term>
<listitem>
<para>The line of development for FreeBSD-3.x, also known as
FreeBSD-stable. Not valid for the ports collection.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RELENG_2_2</term>
<listitem>
<para>The line of development for FreeBSD-2.2.x, also known as
2.2-stable. Not valid for the ports collection.</para>
</listitem>
</varlistentry>
<varlistentry><term>tag=RELENG_2_1_0</term>
<listitem>

View file

@ -88,12 +88,6 @@
FreeBSD-current</entry>
</row>
<row>
<entry>freebsd-stable</entry>
<entry>Discussion concerning the use of
FreeBSD-stable</entry>
</row>
<row>
<entry>freebsd-isp</entry>
<entry>Issues for Internet Service Providers using
@ -113,8 +107,15 @@
<row>
<entry>freebsd-questions</entry>
<entry>User questions</entry>
<entry>User questions and technical support</entry>
</row>
<row>
<entry>freebsd-stable</entry>
<entry>Discussion concerning the use of
FreeBSD-stable</entry>
</row>
</tbody>
</tgroup>
</informaltable>
@ -146,7 +147,7 @@
<row>
<entry>freebsd-doc</entry>
<entry>The FreeBSD Documentation project</entry>
<entry>Creating FreeBSD related documents</entry>
</row>
<row>
@ -608,33 +609,17 @@ help
</listitem>
</varlistentry>
<varlistentry><term>FREEBSD-STABLE</term>
<listitem>
<para><emphasis>Discussions about the use of
FreeBSD-stable</emphasis></para>
<para>This is the
mailing list for users of freebsd-stable. It includes
warnings about new features coming out in -stable that
will affect the users, and instructions on steps that must
be taken to remain -stable. Anyone running &ldquo;stable&rdquo;
should subscribe to this list. This is a technical mailing
list for which strictly technical content is
expected.</para>
</listitem>
</varlistentry>
<varlistentry><term>FREEBSD-DOC</term>
<listitem>
<para><emphasis>Documentation project</emphasis></para>
<para>This mailing list is for the discussion of documentation
related issues and projects. The members of this mailing list
are collectively referred to as &ldquo;The FreeBSD
Documentation Project&rdquo;. It is an open list; feel free to
join and contribute.</para>
<para>This mailing list is for the discussion of issues and
projects related to the creation of documenation for
FreeBSD. The members of this mailing list are collectively
referred to as &ldquo;The FreeBSD Documentation
Project&rdquo;. It is an open list; feel free to join and
contribute!</para>
</listitem>
</varlistentry>
@ -855,7 +840,24 @@ help
</listitem>
</varlistentry>
<varlistentry><term>FREEBSD-USER-GROUPS</term>
<varlistentry><term>FREEBSD-STABLE</term>
<listitem>
<para><emphasis>Discussions about the use of
FreeBSD-stable</emphasis></para>
<para>This is the
mailing list for users of freebsd-stable. It includes
warnings about new features coming out in -stable that
will affect the users, and instructions on steps that must
be taken to remain -stable. Anyone running &ldquo;stable&rdquo;
should subscribe to this list. This is a technical mailing
list for which strictly technical content is
expected.</para>
</listitem>
</varlistentry>
<varlistentry><term>FREEBSD-USER-GROUPS</term>
<listitem>
<para><emphasis>User Group Coordination
@ -1045,27 +1047,52 @@ help
<listitem>
<para><ulink
URL="http://www.au.freebsd.org/FreeBSD/">http://www.au.freebsd.org/FreeBSD/</ulink> &mdash; Australia.</para>
URL="http://www.au.freebsd.org/FreeBSD/">http://www.au.freebsd.org/FreeBSD/</ulink> &mdash; Australia/1.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www2.au.freebsd.org/FreeBSD/">http://www2.au.freebsd.org/FreeBSD/</ulink> &mdash; Australia/2.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www3.au.freebsd.org/FreeBSD/">http://www3.au.freebsd.org/FreeBSD/</ulink> &mdash; Australia/3.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.br.freebsd.org/www.freebsd.org/">http://www.br.freebsd.org/www.freebsd.org/</ulink> &mdash; Brazil/1.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.br.freebsd.org/">http://www.br.freebsd.org/</ulink> &mdash; Brazil.</para>
URL="http://www.br2.freebsd.org/www.freebsd.org/">http://www.br2.freebsd.org/www.freebsd.org/</ulink> &mdash; Brazil/2.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.ca.freebsd.org/">http://www.ca.freebsd.org/</ulink> &mdash; Canada.</para>
URL="http://www3.br.freebsd.org/">http://www3.br.freebsd.org/</ulink> &mdash; Brazil/3.</para>
</listitem>
<listitem>
<para><ulink
URL="http://sunsite.mff.cuni.cz/www.freebsd.org/">http://sunsite.mff.cuni.cz/www.freebsd.org/</ulink> &mdash; Czech Republic.</para>
URL="http://www.bg.freebsd.org/">http://www.bg.freebsd.org/</ulink> &mdash; Bulgaria.</para>
</listitem>
<listitem>
<para><ulink
URL="http://sunsite.auc.dk/www.freebsd.org/">http://sunsite.auc.dk/www.freebsd.org/</ulink> &mdash; Denmark.</para>
URL="http://www.ca.freebsd.org/">http://www.ca.freebsd.org/</ulink> &mdash; Canada/1.</para>
</listitem>
<listitem>
<para><ulink
URL="http://freebsd.kawartha.com/">http://freebsd.kawartha.com/</ulink> &mdash; Canada/2.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.dk.freebsd.org/">http://www.dk.freebsd.org/</ulink> &mdash; Denmark.</para>
</listitem>
<listitem>
@ -1077,10 +1104,35 @@ help
<para><ulink
URL="http://www.fi.freebsd.org/">http://www.fi.freebsd.org/</ulink> &mdash; Finland.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.fr.freebsd.org/">http://www.fr.freebsd.org/</ulink> &mdash; France.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.de.freebsd.org/">http://www.de.freebsd.org/</ulink> &mdash; Germany/1.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.de.freebsd.org/">http://www.de.freebsd.org/</ulink> &mdash; Germany.</para>
URL="http://www1.de.freebsd.org/">http://www1.de.freebsd.org/</ulink> &mdash; Germany/2.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www2.de.freebsd.org/">http://www.de.freebsd.org/</ulink> &mdash; Germany/3.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.hu.freebsd.org/">http://www.hu.freebsd.org/</ulink> &mdash; Hungary.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.is.freebsd.org/">http://www.is.freebsd.org/</ulink> &mdash; Iceland.</para>
</listitem>
<listitem>
@ -1090,7 +1142,7 @@ help
<listitem>
<para><ulink
URL="http://www.jp.freebsd.org/">http://www.jp.freebsd.org/</ulink> &mdash; Japan.</para>
URL="http://www.jp.freebsd.org/www.freebsd.org/">http://www.jp.freebsd.org/www.freebsd.org/</ulink> &mdash; Japan.</para>
</listitem>
<listitem>
@ -1098,6 +1150,16 @@ help
URL="http://www.kr.freebsd.org/">http://www.kr.freebsd.org/</ulink> &mdash; Korea.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.lv.freebsd.org/">http://www.lv.freebsd.org/</ulink> &mdash; Latvia.</para>
</listitem>
<listitem>
<para><ulink
URL="http://rama.asiapac.net/freebsd/">http://rama.asiapac.net/freebsd/</ulink> &mdash; Malaysia.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.nl.freebsd.org/">http://www.nl.freebsd.org/</ulink> &mdash; Netherlands.</para>
@ -1105,7 +1167,67 @@ help
<listitem>
<para><ulink
URL="http://www.pt.freebsd.org/">http://www.pt.freebsd.org/</ulink> &mdash; Portugal.</para>
URL="http://www.no.freebsd.org/">http://www.no.freebsd.org/</ulink> &mdash; Norway.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.pt.freebsd.org/">http://www.pt.freebsd.org/</ulink> &mdash; Portugal/1.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www2.pt.freebsd.org/">http://www2.pt.freebsd.org/</ulink> &mdash; Portugal/2.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www3.pt.freebsd.org/">http://www3.pt.freebsd.org/</ulink> &mdash; Portugal/3.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.ro.freebsd.org/">http://www.ro.freebsd.org/</ulink> &mdash; Romania.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.ru.freebsd.org/">http://www.ru.freebsd.org/</ulink> &mdash; Russia/1.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www2.ru.freebsd.org/">http://www2.ru.freebsd.org/</ulink> &mdash; Russia/2.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www3.ru.freebsd.org/">http://www3.ru.freebsd.org/</ulink> &mdash; Russia/3.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.sk.freebsd.org/">http://www.sk.freebsd.org/</ulink> &mdash; Slovak Republic.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.si.freebsd.org/">http://www.si.freebsd.org/</ulink> &mdash; Slovenia.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.es.freebsd.org/">http://www.es.freebsd.org/</ulink> &mdash; Spain.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.za.freebsd.org/">http://www.za.freebsd.org/</ulink> &mdash; South Africa/1.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www2.za.freebsd.org/">http://www2.za.freebsd.org/</ulink> &mdash; South Africa/2.</para>
</listitem>
<listitem>
@ -1115,14 +1237,38 @@ help
<listitem>
<para><ulink
URL="http://www.tw.freebsd.org/freebsd.html">http://www.tw.freebsd.org/freebsd.html</ulink> &mdash; Taiwan.</para>
URL="http://www.tr.freebsd.org/">http://www.tr.freebsd.org/</ulink> &mdash; Turkey.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www2.ua.freebsd.org/">http://www2.ua.freebsd.org/</ulink> &mdash; Ukraine.</para>
URL="http://www.ua.freebsd.org/">http://www.ua.freebsd.org/</ulink> &mdash; Ukraine/1.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www2.ua.freebsd.org/">http://www2.ua.freebsd.org/</ulink> &mdash; Ukraine/2.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www.uk.freebsd.org/">http://www.uk.freebsd.org/</ulink> &mdash; United Kingdom.</para>
</listitem>
<listitem>
<para><ulink
URL="http://freebsd.advansys.net/">http://freebsd.advansys.net/</ulink> &mdash; USA/Indiana.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www6.freebsd.org/">http://www6.freebsd.org/</ulink> &mdash; USA/Oregon.</para>
</listitem>
<listitem>
<para><ulink
URL="http://www2freebsd.org/">http://www2.freebsd.org/</ulink> &mdash; USA/Texas.</para>
</listitem>
</itemizedlist>

View file

@ -349,13 +349,17 @@
first full release (2.2.1) was released in April, 1997. Further
releases along the 2.2 branch were done in the Summer and Fall of
'97, the latest being 2.2.7 which appeared in late July of '98.
The first official 3.0 release will appear in October, 1998 and the
last release on the 2.2 branch, 2.2.8, will appear in November.</para>
<para>Long term development projects for everything from SMP to DEC
ALPHA support will continue to take place in the 3.0-current branch
and SNAPshot releases of 3.0 on CDROM (and, of course, on the net).</para>
The first official 3.0 release appeared in October, 1998 and the
last release on the 2.2 branch, 2.2.8, appeared in November,
1998.</para>
<para>The tree branched again on Jan 20, 1999. This led to
4.0-current and a 3.x-stable branch, from which 3.1 will be
released on February 15th, 1999.</para>
<para>Long term development projects will continue to take place in
the 4.0-current branch and SNAPshot releases of 4.0 on CDROM (and,
of course, on the net).</para>
</sect1>
<sect1 id="goals">

View file

@ -73,9 +73,11 @@
<note>
<para>If there is <emphasis>not</emphasis> a
<filename>/usr/src/sys</filename> directory on your system, then
the kernel source has not been been installed. Follow the
instructions for installing packages to add this package to your
system.</para>
the kernel source has not been been installed. The easiest way
to do this is by running <command>/stand/sysinstall</command> as
<username>root</username>, choosing <literal>Configure</literal>,
then <literal>Distributions</literal>, then <literal>src</literal>,
then <literal>sys</literal>.</para>
</note>
<para>Next, move to the <filename>i386/conf</filename> directory and

View file

@ -433,7 +433,7 @@ Abort</screen>
</informalexample>
<para>To help the FreeBSD kernel distinguish between a FreeBSD ELF
binary from a Linux one, use the <citerefentry>
binary from a Linux binary, use the <citerefentry>
<refentrytitle>brandelf</refentrytitle>
<manvolnum>1</manvolnum>
</citerefentry> utility.</para>

View file

@ -529,7 +529,7 @@ bigco.com. MX 10 bigco.com.
<filename>/etc/rc.conf</filename> ) 15 minutes to connect to your
host to deliver the mail to the primary MX site.</para>
<para>You might wat to use something like this as a login script.</para>
<para>You might want to use something like this as a login script.</para>
<programlisting>
#!/bin/sh

View file

@ -722,7 +722,7 @@
<listitem>
<para><ulink
URL="ftp://ftp.ua.FreeBSD.ORG/pub/FreeBSD">ftp://ftp.ua.FreeBSD.ORG/pub/FreeBSD</ulink> Contact: <email>archer@lucky.net</email>.</para>
URL="ftp://ftp.ua.FreeBSD.ORG/pub/FreeBSD">ftp://ftp.ua.FreeBSD.ORG/pub/FreeBSD</ulink> Contact: <email>freebsd-mnt@lucky.net</email>.</para>
</listitem>
</itemizedlist>
@ -1269,7 +1269,7 @@
<itemizedlist>
<listitem>
<para>cvsup2.ua.FreeBSD.ORG (maintainer <email>archer@lucky.net</email>)</para>
<para>cvsup2.ua.FreeBSD.ORG (maintainer <email>freebsd-mnt@lucky.net</email>)</para>
</listitem>
</itemizedlist>
@ -1310,6 +1310,9 @@
<para>cvsup3.FreeBSD.ORG (maintainer <email>wollman@FreeBSD.ORG</email>)</para>
</listitem>
<listitem>
<para>cvsup4.FreeBSD.ORG (maintainer <email>shmit@rcn.com</email>)</para>
</listitem>
</itemizedlist>
</listitem>

View file

@ -495,6 +495,75 @@ vvlVQ0UbcR0N2+5F6Mb5GqrXZpIesn7jFJpkQKPU
-----END PGP PUBLIC KEY BLOCK-----</programlisting>
</sect2>
</sect1>
<sect1>
<title>Developers</title>
<sect2>
<title>&a.wosch;</title>
<programlisting>
Type Bits/KeyID Date User ID
pub 1024/2B7181AD 1997/08/09 Wolfram Schneider &lt;wosch@FreeBSD.org&gt;
Fingerprint = CA 16 91 D9 75 33 F1 07 1B F0 B4 9F 3E 95 B6 09
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: 2.6.3ia
mQCNAzPs+aEAAAEEAJqqMm2I9CxWMuHDvuVO/uh0QT0az5ByOktwYLxGXQmqPG1G
Q3hVuHWYs5Vfm/ARU9CRcVHFyqGQ3LepoRhDHk+JcASHan7ptdFsz7xk1iNNEoe0
vE2rns38HIbiyQ/2OZd4XsyhFOFtExNoBuyDyNoe3HbHVBQT7TmN/mkrcYGtAAUR
tCVXb2xmcmFtIFNjaG5laWRlciA8d29zY2hARnJlZUJTRC5vcmc+iQCVAwUQNmrS
AzmN/mkrcYGtAQFQjAP8CthNueur8XDAZqC5q6NQcDs0PqqQ+raTUfQTv6Km6ykf
UzdpDlBoRC+CCyHfBfC5zo9N6mB7iV7qS1PljrdIh6VAwHxJN9iopB/x6+nsBvmy
0YSNt7eyfFrIVegCJvd4ALz5JBV8ZstznOwo8RAhDD0gX58F8nDhgWjy62JekGK0
IldvbGZyYW0gU2NobmVpZGVyIDx3b3NjaEBhcGZlbC5kZT6JARUDBRA2Z9ZcCMks
sk6wLt0BAQBICACcTiDZ/AyYWRDLXsBOK+WMRoNk3+bQZ1cdy11nwJo+taT/389M
0r5TrEJ7CogpXC2rFUExTVWldSFZd8A1YIHtrTsP7YauUH0nA7k0wUnqDRYj8YJR
eMLFvc1OQ2y+mkvxF2BzzBzh/bcYbgJdWCB1MPahSNQfkGXtp+A5PjEs8Cp4+FLu
EUFScyxsD3g5/E+0d7mirJpe3pxcf9KCmFGHM89mrTKODQR/7N8dVqa9npeXZotm
ZK8Jz+tvRKFgNiLf2XL048+IE8ZtJXDYaDzTirHdcAqJMWQuxthCdG3ta4I+w5WM
WR8JtBLfVNpyU7LN6dl0IB7O5sYhyskApmMwiQCVAwUQM+z5oTmN/mkrcYGtAQGU
gAP/cJGro/SbV+L19s/Gem26KmegUH+bfIXoh2EzyRJ7heVdybu1LrSDFApmAE7d
sMDlAA1wd2XjVWD3nIEBl6k+J7qJB4ACjKVGs414jLpdKGPHdLRYqYDj4LyQFMv6
/BpSoX1gnWp6xlC2xeWRan9ns3XZGS55UBVDvBE/B+fPoTe0JFdvbGZyYW0gU2No
bmVpZGVyIDxzY2huZWlkZXJAemliLmRlPokAlQMFEDZq0dI5jf5pK3GBrQEB38QD
/3NYyRPIejtXXq/okdDRyhWmA8cv0KG6gEupKCQKa7ep/OZTw/KxrN3ZOS8zlPod
tEn8mol+4SvY5AgSMdjQ0jTd1JdFcMKFnbJJrJ3b9IpwCqbkXy25rTUcQn9ICP47
rFKC4qR/Ucrg5YVVhQ3pVJX6XuO2XvuG7euHAQNXV3e2
=EpJQ
-----END PGP PUBLIC KEY BLOCK-----</programlisting>
</sect2>
<sect2>
<title>&a.brian;</title>
<programlisting>
Type Bits/KeyID Date User ID
pub 1024/666A7421 1997/04/30 Brian Somers &lt;brian@Awfulhak.org&gt;
Key fingerprint = 2D 91 BD C2 94 2C 46 8F 8F 09 C4 FC AD 12 3B 21
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: 2.6.3ia
mQCNAzNmogUAAAEEALdsjVsV2dzO8UU4EEo7z3nYuvB2Q6YJ8sBUYjB8/vfR5oZ9
7aEQjgY5//pXvS30rHUB9ghk4kIFSljzeMudE0K2zH5n2sxpLbBKWZRDLS7xnrDC
I3j9CNKwQBzMPs0fUT46gp96nf1X8wPiJXkDUEia/c0bRbXlLw7tvOdmanQhAAUR
tCFCcmlhbiBTb21lcnMgPGJyaWFuQGF3ZnVsaGFrLm9yZz6JAJUDBRAzbedc77Ox
BWZTbW0BAVtFA/42QelA3RBXYUtIcYGob+QsWkA1kGyBKQGPSS9coHdUVjClBRl3
UZFmZhxAODb7cBRXmpvx2ZuMrhn/MpXTMqPOJaE3FYm+5SoeArphsRU+T8XofxfL
vRHkM3JURUjIVZdAQNvxxBso8NJG5KayP0Q96Vw+3sEwFK49jt14RCJy4IkAlQMF
EDNzvb1sq+iWcxFJBQEBfZwD/R3KNFf9ype9Dea8j1YIeNZ1E3e03en1I8fMj6Em
S1/L1WfFzMnfFCxZs7JgPtkBuB3CqP8f+LOdDt6PHPqNakmI9E6fiuGfJZ3jFZYA
TXa0XKuIoxIJNKhqkpbF8ixJZFTxFwAAwVYM3+sqr4qQ8FzVc5entxjyxPFNkwJw
RWV+iQCVAwUQM2aiBQ7tvOdmanQhAQE7LgQAiN6Hz+zd8bh0nO6VizbJxWFRHPbr
QWnJXGoMYyy88DyszAXC4zRshlyGUDQdHeP/1DFCXDEu78GfDCLaJ1bm25yVR7kL
xDZaEUQEbWqxfiwuzizAjkaxrW7dBbWILwWqrYF5TXClw+oUU/oIUW4t6t+GpAO1
8PLYhSMXVYErrAA=
=EdyZ
-----END PGP PUBLIC KEY BLOCK-----</programlisting>
</sect2>
</sect1>
</chapter>
<!--

View file

@ -110,7 +110,7 @@
<para>If you look at a port skeleton (either on <ulink
URL="file://localhost/usr/ports/devel/ElectricFence">your FreeBSD
system</ulink> or <ulink
URL="ftp://ftp.freebsd.org/pub/FreeBSD/ports/devel/ElectricFence">the FTP site</ulink>) and expect to find all sorts of pointy-headed rocket science lurking there, you may be disappointed by the one or two rather unexciting-looking files and directories you find there. (We will discuss in a minute how to go about <link
URL="ftp://ftp.freebsd.org/pub/FreeBSD/ports/ports/devel/ElectricFence">the FTP site</ulink>) and expect to find all sorts of pointy-headed rocket science lurking there, you may be disappointed by the one or two rather unexciting-looking files and directories you find there. (We will discuss in a minute how to go about <link
linkend="ports-getting">Getting a port</link>).</para>
<para>&ldquo;How on earth can this do anything?&rdquo; I hear you cry. &ldquo;There
@ -243,7 +243,25 @@ install -c -o bin -g bin -m 444 /usr/ports/devel/ElectricFence/work/ElectricFenc
collection's built in search path should find the tarballs in
<filename>/cdrom/ports/distfiles/</filename> (if they exist there)
rather than downloading them over the net.</para>
<para>Another way of doing this, if you want to just use the port
skeletons on the CDROM, is to set these variables in
<filename>/etc/make.conf</filename>:</para>
<programlisting>
PORTSDIR= /cdrom/ports
DISTDIR= /tmp/distfiles
WRKDIRPREFIX= /tmp</programlisting>
<para>Substitute <literal>/tmp</literal> for any place you have enough
free space. Then, just <command>cd</command> to the appropriate
subdirectory under <filename>/cdrom/ports</filename> and type
<command>make install</command> as
usual. <makevar>WRKDIRPREFIX</makevar> will cause the port to be
build under <filename>/tmp/cdrom/ports</filename>; for instance,
<filename>games/oneko</filename> will be built under
<filename>/tmp/cdrom/ports/games/oneko</filename>.</para>
<note>
<para>There are some ports for which we cannot provide the
original source in the CDROM due to licensing limitations. In
@ -283,7 +301,7 @@ install -c -o bin -g bin -m 444 /usr/ports/devel/ElectricFence/work/ElectricFenc
&prompt.root; <userinput>ftp ftp.freebsd.org</userinput>
[log in as `ftp' and give your email address when asked for a
password. Remember to use binary (also known as image) mode!]
<prompt>&gt;</prompt> <userinput>cd /pub/FreeBSD/ports/databases</userinput>
<prompt>&gt;</prompt> <userinput>cd /pub/FreeBSD/ports/ports/databases</userinput>
<prompt>&gt;</prompt> <userinput>get gnats.tar</userinput>
[tars up the gnats skeleton for us]
<prompt>&gt;</prompt> <userinput>quit</userinput>
@ -315,7 +333,7 @@ password. Remember to use binary (also known as image) mode!]
&prompt.root; <userinput>ftp ftp.freebsd.org</userinput>
[log in as `ftp' and give your email address when asked for a
password. Remember to use binary (also known as image) mode!]
<prompt>&gt;</prompt> <userinput>cd /pub/FreeBSD/ports</userinput>
<prompt>&gt;</prompt> <userinput>cd /pub/FreeBSD/ports/ports</userinput>
<prompt>&gt;</prompt> <userinput>get databases.tar</userinput>
[tars up the databases directory for us]
<prompt>&gt;</prompt> <userinput>quit</userinput>
@ -501,7 +519,7 @@ do-install:
<para>Grab the pre-compiled package from a ftp server. The
&ldquo;master&rdquo; package collection is on FreeBSD's FTP server in
the <ulink
URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/packages/">packages
URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/packages/">packages
directory</ulink>, though check your local mirror first,
please! These are more likely to work (on the whole) than
trying to compile from source and a lot faster besides! Use
@ -759,7 +777,7 @@ do-install:
<informalexample>
<screen>&prompt.root; <userinput>cd /usr/ports/directory</userinput>
&prompt.root; <userinput>make MASTER_SITE_OVERRIDE=ftp://ftp.FreeBSD.ORG/pub/FreeBSD/distfiles/ fetch</userinput></screen>
&prompt.root; <userinput>make MASTER_SITE_OVERRIDE=ftp://ftp.FreeBSD.ORG/pub/FreeBSD/ports/distfiles/ fetch</userinput></screen>
</informalexample>
</listitem>
@ -1348,7 +1366,7 @@ lib/X11/oneko/mouse.xpm
URL <makevar>MASTER_SITES</makevar>,
which is set in the Makefile, as well as our main ftp
site at <ulink
URL="ftp://ftp.freebsd.org/pub/FreeBSD/distfiles/">ftp://ftp.freebsd.org/pub/FreeBSD/distfiles/,</ulink> where we put sanctioned distfiles as backup. It will then attempt to fetch the named distribution file with <makevar>FETCH</makevar>, assuming that the requesting site has direct access to the Internet. If that succeeds, it will save the file in <makevar>DISTDIR</makevar> for future use and proceed.</para>
URL="ftp://ftp.freebsd.org/pub/FreeBSD/ports/distfiles/">ftp://ftp.freebsd.org/pub/FreeBSD/ports/distfiles/,</ulink> where we put sanctioned distfiles as backup. It will then attempt to fetch the named distribution file with <makevar>FETCH</makevar>, assuming that the requesting site has direct access to the Internet. If that succeeds, it will save the file in <makevar>DISTDIR</makevar> for future use and proceed.</para>
</step>
<step>
@ -1398,7 +1416,7 @@ lib/X11/oneko/mouse.xpm
<step>
<para>The <maketarget>build</maketarget> target is run. This is responsible for
descending into the ports' private working directory
descending into the port's private working directory
(<makevar>WRKSRC</makevar>) and
building it. If <makevar>USE_GMAKE</makevar> is set, GNU
<command>make</command> will be used,
@ -1435,7 +1453,7 @@ lib/X11/oneko/mouse.xpm
<note>
<para>The &ldquo;main&rdquo; targets (e.g., <maketarget>extract</maketarget>, <maketarget>configure</maketarget>, etc.) do nothing more than
make sure all the stages up to that one is completed and
make sure all the stages up to that one are completed and
call the real targets or scripts, and they are not intended
to be changed. If you want to fix the extraction, fix
<maketarget>do-extract</maketarget>, but never ever
@ -1471,7 +1489,7 @@ lib/X11/oneko/mouse.xpm
<filename>public_html/</filename> directory on
<hostid>freefall</hostid>),
we can &ldquo;house&rdquo; it ourselves by putting
it on <filename>ftp://ftp.freebsd.org/pub/FreeBSD/distfiles/LOCAL_PORTS/</filename> as the last resort. Please refer to this
it on <filename>ftp://ftp.freebsd.org/pub/FreeBSD/ports/distfiles/LOCAL_PORTS/</filename> as the last resort. Please refer to this
location as <makevar>MASTER_SITE_LOCAL</makevar>. Send mail to
the &a.ports;if you are not sure what to do.</para>
@ -1488,7 +1506,7 @@ lib/X11/oneko/mouse.xpm
<para>If your port requires some additional `patches' that are
available on the Internet, fetch them too and put them in
<makevar>DISTDIR</makevar>. Do not worry if
they come from site other than where you got the main source
they come from a site other than where you got the main source
tarball, we have a way to handle these situations (see the
description of <link
linkend="porting-patchfiles">PATCHFILES</link> below).</para>
@ -1726,7 +1744,7 @@ MASTER_SITE_SUBDIR= applications</programlisting>
<para>If the patch is not relative to the top of the source tree
(i.e., <makevar>WKRSRC</makevar>) because it
contains some extra pathnames, set <makevar>PATCH_DIST_STRIP</makevar> accordingly.
For instance, if all the pathnames in the patch has an extra
For instance, if all the pathnames in the patch have an extra
<literal>foozolix-1.0/</literal> in front of the
filenames, then set
<literal>PATCH_DIST_STRIP=-p1</literal>.</para>
@ -1978,7 +1996,7 @@ BUILD_DEPENDS= /nonexistent:${PORTSDIR}/graphics/jpeg:extract</programlisting>
other way the behaviour you want can be accomplished. It will
cause the other port to be always build (and installed, by
default), and the dependency will go into the packages as
well. If this is really what you need, I recommend you to
well. If this is really what you need, I recommend you
write it as <literal>BUILD_DEPENDS</literal> and
<literal>RUN_DEPENDS</literal> instead&mdash;at least the
intention will be clear.</para>
@ -2077,7 +2095,7 @@ lib/libtvl80.so.1
<sect2>
<title>ELF support</title>
<para>Since FreeBSD is moving to ELF from 3.0-release onwards,
<para>Since FreeBSD is moving to ELF shortly after 3.0-release,
we need to convert many ports that build shared libraries
to support ELF. Complicating this task is that a 3.0
system can run as both ELF and a.out, and that there will
@ -2778,8 +2796,8 @@ diff -u -r1.15 PLIST
<sect3>
<title><filename>INSTALL</filename></title>
<para>If your port needs execute commands when the binary package is
installed with <command>pkg_add</command> you can do with via the
<para>If your port needs to execute commands when the binary package is
installed with <command>pkg_add</command> you can do this via the
<filename>pkg/INSTALL</filename> script. This script will
automatically be added to the package, and will be run twice by
<command>pkg_add</command>. The first time will as
@ -2796,7 +2814,7 @@ diff -u -r1.15 PLIST
<note>
<para>This script is not run automatically if you install the port
with <command>make install</command>. If you are depending on
it being run, you will have to explicitly call it on your port's
it being run, you will have to explicitly call it from your port's
<filename>Makefile</filename>.</para>
</note>
</sect3>
@ -2862,15 +2880,87 @@ PLIST_SUB= OCTAVE_VERSION=${OCTAVE_VERSION}</programlisting>
<maketarget>post-install</maketarget> to a file named
<makevar>TMPPLIST</makevar>.</para>
</sect3>
<sect3>
<title id="porting-pkgsubdir">Changing the names of files in the
<filename>pkg</filename> subdirectory</title>
<para>All the filenames in the <filename>pkg</filename> subdirectory
are defined using variables so you can change them in your
<filename>Makefile</filename> if need be. This is especially useful when you
are sharing the same <filename>pkg</filename> subdirectory among
several ports or have to write to one of the above files (see
<link linkend="porting-wrkdir">writing to places other than
<makevar>WRKDIR</makevar></link> for why it is a bad idea to
write directly in to the <filename>pkg</filename>
subdirectory.</para>
<para>Here is a list of variable names and their default
values.</para>
<informaltable frame="none">
<tgroup cols="2">
<thead>
<row>
<entry>Variable</entry>
<entry>Default value</entry>
</row>
</thead>
<tbody>
<row>
<entry><makevar>COMMENT</makevar></entry>
<entry><literal>${PKGDIR}/DESCR</literal></entry>
</row>
<row>
<entry><makevar>DESCR</makevar></entry>
<entry><literal>${PKGDIR}/DESCR</literal></entry>
</row>
<row>
<entry><makevar>PLIST</makevar></entry>
<entry><literal>${PKGDIR}/PLIST</literal></entry>
</row>
<row>
<entry><makevar>PKGINSTALL</makevar></entry>
<entry><literal>${PKGDIR}/PKGINSTALL</literal></entry>
</row>
<row>
<entry><makevar>PKGDEINSTALL</makevar></entry>
<entry><literal>${PKGDIR}/PKGDEINSTALL</literal></entry>
</row>
<row>
<entry><makevar>PKGREQ</makevar></entry>
<entry><literal>${PKGDIR}/REQ</literal></entry>
</row>
<row>
<entry><makevar>PKGMESSAGE</makevar></entry>
<entry><literal>${PKGDIR}/MESSAGE</literal></entry>
</row>
</tbody>
</tgroup>
</informaltable>
<para>Please change these variables rather than overriding
<makevar>PKG_ARGS</makevar>. If you change
<makevar>PKG_ARGS</makevar>, those files will not correctly be
installed in <filename>/var/db/pkg</filename> upon install from a
port.</para>
</sect3>
</sect2>
<sect2>
<title>Licensing Problems</title>
<para>Some software packages have restrictive licenses or can be
in violation to the law (PKP's patent on public key crypto, ITAR
(export of crypto software) to name just two of them). What we
can do with them vary a lot, depending on the exact wordings of
can do with them varies a lot, depending on the exact wordings of
the respective licenses.</para>
<note>
@ -3031,6 +3121,35 @@ post-install:
with all the appropriate flags. See below for an example on how
to use them.</para>
</sect3>
<sect3 id="porting-wrkdir">
<title><makevar>WRKDIR</makevar></title>
<para>Do not write anything to files outside
<makevar>WRKDIR</makevar>. <makevar>WRKDIR</makevar> is the only
place that is guaranteed to be writable during the port build (see
<link linkend="ports-cd">compiling ports from CDROM</link> for an
example of building ports from a read-only tree). If you need to
modigy some file in <makevar>PKGDIR</makevar>, do so by <link
linkend="porting-pkgsubdir">redefining a variable</link>, not by
writing over it.</para>
</sect3>
<sect3>
<title><makevar>WRKDIRPREFIX</makevar></title>
<para>Make sure your port honors
<makevar>WRKDIRPREFIX</makevar>. Most ports don't have to worry
about this. In particular, if you are referring to a
<makevar>WRKDIR</makevar> of another port, note that the correct
location is
<filename><makevar>WRKDIRPREFIX</makevar><makevar>PORTSDIR</makevar>/<replaceable>subdir</replaceable>/<replaceable>name</replaceable>/work</filename> not <filename><makevar>PORTSDIR</makevar>/<replaceable>subdir</replaceable>/<replaceable>name</replaceable>/work</filename> or <filename><makevar>.CURDIR</makevar>/../../<replaceable>subdir</replaceable>/<replaceable>name</replaceable>/work</filename> or some such.</para>
<para>Also, if you are defining <makevar>WRKDIR</makevar> yourself,
make sure you prepend
<literal>&dollar;{WKRDIRPREFIX}&dollar;{.CURDIR}</literal> in the
front.</para>
</sect3>
<sect3 id="porting-versions">
<title>Differentiating operating systems and OS versions</title>
@ -3055,7 +3174,7 @@ post-install:
#endif</programlisting>
<para>to the proper place in the <filename>.c</filename> file. We
believe that every system that defines these to symbols has
believe that every system that defines these two symbols has
<filename>sys/param.h</filename>. If you find a system that
doesn't, we would like to know. Please send mail to the
&a.ports;.</para>
@ -3094,7 +3213,7 @@ post-install:
<para>The value of the <literal>BSD</literal> macro is
<literal>199506</literal> for the 4.4BSD-Lite2 code base. This is
stated for informational purposes only. It should not be used to
distinguish between version of FreeBSD based only on 4.4-Lite vs.
distinguish between versions of FreeBSD based only on 4.4-Lite vs.
versions that have merged in changes from 4.4-Lite2. The
<literal>__FreeBSD__</literal> macro should be used
instead.</para>
@ -3315,6 +3434,26 @@ post-install:
<entry>3.0-current after 3.0-RELEASE</entry>
<entry>300006</entry>
</row>
<row>
<entry>3.0-stable after 3/4 branch</entry>
<entry>300007</entry>
</row>
<row>
<entry>3.1-RELEASE</entry>
<entry>310000</entry>
</row>
<row>
<entry>3.1-stable after 3.1-RELEASE</entry>
<entry>310001</entry>
</row>
<row>
<entry>4.0-current after 3/4 branch</entry>
<entry>400000</entry>
</row>
</tbody>
</tgroup>
</informaltable>
@ -3649,8 +3788,8 @@ post-install:
<filename>info</filename> (documentation for info browser)
or <filename>share</filename> (architecture independent
files). See man <citerefentry><refentrytitle>hier</refentrytitle><manvolnum>7</manvolnum></citerefentry> for
details, the rule governing <filename>/usr</filename> pretty
much applies to <filename>/usr/local</filename> too. The
details, the rules governing <filename>/usr</filename> pretty
much apply to <filename>/usr/local</filename> too. The
exception are ports dealing with USENET &ldquo;news&rdquo;. They may use
<filename><makevar>PREFIX</makevar>/news</filename> as a destination for
their files.</para>
@ -4125,6 +4264,11 @@ pre-install:
</thead>
<tbody>
<row>
<entry><filename>afterstep*</filename></entry>
<entry>Ports to support AfterStep window manager</entry>
</row>
<row>
<entry><filename>archivers</filename></entry>
<entry>Archiving tools.</entry>
@ -4290,18 +4434,18 @@ pre-install:
<entry>Ports from the OffiX suite.</entry>
</row>
<row>
<entry><filename>palm</filename></entry>
<entry>Software support for the 3Com Palm(tm) series.</entry>
</row>
<row>
<entry><filename>perl5*</filename></entry>
<entry>Ports that require perl version 5 to run.</entry>
</row>
<row>
<entry><filename>pilot*</filename></entry>
<entry>Software to use with the 3Com PalmPilot.</entry>
</row>
<row>
<entry><filename>plan9</filename></entry>
<entry><filename>plan9*</filename></entry>
<entry>Various programs from Plan9.</entry>
</row>
@ -4387,6 +4531,12 @@ pre-install:
<entry>Vietnamese language support.</entry>
</row>
<row>
<entry><filename>windowmaker*</filename></entry>
<entry>Ports to support the WindowMaker window
manager</entry>
</row>
<row>
<entry><filename>www</filename></entry>
<entry>Software related to the World Wide Web. HTML language

View file

@ -1439,6 +1439,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
as any combination of ranges and/or individual types
separated by commas. Commonly used ICMP types are:
<literal>0</literal> echo reply (ping reply),
<literal>3</literal> destination unreachable,
<literal>5</literal> redirect, <literal>8</literal> echo request (ping request), and
<literal>11</literal> time exceeded (used to
indicate TTL expiration as with

View file

@ -216,10 +216,18 @@
<para>&a.lars;</para>
</listitem>
<listitem>
<para>&.dirk;</para>
</listitem>
<listitem>
<para>&a.billf;</para>
</listitem>
<listitem>
<para>&a.gallatin;</para>
</listitem>
<listitem>
<para>&a.tg;</para>
</listitem>
@ -275,7 +283,11 @@
<listitem>
<para>&a.flathill;</para>
</listitem>
<listitem>
<para>&a.foxfair;</para>
</listitem>
<listitem>
<para>&a.hosokawa;</para>
</listitem>
@ -359,7 +371,11 @@
<listitem>
<para>&a.ken;</para>
</listitem>
<listitem>
<para>&a.hm;</para>
</listitem>
<listitem>
<para>&a.tedm;</para>
</listitem>
@ -380,6 +396,10 @@
<para>&a.alex;</para>
</listitem>
<listitem>
<para>&a.newton;</para>
</listitem>
<listitem>
<para>&a.rnordier;</para>
</listitem>
@ -479,7 +499,11 @@
<listitem>
<para>&a.jseger;</para>
</listitem>
<listitem>
<para>&a.simokawa;</para>
</listitem>
<listitem>
<para>&a.vanilla;</para>
</listitem>
@ -495,7 +519,11 @@
<listitem>
<para>&a.brian;</para>
</listitem>
<listitem>
<para>&a.mks;</para>
</listitem>
<listitem>
<para>&a.stark;</para>
</listitem>
@ -604,7 +632,7 @@
</listitem>
</varlistentry>
<varlistentry><term>Gallery and Commercial Editor</term>
<varlistentry><term>Gallery Editor</term>
<listitem>
<para>&a.nsj;</para>
@ -613,7 +641,23 @@
</listitem>
</varlistentry>
<varlistentry>
<term>Commercial Editor</term>
<listitem>
<para>&a.mbarkah;</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Web Changes Editor</term>
<listitem>
<para>&a.mbarkah;</para>
</listitem>
</varlistentry>
<varlistentry><term>Style Police &amp; Art Director</term>
<listitem>

View file

@ -110,7 +110,7 @@
<para>If you look at a port skeleton (either on <ulink
URL="file://localhost/usr/ports/devel/ElectricFence">your FreeBSD
system</ulink> or <ulink
URL="ftp://ftp.freebsd.org/pub/FreeBSD/ports/devel/ElectricFence">the FTP site</ulink>) and expect to find all sorts of pointy-headed rocket science lurking there, you may be disappointed by the one or two rather unexciting-looking files and directories you find there. (We will discuss in a minute how to go about <link
URL="ftp://ftp.freebsd.org/pub/FreeBSD/ports/ports/devel/ElectricFence">the FTP site</ulink>) and expect to find all sorts of pointy-headed rocket science lurking there, you may be disappointed by the one or two rather unexciting-looking files and directories you find there. (We will discuss in a minute how to go about <link
linkend="ports-getting">Getting a port</link>).</para>
<para>&ldquo;How on earth can this do anything?&rdquo; I hear you cry. &ldquo;There
@ -243,7 +243,25 @@ install -c -o bin -g bin -m 444 /usr/ports/devel/ElectricFence/work/ElectricFenc
collection's built in search path should find the tarballs in
<filename>/cdrom/ports/distfiles/</filename> (if they exist there)
rather than downloading them over the net.</para>
<para>Another way of doing this, if you want to just use the port
skeletons on the CDROM, is to set these variables in
<filename>/etc/make.conf</filename>:</para>
<programlisting>
PORTSDIR= /cdrom/ports
DISTDIR= /tmp/distfiles
WRKDIRPREFIX= /tmp</programlisting>
<para>Substitute <literal>/tmp</literal> for any place you have enough
free space. Then, just <command>cd</command> to the appropriate
subdirectory under <filename>/cdrom/ports</filename> and type
<command>make install</command> as
usual. <makevar>WRKDIRPREFIX</makevar> will cause the port to be
build under <filename>/tmp/cdrom/ports</filename>; for instance,
<filename>games/oneko</filename> will be built under
<filename>/tmp/cdrom/ports/games/oneko</filename>.</para>
<note>
<para>There are some ports for which we cannot provide the
original source in the CDROM due to licensing limitations. In
@ -283,7 +301,7 @@ install -c -o bin -g bin -m 444 /usr/ports/devel/ElectricFence/work/ElectricFenc
&prompt.root; <userinput>ftp ftp.freebsd.org</userinput>
[log in as `ftp' and give your email address when asked for a
password. Remember to use binary (also known as image) mode!]
<prompt>&gt;</prompt> <userinput>cd /pub/FreeBSD/ports/databases</userinput>
<prompt>&gt;</prompt> <userinput>cd /pub/FreeBSD/ports/ports/databases</userinput>
<prompt>&gt;</prompt> <userinput>get gnats.tar</userinput>
[tars up the gnats skeleton for us]
<prompt>&gt;</prompt> <userinput>quit</userinput>
@ -315,7 +333,7 @@ password. Remember to use binary (also known as image) mode!]
&prompt.root; <userinput>ftp ftp.freebsd.org</userinput>
[log in as `ftp' and give your email address when asked for a
password. Remember to use binary (also known as image) mode!]
<prompt>&gt;</prompt> <userinput>cd /pub/FreeBSD/ports</userinput>
<prompt>&gt;</prompt> <userinput>cd /pub/FreeBSD/ports/ports</userinput>
<prompt>&gt;</prompt> <userinput>get databases.tar</userinput>
[tars up the databases directory for us]
<prompt>&gt;</prompt> <userinput>quit</userinput>
@ -501,7 +519,7 @@ do-install:
<para>Grab the pre-compiled package from a ftp server. The
&ldquo;master&rdquo; package collection is on FreeBSD's FTP server in
the <ulink
URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/packages/">packages
URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/packages/">packages
directory</ulink>, though check your local mirror first,
please! These are more likely to work (on the whole) than
trying to compile from source and a lot faster besides! Use
@ -759,7 +777,7 @@ do-install:
<informalexample>
<screen>&prompt.root; <userinput>cd /usr/ports/directory</userinput>
&prompt.root; <userinput>make MASTER_SITE_OVERRIDE=ftp://ftp.FreeBSD.ORG/pub/FreeBSD/distfiles/ fetch</userinput></screen>
&prompt.root; <userinput>make MASTER_SITE_OVERRIDE=ftp://ftp.FreeBSD.ORG/pub/FreeBSD/ports/distfiles/ fetch</userinput></screen>
</informalexample>
</listitem>
@ -1348,7 +1366,7 @@ lib/X11/oneko/mouse.xpm
URL <makevar>MASTER_SITES</makevar>,
which is set in the Makefile, as well as our main ftp
site at <ulink
URL="ftp://ftp.freebsd.org/pub/FreeBSD/distfiles/">ftp://ftp.freebsd.org/pub/FreeBSD/distfiles/,</ulink> where we put sanctioned distfiles as backup. It will then attempt to fetch the named distribution file with <makevar>FETCH</makevar>, assuming that the requesting site has direct access to the Internet. If that succeeds, it will save the file in <makevar>DISTDIR</makevar> for future use and proceed.</para>
URL="ftp://ftp.freebsd.org/pub/FreeBSD/ports/distfiles/">ftp://ftp.freebsd.org/pub/FreeBSD/ports/distfiles/,</ulink> where we put sanctioned distfiles as backup. It will then attempt to fetch the named distribution file with <makevar>FETCH</makevar>, assuming that the requesting site has direct access to the Internet. If that succeeds, it will save the file in <makevar>DISTDIR</makevar> for future use and proceed.</para>
</step>
<step>
@ -1398,7 +1416,7 @@ lib/X11/oneko/mouse.xpm
<step>
<para>The <maketarget>build</maketarget> target is run. This is responsible for
descending into the ports' private working directory
descending into the port's private working directory
(<makevar>WRKSRC</makevar>) and
building it. If <makevar>USE_GMAKE</makevar> is set, GNU
<command>make</command> will be used,
@ -1435,7 +1453,7 @@ lib/X11/oneko/mouse.xpm
<note>
<para>The &ldquo;main&rdquo; targets (e.g., <maketarget>extract</maketarget>, <maketarget>configure</maketarget>, etc.) do nothing more than
make sure all the stages up to that one is completed and
make sure all the stages up to that one are completed and
call the real targets or scripts, and they are not intended
to be changed. If you want to fix the extraction, fix
<maketarget>do-extract</maketarget>, but never ever
@ -1471,7 +1489,7 @@ lib/X11/oneko/mouse.xpm
<filename>public_html/</filename> directory on
<hostid>freefall</hostid>),
we can &ldquo;house&rdquo; it ourselves by putting
it on <filename>ftp://ftp.freebsd.org/pub/FreeBSD/distfiles/LOCAL_PORTS/</filename> as the last resort. Please refer to this
it on <filename>ftp://ftp.freebsd.org/pub/FreeBSD/ports/distfiles/LOCAL_PORTS/</filename> as the last resort. Please refer to this
location as <makevar>MASTER_SITE_LOCAL</makevar>. Send mail to
the &a.ports;if you are not sure what to do.</para>
@ -1488,7 +1506,7 @@ lib/X11/oneko/mouse.xpm
<para>If your port requires some additional `patches' that are
available on the Internet, fetch them too and put them in
<makevar>DISTDIR</makevar>. Do not worry if
they come from site other than where you got the main source
they come from a site other than where you got the main source
tarball, we have a way to handle these situations (see the
description of <link
linkend="porting-patchfiles">PATCHFILES</link> below).</para>
@ -1726,7 +1744,7 @@ MASTER_SITE_SUBDIR= applications</programlisting>
<para>If the patch is not relative to the top of the source tree
(i.e., <makevar>WKRSRC</makevar>) because it
contains some extra pathnames, set <makevar>PATCH_DIST_STRIP</makevar> accordingly.
For instance, if all the pathnames in the patch has an extra
For instance, if all the pathnames in the patch have an extra
<literal>foozolix-1.0/</literal> in front of the
filenames, then set
<literal>PATCH_DIST_STRIP=-p1</literal>.</para>
@ -1978,7 +1996,7 @@ BUILD_DEPENDS= /nonexistent:${PORTSDIR}/graphics/jpeg:extract</programlisting>
other way the behaviour you want can be accomplished. It will
cause the other port to be always build (and installed, by
default), and the dependency will go into the packages as
well. If this is really what you need, I recommend you to
well. If this is really what you need, I recommend you
write it as <literal>BUILD_DEPENDS</literal> and
<literal>RUN_DEPENDS</literal> instead&mdash;at least the
intention will be clear.</para>
@ -2077,7 +2095,7 @@ lib/libtvl80.so.1
<sect2>
<title>ELF support</title>
<para>Since FreeBSD is moving to ELF from 3.0-release onwards,
<para>Since FreeBSD is moving to ELF shortly after 3.0-release,
we need to convert many ports that build shared libraries
to support ELF. Complicating this task is that a 3.0
system can run as both ELF and a.out, and that there will
@ -2778,8 +2796,8 @@ diff -u -r1.15 PLIST
<sect3>
<title><filename>INSTALL</filename></title>
<para>If your port needs execute commands when the binary package is
installed with <command>pkg_add</command> you can do with via the
<para>If your port needs to execute commands when the binary package is
installed with <command>pkg_add</command> you can do this via the
<filename>pkg/INSTALL</filename> script. This script will
automatically be added to the package, and will be run twice by
<command>pkg_add</command>. The first time will as
@ -2796,7 +2814,7 @@ diff -u -r1.15 PLIST
<note>
<para>This script is not run automatically if you install the port
with <command>make install</command>. If you are depending on
it being run, you will have to explicitly call it on your port's
it being run, you will have to explicitly call it from your port's
<filename>Makefile</filename>.</para>
</note>
</sect3>
@ -2862,15 +2880,87 @@ PLIST_SUB= OCTAVE_VERSION=${OCTAVE_VERSION}</programlisting>
<maketarget>post-install</maketarget> to a file named
<makevar>TMPPLIST</makevar>.</para>
</sect3>
<sect3>
<title id="porting-pkgsubdir">Changing the names of files in the
<filename>pkg</filename> subdirectory</title>
<para>All the filenames in the <filename>pkg</filename> subdirectory
are defined using variables so you can change them in your
<filename>Makefile</filename> if need be. This is especially useful when you
are sharing the same <filename>pkg</filename> subdirectory among
several ports or have to write to one of the above files (see
<link linkend="porting-wrkdir">writing to places other than
<makevar>WRKDIR</makevar></link> for why it is a bad idea to
write directly in to the <filename>pkg</filename>
subdirectory.</para>
<para>Here is a list of variable names and their default
values.</para>
<informaltable frame="none">
<tgroup cols="2">
<thead>
<row>
<entry>Variable</entry>
<entry>Default value</entry>
</row>
</thead>
<tbody>
<row>
<entry><makevar>COMMENT</makevar></entry>
<entry><literal>${PKGDIR}/DESCR</literal></entry>
</row>
<row>
<entry><makevar>DESCR</makevar></entry>
<entry><literal>${PKGDIR}/DESCR</literal></entry>
</row>
<row>
<entry><makevar>PLIST</makevar></entry>
<entry><literal>${PKGDIR}/PLIST</literal></entry>
</row>
<row>
<entry><makevar>PKGINSTALL</makevar></entry>
<entry><literal>${PKGDIR}/PKGINSTALL</literal></entry>
</row>
<row>
<entry><makevar>PKGDEINSTALL</makevar></entry>
<entry><literal>${PKGDIR}/PKGDEINSTALL</literal></entry>
</row>
<row>
<entry><makevar>PKGREQ</makevar></entry>
<entry><literal>${PKGDIR}/REQ</literal></entry>
</row>
<row>
<entry><makevar>PKGMESSAGE</makevar></entry>
<entry><literal>${PKGDIR}/MESSAGE</literal></entry>
</row>
</tbody>
</tgroup>
</informaltable>
<para>Please change these variables rather than overriding
<makevar>PKG_ARGS</makevar>. If you change
<makevar>PKG_ARGS</makevar>, those files will not correctly be
installed in <filename>/var/db/pkg</filename> upon install from a
port.</para>
</sect3>
</sect2>
<sect2>
<title>Licensing Problems</title>
<para>Some software packages have restrictive licenses or can be
in violation to the law (PKP's patent on public key crypto, ITAR
(export of crypto software) to name just two of them). What we
can do with them vary a lot, depending on the exact wordings of
can do with them varies a lot, depending on the exact wordings of
the respective licenses.</para>
<note>
@ -3031,6 +3121,35 @@ post-install:
with all the appropriate flags. See below for an example on how
to use them.</para>
</sect3>
<sect3 id="porting-wrkdir">
<title><makevar>WRKDIR</makevar></title>
<para>Do not write anything to files outside
<makevar>WRKDIR</makevar>. <makevar>WRKDIR</makevar> is the only
place that is guaranteed to be writable during the port build (see
<link linkend="ports-cd">compiling ports from CDROM</link> for an
example of building ports from a read-only tree). If you need to
modigy some file in <makevar>PKGDIR</makevar>, do so by <link
linkend="porting-pkgsubdir">redefining a variable</link>, not by
writing over it.</para>
</sect3>
<sect3>
<title><makevar>WRKDIRPREFIX</makevar></title>
<para>Make sure your port honors
<makevar>WRKDIRPREFIX</makevar>. Most ports don't have to worry
about this. In particular, if you are referring to a
<makevar>WRKDIR</makevar> of another port, note that the correct
location is
<filename><makevar>WRKDIRPREFIX</makevar><makevar>PORTSDIR</makevar>/<replaceable>subdir</replaceable>/<replaceable>name</replaceable>/work</filename> not <filename><makevar>PORTSDIR</makevar>/<replaceable>subdir</replaceable>/<replaceable>name</replaceable>/work</filename> or <filename><makevar>.CURDIR</makevar>/../../<replaceable>subdir</replaceable>/<replaceable>name</replaceable>/work</filename> or some such.</para>
<para>Also, if you are defining <makevar>WRKDIR</makevar> yourself,
make sure you prepend
<literal>&dollar;{WKRDIRPREFIX}&dollar;{.CURDIR}</literal> in the
front.</para>
</sect3>
<sect3 id="porting-versions">
<title>Differentiating operating systems and OS versions</title>
@ -3055,7 +3174,7 @@ post-install:
#endif</programlisting>
<para>to the proper place in the <filename>.c</filename> file. We
believe that every system that defines these to symbols has
believe that every system that defines these two symbols has
<filename>sys/param.h</filename>. If you find a system that
doesn't, we would like to know. Please send mail to the
&a.ports;.</para>
@ -3094,7 +3213,7 @@ post-install:
<para>The value of the <literal>BSD</literal> macro is
<literal>199506</literal> for the 4.4BSD-Lite2 code base. This is
stated for informational purposes only. It should not be used to
distinguish between version of FreeBSD based only on 4.4-Lite vs.
distinguish between versions of FreeBSD based only on 4.4-Lite vs.
versions that have merged in changes from 4.4-Lite2. The
<literal>__FreeBSD__</literal> macro should be used
instead.</para>
@ -3315,6 +3434,26 @@ post-install:
<entry>3.0-current after 3.0-RELEASE</entry>
<entry>300006</entry>
</row>
<row>
<entry>3.0-stable after 3/4 branch</entry>
<entry>300007</entry>
</row>
<row>
<entry>3.1-RELEASE</entry>
<entry>310000</entry>
</row>
<row>
<entry>3.1-stable after 3.1-RELEASE</entry>
<entry>310001</entry>
</row>
<row>
<entry>4.0-current after 3/4 branch</entry>
<entry>400000</entry>
</row>
</tbody>
</tgroup>
</informaltable>
@ -3649,8 +3788,8 @@ post-install:
<filename>info</filename> (documentation for info browser)
or <filename>share</filename> (architecture independent
files). See man <citerefentry><refentrytitle>hier</refentrytitle><manvolnum>7</manvolnum></citerefentry> for
details, the rule governing <filename>/usr</filename> pretty
much applies to <filename>/usr/local</filename> too. The
details, the rules governing <filename>/usr</filename> pretty
much apply to <filename>/usr/local</filename> too. The
exception are ports dealing with USENET &ldquo;news&rdquo;. They may use
<filename><makevar>PREFIX</makevar>/news</filename> as a destination for
their files.</para>
@ -4125,6 +4264,11 @@ pre-install:
</thead>
<tbody>
<row>
<entry><filename>afterstep*</filename></entry>
<entry>Ports to support AfterStep window manager</entry>
</row>
<row>
<entry><filename>archivers</filename></entry>
<entry>Archiving tools.</entry>
@ -4290,18 +4434,18 @@ pre-install:
<entry>Ports from the OffiX suite.</entry>
</row>
<row>
<entry><filename>palm</filename></entry>
<entry>Software support for the 3Com Palm(tm) series.</entry>
</row>
<row>
<entry><filename>perl5*</filename></entry>
<entry>Ports that require perl version 5 to run.</entry>
</row>
<row>
<entry><filename>pilot*</filename></entry>
<entry>Software to use with the 3Com PalmPilot.</entry>
</row>
<row>
<entry><filename>plan9</filename></entry>
<entry><filename>plan9*</filename></entry>
<entry>Various programs from Plan9.</entry>
</row>
@ -4387,6 +4531,12 @@ pre-install:
<entry>Vietnamese language support.</entry>
</row>
<row>
<entry><filename>windowmaker*</filename></entry>
<entry>Ports to support the WindowMaker window
manager</entry>
</row>
<row>
<entry><filename>www</filename></entry>
<entry>Software related to the World Wide Web. HTML language