diff --git a/en_US.ISO8859-1/articles/contributing/article.sgml b/en_US.ISO8859-1/articles/contributing/article.sgml
index 59dad4639a..830cfb1c6e 100644
--- a/en_US.ISO8859-1/articles/contributing/article.sgml
+++ b/en_US.ISO8859-1/articles/contributing/article.sgml
@@ -1,6311 +1,6315 @@
Contributing to FreeBSDContributed by &a.jkh;.So you want to contribute something to FreeBSD? That is great! We can
always use the help, and FreeBSD is one of those systems that
relies on the contributions of its user base in order
to survive. Your contributions are not only appreciated, they are vital
to FreeBSD's continued growth!Contrary to what some people might also have you believe, you do not
need to be a hot-shot programmer or a close personal friend of the FreeBSD
core team in order to have your contributions accepted. The FreeBSD
Project's development is done by a large and growing number of
international contributors whose ages and areas of technical expertise
vary greatly, and there is always more work to be done than there are
people available to do it.Since the FreeBSD project is responsible for an entire operating
system environment (and its installation) rather than just a kernel or a
few scattered utilities, our TODO list also spans a
very wide range of tasks, from documentation, beta testing and
presentation to highly specialized types of kernel development. No matter
what your skill level, there is almost certainly something you can do to
help the project!Commercial entities engaged in FreeBSD-related enterprises are also
encouraged to contact us. Need a special extension to make your product
work? You will find us receptive to your requests, given that they are not
too outlandish. Working on a value-added product? Please let us know! We
may be able to work cooperatively on some aspect of it. The free software
world is challenging a lot of existing assumptions about how software is
developed, sold, and maintained throughout its life cycle, and we urge you
to at least give it a second look.What is NeededThe following list of tasks and sub-projects represents something of
an amalgam of the various core team TODO lists and
user requests we have collected over the last couple of months. Where
possible, tasks have been ranked by degree of urgency. If you are
interested in working on one of the tasks you see here, send mail to the
coordinator listed by clicking on their names. If no coordinator has
been appointed, maybe you would like to volunteer?High priority tasksThe following tasks are considered to be urgent, usually because
they represent something that is badly broken or sorely needed:3-stage boot issues. Overall coordination: &a.hackers;Do WinNT compatible drive tagging so that the 3rd stage
can provide an accurate mapping of BIOS geometries for
disks.Filesystem problems. Overall coordination: &a.fs;Clean up and document the nullfs filesystem code.
Coordinator: &a.eivind;Fix the union file system. Coordinator: &a.dg;Implement Int13 vm86 disk driver. Coordinator:
&a.hackers;New bus architecture. Coordinator: &a.newbus;Port existing ISA drivers to new architecture.Move all interrupt-management code to appropriate parts of
the bus drivers.Port PCI subsystem to new architecture. Coordinator:
&a.dfr;Figure out the right way to handle removable devices and
then use that as a substrate on which PC-Card and CardBus
support can be implemented.Resolve the probe/attach priority issue once and for
all.Move any remaining buses over to the new
architecture.Kernel issues. Overall coordination: &a.hackers;Add more pro-active security infrastructure. Overall
coordination: &a.security;Build something like Tripwire(TM) into the kernel, with a
remote and local part. There are a number of cryptographic
issues to getting this right; contact the coordinator for
details. Coordinator: &a.eivind;Make the entire kernel use suser()
instead of comparing to 0. It is presently using about half
of each. Coordinator: &a.eivind;Split securelevels into different parts, to allow an
administrator to throw away those privileges he can throw
away. Setting the overall securelevel needs to have the same
effect as now, obviously. Coordinator: &a.eivind;Make it possible to upload a list of allowed
programs to BPF, and then block BPF from accepting other
programs. This would allow BPF to be used e.g. for DHCP,
without allowing an attacker to start snooping the local
network.Update the security checker script. We should at least
grab all the checks from the other BSD derivatives, and add
checks that a system with securelevel increased also have
reasonable flags on the relevant parts. Coordinator:
&a.eivind;Add authorization infrastructure to the kernel, to allow
different authorization policies. Part of this could be done
by modifying suser(). Coordinator:
&a.eivind;Add code to the NFS layer so that you cannot
chdir("..") out of an NFS partition. E.g.,
/usr is a UFS partition with
/usr/src NFS exported. Now it is
possible to use the NFS filehandle for
/usr/src to get access to
/usr.Medium priority tasksThe following tasks need to be done, but not with any particular
urgency:Full KLD based driver support/Configuration Manager.Write a configuration manager (in the 3rd stage boot?)
that probes your hardware in a sane manner, keeps only the
KLDs required for your hardware, etc.PCMCIA/PCCARD. Coordinators: &a.msmith; and &a.imp;Documentation!Reliable operation of the pcic driver (needs
testing).Recognizer and handler for sio.c
(mostly done).Recognizer and handler for ed.c
(mostly done).Recognizer and handler for ep.c
(mostly done).User-mode recognizer and handler (partially done).Advanced Power Management. Coordinators: &a.msmith; and
&a.phk;APM sub-driver (mostly done).IDE/ATA disk sub-driver (partially done).syscons/pcvt sub-driver.Integration with the PCMCIA/PCCARD drivers
(suspend/resume).Low priority tasksThe following tasks are purely cosmetic or represent such an
investment of work that it is not likely that anyone will get them
done anytime soon:The first N items are from Terry Lambert
terry@lambert.orgNetWare Server (protected mode ODI driver) loader and
sub-services to allow the use of ODI card drivers supplied with
network cards. The same thing for NDIS drivers and NetWare SCSI
drivers.An "upgrade system" option that works on Linux boxes instead
of just previous rev FreeBSD boxes.Symmetric Multiprocessing with kernel preemption (requires
kernel preemption).A concerted effort at support for portable computers. This is
somewhat handled by changing PCMCIA bridging rules and power
management event handling. But there are things like detecting
internal v.s.. external display and picking a different screen
resolution based on that fact, not spinning down the disk if the
machine is in dock, and allowing dock-based cards to disappear
without affecting the machines ability to boot (same issue for
PCMCIA).Smaller tasksMost of the tasks listed in the previous sections require either a
considerable investment of time or an in-depth knowledge of the
FreeBSD kernel (or both). However, there are also many useful tasks
which are suitable for "weekend hackers", or people without
programming skills.If you run FreeBSD-current and have a good Internet
connection, there is a machine current.FreeBSD.org which builds a full
release once a day — every now and again, try and install
the latest release from it and report any failures in the
process.Read the freebsd-bugs mailing list. There might be a
problem you can comment constructively on or with patches you
can test. Or you could even try to fix one of the problems
yourself.Read through the FAQ and Handbook periodically. If anything
is badly explained, out of date or even just completely wrong, let
us know. Even better, send us a fix (SGML is not difficult to
learn, but there is no objection to ASCII submissions).Help translate FreeBSD documentation into your native language
(if not already available) — just send an email to &a.doc;
asking if anyone is working on it. Note that you are not
committing yourself to translating every single FreeBSD document
by doing this — in fact, the documentation most in need of
translation is the installation instructions.Read the freebsd-questions mailing list and &ng.misc
occasionally (or even regularly). It can be very satisfying to
share your expertise and help people solve their problems;
sometimes you may even learn something new yourself! These forums
can also be a source of ideas for things to work on.If you know of any bug fixes which have been successfully
applied to -current but have not been merged into -stable after a
decent interval (normally a couple of weeks), send the committer a
polite reminder.Move contributed software to src/contrib
in the source tree.Make sure code in src/contrib is up to
date.Build the source tree (or just part of it) with extra warnings
enabled and clean up the warnings.Fix warnings for ports which do deprecated things like using
gets() or including malloc.h.If you have contributed any ports, send your patches back to
the original author (this will make your life easier when they
bring out the next version)Suggest further tasks for this list!Work through the PR databaseThe FreeBSD PR
list shows all the current active problem reports and
requests for enhancement that have been submitted by FreeBSD users.
Look through the open PRs, and see if anything there takes your
interest. Some of these might be very simple tasks, that just need an
extra pair of eyes to look over them and confirm that the fix in the
PR is a good one. Others might be much more complex.Start with the PRs that have not been assigned to anyone else, but
if one them is assigned to someone else, but it looks like something
you can handle, e-mail the person it is assigned to and ask if you can
work on it—they might already have a patch ready to be tested,
or further ideas that you can discuss with them.How to ContributeContributions to the system generally fall into one or more of the
following 6 categories:Bug reports and general commentaryAn idea or suggestion of general technical
interest should be mailed to the &a.hackers;. Likewise, people with
an interest in such things (and a tolerance for a
high volume of mail!) may subscribe to the
hackers mailing list by sending mail to &a.majordomo;. See mailing lists for more information
about this and other mailing lists.If you find a bug or are submitting a specific change, please
report it using the &man.send-pr.1; program or its WEB-based
equivalent. Try to fill-in each field of the bug report.
Unless they exceed 65KB, include any patches directly in the report.
When including patches, do not use cut-and-paste
because cut-and-paste turns tabs into spaces and makes them unusable.
Consider compressing patches and using &man.uuencode.1; if they exceed
20KB. Upload very large submissions to ftp.FreeBSD.org:/pub/FreeBSD/incoming/.After filing a report, you should receive confirmation along with
a tracking number. Keep this tracking number so that you can update
us with details about the problem by sending mail to
bug-followup@FreeBSD.org. Use the number as the
message subject, e.g. "Re: kern/3377". Additional
information for any bug report should be submitted this way.If you do not receive confirmation in a timely fashion (3 days to
a week, depending on your email connection) or are, for some reason,
unable to use the &man.send-pr.1; command, then you may ask
someone to file it for you by sending mail to the &a.bugs;.Changes to the documentationChanges to the documentation are overseen by the &a.doc;. Send
submissions and changes (even small ones are welcome!) using
send-pr as described in Bug Reports and General
Commentary.Changes to existing source codeAn addition or change to the existing source code is a somewhat
trickier affair and depends a lot on how far out of date you are with
the current state of the core FreeBSD development. There is a special
on-going release of FreeBSD known as FreeBSD-current
which is made available in a variety of ways for the convenience of
developers working actively on the system. See Staying current with FreeBSD for more
information about getting and using FreeBSD-current.Working from older sources unfortunately means that your changes
may sometimes be too obsolete or too divergent for easy re-integration
into FreeBSD. Chances of this can be minimized somewhat by
subscribing to the &a.announce; and the &a.current; lists, where
discussions on the current state of the system take place.Assuming that you can manage to secure fairly up-to-date sources
to base your changes on, the next step is to produce a set of diffs to
send to the FreeBSD maintainers. This is done with the &man.diff.1;
command, with the context diff form
being preferred. For example:&prompt.user; diff -c oldfile newfile
or
&prompt.user; diff -c -r olddir newdir
would generate such a set of context diffs for the given source file
or directory hierarchy. See the man page for &man.diff.1; for more
details.Once you have a set of diffs (which you may test with the
&man.patch.1; command), you should submit them for inclusion with
FreeBSD. Use the &man.send-pr.1; program as described in Bug Reports and General Commentary.
Do not just send the diffs to the &a.hackers; or
they will get lost! We greatly appreciate your submission (this is a
volunteer project!); because we are busy, we may not be able to
address it immediately, but it will remain in the pr database until we
do.If you feel it appropriate (e.g. you have added, deleted, or
renamed files), bundle your changes into a tar file
and run the &man.uuencode.1; program on it. Shar archives are also
welcome.If your change is of a potentially sensitive nature, e.g. you are
unsure of copyright issues governing its further distribution or you
are simply not ready to release it without a tighter review first,
then you should send it to &a.core; directly rather than submitting it
with &man.send-pr.1;. The core mailing list reaches a much smaller
group of people who do much of the day-to-day work on FreeBSD. Note
that this group is also very busy and so you
should only send mail to them where it is truly necessary.Please refer to man 9 intro and man 9
style for some information on coding style. We would
appreciate it if you were at least aware of this information before
submitting code.New code or major value-added packagesIn the case of a significant contribution of a large body
work, or the addition of an important new feature to FreeBSD, it
becomes almost always necessary to either send changes as uuencoded
tar files or upload them to a web or FTP site for other people to
access. If you do not have access to a web or FTP site, ask on an
appropriate FreeBSD mailing list for someone to host the changes for
you.When working with large amounts of code, the touchy subject of
copyrights also invariably comes up. Acceptable copyrights for code
included in FreeBSD are:The BSD copyright. This copyright is most preferred due to
its no strings attached nature and general
attractiveness to commercial enterprises. Far from discouraging
such commercial use, the FreeBSD Project actively encourages such
participation by commercial interests who might eventually be
inclined to invest something of their own into FreeBSD.The GNU Public License, or GPL. This license is
not quite as popular with us due to the amount of extra effort
demanded of anyone using the code for commercial purposes, but
given the sheer quantity of GPL'd code we currently require
(compiler, assembler, text formatter, etc) it would be silly to
refuse additional contributions under this license. Code under
the GPL also goes into a different part of the tree, that being
/sys/gnu or
/usr/src/gnu, and is therefore easily
identifiable to anyone for whom the GPL presents a problem.Contributions coming under any other type of copyright must be
carefully reviewed before their inclusion into FreeBSD will be
considered. Contributions for which particularly restrictive
commercial copyrights apply are generally rejected, though the authors
are always encouraged to make such changes available through their own
channels.To place a BSD-style copyright on your work, include
the following text at the very beginning of every source code file you
wish to protect, replacing the text between the %%
with the appropriate information.Copyright (c) %%proper_years_here%%
%%your_name_here%%, %%your_state%% %%your_zip%%.
All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
1. Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer as
the first lines of this file unmodified.
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
THIS SOFTWARE IS PROVIDED BY %%your_name_here%% ``AS IS'' AND ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
IN NO EVENT SHALL %%your_name_here%% BE LIABLE FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
$Id$For your convenience, a copy of this text can be found in
/usr/share/examples/etc/bsd-style-copyright.Money, Hardware or Internet accessWe are always very happy to accept donations to further the cause
of the FreeBSD Project and, in a volunteer effort like ours, a little
can go a long way! Donations of hardware are also very important to
expanding our list of supported peripherals since we generally lack
the funds to buy such items ourselves.Donating fundsEmpty, pending information from the FreeBSD Foundation.Donating hardwareDonations of hardware in any of the 3 following categories are
also gladly accepted by the FreeBSD Project:General purpose hardware such as disk drives, memory or
complete systems should be sent to the FreeBSD, Inc. address
listed in the donating funds
section.Hardware for which ongoing compliance testing is desired.
We are currently trying to put together a testing lab of all
components that FreeBSD supports so that proper regression
testing can be done with each new release. We are still lacking
many important pieces (network cards, motherboards, etc) and if
you would like to make such a donation, please contact &a.dg;
for information on which items are still required.Hardware currently unsupported by FreeBSD for which you
would like to see such support added. Please contact the
&a.core; before sending such items as we will need to find a
developer willing to take on the task before we can accept
delivery of new hardware.Donating Internet accessWe can always use new mirror sites for FTP, WWW or
cvsup. If you would like to be such a mirror,
please contact the FreeBSD project administrators
hubs@FreeBSD.org for more information.Donors GalleryThe FreeBSD Project is indebted to the following donors and would
like to publicly thank them here!Contributors to the central server
project:The following individuals and businesses made it possible for
the FreeBSD Project to build a new central server machine to
eventually replace freefall.FreeBSD.org
by donating the following items:&a.mbarkah and his employer,
Hemisphere Online, donated a Pentium Pro
(P6) 200Mhz CPUASA
Computers donated a Tyan 1662
motherboard.Joe McGuckin joe@via.net of ViaNet Communications donated
a Kingston ethernet controller.Jack O'Neill jack@diamond.xtalwind.net
donated an NCR 53C875 SCSI controller
card.Ulf Zimmermann ulf@Alameda.net of Alameda Networks donated
128MB of memory, a 4 Gb disk
drive and the case.Direct funding:The following individuals and businesses have generously
contributed direct funding to the project:Annelise Anderson
ANDRSN@HOOVER.STANFORD.EDU&a.dillonBlue Mountain
ArtsEpilogue Technology
Corporation&a.sefGlobal Technology
Associates, IncDon Scott WildeGianmarco Giovannelli
gmarco@masternet.itJosef C. Grosch joeg@truenorth.orgRobert T. Morris&a.chuckrKenneth P. Stox ken@stox.sa.enteract.com of
Imaginary Landscape,
LLC.Dmitry S. Kohmanyuk dk@dog.farm.orgLaser5 of Japan
(a portion of the profits from sales of their various FreeBSD
CDROMs).Fuki Shuppan
Publishing Co. donated a portion of their profits from
Hajimete no FreeBSD (FreeBSD, Getting
started) to the FreeBSD and XFree86 projects.ASCII Corp.
donated a portion of their profits from several FreeBSD-related
books to the FreeBSD project.Yokogawa Electric
Corp has generously donated significant funding to the
FreeBSD project.BuffNETPacific
SolutionsSiemens AG
via Andre Albsmeier
andre.albsmeier@mchp.siemens.deChris Silva ras@interaccess.comHardware contributors:The following individuals and businesses have generously
contributed hardware for testing and device driver
development/support:BSDi for providing the Pentium P5-90 and
486/DX2-66 EISA/VL systems that are being used for our
development work, to say nothing of the network access and other
donations of hardware resources.TRW Financial Systems, Inc. provided 130 PCs, three 68 GB
file servers, twelve Ethernets, two routers and an ATM switch for
debugging the diskless code.Dermot McDonnell donated the Toshiba XM3401B CDROM drive
currently used in freefall.&a.chuck; contributed his floppy tape streamer for
experimental work.Larry Altneu larry@ALR.COM, and &a.wilko;,
provided Wangtek and Archive QIC-02 tape drives in order to
improve the wt driver.Ernst Winter ewinter@lobo.muc.de contributed
a 2.88 MB floppy drive to the project. This will hopefully
increase the pressure for rewriting the floppy disk driver.
;-)Tekram
Technologies sent one each of their DC-390, DC-390U
and DC-390F FAST and ULTRA SCSI host adapter cards for
regression testing of the NCR and AMD drivers with their cards.
They are also to be applauded for making driver sources for free
operating systems available from their FTP server ftp://ftp.tekram.com/scsi/FreeBSD/.Larry M. Augustin contributed not only a
Symbios Sym8751S SCSI card, but also a set of data books,
including one about the forthcoming Sym53c895 chip with Ultra-2
and LVD support, and the latest programming manual with
information on how to safely use the advanced features of the
latest Symbios SCSI chips. Thanks a lot!Christoph Kukulies kuku@FreeBSD.org donated
an FX120 12 speed Mitsumi CDROM drive for IDE CDROM driver
development.Special contributors:BSDi (formerly Walnut Creek CDROM)
has donated almost more than we can say (see the history document for more details).
In particular, we would like to thank them for the original
hardware used for freefall.FreeBSD.org, our primary
development machine, and for thud.FreeBSD.org, a testing and build
box. We are also indebted to them for funding various
contributors over the years and providing us with unrestricted
use of their T1 connection to the Internet.The interface
business GmbH, Dresden has been patiently supporting
&a.joerg; who has often preferred FreeBSD work over paid work, and
used to fall back to their (quite expensive) EUnet Internet
connection whenever his private connection became too slow or
flaky to work with it...Berkeley Software Design,
Inc. has contributed their DOS emulator code to the
remaining BSD world, which is used in the
doscmd command.Core Team AlumniThe following people were members of the FreeBSD core team during
the periods indicated. We thank them for their past efforts in the
service of the FreeBSD project.In rough chronological order:&a.ache (1993 - 2000)&a.jmb (1993 - 2000)&a.bde (1992 - 2000)&a.gibbs (1993 - 2000)&a.rich (1994 - 2000)&a.phk (1992 - 2000)&a.gpalmer (1993 - 2000)&a.sos (1993 - 2000)&a.wollman (1993 - 2000)&a.joerg (1995 - 2000)&a.jdp (1997 - 2000)&a.guido (1995 - 1999)&a.dyson (1993 - 1998)&a.nate (1992 - 1996)&a.rgrimes (1992 - 1995)Andreas Schulz (1992 - 1995)&a.csgr (1993 - 1995)&a.paul (1992 - 1995)&a.smace (1993 - 1994)Andrew Moore (1993 - 1994)Christoph Robitschko (1993 - 1994)J. T. Conklin (1992 - 1993)Development Team AlumniThe following people were members of the FreeBSD development team
during the periods indicated. We thank them for their past efforts
in the service of the FreeBSD project.In rough chronological order:&a.tedm (???? - 2000)&a.karl (???? - 2000)&a.gclarkii (1993 - 2000)&a.jraynard (???? - 2000)&a.jgreco (???? - 1999)&a.ats (???? - 1999)Jamil Weatherby (1997 - 1999)meganm (???? - 1998)&a.dyson (???? - 1998)Amancio Hasty (1997 - 1998)Drew Derbyshire (1997 - 1998)Derived Software ContributorsThis software was originally derived from William F. Jolitz's 386BSD
release 0.1, though almost none of the original 386BSD specific code
remains. This software has been essentially re-implemented from the
4.4BSD-Lite release provided by the Computer Science Research Group
(CSRG) at the University of California, Berkeley and associated academic
contributors.There are also portions of NetBSD and OpenBSD that have been
integrated into FreeBSD as well, and we would therefore like to thank
all the contributors to NetBSD and OpenBSD for their work.Additional FreeBSD Contributors(in alphabetical order by first name):ABURAYA Ryushirou rewsirow@ff.iij4u.or.jpAMAGAI Yoshiji amagai@nue.orgAaron Bornstein aaronb@j51.comAaron Smith aaron@mutex.orgAchim Patzner ap@noses.comAda T Lim ada@bsd.orgAdam Baran badam@mw.mil.plAdam Glass glass@postgres.berkeley.eduAdam Herzog adam@herzogdesigns.comAdam McDougall mcdouga9@egr.msu.eduAdam Strohl troll@digitalspark.netAdoal Xu adoal@iname.comAdrian Colley aecolley@ois.ieAdrian Hall ahall@mirapoint.comAdrian Mariano adrian@cam.cornell.eduAdrian Steinmann ast@marabu.chAdrian T. Filipi-Martin
atf3r@agate.cs.virginia.eduAjit Thyagarajan unknownAkio Morita
amorita@meadow.scphys.kyoto-u.ac.jpAkira SAWADA unknownAkira Watanabe
akira@myaw.ei.meisei-u.ac.jpAkito Fujita fujita@zoo.ncl.omron.co.jpAlain Kalker
A.C.P.M.Kalker@student.utwente.nlAlan Bawden alan@curry.epilogue.comAlec Wolman wolman@cs.washington.eduAled Morris aledm@routers.co.ukAleksandr A Babaylov .@babolo.ruAlex G. Bulushev bag@demos.suAlex D. Chen
dhchen@Canvas.dorm7.nccu.edu.twAlex Le Heux alexlh@funk.orgAlex Kapranoff kappa@zombie.antar.bryansk.ruAlex Perel veers@disturbed.netAlex Semenyaka alex@rinet.ruAlex Varju varju@webct.comAlex Zepeda garbanzo@hooked.netAlexander B. Povolotsky tarkhil@mgt.msk.ruAlexander Gelfenbain mail@gelf.comAlexander Leidinger
netchild@wurzelausix.CS.Uni-SB.DEAlexandre Peixoto
alexandref@tcoip.com.brAlexandre Snarskii snar@paranoia.ruAlistair G. Crooks agc@uts.amdahl.comAllan Bowhill bowhill@bowhill.vservers.comAllan Saddi asaddi@philosophysw.comAllen Campbell allenc@verinet.comAmakawa Shuhei amakawa@hoh.t.u-tokyo.ac.jpAmancio Hasty hasty@star-gate.comAmir Farah amir@comtrol.comAmir Shalem amir@boom.org.ilAmy Baron amee@beer.orgThe Anarcat beaupran@iro.umontreal.caAnatoly A. Orehovsky tolik@mpeks.tomsk.suAnatoly Vorobey mellon@pobox.comAnders Andersson anders@codefactory.seAnders Nordby anders@fix.noAnders Thulin Anders.X.Thulin@telia.seAndras Olah olah@cs.utwente.nlAndre Albsmeier
Andre.Albsmeier@mchp.siemens.deAndre Goeree abgoeree@uwnet.nlAndre Oppermann andre@pipeline.chAndreas Haakh ah@alman.robin.deAndreas Kohout shanee@rabbit.augusta.deAndreas Lohr andreas@marvin.RoBIN.deAndreas Schulz unknownAndreas Wetzel mickey@deadline.snafu.deAndreas Wrede andreas@planix.comAndres Vega Garcia unknownAndrew Atrens atreand@statcan.caAndrew Boothman andrew@cream.orgAndrew Gillham gillham@andrews.eduAndrew Gordon andrew.gordon@net-tel.co.ukAndrew Herbert andrew@werple.apana.org.auAndrew J. Korty ajk@purdue.eduAndrew L. Moore alm@mclink.comAndrew L. Neporada andrew@chg.ruAndrew McRae amcrae@cisco.comAndrew Stevenson andrew@ugh.net.auAndrew Timonin tim@pool1.convey.ruAndrew V. Stesin stesin@elvisti.kiev.uaAndrew Webster awebster@dataradio.comAndrey Novikov andrey@novikov.comAndrey Simonenko simon@comsys.ntu-kpi.kiev.uaAndrey Tchoritch andy@venus.sympad.netAndy Farkas andyf@speednet.com.auAndy Valencia ajv@csd.mot.comAndy Whitcroft andy@sarc.city.ac.ukAngelo Turetta ATuretta@stylo.itAnthony C. Chavez magus@xmission.comAnthony Yee-Hang Chan yeehang@netcom.comAnton N. Bruesov antonz@library.ntu-kpi.kiev.uaAnton Voronin anton@urc.ac.ruAntti Kaipila anttik@iki.fiarci vega@sophia.inria.frAre Bryne are.bryne@communique.noAri Suutari ari@suutari.iki.fiArindum Mukerji rmukerji@execpc.comArjan de Vet devet@IAEhv.nlArne Henrik Juul arnej@Lise.Unit.NOArun Sharma adsharma@sharmas.dhs.orgArnaud S. Launay asl@launay.orgAsk Bjoern Hansen ask@valueclick.comAtsushi Furuta furuta@sra.co.jpAtsushi Murai amurai@spec.co.jpAtushi Sakauchi sakauchi@yamame.toBakul Shah bvs@bitblocks.comBarry Bierbauch pivrnec@vszbr.czBarry Lustig barry@ictv.comBen Hutchinson benhutch@xfiles.org.ukBen Jackson unknownBen Walter bwalter@itachi.swcp.comBenjamin Lewis bhlewis@gte.netBerend de Boer berend@pobox.comBernd Rosauer br@schiele-ct.deBill Kish kish@osf.orgBill Trost trost@cloud.rain.comBlaz Zupan blaz@amis.netBob Van Valzah Bob@whitebarn.comBob Wilcox bob@obiwan.uucpBob Willcox bob@luke.pmr.comBoris Staeblow balu@dva.in-berlin.deBoyd Faulkner faulkner@mpd.tandem.comBoyd R. Faulkner faulkner@asgard.bga.comBrad Chapman chapmanb@arches.uga.eduBrad Hendrickse bradh@uunet.co.zaBrad Karp karp@eecs.harvard.eduBradley Dunn bradley@dunn.orgBrad Jones brad@kazrak.comBrandon Fosdick bfoz@glue.umd.eduBrandon Gillespie brandon@roguetrader.com&a.wlloydBrent J. Nordquist bjn@visi.comBrett Lymn blymn@mulga.awadi.com.AUBrett Taylor
brett@peloton.runet.eduBrian Campbell brianc@pobox.comBrian Clapper bmc@willscreek.comBrian Cully shmit@kublai.comBrian Handy
handy@lambic.space.lockheed.comBrian Litzinger brian@MediaCity.comBrian McGovern bmcgover@cisco.comBrian Moore ziff@houdini.eecs.umich.eduBrian R. Haug haug@conterra.comBrian Tao taob@risc.orgBrion Moss brion@queeg.comBruce Albrecht bruce@zuhause.mn.orgBruce Gingery bgingery@gtcs.comBruce J. Keeler loodvrij@gridpoint.comBruce Murphy packrat@iinet.net.auBruce Walter walter@fortean.comCarey Jones mcj@acquiesce.orgCarl Fongheiser cmf@netins.netCarl Mascott cmascott@world.std.comCasper casper@acc.amCastor Fu castor@geocast.comChad David davidc@acns.ab.caChain Lee chain@110.netCharles Hannum mycroft@ai.mit.eduCharles Henrich henrich@msu.eduCharles Mott cmott@scientech.comCharles Owens owensc@enc.eduChet Ramey chet@odin.INS.CWRU.EduChia-liang Kao clkao@CirX.ORGChiharu Shibata chi@bd.mbn.or.jpChip Norkus unknownChris Csanady cc@tarsier.ca.sandia.govChris Dabrowski chris@vader.orgChris Dillon cdillon@wolves.k12.mo.usChris Shenton
cshenton@angst.it.hq.nasa.gov
+
+ &a.cshumway;
+
+
Chris Stenton jacs@gnome.co.ukChris Timmons skynyrd@opus.cts.cwu.eduChris Torek torek@ee.lbl.govChristian Gusenbauer
cg@fimp01.fim.uni-linz.ac.atChristian Haury Christian.Haury@sagem.frChristian Weisgerber
naddy@mips.inka.deChristoph P. Kukulies kuku@FreeBSD.orgChristoph Robitschko
chmr@edvz.tu-graz.ac.atChristoph Weber-Fahr
wefa@callcenter.systemhaus.netChristopher G. Demetriou
cgd@postgres.berkeley.eduChristopher N. Harrell cnh@ivmg.netChristopher Preston rbg@gayteenresource.orgChristopher T. Johnson
cjohnson@neunacht.netgsi.comChrisy Luke chrisy@flix.netChuck Hein chein@cisco.comCliff Rowley dozprompt@onsea.comColman Reilly careilly@tcd.ieConrad Sabatier conrads@home.comCoranth Gryphon gryphon@healer.comCornelis van der Laan
nils@guru.ims.uni-stuttgart.deCove Schneider cove@brazil.nbn.comCraig Leres leres@ee.lbl.govCraig Loomis unknownCraig Metz cmetz@inner.netCraig Spannring cts@internetcds.comCraig Struble cstruble@vt.eduCristian Ferretti cfs@riemann.mat.puc.clCurt Mayer curt@toad.comCy Schubert cschuber@uumail.gov.bc.caCyrille Lefevre clefevre@citeweb.netCyrus Rahman cr@jcmax.comDai Ishijima ishijima@tri.pref.osaka.jpDaisuke Watanabe NU7D-WTNB@asahi-net.or.jpDamian Hamill damian@cablenet.netDan Cross tenser@spitfire.ecsel.psu.eduDan Langille dan@freebsddiary.orgDan Lukes dan@obluda.czDan Nelson dnelson@emsphone.comDan Papasian bugg@bugg.strangled.netDan Piponi wmtop@tanelorn.demon.co.ukDan Walters hannibal@cyberstation.netDaniel Hagan
dhagan@cs.vt.eduDaniel O'Connor doconnor@gsoft.com.auDaniel Poirot poirot@aio.jsc.nasa.govDaniel Rock rock@cs.uni-sb.deDaniel W. McRobb dwm@caimis.comDanny Egen unknownDanny J. Zerkel dzerkel@phofarm.comDave Adkins adkin003@tc.umn.eduDave Andersen angio@aros.netDave Blizzard dblizzar@sprynet.comDave Bodenstab imdave@synet.netDave Burgess burgess@hrd769.brooks.af.milDave Chapeskie dchapes@ddm.on.caDave Cornejo dave@dogwood.comDave Edmondson davided@sco.comDave Glowacki dglo@ssec.wisc.eduDave Marquardt marquard@austin.ibm.comDave Tweten tweten@FreeBSD.orgDavid A. Adkins adkin003@tc.umn.eduDavid A. Bader dbader@eece.unm.eduDavid Borman dab@bsdi.comDavid Dawes dawes@XFree86.orgDavid Filo unknownDavid Holland dholland@eecs.harvard.eduDavid Holloway daveh@gwythaint.tamis.comDavid Horwitt dhorwitt@ucsd.eduDavid Hovemeyer daveho@infocom.comDavid Jones dej@qpoint.torfree.netDavid Kelly dkelly@tomcat1.tbe.comDavid Kulp dkulp@neomorphic.comDavid L. Nugent davidn@blaze.net.auDavid Leonard d@scry.dstc.edu.auDavid Muir Sharnoff muir@idiom.comDavid S. Miller davem@jenolan.rutgers.eduDavid Sugar dyfet@gnu.orgDavid Wolfskill dhw@whistle.comDean Gaudet dgaudet@arctic.orgDean Huxley dean@fsa.caDenis Fortin unknownDenis Shaposhnikov dsh@vlink.ruDennis Glatting
dennis.glatting@software-munitions.comDenton Gentry denny1@home.comder Mouse mouse@Collatz.McRCIM.McGill.EDUDerek Inksetter derek@saidev.comDI. Christian Gusenbauer
cg@scotty.edvz.uni-linz.ac.atDirk Keunecke dk@panda.rhein-main.deDirk Nehrling nerle@pdv.deDishanker Rajakulendren draj@oceanfree.netDmitry Khrustalev dima@xyzzy.machaon.ruDmitry Kohmanyuk dk@farm.orgDom Mitchell dom@myrddin.demon.co.ukDomas Mituzas midom@dammit.ltDominik Brettnacher domi@saargate.deDominik Rothert dr@domix.deDon Croyle croyle@gelemna.ft-wayne.in.usDonn Miller dmmiller@cvzoom.netDan Pelleg dpelleg+unison@cs.cmu.edu&a.whiteside;Don Morrison dmorrisn@u.washington.eduDon Yuniskis dgy@rtd.comDonald Maddox dmaddox@conterra.comDouglas Ambrisko ambrisko@whistle.comDouglas Carmichael dcarmich@mcs.comDouglas Crosher dtc@scrooge.ee.swin.oz.auDrew Derbyshire ahd@kew.comDustin Sallings dustin@spy.netEckart "Isegrim" Hofmann
Isegrim@Wunder-Nett.orgEd Gold
vegold01@starbase.spd.louisville.eduEd Hudson elh@p5.spnet.comEdward Chuang edwardc@firebird.org.twEdward Wang edward@edcom.comEdwin Groothus edwin@nwm.wan.philips.comEdwin Mons e@ik.nuEge Rekk aagero@aage.priv.noEiji-usagi-MATSUmoto usagi@clave.gr.jpEike Bernhardt eike.bernhardt@gmx.deELISA Font ProjectElmar Bartel
bartel@informatik.tu-muenchen.deEoin Lawless eoin@maths.tcd.ieEric A. Griff eagriff@global2000.netEric Blood eblood@cs.unr.eduEric D. Futch efutch@nyct.netEric J. Haug ejh@slustl.slu.eduEric J. Schwertfeger eric@cybernut.comEric L. Hernes erich@lodgenet.comEric P. Scott eps@sirius.comEric Sprinkle eric@ennovatenetworks.comErich Stefan Boleyn erich@uruk.orgErich Zigler erich@tacni.netErik H. Bakke erikhb@bgnett.noErik E. Rantapaa rantapaa@math.umn.eduErik H. Moe ehm@cris.comErnst de Haan ernst@heinz.jollem.comErnst Winter ewinter@lobo.muc.deEspen Skoglund esk@ira.uka.deEugene M. Kim astralblue@usa.netEugene Radchenko genie@qsar.chem.msu.suEugeny Kuzakov CoreDumped@coredumped.null.ruEvan Champion evanc@synapse.netFaried Nawaz fn@Hungry.COMFlemming Jacobsen fj@tfs.comFong-Ching Liaw fong@juniper.netFrancis M J Hsieh mjshieh@life.nthu.edu.twFrancisco Reyes fjrm@yahoo.comFrank Bartels knarf@camelot.deFrank Chen Hsiung Chan
frankch@waru.life.nthu.edu.twFrank Durda IV uhclem@nemesis.lonestar.orgFrank MacLachlan fpm@n2.netFrank Nobis fn@Radio-do.deFrank ten Wolde franky@pinewood.nlFrank van der Linden frank@fwi.uva.nlFrank Volf volf@oasis.IAEhv.nlFred Cawthorne fcawth@jjarray.umn.eduFred Gilham gilham@csl.sri.comFred Templin templin@erg.sri.comFrederick Earl Gray fgray@rice.eduFUJIMOTO Kensaku
fujimoto@oscar.elec.waseda.ac.jpFURUSAWA Kazuhisa
furusawa@com.cs.osakafu-u.ac.jp&a.stanislav;Gabor Kincses gabor@acm.orgGabor Zahemszky zgabor@CoDe.huGareth McCaughan gjm11@dpmms.cam.ac.ukGary A. Browning gab10@griffcd.amdahl.comGary Howland gary@hotlava.comGary J. garyj@rks32.pcs.dec.comGary Kline kline@thought.orgGaspar Chilingarov nightmar@lemming.acc.amGea-Suan Lin gsl@tpts4.seed.net.twGene Raytsin pal@paladin7.netGeoff Rehmet csgr@alpha.ru.ac.zaGeorg Wagner georg.wagner@ubs.comGianlorenzo Masini masini@uniroma3.itGianmarco Giovannelli
gmarco@giovannelli.itGil Kloepfer Jr. gil@limbic.ssdl.comGilad Rom rom_glsa@ein-hashofet.co.ilGiles Lean giles@nemeton.com.auGinga Kawaguti
ginga@amalthea.phys.s.u-tokyo.ac.jpGiorgos Keramidas keramida@ceid.upatras.grGlen Foster gfoster@gfoster.comGlenn Johnson gljohns@bellsouth.netGodmar Back gback@facility.cs.utah.eduGoran Hammarback goran@astro.uu.seGord Matzigkeit gord@enci.ucalgary.caGordon Greeff gvg@uunet.co.zaGraham Wheeler gram@cdsec.comGreg A. Woods woods@zeus.leitch.comGreg Ansley gja@ansley.comGreg Robinson greg@rosevale.com.auGreg Troxel gdt@ir.bbn.comGreg Ungerer gerg@stallion.oz.auGregory Bond gnb@itga.com.auGregory D. Moncreaff
moncrg@bt340707.res.ray.comGuy Harris guy@netapp.comGuy Helmer ghelmer@cs.iastate.eduHAMADA Naoki hamada@astec.co.jpHannu Savolainen hannu@voxware.pp.fiHans Huebner hans@artcom.deHans Petter Bieker zerium@webindex.noHans Zuidam hans@brandinnovators.comHarlan Stenn Harlan.Stenn@pfcs.comHarold Barker hbarker@dsms.comHarry Newton harry_newton@telinco.co.ukHavard Eidnes
Havard.Eidnes@runit.sintef.noHeikki Suonsivu hsu@cs.hut.fiHeiko W. Rupp unknownHelmut F. Wirth hfwirth@ping.atHenrik Vestergaard Draboel
hvd@terry.ping.dkHerb Peyerl hpeyerl@NetBSD.orgHideaki Ohmon ohmon@tom.sfc.keio.ac.jpHidekazu Kuroki hidekazu@cs.titech.ac.jpHideki Yamamoto hyama@acm.orgHideyuki Suzuki
hideyuki@sat.t.u-tokyo.ac.jpHirayama Issei iss@mail.wbs.ne.jpHiroaki Sakai sakai@miya.ee.kagu.sut.ac.jpHiroharu Tamaru tamaru@ap.t.u-tokyo.ac.jpHironori Ikura hikura@kaisei.orgHiroshi Nishikawa nis@pluto.dti.ne.jpHiroya Tsubakimoto unknownHolger Lamm holger@eit.uni-kl.deHolger Veit Holger.Veit@gmd.deHolm Tiffe holm@geophysik.tu-freiberg.deHONDA Yasuhiro
honda@kashio.info.mie-u.ac.jpHorance Chou
horance@freedom.ie.cycu.edu.twHorihiro Kumagai kuma@jp.FreeBSD.orgHOSOBUCHI Noriyuki hoso@buchi.tama.or.jpHOTARU-YA hotaru@tail.netHr.Ladavac lada@ws2301.gud.siemens.co.atHubert Feyrer hubertf@NetBSD.ORGHugh F. Mahon hugh@nsmdserv.cnd.hp.comHugh Mahon h_mahon@fc.hp.comHung-Chi Chu hcchu@r350.ee.ntu.edu.twIan Holland ianh@tortuga.com.auIan Struble ian@broken.netIan Vaudrey i.vaudrey@bigfoot.comIgor Khasilev igor@jabber.paco.odessa.uaIgor Roshchin str@giganda.komkon.orgIgor Serikov bt@turtle.pangeatech.comIgor Sviridov siac@ua.netIgor Vinokurov igor@zynaps.ruIkuo Nakagawa ikuo@isl.intec.co.jpIlia Chipitsine ilia@jane.cgu.chel.suIlya V. Komarov mur@lynx.ruIMAI Takeshi take-i@ceres.dti.ne.jpIMAMURA Tomoaki
tomoak-i@is.aist-nara.ac.jpItsuro Saito saito@miv.t.u-tokyo.ac.jpIWASHITA Yoji shuna@pop16.odn.ne.jpJ. Bryant jbryant@argus.flash.netJ. David Lowe lowe@saturn5.comJ. Han hjh@photino.comJ. Hawk jhawk@MIT.EDUJ.T. Conklin jtc@cygnus.comJack jack@zeus.xtalwind.netJacob Bohn Lorensen jacob@jblhome.ping.mkJagane D Sundar jagane@netcom.comJake Hamby jehamby@anobject.comJames Clark jjc@jclark.comJames D. Stewart jds@c4systm.comJames da Silva jds@cs.umd.eduJames Jegers jimj@miller.cs.uwm.eduJames Raynard
fhackers@jraynard.demon.co.ukJames T. Liu jtliu@phlebas.rockefeller.eduJamie Heckford jamie@jamiesdomain.co.ukJan Conard
charly@fachschaften.tu-muenchen.deJan Jungnickel Jan@Jungnickel.comJan Koum jkb@FreeBSD.orgJanick Taillandier
Janick.Taillandier@ratp.frJanusz Kokot janek@gaja.ipan.lublin.plJarle Greipsland jarle@idt.unit.noJason Garman init@risen.orgJason R. Mastaler
jason-freebsd@mastaler.comJason Thorpe thorpej@NetBSD.orgJason Wright jason@OpenBSD.orgJason Young
doogie@forbidden-donut.anet-stl.comJavier Martin Rueda jmrueda@diatel.upm.esJay Fenlason hack@datacube.comJay Krell jay.krell@cornell.eduJaye Mathisen mrcpu@cdsnet.netJeff Bartig jeffb@doit.wisc.eduJeff Brown jabrown@caida.orgJeff Forys jeff@forys.cranbury.nj.usJeff Kletsky Jeff@Wagsky.comJeff Palmer scorpio@drkshdw.orgJeffrey Evans evans@scnc.k12.mi.usJeffrey Wheat jeff@cetlink.netJeremy Allison jallison@whistle.comJeremy Chadwick yoshi@parodius.comJeremy Chatfield jdc@xinside.comJeremy Karlson karlj000@unbc.caJeremy Prior unknownJeremy Shaffner jeremy@external.orgJesse McConnell jesse@cylant.comJesse Rosenstock jmr@ugcs.caltech.eduJian-Da Li jdli@csie.nctu.edu.twJim Babb babb@FreeBSD.orgJim Binkley jrb@cs.pdx.eduJim Bloom bloom@acm.orgJim Carroll jim@carroll.comJim Flowers jflowers@ezo.netJim Leppek jleppek@harris.comJim Lowe james@cs.uwm.eduJim Mattson jmattson@sonic.netJim Mercer jim@komodo.reptiles.orgJim Sloan odinn@atlantabiker.netJim Wilson wilson@moria.cygnus.comJimbo Bahooli
griffin@blackhole.iceworld.orgJin Guojun jin@george.lbl.govJoachim Kuebart kuebart@mathematik.uni-ulm.deJoao Carlos Mendes Luis jonny@jonny.eng.brJochen Pohl jpo.drs@sni.deJoe "Marcus" Clarke marcus@marcuscom.comJoe Abley jabley@automagic.orgJoe Jih-Shian Lu jslu@dns.ntu.edu.twJoe Orthoefer j_orthoefer@tia.netJoe Traister traister@mojozone.orgJoel Faedi Joel.Faedi@esial.u-nancy.frJoel Ray Holveck joelh@gnu.orgJoel Sutton jsutton@bbcon.com.auJordan DeLong fracture@allusion.netJoseph Scott joseph@randomnetworks.comJohan Granlund johan@granlund.nuJohan Karlsson k@numeri.campus.luth.seJohan Larsson johan@moon.campus.luth.seJohann Tonsing jtonsing@mikom.csir.co.zaJohannes Helander unknownJohannes Stille unknownJohn Beckett jbeckett@southern.eduJohn Beukema jbeukema@hk.super.netJohn Brezak unknownJohn Capo jc@irbs.comJohn F. Woods jfw@jfwhome.funhouse.comJohn Goerzen
jgoerzen@alexanderwohl.complete.orgJohn Heidemann johnh@isi.eduJohn Hood cgull@owl.orgJohn Kohl unknownJohn Lind john@starfire.mn.orgJohn Mackin john@physiol.su.oz.auJohn P johnp@lodgenet.comJohn Perry perry@vishnu.alias.netJohn Preisler john@vapornet.comJohn Reynolds jjreynold@home.comJohn Rochester jr@cs.mun.caJohn Sadler john_sadler@alum.mit.eduJohn Saunders john@pacer.nlc.net.auJohn Wehle john@feith.comJohn Woods jfw@eddie.mit.eduJohny Mattsson lonewolf@flame.orgJon Morgan morgan@terminus.trailblazer.comJonathan Belson jon@witchspace.comJonathan H N Chin jc254@newton.cam.ac.ukJonathan Hanna
jh@pc-21490.bc.rogers.wave.caJonathan Pennington john@coastalgeology.orgJorge Goncalves j@bug.fe.up.ptJorge M. Goncalves ee96199@tom.fe.up.ptJos Backus jbackus@plex.nlJose Marques jose@nobody.orgJosef Grosch
jgrosch@superior.mooseriver.comJoseph Stein joes@wstein.comJosh Gilliam josh@quick.netJosh Tiefenbach josh@ican.netJuergen Lock nox@jelal.hb.north.deJuha Inkari inkari@cc.hut.fiJukka A. Ukkonen jau@iki.fiJulian Assange proff@suburbia.netJulian Coleman j.d.coleman@ncl.ac.uk&a.jhsJulian Jenkins kaveman@magna.com.auJunichi Satoh junichi@jp.FreeBSD.orgJunji SAKAI sakai@jp.FreeBSD.orgJunya WATANABE junya-w@remus.dti.ne.jpJustas justas@mbank.lvJustin Stanford jus@security.za.netK.Higashino a00303@cc.hc.keio.ac.jpKai Vorma vode@snakemail.hut.fiKaleb S. Keithley kaleb@ics.comKaneda Hiloshi vanitas@ma3.seikyou.ne.jpKang-ming Liu gugod@gugod.orgKapil Chowksey kchowksey@hss.hns.comKarl Denninger karl@mcs.comKarl Dietz Karl.Dietz@triplan.comKarl Lehenbauer karl@NeoSoft.comKATO Tsuguru tkato@prontomail.ne.jpKawanobe Koh kawanobe@st.rim.or.jpKees Jan Koster kjk1@ukc.ac.ukKeith Bostic bostic@bostic.comKeith E. Walker kew@icehouse.netKeith Moore unknownKeith Sklower unknownKen Hornstein unknownKen Key key@cs.utk.eduKen Mayer kmayer@freegate.comKenji Saito marukun@mx2.nisiq.netKenji Tomita tommyk@da2.so-net.or.jpKenneth Furge kenneth.furge@us.endress.comKenneth Monville desmo@bandwidth.orgKenneth R. Westerback krw@tcn.netKenneth Stailey kstailey@gnu.ai.mit.eduKent Talarico kent@shipwreck.tsoft.netKent Vander Velden graphix@iastate.eduKentaro Inagaki JBD01226@niftyserve.ne.jpKevin Bracey kbracey@art.acorn.co.ukKevin Day toasty@dragondata.comKevin Lahey kml@nas.nasa.govKevin Meltzer perlguy@perlguy.comKevin Street street@iname.comKevin Van Maren vanmaren@fast.cs.utah.eduKiller killer@prosalg.noKim Scarborough sluggo@unknown.nuKiril Mitev kiril@ideaglobal.comKiroh HARADA kiroh@kh.rim.or.jpKlaus Herrmann klaus.herrmann@gmx.netKlaus Klein kleink@layla.inka.deKlaus-J. Wolf Yanestra@t-online.deKoichi Sato copan@ppp.fastnet.or.jpKonrad Heuer kheuer@gwdu60.gwdg.deKonstantin Chuguev Konstantin.Chuguev@dante.org.ukKostya Lukin lukin@okbmei.msk.suKouichi Hirabayashi kh@mogami-wire.co.jpKris Dow kris@vilnya.demon.co.ukKUNISHIMA Takeo kunishi@c.oka-pu.ac.jpKurt D. Zeilenga Kurt@Boolean.NETKurt Olsen kurto@tiny.mcs.usu.eduL. Jonas Olsson
ljo@ljo-slip.DIALIN.CWRU.EduLarry Altneu larry@ALR.COMLars Bernhardsson lab@fnurt.netLars Köller
Lars.Koeller@Uni-Bielefeld.DELaurence Lopez lopez@mv.mv.comLee Cremeans lcremean@tidalwave.netLeo Kim leo@florida.sarang.netLeo Serebryakov lev@serebryakov.spb.ruLiang Tai-hwa
avatar@www.mmlab.cse.yzu.edu.twLon Willett lon%softt.uucp@math.utah.eduLouis A. Mamakos louie@TransSys.COMLouis Mamakos loiue@TransSys.comLowell Gilbert lowell@world.std.comLucas James Lucas.James@ldjpc.apana.org.auLyndon Nerenberg lyndon@orthanc.ab.caM. L. Dodson bdodson@scms.utmb.EDUM.C. Wong unknownMagnus Enbom dot@tinto.campus.luth.seMahesh Neelakanta mahesh@gcomm.comMakoto MATSUSHITA matusita@jp.FreeBSD.orgMakoto WATANABE
watanabe@zlab.phys.nagoya-u.ac.jpMakoto YAMAKURA makoto@pinpott.spnet.ne.jpMalte Lance malte.lance@gmx.netMANTANI Nobutaka nobutaka@nobutaka.comManu Iyengar
iyengar@grunthos.pscwa.psca.comMarc Frajola marc@dev.comMarc Ramirez mrami@mramirez.sy.yale.eduMarc Slemko marcs@znep.comMarc van Kempen wmbfmk@urc.tue.nlMarc van Woerkom van.woerkom@netcologne.deMarcin Cieslak saper@system.plMark Andrews unknownMark Cammidge mark@gmtunx.ee.uct.ac.zaMark Diekhans markd@grizzly.comMark Huizer xaa@stack.nlMark J. Taylor mtaylor@cybernet.comMark Knight markk@knigma.orgMark Krentel krentel@rice.eduMark Mayo markm@vmunix.comMark Thompson thompson@tgsoft.comMark Tinguely tinguely@plains.nodak.eduMark Treacy unknownMark Valentine mark@thuvia.orgMarkus Holmberg saska@acc.umu.seMartin Birgmeier unknownMartin Blapp blapp@attic.chMartin Hinner mhi@linux.gyarab.czMartin Ibert mib@ppe.bb-data.deMartin Kammerhofer dada@sbox.tu-graz.ac.atMartin Minkus diskiller@cnbinc.comMartin Renters martin@tdc.on.caMartti Kuparinen
martti.kuparinen@ericsson.comMasachika ISHIZUKA
ishizuka@isis.min.ntt.jpMasahiro Sekiguchi
seki@sysrap.cs.fujitsu.co.jpMasahiro TAKEMURA
mastake@msel.t.u-tokyo.ac.jpMasanobu Saitoh msaitoh@spa.is.uec.ac.jpMasanori Kanaoka kana@saijo.mke.mei.co.jpMasanori Kiriake seiken@ARGV.ACMasatoshi TAMURA
tamrin@shinzan.kuee.kyoto-u.ac.jpMats Lofkvist mal@algonet.seMatt Bartley mbartley@lear35.cytex.comMatt Heckaman matt@LUCIDA.QC.CAMatt Thomas matt@3am-software.comMatt White mwhite+@CMU.EDUMatthew C. Mead mmead@Glock.COMMatthew Cashdollar mattc@rfcnet.comMatthew Emmerton root@gabby.gsicomp.on.caMatthew Flatt mflatt@cs.rice.eduMatthew Fuller fullermd@futuresouth.comMatthew Stein matt@bdd.netMatthew West mwest@uct.ac.zaMatthias Pfaller leo@dachau.marco.deMatthias Scheler tron@netbsd.orgMattias Gronlund
Mattias.Gronlund@sa.erisoft.seMattias Pantzare pantzer@ludd.luth.seMaurice Castro
maurice@planet.serc.rmit.edu.auMax Euston meuston@jmrodgers.comMax Khon fjoe@husky.iclub.nsu.ruMaxim Bolotin max@rsu.ruMaxim Konovalov maxim@macomnet.ruMaxime Henrion mhenrion@cybercable.frMicha Class
michael_class@hpbbse.bbn.hp.comMichael Alyn Miller malyn@strangeGizmo.comMichael Lucas mwlucas@blackhelicopters.orgMichael Lyngbøl michael@lyngbol.dkMichael Butler imb@scgt.oz.auMichael Butschky butsch@computi.erols.comMichael Clay mclay@weareb.orgMichael Galassi nerd@percival.rain.comMichael Hancock michaelh@cet.co.jpMichael Hohmuth hohmuth@inf.tu-dresden.deMichael Perlman canuck@caam.rice.eduMichael Petry petry@netwolf.NetMasters.comMichael Reifenberger root@totum.plaut.deMichael Sardo jaeger16@yahoo.comMichael Searle searle@longacre.demon.co.ukMichael Urban murban@tznet.comMichael Vasilenko acid@stu.cn.uaMichal Listos mcl@Amnesiac.123.orgMichio Karl Jinbo
karl@marcer.nagaokaut.ac.jpMiguel Angel Sagreras
msagre@cactus.fi.uba.arMihoko Tanaka m_tonaka@pa.yokogawa.co.jpMika Nystrom mika@cs.caltech.eduMikael Hybsch micke@dynas.seMikael Karpberg
karpen@ocean.campus.luth.seMike Barcroft mike@q9media.comMike Bristow mike@urgle.comMike Del repenting@hotmail.comMike Durian durian@plutotech.comMike Durkin mdurkin@tsoft.sf-bay.orgMike E. Matsnev mike@azog.cs.msu.suMike Evans mevans@candle.comMike Futerko mike@LITech.lviv.uaMike Grupenhoff kashmir@umiacs.umd.eduMike Harding mvh@ix.netcom.comMike Hibler mike@marker.cs.utah.eduMike Karels unknownMike McGaughey mmcg@cs.monash.edu.auMike Meyer mwm@mired.orgMike Mitchell mitchell@ref.tfs.comMike Murphy mrm@alpharel.comMike Peck mike@binghamton.eduMike Sherwood mike@fate.comMike Spengler mks@msc.eduMikhail A. Sokolov mishania@demos.suMing-I Hseh PA@FreeBSD.ee.Ntu.edu.TWMitsuru Yoshida mitsuru@riken.go.jpMonte Mitzelfelt monte@gonefishing.orgMorgan Davis root@io.cts.comMOROHOSHI Akihiko moro@race.u-tokyo.ac.jpMostyn Lewis mostyn@mrl.comMotomichi Matsuzaki mzaki@e-mail.ne.jpMotoyuki Kasahara m-kasahr@sra.co.jpN.G.Smith ngs@sesame.hensa.ac.ukNadav Eiron nadav@barcode.co.ilNAGAO Tadaaki nagao@cs.titech.ac.jpNAKAJI Hiroyuki
nakaji@tutrp.tut.ac.jpNAKAMURA Kazushi nkazushi@highway.or.jpNAKAMURA Motonori
motonori@econ.kyoto-u.ac.jpNAKATA, Maho chat95@mbox.kyoto-inet.or.jpNanbor Wang nw1@cs.wustl.eduNaofumi Honda
honda@Kururu.math.sci.hokudai.ac.jpNaoki Hamada nao@tom-yam.or.jpNarvi narvi@haldjas.folklore.eeNathan Dorfman nathan@rtfm.netNeal Fachan kneel@ishiboo.comNiall Smart rotel@indigo.ieNicholas Esborn nick@netdot.netNick Barnes Nick.Barnes@pobox.comNick Handel nhandel@NeoSoft.comNick Hilliard nick@foobar.orgNick Johnson freebsd@spatula.netNick Williams njw@cs.city.ac.ukNickolay N. Dudorov nnd@itfs.nsk.suNIIMI Satoshi sa2c@and.or.jpNiklas Hallqvist niklas@filippa.appli.seNils M. Holm nmh@t3x.orgNisha Talagala nisha@cs.berkeley.eduNo Name adrian@virginia.eduNo Name alex@elvisti.kiev.uaNo Name anto@netscape.netNo Name bobson@egg.ics.nitch.ac.jpNo Name bovynf@awe.beNo Name burg@is.ge.comNo Name chris@gnome.co.ukNo Name colsen@usa.netNo Name coredump@nervosa.comNo Name dannyman@arh0300.urh.uiuc.eduNo Name davids@SECNET.COMNo Name derek@free.orgNo Name devet@adv.IAEhv.nlNo Name djv@bedford.netNo Name dvv@sprint.netNo Name enami@ba2.so-net.or.jpNo Name flash@eru.tubank.msk.suNo Name flash@hway.ruNo Name fn@pain.csrv.uidaho.eduNo Name frf@xocolatl.comNo Name gclarkii@netport.neosoft.comNo Name gordon@sheaky.lonestar.orgNo Name graaf@iae.nlNo Name greg@greg.rim.or.jpNo Name grossman@cygnus.comNo Name gusw@fub46.zedat.fu-berlin.deNo Name hfir@math.rochester.eduNo Name hnokubi@yyy.or.jpNo Name iaint@css.tuu.utas.edu.auNo Name invis@visi.comNo Name ishisone@sra.co.jpNo Name iverson@lionheart.comNo Name jpt@magic.netNo Name junker@jazz.snu.ac.krNo Name k-sugyou@ccs.mt.nec.co.jpNo Name kenji@reseau.toyonaka.osaka.jpNo Name kfurge@worldnet.att.netNo Name lh@aus.orgNo Name lhecking@nmrc.ucc.ieNo Name mrgreen@mame.mu.oz.auNo Name nakagawa@jp.FreeBSD.orgNo Name ohki@gssm.otsuka.tsukuba.ac.jpNo Name owaki@st.rim.or.jpNo Name pechter@shell.monmouth.comNo Name pete@pelican.pelican.comNo Name pritc003@maroon.tc.umn.eduNo Name risner@stdio.comNo Name roman@rpd.univ.kiev.uaNo Name root@ns2.redline.ruNo Name root@uglabgw.ug.cs.sunysb.eduNo Name stephen.ma@jtec.com.auNo Name sumii@is.s.u-tokyo.ac.jpNo Name takas-su@is.aist-nara.ac.jpNo Name tamone@eig.unige.chNo Name tjevans@raleigh.ibm.comNo Name tony-o@iij.ad.jp amurai@spec.co.jpNo Name torii@tcd.hitachi.co.jpNo Name uenami@imasy.or.jpNo Name uhlar@netlab.skNo Name vode@hut.fiNo Name wlloyd@mpd.caNo Name wlr@furball.wellsfargo.comNo Name wmbfmk@urc.tue.nlNo Name yamagata@nwgpc.kek.jpNo Name ziggy@ryan.orgNo Name ZW6T-KND@j.asahi-net.or.jpNobuhiro Yasutomi nobu@psrc.isac.co.jpNobuyuki Koganemaru
kogane@koganemaru.co.jpNOKUBI Hirotaka h-nokubi@yyy.or.jpNorio Suzuki nosuzuki@e-mail.ne.jpNoritaka Ishizumi graphite@jp.FreeBSD.orgNoriyuki Soda soda@sra.co.jpOddbjorn Steffenson oddbjorn@tricknology.orgOh Junseon hollywar@mail.holywar.netOlaf Wagner wagner@luthien.in-berlin.deOleg Semyonov os@altavista.netOleg Sharoiko os@rsu.ruOleg V. Volkov rover@lglobus.ruOlexander Kunytsa kunia@wolf.istc.kiev.uaOliver Breuninger ob@seicom.NETOliver Friedrichs oliver@secnet.comOliver Fromme
oliver.fromme@heim3.tu-clausthal.deOliver Helmling
oliver.helmling@stud.uni-bayreuth.deOliver Laumann
net@informatik.uni-bremen.deOliver Lehmann
Kai_Allard_Liao@gmx.deOliver Oberdorf oly@world.std.comOlof Johansson offe@ludd.luth.seOsokin Sergey aka oZZ ozz@FreeBSD.org.ruPace Willisson pace@blitz.comPaco Rosich rosich@modico.eleinf.uv.esPalle Girgensohn girgen@partitur.seParag Patel parag@cgt.comPascal Pederiva pascal@zuo.dec.comPasvorn Boonmark boonmark@juniper.netPatrick Alken cosine@ellipse.mcs.drexel.eduPatrick Bihan-Faou patrick@mindstep.comPatrick Hausen unknownPatrick Li pat@databits.netPatrick Seal patseal@hyperhost.netPaul Antonov apg@demos.suPaul F. Werkowski unknownPaul Fox pgf@foxharp.boston.ma.usPaul Koch koch@thehub.com.auPaul Kranenburg pk@NetBSD.orgPaul M. Lambert plambert@plambert.netPaul Mackerras paulus@cs.anu.edu.auPaul Popelka paulp@uts.amdahl.comPaul S. LaFollette, Jr. unknownPaul Sandys myj@nyct.netPaul T. Root proot@horton.iaces.comPaul Vixie paul@vix.comPaulo Menezes paulo@isr.uc.ptPaulo Menezes pm@dee.uc.ptPedro A M Vazquez vazquez@IQM.Unicamp.BRPedro Giffuni giffunip@asme.orgPer Wigren wigren@home.sePete Bentley pete@demon.netPete Fritchman petef@databits.netPeter Childs pjchilds@imforei.apana.org.auPeter Cornelius pc@inr.fzk.dePeter Haight peterh@prognet.comPeter Jeremy peter.jeremy@alcatel.com.auPeter M. Chen pmchen@eecs.umich.eduPeter Much peter@citylink.dinoex.sub.orgPeter Olsson unknownPeter Philipp pjp@bsd-daemon.netPeter Stubbs PETERS@staidan.qld.edu.auPeter van Heusden pvh@egenetics.comPhil Maker pjm@cs.ntu.edu.auPhil Sutherland
philsuth@mycroft.dialix.oz.auPhil Taylor phil@zipmail.co.ukPhilip Musumeci philip@rmit.edu.auPhilippe Lefebvre nemesis@balistik.netPierre Y. Dampure pierre.dampure@k2c.co.ukPius Fischer pius@ienet.comPomegranate daver@flag.blackened.netPowerdog Industries
kevin.ruddy@powerdog.comPriit Järv priit@cc.ttu.eeR Joseph Wright rjoseph@mammalia.orgR. Kym HorsellRalf Friedl friedl@informatik.uni-kl.deRandal S. Masutani randal@comtest.comRandall Hopper rhh@ct.picker.comRandall W. Dean rwd@osf.orgRandy Bush rbush@bainbridge.verio.netRasmus Kaj kaj@Raditex.seReinier Bezuidenhout
rbezuide@mikom.csir.co.zaRemy Card Remy.Card@masi.ibp.frRicardas Cepas rch@richard.eu.orgRiccardo Veraldi veraldi@cs.unibo.itRich Wood rich@FreeBSD.org.ukRichard Henderson richard@atheist.tamu.eduRichard Hwang rhwang@bigpanda.comRichard Kiss richard@homemail.comRichard J Kuhns rjk@watson.grauel.comRichard M. Neswold
rneswold@enteract.comRichard Seaman, Jr. dick@tar.comRichard Stallman rms@gnu.ai.mit.eduRichard Straka straka@user1.inficad.comRichard Tobin richard@cogsci.ed.ac.ukRichard Wackerbarth rkw@Dataplex.NETRichard Winkel rich@math.missouri.eduRichard Wiwatowski rjwiwat@adelaide.on.netRick Macklem rick@snowhite.cis.uoguelph.caRick Macklin unknownRob Austein sra@epilogue.comRob Mallory rmallory@qualcomm.comRob Snow rsnow@txdirect.netRobert Crowe bob@speakez.comRobert D. Thrush rd@phoenix.aii.comRobert Eckardt
roberte@MEP.Ruhr-Uni-Bochum.deRobert P Ricci ricci@cs.utah.eduRobert Sanders rsanders@mindspring.comRobert Sexton robert@kudra.comRobert Shady rls@id.netRobert Swindells swindellsr@genrad.co.ukRobert Withrow witr@rwwa.comRobert Yoder unknownRobin Carey
robin@mailgate.dtc.rankxerox.co.ukRod Taylor rod@idiotswitch.orgRoger Hardiman roger@cs.strath.ac.ukRoland Jesse jesse@cs.uni-magdeburg.deRoman Shterenzon roman@xpert.comRon Bickers rbickers@intercenter.netRon Lenk rlenk@widget.xmission.comRonald Kuehn kuehn@rz.tu-clausthal.deRudolf Cejka cejkar@dcse.fee.vutbr.czRuslan Belkin rus@home2.UA.netRuslan Shevchenko rssh@cam.grad.kiev.uaRussell L. Carter rcarter@pinyon.orgRussell Vincent rv@groa.uct.ac.zaRyan Younce ryany@pobox.comRyuichiro IMURA imura@af.airnet.ne.jpSakai Hiroaki sakai@miya.ee.kagu.sut.ac.jpSakari Jalovaara sja@tekla.fiSam Hartman hartmans@mit.eduSamuel Lam skl@ScalableNetwork.comSamuel Tardieu sam@inf.enst.frSamuele Zannoli zannoli@cs.unibo.itSander Janssen janssen@rendo.dekooi.nlSander Vesik sander@haldjas.folklore.eeSandro Sigala ssigala@globalnet.itSANETO Takanori sanewo@strg.sony.co.jpSASAKI Shunsuke ele@pop17.odn.ne.jpSascha Blank blank@fox.uni-trier.deSascha Wildner swildner@channelz.GUN.deSatoh Junichi junichi@astec.co.jpSAWADA Mizuki miz@qb3.so-net.ne.jpScot Elliott scot@poptart.orgScot W. Hetzel hetzels@westbend.netScott A. Kenney saken@rmta.ml.orgScott A. Moberly smoberly@xavier.dyndns.orgScott Blachowicz
scott.blachowicz@seaslug.orgScott Burris scott@pita.cns.ucla.eduScott Hazen Mueller scott@zorch.sf-bay.orgScott Michel scottm@cs.ucla.eduScott Mitchel scott@uk.FreeBSD.orgScott Reynolds scott@clmqt.marquette.mi.usSebastian Strollo seb@erix.ericsson.seSerge V. Vakulenko vak@zebub.msk.suSergei Chechetkin csl@whale.sunbay.crimea.uaSergei S. Laskavy laskavy@pc759.cs.msu.suSergey Gershtein sg@mplik.ruSergey Kosyakov ks@itp.ac.ruSergey N. Vorokov serg@tmn.ruSergey Potapov sp@alkor.ruSergey Samoyloff gonza@techline.ruSergey Shkonda serg@bcs.zp.uaSergey Skvortsov skv@protey.ruSergey V.Dorokhov svd@kbtelecom.nalnet.ruSergio Lenzi lenzi@bsi.com.brShaun Courtney shaun@emma.eng.uct.ac.zaShawn M. Carey smcarey@mailbox.syr.eduShigio Yamaguchi shigio@tamacom.comShinya Esu esu@yk.rim.or.jpShinya FUJIE fujie@tk.elec.waseda.ac.jpShuichi Tanaka stanaka@bb.mbn.or.jpSimon simon@masi.ibp.frSimon Burge simonb@telstra.com.auSimon Dick simond@irrelevant.orgSimon J Gerraty sjg@melb.bull.oz.auSimon Marlow simonm@dcs.gla.ac.ukSimon Shapiro shimon@simon-shapiro.orgSin'ichiro MIYATANI siu@phaseone.co.jpSlaven Rezic eserte@cs.tu-berlin.deSoochon Radee slr@mitre.orgSoren Dayton csdayton@midway.uchicago.eduSoren Dossing sauber@netcom.comSoren S. Jorvang soren@wheel.dkStefan Bethke stb@hanse.deStefan Eggers seggers@semyam.dinoco.deStefan Moeding s.moeding@ndh.netStefan Petri unknownStefan `Sec` Zehl sec@42.orgSteinar Haug sthaug@nethelp.noStephane E. Potvin sepotvin@videotron.caStephane Legrand stephane@lituus.frStephen Clawson
sclawson@marker.cs.utah.eduStephen F. Combs combssf@salem.ge.comStephen Farrell stephen@farrell.orgStephen Hocking sysseh@devetir.qld.gov.auStephen J. Roznowski sjr@home.netStephen McKay syssgm@devetir.qld.gov.auStephen Melvin melvin@zytek.comSteve Bauer sbauer@rock.sdsmt.eduSteve Coltrin spcoltri@unm.eduSteve Deering unknownSteve Gerakines steve2@genesis.tiac.netSteve Gericke steveg@comtrol.comSteve Piette steve@simon.chi.il.USSteve Schwarz schwarz@alpharel.comSteven Enderle panic@subphase.deSteven G. Kargl
kargl@troutmask.apl.washington.eduSteven H. Samorodin samorodi@NUXI.comSteven McCanne mccanne@cs.berkeley.eduSteven Plite splite@purdue.eduSteven Wallace unknownStijn Hoop stijn@win.tue.nlStuart Henderson
stuart@internationalschool.co.ukSue Blake sue@welearn.com.auSugimoto Sadahiro ixtl@komaba.utmc.or.jpSUGIMURA Takashi sugimura@jp.FreeBSD.orgSugiura Shiro ssugiura@duo.co.jpSujal Patel smpatel@wam.umd.eduSungman Cho smcho@tsp.korea.ac.krSune Stjerneby stjerneby@usa.netSURANYI Peter
suranyip@jks.is.tsukuba.ac.jpSuzuki Yoshiaki
zensyo@ann.tama.kawasaki.jpSvein Skogen
tds@nsn.noSybolt de Boer bolt@xs4all.nlTadashi Kumano kumano@strl.nhk.or.jpTaguchi Takeshi taguchi@tohoku.iij.ad.jpTAKAHASHI Kaoru kaoru@kaisei.orgTakahiro Yugawa yugawa@orleans.rim.or.jpTakashi Mega mega@minz.orgTakashi Uozu j1594016@ed.kagu.sut.ac.jpTakayuki Ariga a00821@cc.hc.keio.ac.jpTakeru NAIKI naiki@bfd.es.hokudai.ac.jpTakeshi Amaike amaike@iri.co.jpTakeshi MUTOH mutoh@info.nara-k.ac.jpTakeshi Ohashi
ohashi@mickey.ai.kyutech.ac.jpTakeshi WATANABE
watanabe@crayon.earth.s.kobe-u.ac.jpTakuya SHIOZAKI
tshiozak@makino.ise.chuo-u.ac.jpTatoku Ogaito tacha@tera.fukui-med.ac.jpTatsuya Kudoh cdr@cosmonet.orgTed Buswell tbuswell@mediaone.netTed Faber faber@isi.eduTed Lemon mellon@isc.orgTerry Lambert terry@lambert.orgTerry Lee terry@uivlsi.csl.uiuc.eduTetsuya Furukawa tetsuya@secom-sis.co.jpTheo de Raadt deraadt@OpenBSD.orgThomas thomas@mathematik.uni-Bremen.deThomas D. Dean tomdean@ix.netcom.comThomas David Rivers rivers@dignus.comThomas G. McWilliams tgm@netcom.comThomas Graichen
graichen@omega.physik.fu-berlin.deThomas König
Thomas.Koenig@ciw.uni-karlsruhe.deThomas Ptacek unknownThomas Quinot thomas@cuivre.fr.eu.orgThomas A. Stephens tas@stephens.orgThomas Stromberg tstrombe@rtci.comThomas Valentino Crimi
tcrimi+@andrew.cmu.eduThomas Wintergerst thomas@lemur.nord.deÞórður Ívarsson
totii@est.isThierry Thomas tthomas@mail.dotcom.frTimothy Jensen toast@blackened.comTim Kientzle kientzle@netcom.comTim Singletary
tsingle@sunland.gsfc.nasa.govTim Wilkinson tim@sarc.city.ac.ukTimo J. Rinne tri@iki.fiTobias Reifenberger treif@mayn.deTodd Miller millert@openbsd.orgTom root@majestix.cmr.noTom tom@sdf.comTom Gray - DCA dcasba@rain.orgTom Jobbins tom@tom.tjTom Pusateri pusateri@juniper.netTom Rush tarush@mindspring.comTom Samplonius tom@misery.sdf.comTomohiko Kurahashi
kura@melchior.q.t.u-tokyo.ac.jpTony Kimball alk@Think.COMTony Li tli@jnx.comTony Lynn wing@cc.nsysu.edu.twTony Maher tonym@angis.org.auTorbjorn Granlund tege@matematik.su.seToshihiko SHIMOKAWA toshi@tea.forus.or.jpToshihiro Kanda candy@kgc.co.jpToshiomi Moriki
Toshiomi.Moriki@ma1.seikyou.ne.jpTrefor S. trefor@flevel.co.ukTrenton Schulz twschulz@cord.eduTrevor Blackwell tlb@viaweb.comUdo Schweigert ust@cert.siemens.deUgo Paternostro paterno@dsi.unifi.itUlf Kieber kieber@sax.deUlli Linzen ulli@perceval.camelot.deURATA Shuichiro s-urata@nmit.tmg.nec.co.jpUwe Arndt arndt@mailhost.uni-koblenz.deVadim Belman vab@lflat.vas.mobilix.dkVadim Chekan vadim@gc.lviv.uaVadim Kolontsov vadim@tversu.ac.ruVadim Mikhailov mvp@braz.ruValentin Nechayev netch@lucky.net&a.logo;Van Jacobson van@ee.lbl.govVasily V. Grechishnikov
bazilio@ns1.ied-vorstu.ac.ruVasim Valejev vasim@uddias.diaspro.comVernon J. Schryver vjs@mica.denver.sgi.comVeselin Slavov vess@btc.netVic Abell abe@cc.purdue.eduVille Eerola ve@sci.fiVince Valenti vince@blue-box.netVincent Poy vince@venus.gaianet.netVincenzo Capuano
VCAPUANO@vmprofs.esoc.esa.deVirgil Champlin champlin@pa.dec.comVladimir A. Jakovenko
vovik@ntu-kpi.kiev.uaVladimir Kushnir kushn@mail.kar.netVsevolod Lobko seva@alex-ua.comW. Gerald Hicks wghicks@bellsouth.netW. Richard Stevens rstevens@noao.eduWalt Howard howard@ee.utah.eduWalt M. Shandruk walt@erudition.netWarren Toomey wkt@csadfa.cs.adfa.oz.auWayne Scott wscott@ichips.intel.comWerner Griessl
werner@btp1da.phy.uni-bayreuth.deWes Santee wsantee@wsantee.oz.netWietse Venema wietse@wzv.win.tue.nlWiljo Heinen wiljo@freeside.ki.open.deWillem Jan Withagen wjw@surf.IAE.nlWilliam Jolitz withheldWilliam Liao william@tale.netWojtek Pilorz
wpilorz@celebris.bdk.lublin.plWolfgang Helbig helbig@ba-stuttgart.deWolfgang Solfrank ws@tools.deWolfgang Stanglmeier wolf@FreeBSD.orgWu Ching-hong woju@FreeBSD.ee.Ntu.edu.TWYarema yds@ingress.comYaroslav Terletsky ts@polynet.lviv.uaYasuhiro Fukama yasuf@big.or.jpYasuhito FUTATSUKI futatuki@fureai.or.jpYen-Ming Lee leeym@bsd.ce.ntu.edu.twYen-Shuo Su yssu@CCCA.NCTU.edu.twYin-Jieh Chen yinjieh@Crazyman.Dorm13.NCTU.edu.twYixin Jin yjin@rain.cs.ucla.eduYoichi Asai yatt@msc.biglobe.ne.jpYoichi Nakayama yoichi@eken.phys.nagoya-u.ac.jpYoshiaki Uchikawa yoshiaki@kt.rim.or.jpYoshihiko SARUMRU mistral@imasy.or.jpYoshihisa NAKAGAWA
y-nakaga@ccs.mt.nec.co.jpYoshikazu Goto gotoh@ae.anritsu.co.jpYoshimasa Ohnishi
ohnishi@isc.kyutech.ac.jpYoshishige Arai ryo2@on.rim.or.jpYuichi MATSUTAKA matutaka@osa.att.ne.jpYujiro MIYATA
miyata@bioele.nuee.nagoya-u.ac.jpYu-Shun Wang yushunwa@isi.eduYusuke Nawano azuki@azkey.orgYuu Yashiki s974123@cc.matsuyama-u.ac.jpYuuki SAWADA mami@whale.cc.muroran-it.ac.jpYuuichi Narahara aconitum@po.teleway.ne.jpYuval Yarom yval@cs.huji.ac.ilYves Fonk yves@cpcoup5.tn.tudelft.nlYves Fonk yves@dutncp8.tn.tudelft.nlZach Heilig zach@gaffaneys.comZach Zurflu zach@pabst.bendnet.comZahemszhky Gabor zgabor@code.huZhong Ming-Xun zmx@mail.CDPA.nsysu.edu.tw386BSD Patch Kit Patch Contributors(in alphabetical order by first name):Adam Glass glass@postgres.berkeley.eduAdrian Hall ahall@mirapoint.comAndrey A. Chernov ache@astral.msk.suAndrew Herbert andrew@werple.apana.org.auAndrew Moore alm@netcom.comAndy Valencia ajv@csd.mot.comjtk@netcom.comArne Henrik Juul arnej@Lise.Unit.NOBakul Shah bvs@bitblocks.comBarry Lustig barry@ictv.comBob Wilcox bob@obiwan.uucpBranko LankesterBrett Lymn blymn@mulga.awadi.com.AUCharles Hannum mycroft@ai.mit.eduChris G. Demetriou
cgd@postgres.berkeley.eduChris Torek torek@ee.lbl.govChristoph Robitschko
chmr@edvz.tu-graz.ac.atDaniel Poirot poirot@aio.jsc.nasa.govDave Burgess burgess@hrd769.brooks.af.milDave Rivers rivers@ponds.uucpDavid Dawes dawes@physics.su.OZ.AUDavid Greenman dg@Root.COMEric J. Haug ejh@slustl.slu.eduFelix Gaehtgens
felix@escape.vsse.in-berlin.deFrank Maclachlan fpm@crash.cts.comGary A. Browning gab10@griffcd.amdahl.comGary Howland gary@hotlava.comGeoff Rehmet csgr@alpha.ru.ac.zaGoran Hammarback goran@astro.uu.seGuido van Rooij guido@gvr.orgGuy Antony Halse guy@rucus.ru.ac.zaGuy Harris guy@auspex.comHavard Eidnes
Havard.Eidnes@runit.sintef.noHerb Peyerl hpeyerl@novatel.cuc.ab.caHolger Veit Holger.Veit@gmd.deIshii Masahiro, R. Kym HorsellJ.T. Conklin jtc@cygnus.comJagane D Sundar jagane@netcom.comJames Clark jjc@jclark.comJames Jegers jimj@miller.cs.uwm.eduJames W. DolterJames da Silva jds@cs.umd.edu et alJay Fenlason hack@datacube.comJim Wilson wilson@moria.cygnus.comJörg Lohse
lohse@tech7.informatik.uni-hamburg.deJörg Wunsch
joerg_wunsch@uriah.heep.sax.deJohn DysonJohn Woods jfw@eddie.mit.eduJordan K. Hubbard jkh@whisker.hubbard.ieJulian Elischer julian@dialix.oz.auJulian Stacey jhs@FreeBSD.orgKarl Dietz Karl.Dietz@triplan.comKarl Lehenbauer karl@NeoSoft.comkarl@one.neosoft.comKeith Bostic bostic@toe.CS.Berkeley.EDUKen HughesKent Talarico kent@shipwreck.tsoft.netKevin Lahey kml%rokkaku.UUCP@mathcs.emory.edukml@mosquito.cis.ufl.eduKonstantinos Konstantinidis kkonstan@duth.grMarc Frajola marc@dev.comMark Tinguely tinguely@plains.nodak.edutinguely@hookie.cs.ndsu.NoDak.eduMartin Renters martin@tdc.on.caMichael Clay mclay@weareb.orgMichael Galassi nerd@percival.rain.comMike Durkin mdurkin@tsoft.sf-bay.orgNaoki Hamada nao@tom-yam.or.jpNate Williams nate@bsd.coe.montana.eduNick Handel nhandel@NeoSoft.comnick@madhouse.neosoft.comPace Willisson pace@blitz.comPaul Kranenburg pk@cs.few.eur.nlPaul Mackerras paulus@cs.anu.edu.auPaul Popelka paulp@uts.amdahl.comPeter da Silva peter@NeoSoft.comPhil Sutherland
philsuth@mycroft.dialix.oz.auPoul-Henning Kamp phk@FreeBSD.orgRalf Friedl friedl@informatik.uni-kl.deRick Macklem root@snowhite.cis.uoguelph.caRobert D. Thrush rd@phoenix.aii.comRodney W. Grimes rgrimes@cdrom.comSascha Wildner swildner@channelz.GUN.deScott Burris scott@pita.cns.ucla.eduScott Reynolds scott@clmqt.marquette.mi.usSean Eric Fagan sef@kithrup.comSimon J Gerraty sjg@melb.bull.oz.ausjg@zen.void.oz.auStephen McKay syssgm@devetir.qld.gov.auTerry Lambert terry@icarus.weber.eduTerry Lee terry@uivlsi.csl.uiuc.eduTor Egge Tor.Egge@idi.ntnu.noWarren Toomey wkt@csadfa.cs.adfa.oz.auWiljo Heinen wiljo@freeside.ki.open.deWilliam Jolitz withheldWolfgang Solfrank ws@tools.deWolfgang Stanglmeier wolf@dentaro.GUN.deYuval Yarom yval@cs.huji.ac.il
diff --git a/en_US.ISO8859-1/books/handbook/authors.ent b/en_US.ISO8859-1/books/handbook/authors.ent
index 8b4b487c37..b72bcd2587 100644
--- a/en_US.ISO8859-1/books/handbook/authors.ent
+++ b/en_US.ISO8859-1/books/handbook/authors.ent
@@ -1,646 +1,648 @@
abial@FreeBSD.org">
ache@FreeBSD.org">
adam@FreeBSD.org">
ade@FreeBSD.org">
adrian@FreeBSD.org">
akiyama@FreeBSD.org">
alc@FreeBSD.org">
alex@FreeBSD.org">
alfred@FreeBSD.org">
amurai@FreeBSD.org">
andreas@FreeBSD.org">
andy@FreeBSD.org">
archie@FreeBSD.org">
asami@FreeBSD.org">
asmodai@FreeBSD.org">
assar@FreeBSD.org">
ats@FreeBSD.org">
awebster@pubnix.net">
babkin@FreeBSD.org">
bde@FreeBSD.org">
ben@FreeBSD.org">
bean@FreeBSD.org">
benno@FreeBSD.org">
billf@FreeBSD.org">
bmah@FreeBSD.org">
bmilekic@FreeBSD.org">
bp@FreeBSD.org">
brandon@FreeBSD.org">
brian@FreeBSD.org">
brooks@FreeBSD.org">
bsd@FreeBSD.org">
cawimm@FreeBSD.org">
cg@FreeBSD.org">
charnier@FreeBSD.org">
chern@FreeBSD.org">
chm@FreeBSD.org">
chris@FreeBSD.org">
chuckr@glue.umd.edu">
chuckr@FreeBSD.org">
cjc@FreeBSD.org">
cjh@FreeBSD.org">
clive@FreeBSD.org">
cp@FreeBSD.org">
cokane@FreeBSD.org">
cpiazza@FreeBSD.org">
cracauer@FreeBSD.org">
csgr@FreeBSD.org">
+cshumway@FreeBSD.org">
+
cwt@FreeBSD.org">
dan@FreeBSD.org">
danny@FreeBSD.org">
dannyboy@FreeBSD.org">
darrenr@FreeBSD.org">
davidn@blaze.net.au">
dbaker@FreeBSD.org">
dburr@FreeBSD.org">
dcs@FreeBSD.org">
dd@FreeBSD.org">
dec@FreeBSD.org">
deischen@FreeBSD.org">
demon@FreeBSD.org">
des@FreeBSD.org">
dfr@FreeBSD.org">
dg@FreeBSD.org">
dick@FreeBSD.org">
dillon@FreeBSD.org">
dinoex@FreeBSD.org">
dima@FreeBSD.org">
dirk@FreeBSD.org">
Dirk.vanGulik@jrc.it">
dmlb@FreeBSD.org">
DougB@FreeBSD.org">
dt@FreeBSD.org">
dufault@FreeBSD.org">
dwcjr@FreeBSD.org">
dwhite@FreeBSD.org">
dwmalone@FreeBSD.org">
dyson@FreeBSD.org">
eivind@FreeBSD.org">
ejc@FreeBSD.org">
eric@FreeBSD.org">
erich@FreeBSD.org">
faq@FreeBSD.org">
fenner@FreeBSD.org">
flathill@FreeBSD.org">
foxfair@FreeBSD.org">
fsmp@FreeBSD.org">
furuta@FreeBSD.org">
gad@FreeBSD.org">
gallatin@FreeBSD.org">
gclarkii@FreeBSD.org">
gena@NetVision.net.il">
ghelmer@cs.iastate.edu">
gibbs@FreeBSD.org">
gioria@FreeBSD.org">
gj@FreeBSD.org">
gpalmer@FreeBSD.org">
graichen@FreeBSD.org">
green@FreeBSD.org">
greid@FreeBSD.org">
grog@FreeBSD.org">
groudier@club-internet.fr">
gryphon@healer.com">
gshapiro@FreeBSD.org">
gsutter@FreeBSD.org">
guido@FreeBSD.org">
hanai@FreeBSD.org">
handy@sxt4.physics.montana.edu">
hrs@FreeBSD.org">
roger@freebsd.org">
helbig@FreeBSD.org">
hm@FreeBSD.org">
hoek@FreeBSD.org">
horikawa@FreeBSD.org">
hosokawa@FreeBSD.org">
hsu@FreeBSD.org">
iedowse@FreeBSD.org">
ijliao@FreeBSD.org">
imp@FreeBSD.org">
imura@FreeBSD.org">
issei@FreeBSD.org">
itojun@itojun.org">
iwasaki@FreeBSD.org">
jake@FreeBSD.org">
jasone@FreeBSD.org">
jayanth@FreeBSD.org">
jb@cimlogic.com.au">
jdp@FreeBSD.org">
jedgar@FreeBSD.org">
jeh@FreeBSD.org">
jehamby@lightside.com">
jesper@FreeBSD.org">
jesusr@FreeBSD.org">
jfieber@FreeBSD.org">
jfitz@FreeBSD.org">
jgreco@FreeBSD.org">
jhay@FreeBSD.org">
jhb@FreeBSD.org">
jhs@FreeBSD.org">
jim@FreeBSD.org">
jkh@FreeBSD.org">
jkoshy@FreeBSD.org">
jlemon@FreeBSD.org">
john@starfire.MN.ORG">
jlrobin@FreeBSD.org">
jmacd@FreeBSD.org">
jmas@FreeBSD.org">
jmb@FreeBSD.org">
jmg@FreeBSD.org">
jmz@FreeBSD.org">
joe@FreeBSD.org">
keichii@FreeBSD.org">
joerg@FreeBSD.org">
john@FreeBSD.org">
jon@FreeBSD.org">
jraynard@FreeBSD.org">
jseger@FreeBSD.org">
julian@FreeBSD.org">
jwd@FreeBSD.org">
jvh@FreeBSD.org">
karl@FreeBSD.org">
kato@FreeBSD.org">
kbyanc@FreeBSD.org">
keith@FreeBSD.org">
kelly@ad1440.net">
ken@FreeBSD.org">
kevlo@FreeBSD.org">
kiri@FreeBSD.org">
kjc@FreeBSD.org">
knu@FreeBSD.org">
kris@FreeBSD.org">
kuriyama@FreeBSD.org">
lars@FreeBSD.org">
lile@FreeBSD.org">
lioux@FreeBSD.org">
ljo@FreeBSD.org">
lkoeller@FreeBSD.org">
logo@blackened.com">
luigi@FreeBSD.org">
luoqi@FreeBSD.org">
marcel@FreeBSD.org">
markm@FreeBSD.org">
marko@FreeBSD.org">
markp@FreeBSD.org">
martin@FreeBSD.org">
max@FreeBSD.org">
mark@vmunix.com">
mb@FreeBSD.org">
mbarkah@FreeBSD.org">
mckay@FreeBSD.org">
mckusick@FreeBSD.org">
md@bsc.no">
winter@jurai.net">
mharo@FreeBSD.org">
mi@FreeBSD.org">
mikeh@FreeBSD.org">
mita@FreeBSD.org">
mjacob@FreeBSD.org">
mks@FreeBSD.org">
motoyuki@FreeBSD.org">
mph@FreeBSD.org">
mpp@FreeBSD.org">
msmith@FreeBSD.org">
mtaylor@FreeBSD.org">
murray@FreeBSD.org">
nakai@FreeBSD.org">
nate@FreeBSD.org">
nbm@FreeBSD.org">
nectar@FreeBSD.org">
newton@FreeBSD.org">
n_hibma@FreeBSD.org">
nik@FreeBSD.org">
non@FreeBSD.org">
nsayer@FreeBSD.org">
nsj@FreeBSD.org">
nsouch@FreeBSD.org">
nyan@FreeBSD.org">
obrien@FreeBSD.org">
okazaki@FreeBSD.org">
olah@FreeBSD.org">
olgeni@FreeBSD.org">
onoe@FreeBSD.org">
opsys@open-systems.net">
orion@FreeBSD.org">
patrick@FreeBSD.org">
paul@FreeBSD.org">
pb@fasterix.freenix.org">
pds@FreeBSD.org">
peter@FreeBSD.org">
phantom@FreeBSD.org">
phk@FreeBSD.org">
pho@FreeBSD.org">
piero@strider.inet.it">
pirzyk@FreeBSD.org">
pjchilds@imforei.apana.org.au">
proven@FreeBSD.org">
ps@FreeBSD.org">
pst@FreeBSD.org">
reg@FreeBSD.org">
rgrimes@FreeBSD.org">
rhuff@cybercom.net">
ricardag@ag.com.br">
rich@FreeBSD.org">
rnordier@FreeBSD.org">
roam@FreeBSD.org">
roberto@FreeBSD.org">
rse@FreeBSD.org">
ru@FreeBSD.org">
rv@FreeBSD.org">
rvb@FreeBSD.org">
rwatson@FreeBSD.org">
sada@FreeBSD.org">
sanpei@FreeBSD.org">
schweikh@FreeBSD.org">
scottl@FreeBSD.org">
scrappy@FreeBSD.org">
se@FreeBSD.org">
sef@FreeBSD.org">
semenu@FreeBSD.org">
seth.kingsley@windriver.com">
sf@FreeBSD.org">
shafeeq@FreeBSD.org">
sheldonh@FreeBSD.org">
shiba@FreeBSD.org">
shige@FreeBSD.org">
shin@FreeBSD.org">
silby@FreeBSD.org">
simokawa@FreeBSD.org">
smace@FreeBSD.org">
smpatel@FreeBSD.org">
sobomax@FreeBSD.org">
sos@FreeBSD.org">
adam@whizkidtech.net">
stark@FreeBSD.org">
stb@FreeBSD.org">
steve@FreeBSD.org">
sumikawa@FreeBSD.org">
swallace@FreeBSD.org">
tanimura@FreeBSD.org">
taoka@FreeBSD.org">
takawata@FreeBSD.org">
tedm@FreeBSD.org">
tegge@FreeBSD.org">
tg@FreeBSD.org">
thepish@FreeBSD.org">
tmm@FreeBSD.org">
tobez@FreeBSD.org">
tom@FreeBSD.org">
tomsoft@FreeBSD.org">
torstenb@FreeBSD.org">
toshi@FreeBSD.org">
trevor@FreeBSD.org">
truckman@FreeBSD.org">
tshiozak@FreeBSD.org">
uch@FreeBSD.org">
ue@FreeBSD.org">
ugen@FreeBSD.org">
uhclem@FreeBSD.org">
ulf@FreeBSD.org">
ume@FreeBSD.org">
unfurl@FreeBSD.org">
vanilla@FreeBSD.org">
wes@FreeBSD.org">
whiteside@acm.org">
wilko@FreeBSD.org">
will@FreeBSD.org">
wjv@FreeBSD.org">
wlloyd@mpd.ca">
wollman@FreeBSD.org">
wosch@FreeBSD.org">
wpaul@FreeBSD.org">
wsanchez@FreeBSD.org">
wylie@osd.bsdi.com">
yar@FreeBSD.org">
yokota@FreeBSD.org">
diff --git a/en_US.ISO8859-1/books/handbook/basics/chapter.sgml b/en_US.ISO8859-1/books/handbook/basics/chapter.sgml
index f3c40965e8..264b35d9a0 100644
--- a/en_US.ISO8859-1/books/handbook/basics/chapter.sgml
+++ b/en_US.ISO8859-1/books/handbook/basics/chapter.sgml
@@ -1,573 +1,572 @@
Unix BasicsSynopsisbasics
- Rewritten by Chris Shumway
- cshumway@osd.bsdi.com, 10 Mar 2000.
+ Rewritten by &a.cshumway;, 10 Mar 2000.The following chapter will cover the basic commands and
functionality of the FreeBSD operating system. If you are new to
FreeBSD, you will definitely want to read through this chapter before
asking for help.PermissionsUNIXFreeBSD, having its history rooted in BSD UNIX, has its
fundamentals based on several key UNIX concepts. The first, and
most pronounced, is that FreeBSD is a multi-user operating system.
The system can handle several users all working simultaneously on
completely unrelated tasks. The system is responsible for properly
sharing and managing requests for hardware devices, peripherals,
memory, and CPU time evenly to each user.Because the system is capable of supporting multiple users,
everything the system manages has a set of permissions governing who
can read, write, and execute the resource. These permissions are
stored as two octets broken into three pieces, one for the owner of
the file, one for the group that the file belongs to, and one for
everyone else. This numerical representation works like
this:permissionsfilespermissionsValuePermissionDirectory Listing0No read, no write, no execute---1No read, no write, execute--x2No read, write, no execute-w-3No read, write, execute-wx4Read, no write, no executer--5Read, no write, executer-x6Read, write, no executerw-7Read, write, executerwxlsdirectoriesFor the long directory listing by ls -l, a
column will show a file's permissions for the owner, group, and
everyone else. Here's how it is broken up:-rw-r--r--The first character, from left to right, is a special character
that tells if this is a regular file, a directory, a special
character or block device, a socket, or any other special
pseudo-file device. The next three characters, designated as
rw- gives the permissions for the owner of the
file. The next three characters, r-- gives the
permissions for the group that the file belongs to. The final three
characters, r--, gives the permissions for the
rest of the world. A dash means that the permission is turned off.
In the case of this file, the permissions are set so the owner can
read and write to the file, the group can read the file, and the
rest of the world can only read the file. According to the table
above, the permissions for this file would be
644, where each digit represents the three parts
of the file's permission.This is all well and good, but how does the system control
permissions on devices? FreeBSD actually treats most hardware
devices as a file that programs can open, read, and write data to
just like any other file. These special device files are stored on
the /dev directory.Directories are also treated as files. They have read, write,
and execute permissions. The executable bit for a directory has a
slightly different meaning than that of files. When a directory is
marked executable, it means it can be searched into, for example, a
directory listing can be done in that directory.There are more to permissions, but they are primarily used in
special circumstances such as setuid binaries and sticky
directories. If you want more information on file permissions and
how to set them, be sure to look at the &man.chmod.1; man
page.Directory Structuresdirectory hierarchySince FreeBSD uses its file systems to determine many
fundamental system operations, the hierarchy of the file system is
extremely important. Due to the fact that the &man.hier.7; man page
provides a complete description of the directory structure, it will
not be duplicated here. Please read &man.hier.7; for more
information.Of significant importance is the root of all directories, the /
directory. This directory is the first directory mounted at boot
time and it contains the base system necessary at boot time. The
root directory also contains mount points for every other file
system that you want to mount.A mount point is a directory where additional file systems can
be grafted onto the root file system. Standard mount points include
/usr, /var,
/mnt, and /cdrom. These
directories are usually referenced to entries in the file
/etc/fstab. /etc/fstab is
a table of various file systems and mount points for reference by the
system. Most of the file systems in /etc/fstab
are mounted automatically at boot time from the script &man.rc.8;
unless they contain the option. Consult the
&man.fstab.5; manual page for more information on the format of the
/etc/fstab file and the options it
contains.Shellsshellscommand-lineIn FreeBSD, a lot of everyday work is done in a command line
interface called a shell. A shell's main job is to take commands
from the input channel and execute them. A lot of shells also have
built in functions to help everyday tasks such a file management,
file globing, command line editing, command macros, and environment
variables. FreeBSD comes with a set of shells, such as sh, the
Bourne Shell, and csh, the C-shell. Many other shells are available
from the FreeBSD Ports Collection that have much more power, such as
tcsh and bash.Which shell do you use? It is really a matter of taste. If you
are a C programmer you might feel more comfortable with a C-like shell
such as tcsh. If you've come from Linux or are new to a UNIX
command line interface you might try bash. The point is that each
shell has unique properties that may or may not work with your
preferred working environment, and that you have a choice of what
shell to use.One common feature in a shell is file-name completion. Given
the typing of the first few letters of a command or filename, you
can usually have the shell automatically complete the rest of the
command or filename by hitting the TAB key on the keyboard. Here is
an example. Suppose you have two files called
foobar and foo.bar. You
want to delete foo.bar. So what you would type
on the keyboard is: rm fo[TAB].[TAB].The shell would print out rm
foo[BEEP].bar.The [BEEP] is the console bell, which is the shell telling me it
was unable to totally complete the filename because there is more
than one match. Both foobar and
foo.bar start with fo, but
it was able to complete to foo. If you type in
., then hit TAB again, the shell would be able to
fill in the rest of the filename for you.environment variablesAnother function of the shell is environment variables.
Environment variables are a variable key pair stored in the shell's
environment space. This space can be read by any program invoked by
the shell, and thus contains a lot of program configuration. Here
is a list of common environment variables and what they mean:enviornment variablesVariableDescriptionUSERCurrent logged in user's name.PATHColon separated list of directories to search for
binaries.DISPLAYNetwork name of the X11 display to connect to, if
available.SHELLThe current shell.TERMThe name of the user's terminal. Used to determine the
capabilities of the terminal.TERMCAPDatabase entry of the terminal escape codes to perform
various terminal functions.OSTYPEType of operating system. E.g., FreeBSD.MACHTYPEThe CPU architecture that the system is running
on.EDITORThe user's preferred text editor.PAGERThe user's preferred text pager.MANPATHColon separated list of directories to search for
manual pages.Bourne shellsTo view or set an environment variable differs somewhat from
shell to shell. For example, in the C-Style shells such as tcsh
and csh, you would use setenv to set and view
environment variables. Under Bourne shells such as sh and bash, you
would use set and export to
view and set your current environment variables. For example, to
set or modify the EDITOR environment variable, under
csh or tcsh a command like this would set EDITOR to
/usr/local/bin/emacs:&prompt.user; setenv EDITOR /usr/local/bin/emacsUnder Bourne shells:&prompt.user; export EDITOR="/usr/local/bin/emacs"You can also make most shells expand the environment variable by
placing a $ character in front of it on the
command line. For example, echo $TERM would
print out whatever $TERM is set to, because the shell
expands $TERM and passes it on to echo.Shells treat a lot of special characters, called meta-characters
as special representations of data. The most common one is the
* character, which represents any number of
characters in a filename. These special meta-characters can be used
to do file name globing. For example, typing in
echo * is almost the same as typing in
ls because the shell takes all the files that
match * and puts them on the command line for
echo to see.To prevent the shell from interpreting these special characters,
they can be escaped from the shell by putting a backslash
(\) character in front of them. echo
$TERM prints whatever your terminal is set to.
echo \$TERM prints $TERM as
is.Changing your shellThe easiest way to change your shell is to use the
chsh command. Running chsh will
place you into the editor that is in your EDITOR
environment variable; if it is not set, you will be placed in
vi. Change the Shell: line
accordingly.You can also give chsh the
option; this will set your shell for you,
without requiring you to enter an editor.
For example, if you wanted to
change your shell to bash, the following should do the
trick:&prompt.user; chsh -s /usr/local/bin/bashRunning chsh with no parameters and editing
the shell from there would work also.The shell that you wish to use must be
present in the /etc/shells file. If you
have installed a shell from the ports
collection, then this should have been done for you
already. If you installed the shell by hand, you must do
this.For example, if you installed bash by hand
and placed it into /usr/local/bin, you would
want to:&prompt.root; echo "/usr/local/bin/bash" >> /etc/shellsThen rerun chsh.Text Editorstext editorseditorsA lot of configuration in FreeBSD is done by editing a text
file. Because of this, it would be a good idea to become familiar
with a text editor. FreeBSD comes with a few as part of the base
system, and many more are available in the ports collection.eeThe easiest and simplest editor to learn is an editor called
ee, which stands for easy editor. To
start ee, one would type at the command
line ee filename where
filename is the name of the file to be edited.
For example, to edit /etc/rc.conf, type in
ee /etc/rc.conf. Once inside of ee, all of the
commands for manipulating the editor's functions are listed at the
top of the display. The caret ^ character means
the control key on the keyboard, so ^e expands to pressing the
control key plus the letter e. To leave
ee, hit the escape key, then choose leave
editor. The editor will prompt you to save any changes if the file
has been modified.vieditorsviemacseditorsemacsFreeBSD also comes with more powerful text editors such as
vi as part of the base system, and
emacs and vim
as part of the FreeBSD ports collection. These editors offer much
more functionality and power at the expense of being a little more
complicated to learn. However if you plan on doing a lot of text
editing, learning a more powerful editor such as
vim or emacs
will save you much more time in the long run.For More Information...Manual pagesman pagesThe most comprehensive documentation on FreeBSD is in the form
of man pages. Nearly every program on the system comes with a
short reference manual explaining the basic operation and various
arguments. These manuals can be viewed with the man command. Use
of the man command is simple:&prompt.user; man commandcommand is the name of the command you
wish to learn about. For example, to learn more about
ls command type:&prompt.user; man lsThe online manual is divided up into numbered sections:User commands.System calls and error numbers.Functions in the C libraries.Device drivers.File formats.Games and other diversions.Miscellaneous information.System maintenance and operation commands.Kernel developers.In some cases, the same topic may appear in more than one
section of the online manual. For example, there is a chmod user
command and a chmod() system call. In this
case, you can tell the man command which one you want by
specifying the section:&prompt.user; man 1 chmodThis will display the manual page for the user command
chmod. References to a particular section of
the online manual are traditionally placed in parenthesis in
written documentation, so &man.chmod.1; refers to the
chmod user command and &man.chmod.2; refers to
the system call.This is fine if you know the name of the command and simply
wish to know how to use it, but what if you cannot recall the
command name? You can use man to search for keywords in the
command descriptions by using the
switch:&prompt.user; man -k mailWith this command you will be presented with a list of
commands that have the keyword mail in their
descriptions. This is actually functionally equivalent to using
the apropos command.So, you are looking at all those fancy commands in
/usr/bin but do not have the faintest idea
what most of them actually do? Simply do:&prompt.user; cd /usr/bin
&prompt.user; man -f *or&prompt.user; cd /usr/bin
&prompt.user; whatis *which does the same thing.GNU Info FilesFree Software FoundationFreeBSD includes many applications and utilities produced by
the Free Software Foundation (FSF). In addition to man pages,
these programs come with more extensive hypertext documents called
info files which can be viewed with the
info command or, if you installed
emacs, the info mode of
emacs.To use the &man.info.1; command, simply type:&prompt.user; infoFor a brief introduction, type h. For a
quick command reference, type ?.
diff --git a/en_US.ISO8859-1/books/handbook/contrib/chapter.sgml b/en_US.ISO8859-1/books/handbook/contrib/chapter.sgml
index 59dad4639a..830cfb1c6e 100644
--- a/en_US.ISO8859-1/books/handbook/contrib/chapter.sgml
+++ b/en_US.ISO8859-1/books/handbook/contrib/chapter.sgml
@@ -1,6311 +1,6315 @@
Contributing to FreeBSDContributed by &a.jkh;.So you want to contribute something to FreeBSD? That is great! We can
always use the help, and FreeBSD is one of those systems that
relies on the contributions of its user base in order
to survive. Your contributions are not only appreciated, they are vital
to FreeBSD's continued growth!Contrary to what some people might also have you believe, you do not
need to be a hot-shot programmer or a close personal friend of the FreeBSD
core team in order to have your contributions accepted. The FreeBSD
Project's development is done by a large and growing number of
international contributors whose ages and areas of technical expertise
vary greatly, and there is always more work to be done than there are
people available to do it.Since the FreeBSD project is responsible for an entire operating
system environment (and its installation) rather than just a kernel or a
few scattered utilities, our TODO list also spans a
very wide range of tasks, from documentation, beta testing and
presentation to highly specialized types of kernel development. No matter
what your skill level, there is almost certainly something you can do to
help the project!Commercial entities engaged in FreeBSD-related enterprises are also
encouraged to contact us. Need a special extension to make your product
work? You will find us receptive to your requests, given that they are not
too outlandish. Working on a value-added product? Please let us know! We
may be able to work cooperatively on some aspect of it. The free software
world is challenging a lot of existing assumptions about how software is
developed, sold, and maintained throughout its life cycle, and we urge you
to at least give it a second look.What is NeededThe following list of tasks and sub-projects represents something of
an amalgam of the various core team TODO lists and
user requests we have collected over the last couple of months. Where
possible, tasks have been ranked by degree of urgency. If you are
interested in working on one of the tasks you see here, send mail to the
coordinator listed by clicking on their names. If no coordinator has
been appointed, maybe you would like to volunteer?High priority tasksThe following tasks are considered to be urgent, usually because
they represent something that is badly broken or sorely needed:3-stage boot issues. Overall coordination: &a.hackers;Do WinNT compatible drive tagging so that the 3rd stage
can provide an accurate mapping of BIOS geometries for
disks.Filesystem problems. Overall coordination: &a.fs;Clean up and document the nullfs filesystem code.
Coordinator: &a.eivind;Fix the union file system. Coordinator: &a.dg;Implement Int13 vm86 disk driver. Coordinator:
&a.hackers;New bus architecture. Coordinator: &a.newbus;Port existing ISA drivers to new architecture.Move all interrupt-management code to appropriate parts of
the bus drivers.Port PCI subsystem to new architecture. Coordinator:
&a.dfr;Figure out the right way to handle removable devices and
then use that as a substrate on which PC-Card and CardBus
support can be implemented.Resolve the probe/attach priority issue once and for
all.Move any remaining buses over to the new
architecture.Kernel issues. Overall coordination: &a.hackers;Add more pro-active security infrastructure. Overall
coordination: &a.security;Build something like Tripwire(TM) into the kernel, with a
remote and local part. There are a number of cryptographic
issues to getting this right; contact the coordinator for
details. Coordinator: &a.eivind;Make the entire kernel use suser()
instead of comparing to 0. It is presently using about half
of each. Coordinator: &a.eivind;Split securelevels into different parts, to allow an
administrator to throw away those privileges he can throw
away. Setting the overall securelevel needs to have the same
effect as now, obviously. Coordinator: &a.eivind;Make it possible to upload a list of allowed
programs to BPF, and then block BPF from accepting other
programs. This would allow BPF to be used e.g. for DHCP,
without allowing an attacker to start snooping the local
network.Update the security checker script. We should at least
grab all the checks from the other BSD derivatives, and add
checks that a system with securelevel increased also have
reasonable flags on the relevant parts. Coordinator:
&a.eivind;Add authorization infrastructure to the kernel, to allow
different authorization policies. Part of this could be done
by modifying suser(). Coordinator:
&a.eivind;Add code to the NFS layer so that you cannot
chdir("..") out of an NFS partition. E.g.,
/usr is a UFS partition with
/usr/src NFS exported. Now it is
possible to use the NFS filehandle for
/usr/src to get access to
/usr.Medium priority tasksThe following tasks need to be done, but not with any particular
urgency:Full KLD based driver support/Configuration Manager.Write a configuration manager (in the 3rd stage boot?)
that probes your hardware in a sane manner, keeps only the
KLDs required for your hardware, etc.PCMCIA/PCCARD. Coordinators: &a.msmith; and &a.imp;Documentation!Reliable operation of the pcic driver (needs
testing).Recognizer and handler for sio.c
(mostly done).Recognizer and handler for ed.c
(mostly done).Recognizer and handler for ep.c
(mostly done).User-mode recognizer and handler (partially done).Advanced Power Management. Coordinators: &a.msmith; and
&a.phk;APM sub-driver (mostly done).IDE/ATA disk sub-driver (partially done).syscons/pcvt sub-driver.Integration with the PCMCIA/PCCARD drivers
(suspend/resume).Low priority tasksThe following tasks are purely cosmetic or represent such an
investment of work that it is not likely that anyone will get them
done anytime soon:The first N items are from Terry Lambert
terry@lambert.orgNetWare Server (protected mode ODI driver) loader and
sub-services to allow the use of ODI card drivers supplied with
network cards. The same thing for NDIS drivers and NetWare SCSI
drivers.An "upgrade system" option that works on Linux boxes instead
of just previous rev FreeBSD boxes.Symmetric Multiprocessing with kernel preemption (requires
kernel preemption).A concerted effort at support for portable computers. This is
somewhat handled by changing PCMCIA bridging rules and power
management event handling. But there are things like detecting
internal v.s.. external display and picking a different screen
resolution based on that fact, not spinning down the disk if the
machine is in dock, and allowing dock-based cards to disappear
without affecting the machines ability to boot (same issue for
PCMCIA).Smaller tasksMost of the tasks listed in the previous sections require either a
considerable investment of time or an in-depth knowledge of the
FreeBSD kernel (or both). However, there are also many useful tasks
which are suitable for "weekend hackers", or people without
programming skills.If you run FreeBSD-current and have a good Internet
connection, there is a machine current.FreeBSD.org which builds a full
release once a day — every now and again, try and install
the latest release from it and report any failures in the
process.Read the freebsd-bugs mailing list. There might be a
problem you can comment constructively on or with patches you
can test. Or you could even try to fix one of the problems
yourself.Read through the FAQ and Handbook periodically. If anything
is badly explained, out of date or even just completely wrong, let
us know. Even better, send us a fix (SGML is not difficult to
learn, but there is no objection to ASCII submissions).Help translate FreeBSD documentation into your native language
(if not already available) — just send an email to &a.doc;
asking if anyone is working on it. Note that you are not
committing yourself to translating every single FreeBSD document
by doing this — in fact, the documentation most in need of
translation is the installation instructions.Read the freebsd-questions mailing list and &ng.misc
occasionally (or even regularly). It can be very satisfying to
share your expertise and help people solve their problems;
sometimes you may even learn something new yourself! These forums
can also be a source of ideas for things to work on.If you know of any bug fixes which have been successfully
applied to -current but have not been merged into -stable after a
decent interval (normally a couple of weeks), send the committer a
polite reminder.Move contributed software to src/contrib
in the source tree.Make sure code in src/contrib is up to
date.Build the source tree (or just part of it) with extra warnings
enabled and clean up the warnings.Fix warnings for ports which do deprecated things like using
gets() or including malloc.h.If you have contributed any ports, send your patches back to
the original author (this will make your life easier when they
bring out the next version)Suggest further tasks for this list!Work through the PR databaseThe FreeBSD PR
list shows all the current active problem reports and
requests for enhancement that have been submitted by FreeBSD users.
Look through the open PRs, and see if anything there takes your
interest. Some of these might be very simple tasks, that just need an
extra pair of eyes to look over them and confirm that the fix in the
PR is a good one. Others might be much more complex.Start with the PRs that have not been assigned to anyone else, but
if one them is assigned to someone else, but it looks like something
you can handle, e-mail the person it is assigned to and ask if you can
work on it—they might already have a patch ready to be tested,
or further ideas that you can discuss with them.How to ContributeContributions to the system generally fall into one or more of the
following 6 categories:Bug reports and general commentaryAn idea or suggestion of general technical
interest should be mailed to the &a.hackers;. Likewise, people with
an interest in such things (and a tolerance for a
high volume of mail!) may subscribe to the
hackers mailing list by sending mail to &a.majordomo;. See mailing lists for more information
about this and other mailing lists.If you find a bug or are submitting a specific change, please
report it using the &man.send-pr.1; program or its WEB-based
equivalent. Try to fill-in each field of the bug report.
Unless they exceed 65KB, include any patches directly in the report.
When including patches, do not use cut-and-paste
because cut-and-paste turns tabs into spaces and makes them unusable.
Consider compressing patches and using &man.uuencode.1; if they exceed
20KB. Upload very large submissions to ftp.FreeBSD.org:/pub/FreeBSD/incoming/.After filing a report, you should receive confirmation along with
a tracking number. Keep this tracking number so that you can update
us with details about the problem by sending mail to
bug-followup@FreeBSD.org. Use the number as the
message subject, e.g. "Re: kern/3377". Additional
information for any bug report should be submitted this way.If you do not receive confirmation in a timely fashion (3 days to
a week, depending on your email connection) or are, for some reason,
unable to use the &man.send-pr.1; command, then you may ask
someone to file it for you by sending mail to the &a.bugs;.Changes to the documentationChanges to the documentation are overseen by the &a.doc;. Send
submissions and changes (even small ones are welcome!) using
send-pr as described in Bug Reports and General
Commentary.Changes to existing source codeAn addition or change to the existing source code is a somewhat
trickier affair and depends a lot on how far out of date you are with
the current state of the core FreeBSD development. There is a special
on-going release of FreeBSD known as FreeBSD-current
which is made available in a variety of ways for the convenience of
developers working actively on the system. See Staying current with FreeBSD for more
information about getting and using FreeBSD-current.Working from older sources unfortunately means that your changes
may sometimes be too obsolete or too divergent for easy re-integration
into FreeBSD. Chances of this can be minimized somewhat by
subscribing to the &a.announce; and the &a.current; lists, where
discussions on the current state of the system take place.Assuming that you can manage to secure fairly up-to-date sources
to base your changes on, the next step is to produce a set of diffs to
send to the FreeBSD maintainers. This is done with the &man.diff.1;
command, with the context diff form
being preferred. For example:&prompt.user; diff -c oldfile newfile
or
&prompt.user; diff -c -r olddir newdir
would generate such a set of context diffs for the given source file
or directory hierarchy. See the man page for &man.diff.1; for more
details.Once you have a set of diffs (which you may test with the
&man.patch.1; command), you should submit them for inclusion with
FreeBSD. Use the &man.send-pr.1; program as described in Bug Reports and General Commentary.
Do not just send the diffs to the &a.hackers; or
they will get lost! We greatly appreciate your submission (this is a
volunteer project!); because we are busy, we may not be able to
address it immediately, but it will remain in the pr database until we
do.If you feel it appropriate (e.g. you have added, deleted, or
renamed files), bundle your changes into a tar file
and run the &man.uuencode.1; program on it. Shar archives are also
welcome.If your change is of a potentially sensitive nature, e.g. you are
unsure of copyright issues governing its further distribution or you
are simply not ready to release it without a tighter review first,
then you should send it to &a.core; directly rather than submitting it
with &man.send-pr.1;. The core mailing list reaches a much smaller
group of people who do much of the day-to-day work on FreeBSD. Note
that this group is also very busy and so you
should only send mail to them where it is truly necessary.Please refer to man 9 intro and man 9
style for some information on coding style. We would
appreciate it if you were at least aware of this information before
submitting code.New code or major value-added packagesIn the case of a significant contribution of a large body
work, or the addition of an important new feature to FreeBSD, it
becomes almost always necessary to either send changes as uuencoded
tar files or upload them to a web or FTP site for other people to
access. If you do not have access to a web or FTP site, ask on an
appropriate FreeBSD mailing list for someone to host the changes for
you.When working with large amounts of code, the touchy subject of
copyrights also invariably comes up. Acceptable copyrights for code
included in FreeBSD are:The BSD copyright. This copyright is most preferred due to
its no strings attached nature and general
attractiveness to commercial enterprises. Far from discouraging
such commercial use, the FreeBSD Project actively encourages such
participation by commercial interests who might eventually be
inclined to invest something of their own into FreeBSD.The GNU Public License, or GPL. This license is
not quite as popular with us due to the amount of extra effort
demanded of anyone using the code for commercial purposes, but
given the sheer quantity of GPL'd code we currently require
(compiler, assembler, text formatter, etc) it would be silly to
refuse additional contributions under this license. Code under
the GPL also goes into a different part of the tree, that being
/sys/gnu or
/usr/src/gnu, and is therefore easily
identifiable to anyone for whom the GPL presents a problem.Contributions coming under any other type of copyright must be
carefully reviewed before their inclusion into FreeBSD will be
considered. Contributions for which particularly restrictive
commercial copyrights apply are generally rejected, though the authors
are always encouraged to make such changes available through their own
channels.To place a BSD-style copyright on your work, include
the following text at the very beginning of every source code file you
wish to protect, replacing the text between the %%
with the appropriate information.Copyright (c) %%proper_years_here%%
%%your_name_here%%, %%your_state%% %%your_zip%%.
All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
1. Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer as
the first lines of this file unmodified.
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
THIS SOFTWARE IS PROVIDED BY %%your_name_here%% ``AS IS'' AND ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
IN NO EVENT SHALL %%your_name_here%% BE LIABLE FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
$Id$For your convenience, a copy of this text can be found in
/usr/share/examples/etc/bsd-style-copyright.Money, Hardware or Internet accessWe are always very happy to accept donations to further the cause
of the FreeBSD Project and, in a volunteer effort like ours, a little
can go a long way! Donations of hardware are also very important to
expanding our list of supported peripherals since we generally lack
the funds to buy such items ourselves.Donating fundsEmpty, pending information from the FreeBSD Foundation.Donating hardwareDonations of hardware in any of the 3 following categories are
also gladly accepted by the FreeBSD Project:General purpose hardware such as disk drives, memory or
complete systems should be sent to the FreeBSD, Inc. address
listed in the donating funds
section.Hardware for which ongoing compliance testing is desired.
We are currently trying to put together a testing lab of all
components that FreeBSD supports so that proper regression
testing can be done with each new release. We are still lacking
many important pieces (network cards, motherboards, etc) and if
you would like to make such a donation, please contact &a.dg;
for information on which items are still required.Hardware currently unsupported by FreeBSD for which you
would like to see such support added. Please contact the
&a.core; before sending such items as we will need to find a
developer willing to take on the task before we can accept
delivery of new hardware.Donating Internet accessWe can always use new mirror sites for FTP, WWW or
cvsup. If you would like to be such a mirror,
please contact the FreeBSD project administrators
hubs@FreeBSD.org for more information.Donors GalleryThe FreeBSD Project is indebted to the following donors and would
like to publicly thank them here!Contributors to the central server
project:The following individuals and businesses made it possible for
the FreeBSD Project to build a new central server machine to
eventually replace freefall.FreeBSD.org
by donating the following items:&a.mbarkah and his employer,
Hemisphere Online, donated a Pentium Pro
(P6) 200Mhz CPUASA
Computers donated a Tyan 1662
motherboard.Joe McGuckin joe@via.net of ViaNet Communications donated
a Kingston ethernet controller.Jack O'Neill jack@diamond.xtalwind.net
donated an NCR 53C875 SCSI controller
card.Ulf Zimmermann ulf@Alameda.net of Alameda Networks donated
128MB of memory, a 4 Gb disk
drive and the case.Direct funding:The following individuals and businesses have generously
contributed direct funding to the project:Annelise Anderson
ANDRSN@HOOVER.STANFORD.EDU&a.dillonBlue Mountain
ArtsEpilogue Technology
Corporation&a.sefGlobal Technology
Associates, IncDon Scott WildeGianmarco Giovannelli
gmarco@masternet.itJosef C. Grosch joeg@truenorth.orgRobert T. Morris&a.chuckrKenneth P. Stox ken@stox.sa.enteract.com of
Imaginary Landscape,
LLC.Dmitry S. Kohmanyuk dk@dog.farm.orgLaser5 of Japan
(a portion of the profits from sales of their various FreeBSD
CDROMs).Fuki Shuppan
Publishing Co. donated a portion of their profits from
Hajimete no FreeBSD (FreeBSD, Getting
started) to the FreeBSD and XFree86 projects.ASCII Corp.
donated a portion of their profits from several FreeBSD-related
books to the FreeBSD project.Yokogawa Electric
Corp has generously donated significant funding to the
FreeBSD project.BuffNETPacific
SolutionsSiemens AG
via Andre Albsmeier
andre.albsmeier@mchp.siemens.deChris Silva ras@interaccess.comHardware contributors:The following individuals and businesses have generously
contributed hardware for testing and device driver
development/support:BSDi for providing the Pentium P5-90 and
486/DX2-66 EISA/VL systems that are being used for our
development work, to say nothing of the network access and other
donations of hardware resources.TRW Financial Systems, Inc. provided 130 PCs, three 68 GB
file servers, twelve Ethernets, two routers and an ATM switch for
debugging the diskless code.Dermot McDonnell donated the Toshiba XM3401B CDROM drive
currently used in freefall.&a.chuck; contributed his floppy tape streamer for
experimental work.Larry Altneu larry@ALR.COM, and &a.wilko;,
provided Wangtek and Archive QIC-02 tape drives in order to
improve the wt driver.Ernst Winter ewinter@lobo.muc.de contributed
a 2.88 MB floppy drive to the project. This will hopefully
increase the pressure for rewriting the floppy disk driver.
;-)Tekram
Technologies sent one each of their DC-390, DC-390U
and DC-390F FAST and ULTRA SCSI host adapter cards for
regression testing of the NCR and AMD drivers with their cards.
They are also to be applauded for making driver sources for free
operating systems available from their FTP server ftp://ftp.tekram.com/scsi/FreeBSD/.Larry M. Augustin contributed not only a
Symbios Sym8751S SCSI card, but also a set of data books,
including one about the forthcoming Sym53c895 chip with Ultra-2
and LVD support, and the latest programming manual with
information on how to safely use the advanced features of the
latest Symbios SCSI chips. Thanks a lot!Christoph Kukulies kuku@FreeBSD.org donated
an FX120 12 speed Mitsumi CDROM drive for IDE CDROM driver
development.Special contributors:BSDi (formerly Walnut Creek CDROM)
has donated almost more than we can say (see the history document for more details).
In particular, we would like to thank them for the original
hardware used for freefall.FreeBSD.org, our primary
development machine, and for thud.FreeBSD.org, a testing and build
box. We are also indebted to them for funding various
contributors over the years and providing us with unrestricted
use of their T1 connection to the Internet.The interface
business GmbH, Dresden has been patiently supporting
&a.joerg; who has often preferred FreeBSD work over paid work, and
used to fall back to their (quite expensive) EUnet Internet
connection whenever his private connection became too slow or
flaky to work with it...Berkeley Software Design,
Inc. has contributed their DOS emulator code to the
remaining BSD world, which is used in the
doscmd command.Core Team AlumniThe following people were members of the FreeBSD core team during
the periods indicated. We thank them for their past efforts in the
service of the FreeBSD project.In rough chronological order:&a.ache (1993 - 2000)&a.jmb (1993 - 2000)&a.bde (1992 - 2000)&a.gibbs (1993 - 2000)&a.rich (1994 - 2000)&a.phk (1992 - 2000)&a.gpalmer (1993 - 2000)&a.sos (1993 - 2000)&a.wollman (1993 - 2000)&a.joerg (1995 - 2000)&a.jdp (1997 - 2000)&a.guido (1995 - 1999)&a.dyson (1993 - 1998)&a.nate (1992 - 1996)&a.rgrimes (1992 - 1995)Andreas Schulz (1992 - 1995)&a.csgr (1993 - 1995)&a.paul (1992 - 1995)&a.smace (1993 - 1994)Andrew Moore (1993 - 1994)Christoph Robitschko (1993 - 1994)J. T. Conklin (1992 - 1993)Development Team AlumniThe following people were members of the FreeBSD development team
during the periods indicated. We thank them for their past efforts
in the service of the FreeBSD project.In rough chronological order:&a.tedm (???? - 2000)&a.karl (???? - 2000)&a.gclarkii (1993 - 2000)&a.jraynard (???? - 2000)&a.jgreco (???? - 1999)&a.ats (???? - 1999)Jamil Weatherby (1997 - 1999)meganm (???? - 1998)&a.dyson (???? - 1998)Amancio Hasty (1997 - 1998)Drew Derbyshire (1997 - 1998)Derived Software ContributorsThis software was originally derived from William F. Jolitz's 386BSD
release 0.1, though almost none of the original 386BSD specific code
remains. This software has been essentially re-implemented from the
4.4BSD-Lite release provided by the Computer Science Research Group
(CSRG) at the University of California, Berkeley and associated academic
contributors.There are also portions of NetBSD and OpenBSD that have been
integrated into FreeBSD as well, and we would therefore like to thank
all the contributors to NetBSD and OpenBSD for their work.Additional FreeBSD Contributors(in alphabetical order by first name):ABURAYA Ryushirou rewsirow@ff.iij4u.or.jpAMAGAI Yoshiji amagai@nue.orgAaron Bornstein aaronb@j51.comAaron Smith aaron@mutex.orgAchim Patzner ap@noses.comAda T Lim ada@bsd.orgAdam Baran badam@mw.mil.plAdam Glass glass@postgres.berkeley.eduAdam Herzog adam@herzogdesigns.comAdam McDougall mcdouga9@egr.msu.eduAdam Strohl troll@digitalspark.netAdoal Xu adoal@iname.comAdrian Colley aecolley@ois.ieAdrian Hall ahall@mirapoint.comAdrian Mariano adrian@cam.cornell.eduAdrian Steinmann ast@marabu.chAdrian T. Filipi-Martin
atf3r@agate.cs.virginia.eduAjit Thyagarajan unknownAkio Morita
amorita@meadow.scphys.kyoto-u.ac.jpAkira SAWADA unknownAkira Watanabe
akira@myaw.ei.meisei-u.ac.jpAkito Fujita fujita@zoo.ncl.omron.co.jpAlain Kalker
A.C.P.M.Kalker@student.utwente.nlAlan Bawden alan@curry.epilogue.comAlec Wolman wolman@cs.washington.eduAled Morris aledm@routers.co.ukAleksandr A Babaylov .@babolo.ruAlex G. Bulushev bag@demos.suAlex D. Chen
dhchen@Canvas.dorm7.nccu.edu.twAlex Le Heux alexlh@funk.orgAlex Kapranoff kappa@zombie.antar.bryansk.ruAlex Perel veers@disturbed.netAlex Semenyaka alex@rinet.ruAlex Varju varju@webct.comAlex Zepeda garbanzo@hooked.netAlexander B. Povolotsky tarkhil@mgt.msk.ruAlexander Gelfenbain mail@gelf.comAlexander Leidinger
netchild@wurzelausix.CS.Uni-SB.DEAlexandre Peixoto
alexandref@tcoip.com.brAlexandre Snarskii snar@paranoia.ruAlistair G. Crooks agc@uts.amdahl.comAllan Bowhill bowhill@bowhill.vservers.comAllan Saddi asaddi@philosophysw.comAllen Campbell allenc@verinet.comAmakawa Shuhei amakawa@hoh.t.u-tokyo.ac.jpAmancio Hasty hasty@star-gate.comAmir Farah amir@comtrol.comAmir Shalem amir@boom.org.ilAmy Baron amee@beer.orgThe Anarcat beaupran@iro.umontreal.caAnatoly A. Orehovsky tolik@mpeks.tomsk.suAnatoly Vorobey mellon@pobox.comAnders Andersson anders@codefactory.seAnders Nordby anders@fix.noAnders Thulin Anders.X.Thulin@telia.seAndras Olah olah@cs.utwente.nlAndre Albsmeier
Andre.Albsmeier@mchp.siemens.deAndre Goeree abgoeree@uwnet.nlAndre Oppermann andre@pipeline.chAndreas Haakh ah@alman.robin.deAndreas Kohout shanee@rabbit.augusta.deAndreas Lohr andreas@marvin.RoBIN.deAndreas Schulz unknownAndreas Wetzel mickey@deadline.snafu.deAndreas Wrede andreas@planix.comAndres Vega Garcia unknownAndrew Atrens atreand@statcan.caAndrew Boothman andrew@cream.orgAndrew Gillham gillham@andrews.eduAndrew Gordon andrew.gordon@net-tel.co.ukAndrew Herbert andrew@werple.apana.org.auAndrew J. Korty ajk@purdue.eduAndrew L. Moore alm@mclink.comAndrew L. Neporada andrew@chg.ruAndrew McRae amcrae@cisco.comAndrew Stevenson andrew@ugh.net.auAndrew Timonin tim@pool1.convey.ruAndrew V. Stesin stesin@elvisti.kiev.uaAndrew Webster awebster@dataradio.comAndrey Novikov andrey@novikov.comAndrey Simonenko simon@comsys.ntu-kpi.kiev.uaAndrey Tchoritch andy@venus.sympad.netAndy Farkas andyf@speednet.com.auAndy Valencia ajv@csd.mot.comAndy Whitcroft andy@sarc.city.ac.ukAngelo Turetta ATuretta@stylo.itAnthony C. Chavez magus@xmission.comAnthony Yee-Hang Chan yeehang@netcom.comAnton N. Bruesov antonz@library.ntu-kpi.kiev.uaAnton Voronin anton@urc.ac.ruAntti Kaipila anttik@iki.fiarci vega@sophia.inria.frAre Bryne are.bryne@communique.noAri Suutari ari@suutari.iki.fiArindum Mukerji rmukerji@execpc.comArjan de Vet devet@IAEhv.nlArne Henrik Juul arnej@Lise.Unit.NOArun Sharma adsharma@sharmas.dhs.orgArnaud S. Launay asl@launay.orgAsk Bjoern Hansen ask@valueclick.comAtsushi Furuta furuta@sra.co.jpAtsushi Murai amurai@spec.co.jpAtushi Sakauchi sakauchi@yamame.toBakul Shah bvs@bitblocks.comBarry Bierbauch pivrnec@vszbr.czBarry Lustig barry@ictv.comBen Hutchinson benhutch@xfiles.org.ukBen Jackson unknownBen Walter bwalter@itachi.swcp.comBenjamin Lewis bhlewis@gte.netBerend de Boer berend@pobox.comBernd Rosauer br@schiele-ct.deBill Kish kish@osf.orgBill Trost trost@cloud.rain.comBlaz Zupan blaz@amis.netBob Van Valzah Bob@whitebarn.comBob Wilcox bob@obiwan.uucpBob Willcox bob@luke.pmr.comBoris Staeblow balu@dva.in-berlin.deBoyd Faulkner faulkner@mpd.tandem.comBoyd R. Faulkner faulkner@asgard.bga.comBrad Chapman chapmanb@arches.uga.eduBrad Hendrickse bradh@uunet.co.zaBrad Karp karp@eecs.harvard.eduBradley Dunn bradley@dunn.orgBrad Jones brad@kazrak.comBrandon Fosdick bfoz@glue.umd.eduBrandon Gillespie brandon@roguetrader.com&a.wlloydBrent J. Nordquist bjn@visi.comBrett Lymn blymn@mulga.awadi.com.AUBrett Taylor
brett@peloton.runet.eduBrian Campbell brianc@pobox.comBrian Clapper bmc@willscreek.comBrian Cully shmit@kublai.comBrian Handy
handy@lambic.space.lockheed.comBrian Litzinger brian@MediaCity.comBrian McGovern bmcgover@cisco.comBrian Moore ziff@houdini.eecs.umich.eduBrian R. Haug haug@conterra.comBrian Tao taob@risc.orgBrion Moss brion@queeg.comBruce Albrecht bruce@zuhause.mn.orgBruce Gingery bgingery@gtcs.comBruce J. Keeler loodvrij@gridpoint.comBruce Murphy packrat@iinet.net.auBruce Walter walter@fortean.comCarey Jones mcj@acquiesce.orgCarl Fongheiser cmf@netins.netCarl Mascott cmascott@world.std.comCasper casper@acc.amCastor Fu castor@geocast.comChad David davidc@acns.ab.caChain Lee chain@110.netCharles Hannum mycroft@ai.mit.eduCharles Henrich henrich@msu.eduCharles Mott cmott@scientech.comCharles Owens owensc@enc.eduChet Ramey chet@odin.INS.CWRU.EduChia-liang Kao clkao@CirX.ORGChiharu Shibata chi@bd.mbn.or.jpChip Norkus unknownChris Csanady cc@tarsier.ca.sandia.govChris Dabrowski chris@vader.orgChris Dillon cdillon@wolves.k12.mo.usChris Shenton
cshenton@angst.it.hq.nasa.gov
+
+ &a.cshumway;
+
+
Chris Stenton jacs@gnome.co.ukChris Timmons skynyrd@opus.cts.cwu.eduChris Torek torek@ee.lbl.govChristian Gusenbauer
cg@fimp01.fim.uni-linz.ac.atChristian Haury Christian.Haury@sagem.frChristian Weisgerber
naddy@mips.inka.deChristoph P. Kukulies kuku@FreeBSD.orgChristoph Robitschko
chmr@edvz.tu-graz.ac.atChristoph Weber-Fahr
wefa@callcenter.systemhaus.netChristopher G. Demetriou
cgd@postgres.berkeley.eduChristopher N. Harrell cnh@ivmg.netChristopher Preston rbg@gayteenresource.orgChristopher T. Johnson
cjohnson@neunacht.netgsi.comChrisy Luke chrisy@flix.netChuck Hein chein@cisco.comCliff Rowley dozprompt@onsea.comColman Reilly careilly@tcd.ieConrad Sabatier conrads@home.comCoranth Gryphon gryphon@healer.comCornelis van der Laan
nils@guru.ims.uni-stuttgart.deCove Schneider cove@brazil.nbn.comCraig Leres leres@ee.lbl.govCraig Loomis unknownCraig Metz cmetz@inner.netCraig Spannring cts@internetcds.comCraig Struble cstruble@vt.eduCristian Ferretti cfs@riemann.mat.puc.clCurt Mayer curt@toad.comCy Schubert cschuber@uumail.gov.bc.caCyrille Lefevre clefevre@citeweb.netCyrus Rahman cr@jcmax.comDai Ishijima ishijima@tri.pref.osaka.jpDaisuke Watanabe NU7D-WTNB@asahi-net.or.jpDamian Hamill damian@cablenet.netDan Cross tenser@spitfire.ecsel.psu.eduDan Langille dan@freebsddiary.orgDan Lukes dan@obluda.czDan Nelson dnelson@emsphone.comDan Papasian bugg@bugg.strangled.netDan Piponi wmtop@tanelorn.demon.co.ukDan Walters hannibal@cyberstation.netDaniel Hagan
dhagan@cs.vt.eduDaniel O'Connor doconnor@gsoft.com.auDaniel Poirot poirot@aio.jsc.nasa.govDaniel Rock rock@cs.uni-sb.deDaniel W. McRobb dwm@caimis.comDanny Egen unknownDanny J. Zerkel dzerkel@phofarm.comDave Adkins adkin003@tc.umn.eduDave Andersen angio@aros.netDave Blizzard dblizzar@sprynet.comDave Bodenstab imdave@synet.netDave Burgess burgess@hrd769.brooks.af.milDave Chapeskie dchapes@ddm.on.caDave Cornejo dave@dogwood.comDave Edmondson davided@sco.comDave Glowacki dglo@ssec.wisc.eduDave Marquardt marquard@austin.ibm.comDave Tweten tweten@FreeBSD.orgDavid A. Adkins adkin003@tc.umn.eduDavid A. Bader dbader@eece.unm.eduDavid Borman dab@bsdi.comDavid Dawes dawes@XFree86.orgDavid Filo unknownDavid Holland dholland@eecs.harvard.eduDavid Holloway daveh@gwythaint.tamis.comDavid Horwitt dhorwitt@ucsd.eduDavid Hovemeyer daveho@infocom.comDavid Jones dej@qpoint.torfree.netDavid Kelly dkelly@tomcat1.tbe.comDavid Kulp dkulp@neomorphic.comDavid L. Nugent davidn@blaze.net.auDavid Leonard d@scry.dstc.edu.auDavid Muir Sharnoff muir@idiom.comDavid S. Miller davem@jenolan.rutgers.eduDavid Sugar dyfet@gnu.orgDavid Wolfskill dhw@whistle.comDean Gaudet dgaudet@arctic.orgDean Huxley dean@fsa.caDenis Fortin unknownDenis Shaposhnikov dsh@vlink.ruDennis Glatting
dennis.glatting@software-munitions.comDenton Gentry denny1@home.comder Mouse mouse@Collatz.McRCIM.McGill.EDUDerek Inksetter derek@saidev.comDI. Christian Gusenbauer
cg@scotty.edvz.uni-linz.ac.atDirk Keunecke dk@panda.rhein-main.deDirk Nehrling nerle@pdv.deDishanker Rajakulendren draj@oceanfree.netDmitry Khrustalev dima@xyzzy.machaon.ruDmitry Kohmanyuk dk@farm.orgDom Mitchell dom@myrddin.demon.co.ukDomas Mituzas midom@dammit.ltDominik Brettnacher domi@saargate.deDominik Rothert dr@domix.deDon Croyle croyle@gelemna.ft-wayne.in.usDonn Miller dmmiller@cvzoom.netDan Pelleg dpelleg+unison@cs.cmu.edu&a.whiteside;Don Morrison dmorrisn@u.washington.eduDon Yuniskis dgy@rtd.comDonald Maddox dmaddox@conterra.comDouglas Ambrisko ambrisko@whistle.comDouglas Carmichael dcarmich@mcs.comDouglas Crosher dtc@scrooge.ee.swin.oz.auDrew Derbyshire ahd@kew.comDustin Sallings dustin@spy.netEckart "Isegrim" Hofmann
Isegrim@Wunder-Nett.orgEd Gold
vegold01@starbase.spd.louisville.eduEd Hudson elh@p5.spnet.comEdward Chuang edwardc@firebird.org.twEdward Wang edward@edcom.comEdwin Groothus edwin@nwm.wan.philips.comEdwin Mons e@ik.nuEge Rekk aagero@aage.priv.noEiji-usagi-MATSUmoto usagi@clave.gr.jpEike Bernhardt eike.bernhardt@gmx.deELISA Font ProjectElmar Bartel
bartel@informatik.tu-muenchen.deEoin Lawless eoin@maths.tcd.ieEric A. Griff eagriff@global2000.netEric Blood eblood@cs.unr.eduEric D. Futch efutch@nyct.netEric J. Haug ejh@slustl.slu.eduEric J. Schwertfeger eric@cybernut.comEric L. Hernes erich@lodgenet.comEric P. Scott eps@sirius.comEric Sprinkle eric@ennovatenetworks.comErich Stefan Boleyn erich@uruk.orgErich Zigler erich@tacni.netErik H. Bakke erikhb@bgnett.noErik E. Rantapaa rantapaa@math.umn.eduErik H. Moe ehm@cris.comErnst de Haan ernst@heinz.jollem.comErnst Winter ewinter@lobo.muc.deEspen Skoglund esk@ira.uka.deEugene M. Kim astralblue@usa.netEugene Radchenko genie@qsar.chem.msu.suEugeny Kuzakov CoreDumped@coredumped.null.ruEvan Champion evanc@synapse.netFaried Nawaz fn@Hungry.COMFlemming Jacobsen fj@tfs.comFong-Ching Liaw fong@juniper.netFrancis M J Hsieh mjshieh@life.nthu.edu.twFrancisco Reyes fjrm@yahoo.comFrank Bartels knarf@camelot.deFrank Chen Hsiung Chan
frankch@waru.life.nthu.edu.twFrank Durda IV uhclem@nemesis.lonestar.orgFrank MacLachlan fpm@n2.netFrank Nobis fn@Radio-do.deFrank ten Wolde franky@pinewood.nlFrank van der Linden frank@fwi.uva.nlFrank Volf volf@oasis.IAEhv.nlFred Cawthorne fcawth@jjarray.umn.eduFred Gilham gilham@csl.sri.comFred Templin templin@erg.sri.comFrederick Earl Gray fgray@rice.eduFUJIMOTO Kensaku
fujimoto@oscar.elec.waseda.ac.jpFURUSAWA Kazuhisa
furusawa@com.cs.osakafu-u.ac.jp&a.stanislav;Gabor Kincses gabor@acm.orgGabor Zahemszky zgabor@CoDe.huGareth McCaughan gjm11@dpmms.cam.ac.ukGary A. Browning gab10@griffcd.amdahl.comGary Howland gary@hotlava.comGary J. garyj@rks32.pcs.dec.comGary Kline kline@thought.orgGaspar Chilingarov nightmar@lemming.acc.amGea-Suan Lin gsl@tpts4.seed.net.twGene Raytsin pal@paladin7.netGeoff Rehmet csgr@alpha.ru.ac.zaGeorg Wagner georg.wagner@ubs.comGianlorenzo Masini masini@uniroma3.itGianmarco Giovannelli
gmarco@giovannelli.itGil Kloepfer Jr. gil@limbic.ssdl.comGilad Rom rom_glsa@ein-hashofet.co.ilGiles Lean giles@nemeton.com.auGinga Kawaguti
ginga@amalthea.phys.s.u-tokyo.ac.jpGiorgos Keramidas keramida@ceid.upatras.grGlen Foster gfoster@gfoster.comGlenn Johnson gljohns@bellsouth.netGodmar Back gback@facility.cs.utah.eduGoran Hammarback goran@astro.uu.seGord Matzigkeit gord@enci.ucalgary.caGordon Greeff gvg@uunet.co.zaGraham Wheeler gram@cdsec.comGreg A. Woods woods@zeus.leitch.comGreg Ansley gja@ansley.comGreg Robinson greg@rosevale.com.auGreg Troxel gdt@ir.bbn.comGreg Ungerer gerg@stallion.oz.auGregory Bond gnb@itga.com.auGregory D. Moncreaff
moncrg@bt340707.res.ray.comGuy Harris guy@netapp.comGuy Helmer ghelmer@cs.iastate.eduHAMADA Naoki hamada@astec.co.jpHannu Savolainen hannu@voxware.pp.fiHans Huebner hans@artcom.deHans Petter Bieker zerium@webindex.noHans Zuidam hans@brandinnovators.comHarlan Stenn Harlan.Stenn@pfcs.comHarold Barker hbarker@dsms.comHarry Newton harry_newton@telinco.co.ukHavard Eidnes
Havard.Eidnes@runit.sintef.noHeikki Suonsivu hsu@cs.hut.fiHeiko W. Rupp unknownHelmut F. Wirth hfwirth@ping.atHenrik Vestergaard Draboel
hvd@terry.ping.dkHerb Peyerl hpeyerl@NetBSD.orgHideaki Ohmon ohmon@tom.sfc.keio.ac.jpHidekazu Kuroki hidekazu@cs.titech.ac.jpHideki Yamamoto hyama@acm.orgHideyuki Suzuki
hideyuki@sat.t.u-tokyo.ac.jpHirayama Issei iss@mail.wbs.ne.jpHiroaki Sakai sakai@miya.ee.kagu.sut.ac.jpHiroharu Tamaru tamaru@ap.t.u-tokyo.ac.jpHironori Ikura hikura@kaisei.orgHiroshi Nishikawa nis@pluto.dti.ne.jpHiroya Tsubakimoto unknownHolger Lamm holger@eit.uni-kl.deHolger Veit Holger.Veit@gmd.deHolm Tiffe holm@geophysik.tu-freiberg.deHONDA Yasuhiro
honda@kashio.info.mie-u.ac.jpHorance Chou
horance@freedom.ie.cycu.edu.twHorihiro Kumagai kuma@jp.FreeBSD.orgHOSOBUCHI Noriyuki hoso@buchi.tama.or.jpHOTARU-YA hotaru@tail.netHr.Ladavac lada@ws2301.gud.siemens.co.atHubert Feyrer hubertf@NetBSD.ORGHugh F. Mahon hugh@nsmdserv.cnd.hp.comHugh Mahon h_mahon@fc.hp.comHung-Chi Chu hcchu@r350.ee.ntu.edu.twIan Holland ianh@tortuga.com.auIan Struble ian@broken.netIan Vaudrey i.vaudrey@bigfoot.comIgor Khasilev igor@jabber.paco.odessa.uaIgor Roshchin str@giganda.komkon.orgIgor Serikov bt@turtle.pangeatech.comIgor Sviridov siac@ua.netIgor Vinokurov igor@zynaps.ruIkuo Nakagawa ikuo@isl.intec.co.jpIlia Chipitsine ilia@jane.cgu.chel.suIlya V. Komarov mur@lynx.ruIMAI Takeshi take-i@ceres.dti.ne.jpIMAMURA Tomoaki
tomoak-i@is.aist-nara.ac.jpItsuro Saito saito@miv.t.u-tokyo.ac.jpIWASHITA Yoji shuna@pop16.odn.ne.jpJ. Bryant jbryant@argus.flash.netJ. David Lowe lowe@saturn5.comJ. Han hjh@photino.comJ. Hawk jhawk@MIT.EDUJ.T. Conklin jtc@cygnus.comJack jack@zeus.xtalwind.netJacob Bohn Lorensen jacob@jblhome.ping.mkJagane D Sundar jagane@netcom.comJake Hamby jehamby@anobject.comJames Clark jjc@jclark.comJames D. Stewart jds@c4systm.comJames da Silva jds@cs.umd.eduJames Jegers jimj@miller.cs.uwm.eduJames Raynard
fhackers@jraynard.demon.co.ukJames T. Liu jtliu@phlebas.rockefeller.eduJamie Heckford jamie@jamiesdomain.co.ukJan Conard
charly@fachschaften.tu-muenchen.deJan Jungnickel Jan@Jungnickel.comJan Koum jkb@FreeBSD.orgJanick Taillandier
Janick.Taillandier@ratp.frJanusz Kokot janek@gaja.ipan.lublin.plJarle Greipsland jarle@idt.unit.noJason Garman init@risen.orgJason R. Mastaler
jason-freebsd@mastaler.comJason Thorpe thorpej@NetBSD.orgJason Wright jason@OpenBSD.orgJason Young
doogie@forbidden-donut.anet-stl.comJavier Martin Rueda jmrueda@diatel.upm.esJay Fenlason hack@datacube.comJay Krell jay.krell@cornell.eduJaye Mathisen mrcpu@cdsnet.netJeff Bartig jeffb@doit.wisc.eduJeff Brown jabrown@caida.orgJeff Forys jeff@forys.cranbury.nj.usJeff Kletsky Jeff@Wagsky.comJeff Palmer scorpio@drkshdw.orgJeffrey Evans evans@scnc.k12.mi.usJeffrey Wheat jeff@cetlink.netJeremy Allison jallison@whistle.comJeremy Chadwick yoshi@parodius.comJeremy Chatfield jdc@xinside.comJeremy Karlson karlj000@unbc.caJeremy Prior unknownJeremy Shaffner jeremy@external.orgJesse McConnell jesse@cylant.comJesse Rosenstock jmr@ugcs.caltech.eduJian-Da Li jdli@csie.nctu.edu.twJim Babb babb@FreeBSD.orgJim Binkley jrb@cs.pdx.eduJim Bloom bloom@acm.orgJim Carroll jim@carroll.comJim Flowers jflowers@ezo.netJim Leppek jleppek@harris.comJim Lowe james@cs.uwm.eduJim Mattson jmattson@sonic.netJim Mercer jim@komodo.reptiles.orgJim Sloan odinn@atlantabiker.netJim Wilson wilson@moria.cygnus.comJimbo Bahooli
griffin@blackhole.iceworld.orgJin Guojun jin@george.lbl.govJoachim Kuebart kuebart@mathematik.uni-ulm.deJoao Carlos Mendes Luis jonny@jonny.eng.brJochen Pohl jpo.drs@sni.deJoe "Marcus" Clarke marcus@marcuscom.comJoe Abley jabley@automagic.orgJoe Jih-Shian Lu jslu@dns.ntu.edu.twJoe Orthoefer j_orthoefer@tia.netJoe Traister traister@mojozone.orgJoel Faedi Joel.Faedi@esial.u-nancy.frJoel Ray Holveck joelh@gnu.orgJoel Sutton jsutton@bbcon.com.auJordan DeLong fracture@allusion.netJoseph Scott joseph@randomnetworks.comJohan Granlund johan@granlund.nuJohan Karlsson k@numeri.campus.luth.seJohan Larsson johan@moon.campus.luth.seJohann Tonsing jtonsing@mikom.csir.co.zaJohannes Helander unknownJohannes Stille unknownJohn Beckett jbeckett@southern.eduJohn Beukema jbeukema@hk.super.netJohn Brezak unknownJohn Capo jc@irbs.comJohn F. Woods jfw@jfwhome.funhouse.comJohn Goerzen
jgoerzen@alexanderwohl.complete.orgJohn Heidemann johnh@isi.eduJohn Hood cgull@owl.orgJohn Kohl unknownJohn Lind john@starfire.mn.orgJohn Mackin john@physiol.su.oz.auJohn P johnp@lodgenet.comJohn Perry perry@vishnu.alias.netJohn Preisler john@vapornet.comJohn Reynolds jjreynold@home.comJohn Rochester jr@cs.mun.caJohn Sadler john_sadler@alum.mit.eduJohn Saunders john@pacer.nlc.net.auJohn Wehle john@feith.comJohn Woods jfw@eddie.mit.eduJohny Mattsson lonewolf@flame.orgJon Morgan morgan@terminus.trailblazer.comJonathan Belson jon@witchspace.comJonathan H N Chin jc254@newton.cam.ac.ukJonathan Hanna
jh@pc-21490.bc.rogers.wave.caJonathan Pennington john@coastalgeology.orgJorge Goncalves j@bug.fe.up.ptJorge M. Goncalves ee96199@tom.fe.up.ptJos Backus jbackus@plex.nlJose Marques jose@nobody.orgJosef Grosch
jgrosch@superior.mooseriver.comJoseph Stein joes@wstein.comJosh Gilliam josh@quick.netJosh Tiefenbach josh@ican.netJuergen Lock nox@jelal.hb.north.deJuha Inkari inkari@cc.hut.fiJukka A. Ukkonen jau@iki.fiJulian Assange proff@suburbia.netJulian Coleman j.d.coleman@ncl.ac.uk&a.jhsJulian Jenkins kaveman@magna.com.auJunichi Satoh junichi@jp.FreeBSD.orgJunji SAKAI sakai@jp.FreeBSD.orgJunya WATANABE junya-w@remus.dti.ne.jpJustas justas@mbank.lvJustin Stanford jus@security.za.netK.Higashino a00303@cc.hc.keio.ac.jpKai Vorma vode@snakemail.hut.fiKaleb S. Keithley kaleb@ics.comKaneda Hiloshi vanitas@ma3.seikyou.ne.jpKang-ming Liu gugod@gugod.orgKapil Chowksey kchowksey@hss.hns.comKarl Denninger karl@mcs.comKarl Dietz Karl.Dietz@triplan.comKarl Lehenbauer karl@NeoSoft.comKATO Tsuguru tkato@prontomail.ne.jpKawanobe Koh kawanobe@st.rim.or.jpKees Jan Koster kjk1@ukc.ac.ukKeith Bostic bostic@bostic.comKeith E. Walker kew@icehouse.netKeith Moore unknownKeith Sklower unknownKen Hornstein unknownKen Key key@cs.utk.eduKen Mayer kmayer@freegate.comKenji Saito marukun@mx2.nisiq.netKenji Tomita tommyk@da2.so-net.or.jpKenneth Furge kenneth.furge@us.endress.comKenneth Monville desmo@bandwidth.orgKenneth R. Westerback krw@tcn.netKenneth Stailey kstailey@gnu.ai.mit.eduKent Talarico kent@shipwreck.tsoft.netKent Vander Velden graphix@iastate.eduKentaro Inagaki JBD01226@niftyserve.ne.jpKevin Bracey kbracey@art.acorn.co.ukKevin Day toasty@dragondata.comKevin Lahey kml@nas.nasa.govKevin Meltzer perlguy@perlguy.comKevin Street street@iname.comKevin Van Maren vanmaren@fast.cs.utah.eduKiller killer@prosalg.noKim Scarborough sluggo@unknown.nuKiril Mitev kiril@ideaglobal.comKiroh HARADA kiroh@kh.rim.or.jpKlaus Herrmann klaus.herrmann@gmx.netKlaus Klein kleink@layla.inka.deKlaus-J. Wolf Yanestra@t-online.deKoichi Sato copan@ppp.fastnet.or.jpKonrad Heuer kheuer@gwdu60.gwdg.deKonstantin Chuguev Konstantin.Chuguev@dante.org.ukKostya Lukin lukin@okbmei.msk.suKouichi Hirabayashi kh@mogami-wire.co.jpKris Dow kris@vilnya.demon.co.ukKUNISHIMA Takeo kunishi@c.oka-pu.ac.jpKurt D. Zeilenga Kurt@Boolean.NETKurt Olsen kurto@tiny.mcs.usu.eduL. Jonas Olsson
ljo@ljo-slip.DIALIN.CWRU.EduLarry Altneu larry@ALR.COMLars Bernhardsson lab@fnurt.netLars Köller
Lars.Koeller@Uni-Bielefeld.DELaurence Lopez lopez@mv.mv.comLee Cremeans lcremean@tidalwave.netLeo Kim leo@florida.sarang.netLeo Serebryakov lev@serebryakov.spb.ruLiang Tai-hwa
avatar@www.mmlab.cse.yzu.edu.twLon Willett lon%softt.uucp@math.utah.eduLouis A. Mamakos louie@TransSys.COMLouis Mamakos loiue@TransSys.comLowell Gilbert lowell@world.std.comLucas James Lucas.James@ldjpc.apana.org.auLyndon Nerenberg lyndon@orthanc.ab.caM. L. Dodson bdodson@scms.utmb.EDUM.C. Wong unknownMagnus Enbom dot@tinto.campus.luth.seMahesh Neelakanta mahesh@gcomm.comMakoto MATSUSHITA matusita@jp.FreeBSD.orgMakoto WATANABE
watanabe@zlab.phys.nagoya-u.ac.jpMakoto YAMAKURA makoto@pinpott.spnet.ne.jpMalte Lance malte.lance@gmx.netMANTANI Nobutaka nobutaka@nobutaka.comManu Iyengar
iyengar@grunthos.pscwa.psca.comMarc Frajola marc@dev.comMarc Ramirez mrami@mramirez.sy.yale.eduMarc Slemko marcs@znep.comMarc van Kempen wmbfmk@urc.tue.nlMarc van Woerkom van.woerkom@netcologne.deMarcin Cieslak saper@system.plMark Andrews unknownMark Cammidge mark@gmtunx.ee.uct.ac.zaMark Diekhans markd@grizzly.comMark Huizer xaa@stack.nlMark J. Taylor mtaylor@cybernet.comMark Knight markk@knigma.orgMark Krentel krentel@rice.eduMark Mayo markm@vmunix.comMark Thompson thompson@tgsoft.comMark Tinguely tinguely@plains.nodak.eduMark Treacy unknownMark Valentine mark@thuvia.orgMarkus Holmberg saska@acc.umu.seMartin Birgmeier unknownMartin Blapp blapp@attic.chMartin Hinner mhi@linux.gyarab.czMartin Ibert mib@ppe.bb-data.deMartin Kammerhofer dada@sbox.tu-graz.ac.atMartin Minkus diskiller@cnbinc.comMartin Renters martin@tdc.on.caMartti Kuparinen
martti.kuparinen@ericsson.comMasachika ISHIZUKA
ishizuka@isis.min.ntt.jpMasahiro Sekiguchi
seki@sysrap.cs.fujitsu.co.jpMasahiro TAKEMURA
mastake@msel.t.u-tokyo.ac.jpMasanobu Saitoh msaitoh@spa.is.uec.ac.jpMasanori Kanaoka kana@saijo.mke.mei.co.jpMasanori Kiriake seiken@ARGV.ACMasatoshi TAMURA
tamrin@shinzan.kuee.kyoto-u.ac.jpMats Lofkvist mal@algonet.seMatt Bartley mbartley@lear35.cytex.comMatt Heckaman matt@LUCIDA.QC.CAMatt Thomas matt@3am-software.comMatt White mwhite+@CMU.EDUMatthew C. Mead mmead@Glock.COMMatthew Cashdollar mattc@rfcnet.comMatthew Emmerton root@gabby.gsicomp.on.caMatthew Flatt mflatt@cs.rice.eduMatthew Fuller fullermd@futuresouth.comMatthew Stein matt@bdd.netMatthew West mwest@uct.ac.zaMatthias Pfaller leo@dachau.marco.deMatthias Scheler tron@netbsd.orgMattias Gronlund
Mattias.Gronlund@sa.erisoft.seMattias Pantzare pantzer@ludd.luth.seMaurice Castro
maurice@planet.serc.rmit.edu.auMax Euston meuston@jmrodgers.comMax Khon fjoe@husky.iclub.nsu.ruMaxim Bolotin max@rsu.ruMaxim Konovalov maxim@macomnet.ruMaxime Henrion mhenrion@cybercable.frMicha Class
michael_class@hpbbse.bbn.hp.comMichael Alyn Miller malyn@strangeGizmo.comMichael Lucas mwlucas@blackhelicopters.orgMichael Lyngbøl michael@lyngbol.dkMichael Butler imb@scgt.oz.auMichael Butschky butsch@computi.erols.comMichael Clay mclay@weareb.orgMichael Galassi nerd@percival.rain.comMichael Hancock michaelh@cet.co.jpMichael Hohmuth hohmuth@inf.tu-dresden.deMichael Perlman canuck@caam.rice.eduMichael Petry petry@netwolf.NetMasters.comMichael Reifenberger root@totum.plaut.deMichael Sardo jaeger16@yahoo.comMichael Searle searle@longacre.demon.co.ukMichael Urban murban@tznet.comMichael Vasilenko acid@stu.cn.uaMichal Listos mcl@Amnesiac.123.orgMichio Karl Jinbo
karl@marcer.nagaokaut.ac.jpMiguel Angel Sagreras
msagre@cactus.fi.uba.arMihoko Tanaka m_tonaka@pa.yokogawa.co.jpMika Nystrom mika@cs.caltech.eduMikael Hybsch micke@dynas.seMikael Karpberg
karpen@ocean.campus.luth.seMike Barcroft mike@q9media.comMike Bristow mike@urgle.comMike Del repenting@hotmail.comMike Durian durian@plutotech.comMike Durkin mdurkin@tsoft.sf-bay.orgMike E. Matsnev mike@azog.cs.msu.suMike Evans mevans@candle.comMike Futerko mike@LITech.lviv.uaMike Grupenhoff kashmir@umiacs.umd.eduMike Harding mvh@ix.netcom.comMike Hibler mike@marker.cs.utah.eduMike Karels unknownMike McGaughey mmcg@cs.monash.edu.auMike Meyer mwm@mired.orgMike Mitchell mitchell@ref.tfs.comMike Murphy mrm@alpharel.comMike Peck mike@binghamton.eduMike Sherwood mike@fate.comMike Spengler mks@msc.eduMikhail A. Sokolov mishania@demos.suMing-I Hseh PA@FreeBSD.ee.Ntu.edu.TWMitsuru Yoshida mitsuru@riken.go.jpMonte Mitzelfelt monte@gonefishing.orgMorgan Davis root@io.cts.comMOROHOSHI Akihiko moro@race.u-tokyo.ac.jpMostyn Lewis mostyn@mrl.comMotomichi Matsuzaki mzaki@e-mail.ne.jpMotoyuki Kasahara m-kasahr@sra.co.jpN.G.Smith ngs@sesame.hensa.ac.ukNadav Eiron nadav@barcode.co.ilNAGAO Tadaaki nagao@cs.titech.ac.jpNAKAJI Hiroyuki
nakaji@tutrp.tut.ac.jpNAKAMURA Kazushi nkazushi@highway.or.jpNAKAMURA Motonori
motonori@econ.kyoto-u.ac.jpNAKATA, Maho chat95@mbox.kyoto-inet.or.jpNanbor Wang nw1@cs.wustl.eduNaofumi Honda
honda@Kururu.math.sci.hokudai.ac.jpNaoki Hamada nao@tom-yam.or.jpNarvi narvi@haldjas.folklore.eeNathan Dorfman nathan@rtfm.netNeal Fachan kneel@ishiboo.comNiall Smart rotel@indigo.ieNicholas Esborn nick@netdot.netNick Barnes Nick.Barnes@pobox.comNick Handel nhandel@NeoSoft.comNick Hilliard nick@foobar.orgNick Johnson freebsd@spatula.netNick Williams njw@cs.city.ac.ukNickolay N. Dudorov nnd@itfs.nsk.suNIIMI Satoshi sa2c@and.or.jpNiklas Hallqvist niklas@filippa.appli.seNils M. Holm nmh@t3x.orgNisha Talagala nisha@cs.berkeley.eduNo Name adrian@virginia.eduNo Name alex@elvisti.kiev.uaNo Name anto@netscape.netNo Name bobson@egg.ics.nitch.ac.jpNo Name bovynf@awe.beNo Name burg@is.ge.comNo Name chris@gnome.co.ukNo Name colsen@usa.netNo Name coredump@nervosa.comNo Name dannyman@arh0300.urh.uiuc.eduNo Name davids@SECNET.COMNo Name derek@free.orgNo Name devet@adv.IAEhv.nlNo Name djv@bedford.netNo Name dvv@sprint.netNo Name enami@ba2.so-net.or.jpNo Name flash@eru.tubank.msk.suNo Name flash@hway.ruNo Name fn@pain.csrv.uidaho.eduNo Name frf@xocolatl.comNo Name gclarkii@netport.neosoft.comNo Name gordon@sheaky.lonestar.orgNo Name graaf@iae.nlNo Name greg@greg.rim.or.jpNo Name grossman@cygnus.comNo Name gusw@fub46.zedat.fu-berlin.deNo Name hfir@math.rochester.eduNo Name hnokubi@yyy.or.jpNo Name iaint@css.tuu.utas.edu.auNo Name invis@visi.comNo Name ishisone@sra.co.jpNo Name iverson@lionheart.comNo Name jpt@magic.netNo Name junker@jazz.snu.ac.krNo Name k-sugyou@ccs.mt.nec.co.jpNo Name kenji@reseau.toyonaka.osaka.jpNo Name kfurge@worldnet.att.netNo Name lh@aus.orgNo Name lhecking@nmrc.ucc.ieNo Name mrgreen@mame.mu.oz.auNo Name nakagawa@jp.FreeBSD.orgNo Name ohki@gssm.otsuka.tsukuba.ac.jpNo Name owaki@st.rim.or.jpNo Name pechter@shell.monmouth.comNo Name pete@pelican.pelican.comNo Name pritc003@maroon.tc.umn.eduNo Name risner@stdio.comNo Name roman@rpd.univ.kiev.uaNo Name root@ns2.redline.ruNo Name root@uglabgw.ug.cs.sunysb.eduNo Name stephen.ma@jtec.com.auNo Name sumii@is.s.u-tokyo.ac.jpNo Name takas-su@is.aist-nara.ac.jpNo Name tamone@eig.unige.chNo Name tjevans@raleigh.ibm.comNo Name tony-o@iij.ad.jp amurai@spec.co.jpNo Name torii@tcd.hitachi.co.jpNo Name uenami@imasy.or.jpNo Name uhlar@netlab.skNo Name vode@hut.fiNo Name wlloyd@mpd.caNo Name wlr@furball.wellsfargo.comNo Name wmbfmk@urc.tue.nlNo Name yamagata@nwgpc.kek.jpNo Name ziggy@ryan.orgNo Name ZW6T-KND@j.asahi-net.or.jpNobuhiro Yasutomi nobu@psrc.isac.co.jpNobuyuki Koganemaru
kogane@koganemaru.co.jpNOKUBI Hirotaka h-nokubi@yyy.or.jpNorio Suzuki nosuzuki@e-mail.ne.jpNoritaka Ishizumi graphite@jp.FreeBSD.orgNoriyuki Soda soda@sra.co.jpOddbjorn Steffenson oddbjorn@tricknology.orgOh Junseon hollywar@mail.holywar.netOlaf Wagner wagner@luthien.in-berlin.deOleg Semyonov os@altavista.netOleg Sharoiko os@rsu.ruOleg V. Volkov rover@lglobus.ruOlexander Kunytsa kunia@wolf.istc.kiev.uaOliver Breuninger ob@seicom.NETOliver Friedrichs oliver@secnet.comOliver Fromme
oliver.fromme@heim3.tu-clausthal.deOliver Helmling
oliver.helmling@stud.uni-bayreuth.deOliver Laumann
net@informatik.uni-bremen.deOliver Lehmann
Kai_Allard_Liao@gmx.deOliver Oberdorf oly@world.std.comOlof Johansson offe@ludd.luth.seOsokin Sergey aka oZZ ozz@FreeBSD.org.ruPace Willisson pace@blitz.comPaco Rosich rosich@modico.eleinf.uv.esPalle Girgensohn girgen@partitur.seParag Patel parag@cgt.comPascal Pederiva pascal@zuo.dec.comPasvorn Boonmark boonmark@juniper.netPatrick Alken cosine@ellipse.mcs.drexel.eduPatrick Bihan-Faou patrick@mindstep.comPatrick Hausen unknownPatrick Li pat@databits.netPatrick Seal patseal@hyperhost.netPaul Antonov apg@demos.suPaul F. Werkowski unknownPaul Fox pgf@foxharp.boston.ma.usPaul Koch koch@thehub.com.auPaul Kranenburg pk@NetBSD.orgPaul M. Lambert plambert@plambert.netPaul Mackerras paulus@cs.anu.edu.auPaul Popelka paulp@uts.amdahl.comPaul S. LaFollette, Jr. unknownPaul Sandys myj@nyct.netPaul T. Root proot@horton.iaces.comPaul Vixie paul@vix.comPaulo Menezes paulo@isr.uc.ptPaulo Menezes pm@dee.uc.ptPedro A M Vazquez vazquez@IQM.Unicamp.BRPedro Giffuni giffunip@asme.orgPer Wigren wigren@home.sePete Bentley pete@demon.netPete Fritchman petef@databits.netPeter Childs pjchilds@imforei.apana.org.auPeter Cornelius pc@inr.fzk.dePeter Haight peterh@prognet.comPeter Jeremy peter.jeremy@alcatel.com.auPeter M. Chen pmchen@eecs.umich.eduPeter Much peter@citylink.dinoex.sub.orgPeter Olsson unknownPeter Philipp pjp@bsd-daemon.netPeter Stubbs PETERS@staidan.qld.edu.auPeter van Heusden pvh@egenetics.comPhil Maker pjm@cs.ntu.edu.auPhil Sutherland
philsuth@mycroft.dialix.oz.auPhil Taylor phil@zipmail.co.ukPhilip Musumeci philip@rmit.edu.auPhilippe Lefebvre nemesis@balistik.netPierre Y. Dampure pierre.dampure@k2c.co.ukPius Fischer pius@ienet.comPomegranate daver@flag.blackened.netPowerdog Industries
kevin.ruddy@powerdog.comPriit Järv priit@cc.ttu.eeR Joseph Wright rjoseph@mammalia.orgR. Kym HorsellRalf Friedl friedl@informatik.uni-kl.deRandal S. Masutani randal@comtest.comRandall Hopper rhh@ct.picker.comRandall W. Dean rwd@osf.orgRandy Bush rbush@bainbridge.verio.netRasmus Kaj kaj@Raditex.seReinier Bezuidenhout
rbezuide@mikom.csir.co.zaRemy Card Remy.Card@masi.ibp.frRicardas Cepas rch@richard.eu.orgRiccardo Veraldi veraldi@cs.unibo.itRich Wood rich@FreeBSD.org.ukRichard Henderson richard@atheist.tamu.eduRichard Hwang rhwang@bigpanda.comRichard Kiss richard@homemail.comRichard J Kuhns rjk@watson.grauel.comRichard M. Neswold
rneswold@enteract.comRichard Seaman, Jr. dick@tar.comRichard Stallman rms@gnu.ai.mit.eduRichard Straka straka@user1.inficad.comRichard Tobin richard@cogsci.ed.ac.ukRichard Wackerbarth rkw@Dataplex.NETRichard Winkel rich@math.missouri.eduRichard Wiwatowski rjwiwat@adelaide.on.netRick Macklem rick@snowhite.cis.uoguelph.caRick Macklin unknownRob Austein sra@epilogue.comRob Mallory rmallory@qualcomm.comRob Snow rsnow@txdirect.netRobert Crowe bob@speakez.comRobert D. Thrush rd@phoenix.aii.comRobert Eckardt
roberte@MEP.Ruhr-Uni-Bochum.deRobert P Ricci ricci@cs.utah.eduRobert Sanders rsanders@mindspring.comRobert Sexton robert@kudra.comRobert Shady rls@id.netRobert Swindells swindellsr@genrad.co.ukRobert Withrow witr@rwwa.comRobert Yoder unknownRobin Carey
robin@mailgate.dtc.rankxerox.co.ukRod Taylor rod@idiotswitch.orgRoger Hardiman roger@cs.strath.ac.ukRoland Jesse jesse@cs.uni-magdeburg.deRoman Shterenzon roman@xpert.comRon Bickers rbickers@intercenter.netRon Lenk rlenk@widget.xmission.comRonald Kuehn kuehn@rz.tu-clausthal.deRudolf Cejka cejkar@dcse.fee.vutbr.czRuslan Belkin rus@home2.UA.netRuslan Shevchenko rssh@cam.grad.kiev.uaRussell L. Carter rcarter@pinyon.orgRussell Vincent rv@groa.uct.ac.zaRyan Younce ryany@pobox.comRyuichiro IMURA imura@af.airnet.ne.jpSakai Hiroaki sakai@miya.ee.kagu.sut.ac.jpSakari Jalovaara sja@tekla.fiSam Hartman hartmans@mit.eduSamuel Lam skl@ScalableNetwork.comSamuel Tardieu sam@inf.enst.frSamuele Zannoli zannoli@cs.unibo.itSander Janssen janssen@rendo.dekooi.nlSander Vesik sander@haldjas.folklore.eeSandro Sigala ssigala@globalnet.itSANETO Takanori sanewo@strg.sony.co.jpSASAKI Shunsuke ele@pop17.odn.ne.jpSascha Blank blank@fox.uni-trier.deSascha Wildner swildner@channelz.GUN.deSatoh Junichi junichi@astec.co.jpSAWADA Mizuki miz@qb3.so-net.ne.jpScot Elliott scot@poptart.orgScot W. Hetzel hetzels@westbend.netScott A. Kenney saken@rmta.ml.orgScott A. Moberly smoberly@xavier.dyndns.orgScott Blachowicz
scott.blachowicz@seaslug.orgScott Burris scott@pita.cns.ucla.eduScott Hazen Mueller scott@zorch.sf-bay.orgScott Michel scottm@cs.ucla.eduScott Mitchel scott@uk.FreeBSD.orgScott Reynolds scott@clmqt.marquette.mi.usSebastian Strollo seb@erix.ericsson.seSerge V. Vakulenko vak@zebub.msk.suSergei Chechetkin csl@whale.sunbay.crimea.uaSergei S. Laskavy laskavy@pc759.cs.msu.suSergey Gershtein sg@mplik.ruSergey Kosyakov ks@itp.ac.ruSergey N. Vorokov serg@tmn.ruSergey Potapov sp@alkor.ruSergey Samoyloff gonza@techline.ruSergey Shkonda serg@bcs.zp.uaSergey Skvortsov skv@protey.ruSergey V.Dorokhov svd@kbtelecom.nalnet.ruSergio Lenzi lenzi@bsi.com.brShaun Courtney shaun@emma.eng.uct.ac.zaShawn M. Carey smcarey@mailbox.syr.eduShigio Yamaguchi shigio@tamacom.comShinya Esu esu@yk.rim.or.jpShinya FUJIE fujie@tk.elec.waseda.ac.jpShuichi Tanaka stanaka@bb.mbn.or.jpSimon simon@masi.ibp.frSimon Burge simonb@telstra.com.auSimon Dick simond@irrelevant.orgSimon J Gerraty sjg@melb.bull.oz.auSimon Marlow simonm@dcs.gla.ac.ukSimon Shapiro shimon@simon-shapiro.orgSin'ichiro MIYATANI siu@phaseone.co.jpSlaven Rezic eserte@cs.tu-berlin.deSoochon Radee slr@mitre.orgSoren Dayton csdayton@midway.uchicago.eduSoren Dossing sauber@netcom.comSoren S. Jorvang soren@wheel.dkStefan Bethke stb@hanse.deStefan Eggers seggers@semyam.dinoco.deStefan Moeding s.moeding@ndh.netStefan Petri unknownStefan `Sec` Zehl sec@42.orgSteinar Haug sthaug@nethelp.noStephane E. Potvin sepotvin@videotron.caStephane Legrand stephane@lituus.frStephen Clawson
sclawson@marker.cs.utah.eduStephen F. Combs combssf@salem.ge.comStephen Farrell stephen@farrell.orgStephen Hocking sysseh@devetir.qld.gov.auStephen J. Roznowski sjr@home.netStephen McKay syssgm@devetir.qld.gov.auStephen Melvin melvin@zytek.comSteve Bauer sbauer@rock.sdsmt.eduSteve Coltrin spcoltri@unm.eduSteve Deering unknownSteve Gerakines steve2@genesis.tiac.netSteve Gericke steveg@comtrol.comSteve Piette steve@simon.chi.il.USSteve Schwarz schwarz@alpharel.comSteven Enderle panic@subphase.deSteven G. Kargl
kargl@troutmask.apl.washington.eduSteven H. Samorodin samorodi@NUXI.comSteven McCanne mccanne@cs.berkeley.eduSteven Plite splite@purdue.eduSteven Wallace unknownStijn Hoop stijn@win.tue.nlStuart Henderson
stuart@internationalschool.co.ukSue Blake sue@welearn.com.auSugimoto Sadahiro ixtl@komaba.utmc.or.jpSUGIMURA Takashi sugimura@jp.FreeBSD.orgSugiura Shiro ssugiura@duo.co.jpSujal Patel smpatel@wam.umd.eduSungman Cho smcho@tsp.korea.ac.krSune Stjerneby stjerneby@usa.netSURANYI Peter
suranyip@jks.is.tsukuba.ac.jpSuzuki Yoshiaki
zensyo@ann.tama.kawasaki.jpSvein Skogen
tds@nsn.noSybolt de Boer bolt@xs4all.nlTadashi Kumano kumano@strl.nhk.or.jpTaguchi Takeshi taguchi@tohoku.iij.ad.jpTAKAHASHI Kaoru kaoru@kaisei.orgTakahiro Yugawa yugawa@orleans.rim.or.jpTakashi Mega mega@minz.orgTakashi Uozu j1594016@ed.kagu.sut.ac.jpTakayuki Ariga a00821@cc.hc.keio.ac.jpTakeru NAIKI naiki@bfd.es.hokudai.ac.jpTakeshi Amaike amaike@iri.co.jpTakeshi MUTOH mutoh@info.nara-k.ac.jpTakeshi Ohashi
ohashi@mickey.ai.kyutech.ac.jpTakeshi WATANABE
watanabe@crayon.earth.s.kobe-u.ac.jpTakuya SHIOZAKI
tshiozak@makino.ise.chuo-u.ac.jpTatoku Ogaito tacha@tera.fukui-med.ac.jpTatsuya Kudoh cdr@cosmonet.orgTed Buswell tbuswell@mediaone.netTed Faber faber@isi.eduTed Lemon mellon@isc.orgTerry Lambert terry@lambert.orgTerry Lee terry@uivlsi.csl.uiuc.eduTetsuya Furukawa tetsuya@secom-sis.co.jpTheo de Raadt deraadt@OpenBSD.orgThomas thomas@mathematik.uni-Bremen.deThomas D. Dean tomdean@ix.netcom.comThomas David Rivers rivers@dignus.comThomas G. McWilliams tgm@netcom.comThomas Graichen
graichen@omega.physik.fu-berlin.deThomas König
Thomas.Koenig@ciw.uni-karlsruhe.deThomas Ptacek unknownThomas Quinot thomas@cuivre.fr.eu.orgThomas A. Stephens tas@stephens.orgThomas Stromberg tstrombe@rtci.comThomas Valentino Crimi
tcrimi+@andrew.cmu.eduThomas Wintergerst thomas@lemur.nord.deÞórður Ívarsson
totii@est.isThierry Thomas tthomas@mail.dotcom.frTimothy Jensen toast@blackened.comTim Kientzle kientzle@netcom.comTim Singletary
tsingle@sunland.gsfc.nasa.govTim Wilkinson tim@sarc.city.ac.ukTimo J. Rinne tri@iki.fiTobias Reifenberger treif@mayn.deTodd Miller millert@openbsd.orgTom root@majestix.cmr.noTom tom@sdf.comTom Gray - DCA dcasba@rain.orgTom Jobbins tom@tom.tjTom Pusateri pusateri@juniper.netTom Rush tarush@mindspring.comTom Samplonius tom@misery.sdf.comTomohiko Kurahashi
kura@melchior.q.t.u-tokyo.ac.jpTony Kimball alk@Think.COMTony Li tli@jnx.comTony Lynn wing@cc.nsysu.edu.twTony Maher tonym@angis.org.auTorbjorn Granlund tege@matematik.su.seToshihiko SHIMOKAWA toshi@tea.forus.or.jpToshihiro Kanda candy@kgc.co.jpToshiomi Moriki
Toshiomi.Moriki@ma1.seikyou.ne.jpTrefor S. trefor@flevel.co.ukTrenton Schulz twschulz@cord.eduTrevor Blackwell tlb@viaweb.comUdo Schweigert ust@cert.siemens.deUgo Paternostro paterno@dsi.unifi.itUlf Kieber kieber@sax.deUlli Linzen ulli@perceval.camelot.deURATA Shuichiro s-urata@nmit.tmg.nec.co.jpUwe Arndt arndt@mailhost.uni-koblenz.deVadim Belman vab@lflat.vas.mobilix.dkVadim Chekan vadim@gc.lviv.uaVadim Kolontsov vadim@tversu.ac.ruVadim Mikhailov mvp@braz.ruValentin Nechayev netch@lucky.net&a.logo;Van Jacobson van@ee.lbl.govVasily V. Grechishnikov
bazilio@ns1.ied-vorstu.ac.ruVasim Valejev vasim@uddias.diaspro.comVernon J. Schryver vjs@mica.denver.sgi.comVeselin Slavov vess@btc.netVic Abell abe@cc.purdue.eduVille Eerola ve@sci.fiVince Valenti vince@blue-box.netVincent Poy vince@venus.gaianet.netVincenzo Capuano
VCAPUANO@vmprofs.esoc.esa.deVirgil Champlin champlin@pa.dec.comVladimir A. Jakovenko
vovik@ntu-kpi.kiev.uaVladimir Kushnir kushn@mail.kar.netVsevolod Lobko seva@alex-ua.comW. Gerald Hicks wghicks@bellsouth.netW. Richard Stevens rstevens@noao.eduWalt Howard howard@ee.utah.eduWalt M. Shandruk walt@erudition.netWarren Toomey wkt@csadfa.cs.adfa.oz.auWayne Scott wscott@ichips.intel.comWerner Griessl
werner@btp1da.phy.uni-bayreuth.deWes Santee wsantee@wsantee.oz.netWietse Venema wietse@wzv.win.tue.nlWiljo Heinen wiljo@freeside.ki.open.deWillem Jan Withagen wjw@surf.IAE.nlWilliam Jolitz withheldWilliam Liao william@tale.netWojtek Pilorz
wpilorz@celebris.bdk.lublin.plWolfgang Helbig helbig@ba-stuttgart.deWolfgang Solfrank ws@tools.deWolfgang Stanglmeier wolf@FreeBSD.orgWu Ching-hong woju@FreeBSD.ee.Ntu.edu.TWYarema yds@ingress.comYaroslav Terletsky ts@polynet.lviv.uaYasuhiro Fukama yasuf@big.or.jpYasuhito FUTATSUKI futatuki@fureai.or.jpYen-Ming Lee leeym@bsd.ce.ntu.edu.twYen-Shuo Su yssu@CCCA.NCTU.edu.twYin-Jieh Chen yinjieh@Crazyman.Dorm13.NCTU.edu.twYixin Jin yjin@rain.cs.ucla.eduYoichi Asai yatt@msc.biglobe.ne.jpYoichi Nakayama yoichi@eken.phys.nagoya-u.ac.jpYoshiaki Uchikawa yoshiaki@kt.rim.or.jpYoshihiko SARUMRU mistral@imasy.or.jpYoshihisa NAKAGAWA
y-nakaga@ccs.mt.nec.co.jpYoshikazu Goto gotoh@ae.anritsu.co.jpYoshimasa Ohnishi
ohnishi@isc.kyutech.ac.jpYoshishige Arai ryo2@on.rim.or.jpYuichi MATSUTAKA matutaka@osa.att.ne.jpYujiro MIYATA
miyata@bioele.nuee.nagoya-u.ac.jpYu-Shun Wang yushunwa@isi.eduYusuke Nawano azuki@azkey.orgYuu Yashiki s974123@cc.matsuyama-u.ac.jpYuuki SAWADA mami@whale.cc.muroran-it.ac.jpYuuichi Narahara aconitum@po.teleway.ne.jpYuval Yarom yval@cs.huji.ac.ilYves Fonk yves@cpcoup5.tn.tudelft.nlYves Fonk yves@dutncp8.tn.tudelft.nlZach Heilig zach@gaffaneys.comZach Zurflu zach@pabst.bendnet.comZahemszhky Gabor zgabor@code.huZhong Ming-Xun zmx@mail.CDPA.nsysu.edu.tw386BSD Patch Kit Patch Contributors(in alphabetical order by first name):Adam Glass glass@postgres.berkeley.eduAdrian Hall ahall@mirapoint.comAndrey A. Chernov ache@astral.msk.suAndrew Herbert andrew@werple.apana.org.auAndrew Moore alm@netcom.comAndy Valencia ajv@csd.mot.comjtk@netcom.comArne Henrik Juul arnej@Lise.Unit.NOBakul Shah bvs@bitblocks.comBarry Lustig barry@ictv.comBob Wilcox bob@obiwan.uucpBranko LankesterBrett Lymn blymn@mulga.awadi.com.AUCharles Hannum mycroft@ai.mit.eduChris G. Demetriou
cgd@postgres.berkeley.eduChris Torek torek@ee.lbl.govChristoph Robitschko
chmr@edvz.tu-graz.ac.atDaniel Poirot poirot@aio.jsc.nasa.govDave Burgess burgess@hrd769.brooks.af.milDave Rivers rivers@ponds.uucpDavid Dawes dawes@physics.su.OZ.AUDavid Greenman dg@Root.COMEric J. Haug ejh@slustl.slu.eduFelix Gaehtgens
felix@escape.vsse.in-berlin.deFrank Maclachlan fpm@crash.cts.comGary A. Browning gab10@griffcd.amdahl.comGary Howland gary@hotlava.comGeoff Rehmet csgr@alpha.ru.ac.zaGoran Hammarback goran@astro.uu.seGuido van Rooij guido@gvr.orgGuy Antony Halse guy@rucus.ru.ac.zaGuy Harris guy@auspex.comHavard Eidnes
Havard.Eidnes@runit.sintef.noHerb Peyerl hpeyerl@novatel.cuc.ab.caHolger Veit Holger.Veit@gmd.deIshii Masahiro, R. Kym HorsellJ.T. Conklin jtc@cygnus.comJagane D Sundar jagane@netcom.comJames Clark jjc@jclark.comJames Jegers jimj@miller.cs.uwm.eduJames W. DolterJames da Silva jds@cs.umd.edu et alJay Fenlason hack@datacube.comJim Wilson wilson@moria.cygnus.comJörg Lohse
lohse@tech7.informatik.uni-hamburg.deJörg Wunsch
joerg_wunsch@uriah.heep.sax.deJohn DysonJohn Woods jfw@eddie.mit.eduJordan K. Hubbard jkh@whisker.hubbard.ieJulian Elischer julian@dialix.oz.auJulian Stacey jhs@FreeBSD.orgKarl Dietz Karl.Dietz@triplan.comKarl Lehenbauer karl@NeoSoft.comkarl@one.neosoft.comKeith Bostic bostic@toe.CS.Berkeley.EDUKen HughesKent Talarico kent@shipwreck.tsoft.netKevin Lahey kml%rokkaku.UUCP@mathcs.emory.edukml@mosquito.cis.ufl.eduKonstantinos Konstantinidis kkonstan@duth.grMarc Frajola marc@dev.comMark Tinguely tinguely@plains.nodak.edutinguely@hookie.cs.ndsu.NoDak.eduMartin Renters martin@tdc.on.caMichael Clay mclay@weareb.orgMichael Galassi nerd@percival.rain.comMike Durkin mdurkin@tsoft.sf-bay.orgNaoki Hamada nao@tom-yam.or.jpNate Williams nate@bsd.coe.montana.eduNick Handel nhandel@NeoSoft.comnick@madhouse.neosoft.comPace Willisson pace@blitz.comPaul Kranenburg pk@cs.few.eur.nlPaul Mackerras paulus@cs.anu.edu.auPaul Popelka paulp@uts.amdahl.comPeter da Silva peter@NeoSoft.comPhil Sutherland
philsuth@mycroft.dialix.oz.auPoul-Henning Kamp phk@FreeBSD.orgRalf Friedl friedl@informatik.uni-kl.deRick Macklem root@snowhite.cis.uoguelph.caRobert D. Thrush rd@phoenix.aii.comRodney W. Grimes rgrimes@cdrom.comSascha Wildner swildner@channelz.GUN.deScott Burris scott@pita.cns.ucla.eduScott Reynolds scott@clmqt.marquette.mi.usSean Eric Fagan sef@kithrup.comSimon J Gerraty sjg@melb.bull.oz.ausjg@zen.void.oz.auStephen McKay syssgm@devetir.qld.gov.auTerry Lambert terry@icarus.weber.eduTerry Lee terry@uivlsi.csl.uiuc.eduTor Egge Tor.Egge@idi.ntnu.noWarren Toomey wkt@csadfa.cs.adfa.oz.auWiljo Heinen wiljo@freeside.ki.open.deWilliam Jolitz withheldWolfgang Solfrank ws@tools.deWolfgang Stanglmeier wolf@dentaro.GUN.deYuval Yarom yval@cs.huji.ac.il
diff --git a/en_US.ISO8859-1/books/handbook/x11/chapter.sgml b/en_US.ISO8859-1/books/handbook/x11/chapter.sgml
index 70050889c7..fdd1fa5bd0 100644
--- a/en_US.ISO8859-1/books/handbook/x11/chapter.sgml
+++ b/en_US.ISO8859-1/books/handbook/x11/chapter.sgml
@@ -1,2289 +1,2292 @@
The X Window SystemThis chapter has been graciously donated by &a.grog;
from his book, The
Complete FreeBSD, and remains copyright of him.
Modifications for the handbook made by &a.jim;. The section on
fonts in XFree86 was contributed by &a.murray; and the section on
XDM was contributed by &a.sethk;.SynopsisThe following chapter will cover installing and configuring X11
on your system. For more information on X11 and to see whether your
video card is supported, check the XFree86 web site.OverviewFreeBSD comes with XFree86, a port of X11R6 that supports
several versions of Intel-based UNIX. This chapter describes how
to set up your XFree86 server. It is based on material supplied
with the FreeBSD release, specifically the files README.FreeBSD
and README.Config in the directory
/usr/X11R6/lib/X11/doc. If you find any
discrepancy, the material in those files will be more up-to-date
than this description. In addition, the file
/usr/X11R6/lib/X11/doc/RELNOTES contains
OS-independent information about the current release.X uses a lot of memory. In order to run X, your system should
have an absolute minimum of 8 MB of memory, but performance will be
painful with so little memory. A more practical minimum is 16 MB,
and you can improve performance by adding more memory. If you use
X intensively, you will continue seeing performance improvement by
increasing to as much as 128 MB of RAM.There is lots of useful information in the rest of this chapter,
but maybe you are not interested in information right now. You just
want to get your X server up and running. However, be warned:An incorrect installation can burn out your monitor or your
video board.However, if you know you are in spec, and you have a standard
Super VGA board and a good multi-frequency monitor, then you can
probably get things up and running without reading this
chapter.Installing XFree86The easiest way to install XFree86 is with the sysinstall
program, either when you are installing the system, or later by
starting the program /stand/sysinstall. In the
rest of this chapter, we will look at what makes up the
distribution, and we will also take a look at manually installing
X11.The XFree86 DistributionXFree86 is distributed as a bewildering number of archives.
In the following section, we will take a look at what you should
install. Do not worry too much, though; if you cannot decide
what to pick and you have 200MB of disk space free, it's safe to
unpack everything.At a minimum you need to unpack the archives in the
following table and at least one server that matches your VGA
board. You will need 10Mb for the minimum required run-time
binaries only, and between 1.7 and 3 MB for the server.Below is a table of the required components.ArchiveDescriptionXbin.tgzAll the executable X client applications and shared
libraries.Xfnts.tgzThe misc and 75 dpi fonts.Xlib.tgzData files and libraries needed at runtime.The X ServerIn addition to the archives above, you need at least one
server, which will take up about 3 MB of disk. The choice
depends primarily on what kind of display board you have. The
default server name is /usr/X11R6/bin/X, and
it is a link to a specific server binary
/usr/X11R6/bin/XF86_xxxx. You will find the
server archives for the standard PC architecture in
/cdrom/XF86336/Servers, and the servers for
the Japanese PC98 architecture in
/cdrom/XF86336/PC98-Servers if you have the
CD set. Alternatively, they are available on our FTP site at
ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/XF86336/Servers/ or ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/XF86336/PC98-Servers/Available X servers for the standard PC architecture:ArchiveDescriptionX8514.tgz8-bit color for IBM 8514 and true
compatibles.XAGX.tgz8 and 16-bit color for AGX and XGA boards.XI128.tgz8 and 16-bit color for I128 boards.XMa32.tgz8 and 16-bit color for ATI Mach32 boards.XMa64.tgz8, 16, and 32-bit color fot ATI Mach64
boards.XMa8.tgz8-bit color for ATI Mach8 boards.XMono.tgz1-bit monochrome for VGA, Super-VGA, Hercules, and
others.XP9K.tgz8, 16, and 32-bit color for Weitek P9000 boards
(Diamond Viper).XS3.tgz8, 16, and 32-bit color for S3 boards.XS3V.tgz8 and 16-bit color for S3 ViRGE boards.XSVGA.tgz>=8-bit color for Super-VGA cards.XVG16.tgz4-bit color for VGA and Super-VGA cards.XW32.tgz8-bit color for ET4000/W32, /W32i, /W32p, and
ET6000 cards.Available X servers for the Japanese PC98 architecture:ArchiveDescriptionX9GAN.tgz8-bit color for PC98 GA-98NB/WAP boards.X9GA9.tgz8, 16, and 32-bit color for PC98 S3 GA-968
boards.X9480.tgz8-bit color for PC98 PEGCX9NKV.tgz8-bit color for PC98 NEC-CIRRUS/EPSON NKV/NKV2
boards.X9WBS.tgz8-bit color for PC98 WAB-S boards.X9WEP.tgz8-bit color for PC98 WAB-EP boards.X9WSN.tgz8-bit color for PC98 WSN-A2F boards.X9EGC.tgz4-bit color for PC98 EGC.X9TGU.tgz8 and 16-bit color for PC98 Trident Cyber9320/9680
boards.X9NS3.tgz8 and 16-bit color for PC98 NEC S3 boards.X9SPW.tgz8 and 16-bit color for PC98 S3 PW/PCSKB
boards.X9LPW.tgz8 and 16-bit color for PC98 S3 PW/LB boards.Each of these servers includes a manual page which contains
details of supported chipsets and server-specific configuration
options.There are also a number of archives are provided for X
programmers:ArchiveDescriptionXprog.tgzConfig, lib*.a, and
*.h files needed for compiling
clients.Xctrb.tgzContributed sources.Xlk98.tgzThe link kit for building servers,
Japanese PC98 version.Xlkit.tgzThe link kit for building servers,
normal PC architecture.Xsrc-1.tgzPart 1 of the complete sources.Xsrc-2.tgzPart 2 of the complete sources.Xsrc-3.tgzPart 3 of the complete sources.You will need Xprog.tgz if you intend
to install ports of X software.XFree86 also includes a number of optional parts, such as
documentation, and setup programs.ArchiveDescriptionXdoc.tgzREADMEsXjdoc.tgzREADMEs in Japanese.Xps.tgzREADMEs in PostScript.Xhtml.tgzREADMEs in HTML.Xman.tgzManual pages.Xcfg.tgzCustomizable xinit and
xdm runtime configuration
files.Xset.tgzThe X86Setup utility; a
graphical version of the xf86config
utility.Xjset.tgzThe XF86Setup utility,
Japanese version, for the normal PC architecture.XF86Setup is a graphical mode setup
program for XFree86, and you may prefer it to the standard setup
program xf86config. You do not need any
special archives for xf86config; it is
included in Xbin.tgz.The first time you install, you will need
Xcfg.tgz to create your initial configuration
files. Do not use it when upgrading; it overwrites your
configuration files.There are also additional fonts that are available with
XFree86:ArchiveDescriptionXf100.tgz100 dpi fonts.Xfscl.tgzSpeedo and Type1 fonts.Xfnon.tgzJapanese, Chinese, and other non-english
fonts.Xfcyr.tgzCyrillic fonts.Unlike the X servers described above, the archives for the
following servers are all in the main directory.ArchiveDescriptionXfsrv.tgzThe font server.Xnest.tgzA nested server running as a client window on
another display.Xprt.tgzThe print server.Xvfb.tgzThe Virtual Framebuffer X server, which renders
into memory or an mmapped file.Installing XFree86 ManuallyIf you do not use sysinstall to install X, you need to perform
a number of steps:Create the directories and unpack the required
archives.Choose and install an X server.Set up the environment to be able to access X.Find a virtual terminal in which to run X.Configure X for your hardware.This sounds like a lot of work, but if you approach it
methodically, it is not too bad. In the rest of this section,
we will look at each step in turn.Unpacking the ArchivesYou must unpack the archives as root, since a number of
the executables are set-user-id (they run as root even when
started by other users). If you unpack the server as an
ordinary user, it may abort when you try to run it. You must
also use a umask value of 022 (permissions rwxr-xr-x), because
the X server requires special permissions.&prompt.user; su
Password:
&prompt.root; umask 022If you do not have enough space in the
/usr file system, create a directory on
another partition and symlink it to /usr. For example, if you
have a file system /home with adequate
space, you could do:&prompt.root; cd /home
&prompt.root; mkdir X11R6
&prompt.root; ln -s /home/X11R6 /usr/X11R6Next, decide which archives you want to install. For a
minimal installation, choose Xbin.tgz,
Xfnts.tgz, Xlib.tgz,
and Xcfg.tgz. If you have already
configured X for your hardware, you can omit
Xcfg.tgz.If you are using sh, unpack like this:&prompt.root; mkdir -p /usr/X11R6
&prompt.root; cd /usr/X11R6
&prompt.root; for i in bin fnts lib cfg; do
&prompt.root; tar xzf X$i.tgz
&prompt.root; doneIf you are using csh, enter:&prompt.root; mkdir -p /usr/X11R6
&prompt.root; cd /usr/X11R6
&prompt.root; foreach i (bin fnts lib cfg)? tar xzf X$i.tgz?endInstalling the ServerChoose a server archive corresponding to your VGA board.
If the table in the section above does not give you enough
information, check the server man pages,
/usr/X11R6/man/man1/XF86_*, which list
the VGA chipsets supported by each server. For example, if
you have an ET4000 based board you will use the
XF86_SVGA server. In this case you
would enter:&prompt.root; cd /usr/X11R6
&prompt.root; tar xzf XSVGA.tgz [substitute your server name here]Setting up the environmentNext, you may wish to create a symbolic link
/usr/X11/bin/X that points to the server
that matches your video board. In this example, it is the
XF86_SVGA server:&prompt.root; cd /usr/X11R6/bin
&prompt.root; rm X
&prompt.root; ln -s XF86_SVGA XX needs this symbolic link in order to be able to work
correctly, but you have the option of setting it when you run
xf86config – see below.Next, check that the directory
/usr/X11R6/bin is in the default path for
sh in /etc/profile and for csh in
/etc/csh.login, and add it if it is not.
It is best to do this with an editor, but if you want to take
a shortcut, you can enter:&prompt.root; echo 'PATH=$PATH:/usr/X11R6/bin' >>/etc/profileor:&prompt.root; echo 'set path = ($path /usr/X11R6/bin)' >>/etc/csh.loginAlternatively, make sure everybody who uses X puts
/usr/X11R6/bin in their shell's
PATH variable.Next, invoke ldconfig to put the shared libraries in
ld.so's cache:&prompt.root; ldconfig -m /usr/X11R6/libYou can omit invoking ldconfig if you
plan to reboot before using X.You do not need to uncompress the font files, but if you
do, you must run mkfontdir in the
corresponding font directory, otherwise your server will abort
with the message could not open default font
`fixed'.Assigning a virtual terminal to XNext, make sure you have a spare virtual console which is
running a getty. First check how many virtual consoles you
have:&prompt.root; dmesg | grep virtual
sc0: VGA color <16 virtual consoles, flags=0x0>Then check /etc/ttys to make sure
there is at least one virtual terminal (ttyvxx device) which
does not have a getty enabled. Look for the keyword
off:&prompt.root; grep ttyv /etc/ttys
ttyv0 "/usr/libexec/getty Pc" cons25 on secure
ttyv1 "/usr/libexec/getty Pc" cons25 on secure
ttyv2 "/usr/libexec/getty Pc" cons25 on secure
ttyv3 "/usr/libexec/getty Pc" cons25 off secureIn this case, /dev/ttyv3 is
available, if your kernel has least 4 VTs. If not, either
disable a getty in /etc/ttys by
changing on to off, or build another kernel with more virtual
terminals.Configuring X for Your HardwareAfter installing the X software, you will need to
customize the file XF86Config, which
tells the X server about your hardware and how you want to
run it.In order to set up XF86Config, you
will need the following hardware information:Your mouse type, the bit rate if it is a serial mouse,
and the name of the device to which it is connected. This
will typically be /dev/ttyd0 or
/dev/ttyd1 for a serial mouse,
/dev/psm0 for a PS/2 mouse, or
/dev/mse0 for a bus mouse.The type of the video board and the amount of display
memory. If it is a no-name board, establish what VGA chip
set it uses.The parameters of your monitor; vertical and
horizontal frequency.Identifying the hardwareHow do you decide what your hardware is? The manufacturer
should tell you, but very often the information you get about
your display board and monitor is pitiful; Super VGA
board with 76 Hz refresh rate and 16,777,216 colors.
This tells you the maximum pixel depth (24 bits – - the
number of colors is 2(pixel depth)), but it doesn't tell you
anything else about the display board.As we will see later, the real parameters you need to know
are the maximum horizontal frequency, the dot clock range, the
chipset and the amount of display memory.You could be unlucky trying to get some of this
information, but you can get some with the
SuperProbe program. It should always be
able to tell you the chipset and the amount of memory on
board.Occasionally SuperProbe can crash your
system. Make sure you are not doing anything important when
you run it. Running SuperProbe looks like this:&prompt.root; SuperProbe
(warnings and acknowledgments omitted)
First video: Super-VGA
Chipset: Tseng ET4000 (Port Probed)
Memory: 1024 Kbytes
RAMDAC: Generic 8-bit pseudo-color DAC
(with 6-bit wide lookup tables (or in 6-bit mode))SuperProbe is very finicky about
running at all, and you will often get messages like:SuperProbe: Cannot be run while an X server is running
SuperProbe: If an X server is not running, unset $DISPLAY and try again
SuperProbe: Cannot open videoIn other words, even if no X server is running,
SuperProbe will not work if you have the
environment variable DISPLAY set. How do you
unset it? With Bourne-style shells, you enter:&prompt.root; unset DISPLAYIn the C shell, you enter:&prompt.root; unsetenv DISPLAYRunning xf86configThe easy way to create your configuration file is with one
of the utilities xf86config (note the lower
case name) or XF86Setup. Both lead you
through the configuration step by step.
xf86config runs in character mode, while
XF86Setup runs in a graphical mode.
XF86Setup can have problems with unusual
hardware, so I personally prefer
xf86config.You can also use sysinstall, but this does not change
much; sysinstall just starts
xf86config for you, and it is easier to
start it directly. In this section, we will use an example to
illustrate configuration via xf86config.
We are installing X for an ancient Diamond SpeedStar with 1 MB
of display memory, a Logitech MouseMan mouse, and an ADI
MicroScan 5AP monitor. The mouse is connected to the system
via the first serial port,
/dev/ttyd0.To run xf86config, type in the name. If
/usr/X11R6/bin is included in your
PATH environment variable, you just need to type
xf86config. If it is not, you need to type
out the full path to xf86config, like
so:&prompt.root; /usr/X11R6/bin/xf86configThis program will create a basic
XF86Configfile, based on menu selections
you make.The XF86Config file usually resides
in /usr/X11R6/lib/X11 or
/etc. A sample
XF86Config file is supplied with XFree86;
it is configured for a standard VGA card and monitor with
640x480 resolution. This program will ask for a pathname when
it is ready to write the file.You can either take the sample
XF86Config as a base and edit it for your
configuration, or let this program produce a base
XF86Config file for your configuration
and fine-tune it. Refer to
/usr/X11R6/lib/X11/doc/README.Config for
a detailed overview of the configuration process.For accelerated servers (including accelerated drivers in
the SVGA server), there are many chipset and card-specific
options and settings. This program does not know about these.
On some configurations some of these settings must be
specified. Refer to the server man pages and chipset-specific
READMEs.Before continuing with this program, make sure you know
the chipset and amount of video memory on your video card.
SuperProbe can help with this. It is also
helpful if you know what server you want to run.Press enter to continue, or ctrl-c to abort. ENTER
First specify a mouse protocol type. Choose one from the following list:
1. Microsoft compatible (2-button protocol)
2. Mouse Systems (3-button protocol)
3. Bus Mouse
4. PS/2 Mouse
5. Logitech Mouse (serial, old type, Logitech protocol)
6. Logitech MouseMan (Microsoft compatible)
7. MM Series
8. MM HitTablet
9. Microsoft IntelliMouseIf you have a two-button mouse, it is most likely of type
1, and if you have a three-button mouse, it can probably
support both protocol 1 and 2. There are two main varieties
of the latter type; mice with a switch to select the protocol,
and mice that default to 1 and require a button to be held at
boot-time to select protocol 2. Some mice can be convinced to
do 2 by sending a special sequence to the serial port (see the
ClearDTR/ClearRTS options).Enter a protocol number: 6 Logitech MouseMan
You have selected a Logitech MouseMan type mouse. You might want to enable
ChordMiddle which could cause the third button to work.
Please answer the following question with either 'y' or 'n'.
Do you want to enable ChordMiddle? nYou definitely want to enable the third button on your
mouse, since many X clients use it. With a genuine Logitech
mouse, however, you don't need to enable
ChordMiddle in order to use the button. If
you find that the third button does not work when you start X,
you can enable ChordMiddle by editing the
configuration file – it is much easier and less
error-prone than re-running XF86Setup.Continuing through the setup:If your mouse has only two buttons, it is recommended that you enable Emulate3Buttons.
Please answer the following question with either 'y' or 'n'.
Do you want to enable Emulate3Buttons? n
Now give the full device name that the mouse is connected to, for example
/dev/tty00. Just pressing enter will use the default, /dev/mouse.
Mouse device: /dev/ttyd1Be very careful about this entry. You must specify the
correct name for the device to which the mouse is connected.
xf86config is not specific to FreeBSD, and
the suggested example is just plain wrong for FreeBSD. Use
the names /dev/ttyd0 through
/dev/ttyd3 for serial mice,
/dev/psm0 for PS/2 mice or
/dev/mse0 for a bus mouse.Continuing, we see:Beginning with XFree86 3.1.2D, you can use the new X11R6.1
XKEYBOARD extension to manage the keyboard layout. If you answer 'n' to the
following question, the server will use the old method, and you have to
adjust your keyboard layout with xmodmap.
Please answer the following question with either 'y' or 'n'.
Do you want to use XKB? y
The following dialogue will allow you to select from a list of already
preconfigured keymaps. If you don't find a suitable keymap in the list,
the program will try to combine a keymap from additional information you
are asked then. Such a keymap is by default untested and may require
manual tuning. Please report success or required changes for such a
keymap to XFREE86@XFREE86.ORG for addition to the list of preconfigured
keymaps in the future.
Press enter to continue, or ctrl-c to abort.
List of preconfigured keymaps:
1 Standard 101-key, US encoding
2 Microsoft Natural, US encoding
3 KeyTronic FlexPro, US encoding
4 Standard 101-key, US encoding with ISO9995-3 extensions
5 Standard 101-key, German encoding
6 Standard 101-key, French encoding
7 Standard 101-key, Thai encoding
8 Standard 101-key, Swiss/German encoding
9 Standard 101-key, Swiss/French encoding
10 None of the above
Enter a number to choose the keymap.
1 Choose the standard US keyboardNow we want to set the specifications of the monitor. The
two critical parameters are the vertical refresh rate, which
is the rate at which the whole screen is refreshed, and
most importantly the horizontal sync rate, which is the rate
at which scanlines are displayed.The valid range for horizontal sync and vertical sync
should be documented in the manual of your monitor. If in
doubt, check the monitor database
/usr/X11R6/lib/X11/doc/Monitors to see if
your monitor is there.Press enter to continue, or ctrl-c to abort. ENTER
You must indicate the horizontal sync range of your monitor. You can either
select one of the predefined ranges below that correspond to industry-
standard monitor types, or give a specific range.
It is VERY IMPORTANT that you do not specify a monitor type with a horizontal
sync range that is beyond the capabilities of your monitor. If in doubt,
choose a conservative setting.
hsync in kHz; monitor type with characteristic modes
1 31.5; Standard VGA, 640x480 @@ 60 Hz
2 31.5 - 35.1; Super VGA, 800x600 @@ 56 Hz
3 31.5, 35.5; 8514 Compatible, 1024x768 @@ 87 Hz interlaced (no 800x600)
4 31.5, 35.15, 35.5; Super VGA, 1024x768 @@ 87 Hz interlaced, 800x600 @@ 56 Hz
5 31.5 - 37.9; Extended Super VGA, 800x600 @@ 60 Hz, 640x480 @@ 72 Hz
6 31.5 - 48.5; Non-Interlaced SVGA, 1024x768 @@ 60 Hz, 800x600 @@ 72 Hz
7 31.5 - 57.0; High Frequency SVGA, 1024x768 @@ 70 Hz
8 31.5 - 64.3; Monitor that can do 1280x1024 @@ 60 Hz
9 31.5 - 79.0; Monitor that can do 1280x1024 @@ 74 Hz
10 31.5 - 82.0; Monitor that can do 1280x1024 @@ 76 Hz
11 Enter your own horizontal sync range
Enter your choice (1-11):Unfortunately, our monitor is not mentioned in the file
/usr/X11R6/lib/X11/doc/Monitors, but by
chance the manual does specify the frequency range in the
Technical Data section. The horizontal frequency range is
from 30 to 64 kHz, and the vertical frequency range is from
50 to 100 Hz. The horizontal frequency range is almost
exactly covered by choice 8, but that setting threatens to go
0.3 kHz higher in frequency than the technical data state. Do
you want to risk it? Doing so will most likely not be a
problem, since it is unlikely that the monitor will die at
such a small deviation from the specs, and it is also unlikely
that your XF86Config will actually
generate a horizontal frequency between 64.0 and 64.3 kHz.
However, there is no need to take even this slight risk. Just
specify the real values:Enter your choice (1-11): 11
Please enter the horizontal sync range of your monitor, in the format used
in the table of monitor types above. You can either specify one or more
continuous ranges (e.g. 15-25, 30-50), or one or more fixed sync
frequencies.
Horizontal sync range: 30-64Next, we select the vertical frequency range:You must indicate the vertical sync range of your monitor.
You can either select one of the predefined ranges below that correspond
to industry-standard monitor types, or give a specific range. For
interlaced modes, the number that counts is the high one (e.g., 87 Hz
rather than 43 Hz).
1 50-70
2 50-90
3 50-100
4 40-150
5 Enter your own vertical sync range
Enter your choice: 3 exactly the range of the monitorThe next step is to specify identification strings. You
can think out names if you want, but unless you are juggling a
lot of different hardware, you can let
xf86config do it for you:You must now enter a few identification/description strings,
namely an identifier, a vendor name, and a model name. Just pressing enter
will fill in default names.
The strings are free-form, spaces are allowed.
Enter an identifier for your monitor definition: ENTER
Enter the vendor name of your monitor: ENTER
Enter the model name of your monitor: ENTERNext comes the choice of the video board. We have an
elderly Diamond SpeedStar Plus with an ET4000 chip, and
unknown Ramdac and Clock Chip. Let's see how we fare:Now we must configure video card specific settings. At
this point you can choose to make a selection out of a database of video
card definitions. Because there can be variation in Ramdacs and clock
generators even between cards of the same model, it is not sensible to
blindly copy the settings (e.g., a Device section). For this reason,
after you make a selection, you will still be asked about the components
of the card, with the settings from the chosen database entry presented as
a strong hint.
The database entries include information about the chipset, what server to
run, the Ramdac and ClockChip, and comments that will be included in the
Device section. However, a lot of definitions only hint about what server
to run (based on the chipset the card uses) and are untested.
If you can't find your card in the database, there's nothing to worry about.
You should only choose a database entry that is exactly the same model as
your card; choosing one that looks similar is just a bad idea (e.g. a
GemStone Snail 64 may be as different from a GemStone Snail 64+ in terms of
hardware as can be).
Do you want to look at the card database? y
0 2 the Max MAXColor S3 Trio64V+ S3 Trio64V+
1 928Movie S3 928
2 AGX (generic) AGX-014/15/16
3 ALG-5434(E) CL-GD5434
4 ASUS 3Dexplorer RIVA128
5 ASUS PCI-AV264CT ATI-Mach64
6 ASUS PCI-V264CT ATI-Mach64
7 ASUS Video Magic PCI V864 S3 864
8 ASUS Video Magic PCI VT64 S3 Trio64
9 AT25 Alliance AT3D
10 AT3D Alliance AT3D
11 ATI 3D Pro Turbo ATI-Mach64
12 ATI 3D Xpression ATI-Mach64
13 ATI 3D Xpression+ PC2TV ATI-Mach64
14 ATI 8514 Ultra (no VGA) ATI-Mach8
15 ATI All-in-Wonder ATI-Mach64
16 ATI Graphics Pro Turbo ATI-Mach64
17 ATI Graphics Pro Turbo 1600 ATI-Mach64
Enter a number to choose the corresponding card definition.
Press enter for the next page, q to continue configuration.
ENTERDozens of board definitions come in alphabetic order.
Finally we see:108 DSV3325 S3 ViRGE
109 DSV3326 S3 Trio64V+
110 DataExpert DSV3325 S3 ViRGE
111 DataExpert DSV3365 S3 Trio64V+
112 Dell S3 805 S3 801/805
113 Dell onboard ET4000 ET4000
114 Diamond Edge 3D nv1
115 Diamond Multimedia Stealth 3D 2000 S3 ViRGE
116 Diamond Multimedia Stealth 3D 2000 PRO S3 ViRGE/DX
117 Diamond SpeedStar (Plus) ET4000
118 Diamond SpeedStar 24 ET4000
119 Diamond SpeedStar 24X (not fully supported) WD90C31
120 Diamond SpeedStar 64 CL-GD5434
121 Diamond SpeedStar HiColor ET4000
122 Diamond SpeedStar Pro (not SE) CL-GD5426/28
123 Diamond SpeedStar Pro 1100 CL-GD5420/2/4/6/8/9
124 Diamond SpeedStar Pro SE (CL-GD5430/5434) CL-GD5430/5434
125 Diamond SpeedStar64 Graphics 2000/2200 CL-GD5434
Enter a number to choose the corresponding card definition.
Press enter for the next page, q to continue configuration.
117
Your selected card definition:
Identifier: Diamond SpeedStar (Plus)
Chipset: ET4000
Server: XF86_SVGA
Press enter to continue, or ctrl-c to abort.ENTER
Now you must determine which server to run. Refer to the man pages and
other documentation. The following servers are available (they may not
all be installed on your system):
1 The XF86_Mono server. This a monochrome server that should work on any
VGA-compatible card, in 640x480 (more on some SVGA chipsets).
2 The XF86_VGA16 server. This is a 16-color VGA server that should work on
any VGA-compatible card.
3 The XF86_SVGA server. This is a 256 color SVGA server that supports
a number of SVGA chipsets. On some chipsets it is accelerated or
supports higher color depths.
4 The accelerated servers. These include XF86_S3, XF86_Mach32, XF86_Mach8,
XF86_8514, XF86_P9000, XF86_AGX, XF86_W32, XF86_Mach64, XF86_I128 and
XF86_S3V.
These four server types correspond to the four different "Screen" sections in
XF86Config (vga2, vga16, svga, accel).
5 Choose the server from the card definition, XF86_SVGA.
Which one of these screen types do you intend to run by default (1-5)?The system already chose XF86_SVGA for us. Do we want to
change? We would need a good reason. In this case, we do not
have a reason, so we will keep the server from the card
definition:Which one of these screen types do you intend to run by default (1-5)? 5
The server to run is selected by changing the symbolic link 'X'. For example,
the SVGA server.
Please answer the following question with either 'y' or 'n'.
Do you want me to set the symbolic link? yAll the programs that start X (xinit, startx, and xdm)
start a program /usr/X11R6/bin/X. This
symbolic link makes /usr/X11R6/bin/X
point to your X server. If you don't have a link, you will
not be able to start X.Now you must give information about your video card. This
will be used for the "Device" section of your video card in XF86Config.
You must indicate how much video memory you have. It is probably a good
idea to use the same approximate amount as that detected by the server you
intend to use. If you encounter problems that are due to the used server
not supporting the amount memory you have (e.g. ATI Mach64 is limited to
1024K with the SVGA server), specify the maximum amount supported by the
server.
How much video memory do you have on your video card:
1 256K
2 512K
3 1024K
4 2048K
5 4096K
6 Other
Enter your choice: 3
You must now enter a few identification/description strings, namely an
identifier, a vendor name, and a model name. Just pressing enter will fill
in default names (possibly from a card definition).
Your card definition is Diamond SpeedStar (Plus).
The strings are free-form, spaces are allowed.
Enter an identifier for your video card definition: ENTER
You can simply press enter here if you have a generic card, or want to
describe your card with one string.
Enter the vendor name of your video card: ENTER
Enter the model (board) name of your video card: ENTER
Especially for accelerated servers, Ramdac, Dacspeed and ClockChip settings
or special options may be required in the Device section.
The RAMDAC setting only applies to the S3, AGX, W32 servers, and some
drivers in the SVGA servers. Some RAMDAC's are auto-detected by the server.
The detection of a RAMDAC is forced by using a Ramdac "identifier" line in
the Device section. The identifiers are shown at the right of the following
table of RAMDAC types:
1 AT&T 20C490 (S3 and AGX servers, ARK driver) att20c490
2 AT&T 20C498/21C498/22C498 (S3, autodetected) att20c498
3 AT&T 20C409/20C499 (S3, autodetected) att20c409
4 AT&T 20C505 (S3) att20c505
5 BrookTree BT481 (AGX) bt481
6 BrookTree BT482 (AGX) bt482
7 BrookTree BT485/9485 (S3) bt485
8 Sierra SC15025 (S3, AGX) sc15025
9 S3 GenDAC (86C708) (autodetected) s3gendac
10 S3 SDAC (86C716) (autodetected) s3_sdac
11 STG-1700 (S3, autodetected) stg1700
12 STG-1703 (S3, autodetected) stg1703
Enter a number to choose the corresponding RAMDAC.
Press enter for the next page, q to quit without selection of a RAMDAC.
q We don't need this
A Clockchip line in the Device section forces the detection of a
programmable clock device. With a clockchip enabled, any required
clock can be programmed without requiring probing of clocks or a
Clocks line. Most cards don't have a programmable clock chip.
Choose from the following list:
1 Chrontel 8391 ch8391
2 ICD2061A and compatibles (ICS9161A, DCS2824) icd2061a
3 ICS2595 ics2595
4 ICS5342 (similar to SDAC, but not completely compatible) ics5342
5 ICS5341 ics5341
6 S3 GenDAC (86C708) and ICS5300 (autodetected) s3gendac
7 S3 SDAC (86C716) s3_sdac
8 STG 1703 (autodetected) stg1703
9 Sierra SC11412 sc11412
10 TI 3025 (autodetected) ti3025
11 TI 3026 (autodetected) ti3026
12 IBM RGB 51x/52x (autodetected) ibm_rgb5xx
Just press enter if you don't want a Clockchip setting.
What Clockchip setting do you want (1-12)? ENTER
For most configurations, a Clocks line is useful since it prevents the slow
and nasty sounding clock probing at server start-up. Probed clocks are
displayed at server startup, along with other server and hardware
configuration info. You can save this information in a file by running
imprecise; some clocks may be slightly too high (varies per run).
At this point I can run X -probeonly, and try to extract the clock information
from the output. It is recommended that you do this yourself and add a clocks
line (note that the list of clocks may be split over multiple Clocks lines) to
your Device section afterwards. Be aware that a clocks line is not
appropriate for drivers that have a fixed set of clocks and don't probe by
default (e.g. Cirrus). Also, for the P9000 server you must simply specify
clocks line that matches the modes you want to use. For the S3 server with
a programmable clock chip you need a 'ClockChip' line and no Clocks line.
You must be root to be able to run X -probeonly now.
Do you want me to run 'X -probeonly' now?This last question is worth thinking about. You should
run X -probeonly at some point, but it requires some extra
work. We'll take the recommendation and try it later.Do you want me to run 'X -probeonly' now? n
For each depth, a list of modes (resolutions) is defined. The default
resolution that the server will start-up with will be the first listed
mode that can be supported by the monitor and card.
Currently it is set to:
"640x480" "800x600" "1024x768" for 8bpp
"640x480" "800x600" for 16bpp
"640x480" for 24bpp
"640x400" for 32bpp
Note that 16, 24 and 32bpp are only supported on a few configurations.
Modes that cannot be supported due to monitor or clock constraints will
be automatically skipped by the server.
1 Change the modes for 8pp (256 colors)
2 Change the modes for 16bpp (32K/64K colors)
3 Change the modes for 24bpp (24-bit color, packed pixel)
4 Change the modes for 32bpp (24-bit color)
5 The modes are OK, continue.
Enter your choice: 5 accept the defaults
You can have a virtual screen (desktop), which is screen area that is larger
than the physical screen and which is panned by moving the mouse to the edge
of the screen. If you don't want virtual desktop at a certain resolution,
you cannot have modes listed that are larger. Each color depth can have a
differently-sized virtual screen
Please answer the following question with either 'y' or 'n'.
Do you want a virtual screen that is larger than the physical screen? nIt is difficult to decide whether you want a virtual
screen larger than the physical screen. I find it extremely
disturbing, so I suggest you answer n. You might find it
useful, especially if your highest resolution is small.Now the configuration is complete, and
sysinstall just need to write the
configuration file:I am going to write the XF86Config file now. Make sure
you don't accidently overwrite a previously configured one.
Shall I write it to /etc/XF86Config? y
File has been written. Take a look at it before running 'startx'. Note that
the XF86Config file must be in one of the directories searched by the server
(e.g. /usr/X11R6/lib/X11) in order to be used. Within the server press
ctrl, alt and '+' simultaneously to cycle video resolutions. Pressing ctrl,
alt and backspace simultaneously immediately exits the server (use if
the monitor doesn't sync for a particular mode).
For further configuration, refer to /usr/X11R6/lib/X11/doc/README.Config.Once you have completed this configuration, you are ready to
start X.XFree86 4.x ConfigurationIntroductionThis chapter will introduce the steps necessary to install
and configure the XFree86 X Windows System under FreeBSD.
Once your server is installed and configured properly. you can
read to setup your desktop
environment.XFree86 4.xXFree86Before You StartBefore the user is to start configuration of XFree86-4,
the the following information will need to be known about the
target system:Monitor specificationsVideo Adapter chipsetVideo Adapter memoryhorizontal scan ratevertical scan rateThe specifications for the target system's monitor are
used by XFree86 to determine the resolution and refresh rate
to run at. These specifications can usually be obtained from
the documentation that came with your monitor or from the
manufacturer's website. There are two ranges of numbers that
are needed, the horizontal scan rate and the vertical
synchronization rate.The video adapter's chipset defines what driver module
XFree86 uses to talk to the graphics hardware. With most
chipsets, this can be automatically determined, but it is still
useful to know in case the automatic detection doesn't work
correctly.Video memory on the graphic adapter determines the
resolution and color depth the target system can run at. This
is important to know so the user knows the limitations of the
target system.Installing XFree86 4.x software
+ Contributed by &a.cshumway;, July 2001.
+
+
XFree86 4 can be installed using the FreeBSD ports system
or using &man.pkg.add.1;. If the user is building XFree86-4
from source and has USA_RESIDENT set in
/etc/make.conf, the user may first have to
fetch Wraphelp.c if XDM-AUTHORIZATION-1
support is desired.Configuring XFree86 4.xConfiguration of XFree86 4.1 is a several step process.
The first step is to build an initial configuration file with
the configure option to XFree86. As the super user, simply run:&prompt.root; XFree86 -configureThis will generate a skeleton XFree86 configuration file
in the current working directory called XF86Config.new. The
XFree86 program will attempt to probe the graphics hardware on
the system and will write a configuration file to load the
proper drivers for the detected hardware on the target system.The next step is to test the currently existing
configuration to verify that XFree86 can work with the graphics
hardware on the target system. To preform this task, the user
needs to run:&prompt.root; XFree86 -xf86config XF86Config.newIf the user is presented with a black and grey grid and an
X mouse cursor, then the configuration was successful. To exit
the test, just press ctrl, alt and backspace simultaneously.XFree86 4 TuningNext, the user needs to tune the
XF86Config.new configuration file to their
personal taste. Open up the file in a text editor such as
&man.emacs.1; or &man.ee.1;. The first thing the user will want to
do is add the frequencies for the target system's monitor.
These are usually expressed as a horizontal and vertical
synchronization rate. These values are added to the
XF86Config.new file under the "Monitor"
section as such:Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
Horizsync 30-107
VertRefresh 48-120
EndSectionThe Horizsync and
VertRefresh keywords may not exist in the
user's configuration file. If they do not, they need to be
added, with the correct horizontal synchronization rate placed
after the Horizsync keyword and the vertical
synchronization rate after the VertRefresh
keyword. In the example above the target monitor's rates where
entered.XF86ConfigWhile the XF86Config.new
configuration file is still open in an editor, next the user
needs to select what the default resolution and color depth is
desired. This is defined in the Screen
section.Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultColorDepth 24
SubSection "Display"
Depth 24
Modes "1024x768"
EndSubSection
EndSectionThe DefaultColorDepth keyword describes
the color depth the user wishes to run at by default. This can
be overridden with the -bpp command line
switch to XFree861. The Modes keyword describes the
resolution the user wishes to run at for the given color depth.
In the example above, the default color depth is twenty four
bits per pixel. At this color depth, the accepted resolution is
one thousand twenty four pixels by seven hundred and sixty eight
pixels.If a user wants to run at a resolution of one thousand
twenty four pixels by seven hundred sixty eight pixels at twenty
four bits per pixel, then the user needs to add the
DefaultColorDepth keyword with the value of
twenty four, and add to the "Display"
subsection with the desired Depth the Modes keyword with the
resolution the user wishes to run at. Note that only VESA
standard modes are supported as defined by the target system's
graphics hardware.Finally, the user can write out the configuration file and
test it using the test mode given above. If all is well, then
the configuration file needs to be installed in a common
location where XFree861 can source it in the future.
This is typically /etc/X11/XF86Config or
/usr/X11R6/etc/X11/XF86Config.&prompt.root; cp XF86Config.new /etc/X11/XF86ConfigOnce the configuration file has been placed in a common
location, XFree86 can then be used through &man.xdm.1;. In
order to use startx1 the user will have to install
the X11/wrapper port.Advanced Configuration TopicsConfiguration with Intel i810 graphics chipsetsIntel i810 graphic chipsetConfiguration with Intel i810 integrated chipsets
requires the agpgart AGP programming interface for XFree86 to
be able to drive the card. To enable the agpgart programming
interface, the agp.ko kernel loadable
module needs to be loaded into the kernel with
&man.kldload.8;. This can be done automatically with the
&man.loader.8;. Simply add this line to
/boot/loader.conf to have the loader load
agp.ko at boot time:agp_load="YES"Next, a device node needs to be created for the
programming interface. To create the agp device node, run
&man.MAKEDEV.8; in the /dev directory as
such:&prompt.root; cd /dev
&prompt.root; sh MAKEDEV agpgartThis will allow the user to configure the graphics
hardware as any other graphics board.Using Fonts in XFree86Type1 FontsThe default fonts that ship with
XFree86 are less than ideal for typical
desktop publishing applications. Large presentation fonts show up
jagged and unprofessional looking and small fonts in Netscape are
almost completely unintelligible. However, there are several
free, high quality Type1 (PostScript) fonts available which
can be readily used
with XFree86, either version 3.x or
version 4.x. For instance, the URW font collection
(/usr/ports/x11-fonts/urwfonts) includes
high quality versions of standard type1 fonts (Times Roman,
Helvetica, Palatino and others). The Freefont collection
(/usr/ports/x11-fonts/freefont) includes
many more fonts, but most of them are intended for use in
graphics software such as the Gimp, and are not complete
enough to serve as screen fonts. In addition,
XFree86 can be configured to use
TrueType fonts with a minimum of effort: see the
section on TrueType fonts later.To install the above Type1 font collections from the ports
collection you can run the following commands.&prompt.root; cd /usr/ports/x11-fonts/urwfonts
&prompt.root; make install cleanAnd likewise with the freefont or other collections. To tell the X server
that these fonts exist, you can add an appropriate line
to your XF86Config file (in
/etc/ for XFree86
version 3, or in /etc/X11/ for version 4),
which reads:FontPath "/usr/X11R6/lib/X11/fonts/URW/"Alternatively, at the command line in your X session you can
write:&prompt.user; xset fp+ /usr/X11R6/lib/X11/fonts/URW
&prompt.user; xset fp rehashThis will work but will be lost when you log out from this
session, unless you add it to your startup file
(~/.xinitrc for a normal startx session,
or ~/.xsession when logging in through a
graphical login manager like XDM).
A third way is to use the new
XftConfig file: see the
section on anti-aliasing, later.
TrueType FontsXFree86 4.0 has built in support
for rendering TrueType fonts. There are two different modules
that can enable this functionality. The "freetype" module is used
in this example because it is more consistent with the other font
rendering backends. To enable the freetype module just add the
following line to the module section of your
/etc/X11/XF86Config file.Load "freetype"For XFree86 3.3.X you will need
to run a separate TrueType font
server. Xfstt is commonly used for
this purpose. To install Xfstt on
your FreeBSD system simply install the port from
/usr/ports/x11-servers/XfsttYou should now make a directory for your TrueType fonts
(e.g. /usr/X11R6/lib/X11/fonts/TrueType)
and copy all of your TrueType fonts into this directory. Keep in
mind that you can not take TrueType fonts directly from a
Macintosh; they must be in Unix/DOS/Windows format for use by
XFree86. Once you have copied the
files into this directory you need to use
ttmkfdir to create a
fonts.dir file so that the X font renderer
knows that you've installed these new files. There is a FreeBSD
port for ttmkfdir in
/usr/ports/x11-fonts/ttmkfdir.&prompt.root; cd /usr/X11R6/lib/X11/fonts/TrueType
&prompt.root; ttmkfdir > fonts.dirNow you need to add your TrueType directory to your fonts
path. This is just the same as described above for Type1 fonts, that is, use
&prompt.user; xset fp+ /usr/X11R6/lib/X11/fonts/TrueType
&prompt.user; xset fp rehash
or add a FontPath line to the XF86Config file.That's it. Now Netscape, Gimp, StarOffice, and all of your
other X applications should now recognize your installed
TrueType fonts. Extremely small fonts (as with text in a high
resolution display on a web page) and extremely large fonts
(within StarOffice) will look much better now.Anti-Aliasing your fontsStarting with version 4.0.2, XFree86 supports anti-aliased
fonts. Currently, most software has not been updated to take
advantage of this new functionality. However, Qt (the toolkit
for the KDE desktop) does; so if you are running XFree86 4.0.2
(or higher), Qt 2.3 (or higher) and KDE, all your KDE/Qt
applications can be made to use anti-aliased fonts.To configure anti-aliasing, you need to create (or edit, if
it already exists) the file
/usr/X11R6/lib/X11/XftConfig. Several
advanced things can be done with this file; this section
describes only the simplest possibilities.First, you need to tell the X server about the fonts which you
want anti-aliased. To do that, for each font directory you have
a line, which looks like this:dir "/usr/X11R6/lib/X11/Type1"And likewise for the other font directories (URW, truetype, etc)
containing fonts you'd like anti-aliased. Anti-aliasing makes
sense only for scalable fonts (basically, Type1 and TrueType) so
don't include bitmap font directories here. The
directories which you included here can now be commented out
of your XF86Config file.Next, you may not want to anti-alias normal-sized text.
(Antialiasing makes borders slightly fuzzy, which makes very
small text more readable and removes "staircases" from large text,
but can cause eyestrain if applied to normal text.) To exclude
point sizes between 9 and 13 from anti-aliasing, include these
lines:match
any size > 8
any size < 14
edit
antialias = false;You may also find that the spacing for some monospaced fonts
gets messed up when you turn on anti-aliasing. This seems to
be an issue with KDE, in particular. One possible fix for this
is to force the spacing for such fonts to be 100: add the
following lines:match any family == "fixed" edit family =+ "mono";
match any family == "console" edit family =+ "mono";(this aliases the other common names for fixed fonts as "mono"),
and then add:match any family == "mono" edit spacing = 100;Supposing you want to use the Lucidux fonts whenever monospaced
fonts are required (these look nice, and don't seem to suffer
from the spacing problem), you could replace that last line
with these:match any family == "mono" edit family += "LuciduxMono";
match any family == "Lucidux Mono" edit family += "LuciduxMono";
match any family == "LuciduxMono" edit family =+ "Lucidux Mono";(the last lines alias different equivalent family names).Finally, you want to allow users to add commands to this
file, via their personal .xftconfig
files. To do this, add a last line:includeif "~/.xftconfig"That's all; anti-aliasing should be enabled the next
time you start the X server. However, note that your programs must
know how to take advantage of it. At the present time, the toolkit
Qt does, so the entire KDE environment can use anti-aliased fonts
(see on KDE for
details); there are patches for gtk+ to do the same,
so if compiled against such a patched gtk+, the GNOME environment
and Mozilla can also use anti-aliased fonts.Anti-aliasing is still new to FreeBSD and XFree86;
configuring it should get easier with time, and it will soon be
supported by many more applications.The X Display ManagerOverviewThe X Display Manager (XDM) is an optional part of the X
Window System that is used for login session management. This is
useful for several types of situations, including minimal
X Terminals (see
), desktops, and large network display
servers. Since the X Window System is network and protocol
independent, there are a wide variety of possible configurations
for running X clients and servers on different machines
connected by a network. XDM provides a graphical interface for
choosing which display server to connect to, and entering
authorization information such as a login and password
combination.You may think of XDM as providing the same functionality to
the user as the &man.getty.8; utility (see for details). That is, it performs system
logins to the display being connected to and then runs a session
manager on behalf of the user (usually an X window manager). XDM
then waits for this program to exit, signaling that the user is
done and should be logged out of the display. At this point, XDM
can display the login and display chooser screens for the next
user to login.Using XDMThe XDM daemon program is located in
/usr/X11R6/bin/xdm. You can run this
program at any time as root and it will start managing the X
display on the local machine. If you want XDM to run in the
background every time the machine boots up, a convenient way to
do this is by adding an entry to /etc/ttys.
For more information about the format and usage of this file,
see . There is a line in the
default /etc/ttys file for running the xdm
daemon on a virtual terminal:
ttyv8 "/usr/X11R6/bin/xdm -nodaemon" xterm off secure
By default this entry is disabled, and in order to enable it you
will need to change field 5 from off to
on and then restart &man.init.8; using the
directions in . The first field, the
name of the terminal this program will manage, is
ttyv8. This means that XDM will start running
on the 9th virtual terminal.Configuring XDMThe XDM configuration directory is located in
/usr/X11R6/lib/X11/xdm. In this directory
you will see several files used to change the behavior and
appearance of XDM. Typically you will find these files:FileDescriptionXaccessClient authorization ruleset.XresourcesDefault X resource values.XserversList of remote and local displays to manage.XsessionDefault session script for logins.Xsetup_*xdm-configGlobal configuration for all displays running on
this machine.xdm-errorsErrors generated by the server program.xdm-pidThe process ID of the currently running XDM.Also in this directory are a few scripts and programs used
to setup the desktop when XDM is running. In the next few
sections I will briefly describe the purpose of each of these
files. The exact syntax and usage of all of these files is
described in &man.xdm.1;The default configuration is a simple rectangular login
window with the hostname of the machine displayed at the top in
a large font and Login: and
Password: prompts below. This is a good starting
point if you are planning to design your own look and feel for
the XDM screens.XaccessThe protocol for connecting to XDM controlled displays is
called the X Display Manager Connection Protocol (XDMCP). This
file is basically just a ruleset for controlling XDMCP
connections from remote machines. By default, it allows any
client to connect, but you will see this will not matter
because the default xdm-config file does not listen for remote
connections.XresourcesThis is an application-defaults file for the display
chooser and the login screens. This is where you can customize
the appearance of the login program. The format is identical
to the app-defaults file described in the XFree86
documentation.XserversThis is a list of the remote displays the chooser should
provide as choices.XsessionThis is the default session script for XDM to run after a
user has logged in. Normally each user will have a customized
session script in ~/.xsessionrc that
overrides this script.Xsetup_*These files contain scripts that will be run automatically
before displaying the chooser or login interfaces. There is a
script for each display being used, named
Xsetup_followed by the local display
number (for instance Xsetup_0). Typically
these scripts will run one or two programs in the background
such as xconsole.xdm-configThis file contains settings in the form of app-defaults
that are applicable to every display that this installation
manages.xdm-errorsThis file contains the output of the X servers that XDM is
trying to run. If a display that XDM is trying to start hangs
for some reason, this is a good place to look for error
messages. These messages are also written to the user's
~/.xsession-errors file on a per-session basisRunning A Network Display ServerIn order for other clients to connect to your display
server, you will need to edit the access control rules, and
enable the connection listener. By default these are set to
conservative values, which is a good decision security-wise. To
get XDM to listen for connections first comment out a line in
the xdm-config file:
! SECURITY: do not listen for XDMCP or Chooser requests
! Comment out this line if you want to manage X terminals with xdm
DisplayManager.requestPort: 0
and then restart XDM. Remember that comments in app-defaults
files begin with a ! character, not a
#. After this, you may need to put more strict
access controls in place. Look at the example entries in
Xaccess file, and refer to the &man.xdm.1;
manual page.Replacements for XDMSeveral replacements for the default XDM program exist.
One of them, KDM (bundled with KDE) is described in a later
section. Apart from
various visual improvements and cosmetic frills, it can be
easily configured to let users choose their window manager of
choice at the time they log in.Desktop EnvironmentsWritten by &a.logo;, June 2001This section describes the different desktop environments
available for X-Windows on FreeBSD. For our purposes a "desktop
environment" will mean anything ranging from a simple window
manager, to a complete suite of desktop applications such as KDE
or GNOME.GNOMEAbout GNOMEGNOME is a user-friendly desktop environment that
enables users to easily use and configure their computers.
GNOME includes a panel (for starting applications and displaying
status), a desktop (where data and applications can be placed),
a set of standard desktop tools and applications, and a set of
conventions that make it easy for applications to cooperate and
be consistent with each other. Users of other operating systems
or environments should feel right at home using the powerful
graphics-driven environment that GNOME provides.Installing GNOMETo install GNOME from the network, simply type:&prompt.root; pkg_add -r gnomeIf you would rather build GNOME from source, then use
the ports tree:&prompt.root; cd /usr/ports/x11/gnome
&prompt.root; make install cleanOnce GNOME is installed, we must have the X server start
GNOME instead of a default window mananger. If you have
already customized your .xinitrc file
then you should simply replace the line that starts your
current window manager with one that starts
/usr/X11R6/bin/gnome-wm instead. If
you haven't added anything special to your configuration
file, then it is enough to simply type:&prompt.root; echo "/usr/X11R6/bin/gnome-wm" > ~/.xinitrcThat's it. Type 'startx' and you will be in the
GNOME desktop environment. Note: if you're running a display manager like xdm,
this will not work. Instead, you should create an
executable .xsession file with the same
command in it. To do this, edit your file (if you already
have one) and replace the existing wm command with
/usr/X11R6/bin/gnome-wm; or
else,&prompt.root; echo "#!/bin/sh" > ~/.xsession
&prompt.root; echo "/usr/X11R6/bin/gnome-wm" >> ~/.xsession
&prompt.root; chmod +x ~/.xsessionAnother option is to configure your display manager to
allow choosing the window manager at login time; the section on
KDE2 details
explains how to do this for kdm, the
display manager of KDE.KDE2About KDE2KDE is an easy to use contemporary desktop environment.
Some of the things that KDE brings to the user are:A beautiful contemporary desktopA desktop exhibiting complete network transparencyAn integrated help system allowing for convenient,
consistent access to help on the use of the KDE desktop and its
applicationsConsistent look and feel of all KDE applicationsStandardized menu and toolbars, keybindings, color-schemes, etc.Internationalization: KDE is available in more than 40 languagesCentralized consisted dialog driven desktop configurationA great number of useful KDE applicationsKDE has an office application suite based on KDE's
KParts technology consisting of a spread-sheet, a
presentation application, an organizer, a news client and
more. KDE is also comes with a web browser called Konqeuror,
which represents already a solid competitor to other
existing web browsers on Unix systems. More information on
KDE can be found on the KDE
websiteInstalling KDE2At the time of writing, a package for kde2 doesn't
exist yet. No problem! The ports tree hides all the
complexity of building a package from source. To install
KDE2, do this :&prompt.root; cd /usr/ports/x11/kde2
&prompt.root; make install cleanThis command will fetch all the necessary files from the
Internet, configure and compile KDE2, install the
applications, and then clean up after itself.Now you're going to have to tell the X server to launch
KDE2 instead of a default window manager. Do this by typing
this:&prompt.root; echo "/usr/X11R6/bin/startkde" > ~/.xinitrcNow, whenever you go into X-Windows, KDE2 will be your
desktop. (Note: this will not work if you're logging in via
a display manager like xdm. In that
case you have two options: create an
.xsession file as described in the
section on GNOME, but
with the /usr/X11R6/bin/startkde
command instead of the gnome-wm
command; or, configure your display manager to allow
choosing a desktop at login time. Below it is explained how
to do this for kdm, KDE's display
manager.)More details on KDE2Now that KDE2 is installed on your system, you'll find
that you can learn a lot from its help pages, or just by
pointing and clicking at various menus. Windows or Mac
users will feel quite at home.The best reference for KDE is the on-line documentation.
KDE comes with its own web browser, Konqueror, dozens of
useful applications, and extensive documentation. This
section only discusses somewhat technical things which are
difficult to learn just by random exploration.The KDE display managerIf you're an administrator on a multi-user system, you
may like to have a graphical login screen to welcome users.
You can use xdm, as
described earlier. However, KDE includes an alternative,
kdm, which is designed to look more attractive and include
more login-time options. In particular, users can easily
choose (via a menu) which desktop environment (KDE2, GNOME,
or something else) to run after logging on. If you're slightly
adventurous and you want this added flexibility and visual
appeal, read on.To begin with, run the KDE2 control panel,
kcontrol, as root. Note: it is
generally considered unsafe to run your entire X environment
as root. Instead, run your window manager as a normal user,
open a terminal window (such as xterm
or KDE's konsole, become root with
su (you need to be in the "wheel"
group in /etc/group for this), and then
type kcontrol. Click on the icon on the left marked "System", then on
"Login manager". On the right you'll see various
configurable options, which the KDE manual will explain in
greater detail. Click on "sessions" on the right.
Depending on what window managers or desktop environments
you have currently installed, you can type their names in
"New type" and add them. (These are just labels so far, not
commands, so you can write "KDE" and "GNOME" rather than
"startkde" or "gnome-wm".) Include a label
"failsafe". Play with the other menus as you like (those are mainly
cosmetic and self-explanatory). When you're done, click on
"Apply" at the bottom, and quit the control center. To make sure kdm understands what your above labels
(KDE, GNOME etc) mean, you need to edit some more files: the
same ones used by xdm. In your
terminal window, as root, edit the file
/usr/X11R6/lib/X11/xdm/Xsession. You
will come across a section in the middle looking like this
(by default):case $# in
1)
case $1 in
failsafe)
exec xterm -geometry 80x24-0-0
;;
esac
esacYou will need to add a few lines to this section.
Assuming the labels you gave earlier were KDE2 and GNOME,
the following will do:case $# in
1)
case $1 in
KDE2)
exec /usr/X11R6/bin/startkde
;;
GNOME)
exec /usr/X11R6/bin/gnome-wm
;;
failsafe)
exec xterm -geometry 80x24-0-0
;;
esac
esacTo make sure your KDE choice of a login-time desktop
background is also honored, you will need to add the
following line to
/usr/X11R6/lib/X11/xdm/Xsetup_0:/usr/X11R6/bin/kdmdesktopNow, you need only to make sure kdm is started at the
next bootup. To learn how to do this, read the section on
xdm, and do the same thing
replacing references to the xdm program
by kdm.That's it. Your next login screen should have a pretty
face and lots of menus.Anti-aliased fontsTired of blocky staircase edges to your fonts under X11?
Tired of unreadable text in web browsers? Well, no
more.Starting with version 4.0.2, XFree86 supports
anti-aliasing via its "RENDER" extension, and starting with
version 2.3, Qt (the toolkit used by KDE) supports this
extension. Configuring this is described in on antialiasing X11 fonts.
So if you're running up-to-date software,
anti-aliasing is possible on your KDE2 desktop. Just go to
your KDE2 menu, go to Preferences -> Look and Feel -> Style,
and click on the checkbox "Use Anti-Aliasing for Fonts and
Icons". That's all. If you're running a Qt application
which is not part of KDE, you may need to set the
environment variable QT_XFT to true before starting your
program.XFCEAbout XFCEXFCE is based on the gtk+ toolkit used by GNOME, but is
much more lightweight and meant for those who want a simple,
efficient desktop which is nevertheless easy to use and
configure. Visually, it looks very much like CDE, found on
commercial Unix systems.
Some of XFCE's features are:A simple, easy-to-handle desktopFully configurable via mouse, with drag and
drop, etc Main panel similar to CDE, with menus, applets and
app launchersIntegrated window manager, file manager,
sound manager, GNOME compliance module, and other things Themable (since it uses gtk+) Fast, light and efficient: ideal for
older/slower machines or machiens with memory limitations More information on
XFCE can be found on the XFCE
website.Installing XFCEA binary package for xfce exists (at the time of
writing). To install, simply do this:&prompt.root; pkg_add -r xfce Alternatively, you may prefer to build from source.
The ports tree comes to the rescue again: &prompt.root; cd /usr/ports/x11-wm/xfce
&prompt.root; make install clean All necessary source packages (including dependencies)
will be automagically fetched, built and installed, and
the build areas cleaned up afterwards.Now you want to tell the X server to launch
XFCE the next time you start X. Simply type
this:&prompt.root; echo "/usr/X11R6/bin/startxfce" > ~/.xinitrcThe next time you start X, XFCE will be your
desktop. (Note, as before:
if you're logging in via a display manager like
xdm, you should either create an
.xsession, as described in the
section on GNOME, but
with the /usr/X11R6/bin/startxfce
command; or, configure your display manager to allow
choosing a desktop at login time, as explained in
the section on kdm.)
diff --git a/en_US.ISO8859-1/share/sgml/authors.ent b/en_US.ISO8859-1/share/sgml/authors.ent
index 8b4b487c37..b72bcd2587 100644
--- a/en_US.ISO8859-1/share/sgml/authors.ent
+++ b/en_US.ISO8859-1/share/sgml/authors.ent
@@ -1,646 +1,648 @@
abial@FreeBSD.org">
ache@FreeBSD.org">
adam@FreeBSD.org">
ade@FreeBSD.org">
adrian@FreeBSD.org">
akiyama@FreeBSD.org">
alc@FreeBSD.org">
alex@FreeBSD.org">
alfred@FreeBSD.org">
amurai@FreeBSD.org">
andreas@FreeBSD.org">
andy@FreeBSD.org">
archie@FreeBSD.org">
asami@FreeBSD.org">
asmodai@FreeBSD.org">
assar@FreeBSD.org">
ats@FreeBSD.org">
awebster@pubnix.net">
babkin@FreeBSD.org">
bde@FreeBSD.org">
ben@FreeBSD.org">
bean@FreeBSD.org">
benno@FreeBSD.org">
billf@FreeBSD.org">
bmah@FreeBSD.org">
bmilekic@FreeBSD.org">
bp@FreeBSD.org">
brandon@FreeBSD.org">
brian@FreeBSD.org">
brooks@FreeBSD.org">
bsd@FreeBSD.org">
cawimm@FreeBSD.org">
cg@FreeBSD.org">
charnier@FreeBSD.org">
chern@FreeBSD.org">
chm@FreeBSD.org">
chris@FreeBSD.org">
chuckr@glue.umd.edu">
chuckr@FreeBSD.org">
cjc@FreeBSD.org">
cjh@FreeBSD.org">
clive@FreeBSD.org">
cp@FreeBSD.org">
cokane@FreeBSD.org">
cpiazza@FreeBSD.org">
cracauer@FreeBSD.org">
csgr@FreeBSD.org">
+cshumway@FreeBSD.org">
+
cwt@FreeBSD.org">
dan@FreeBSD.org">
danny@FreeBSD.org">
dannyboy@FreeBSD.org">
darrenr@FreeBSD.org">
davidn@blaze.net.au">
dbaker@FreeBSD.org">
dburr@FreeBSD.org">
dcs@FreeBSD.org">
dd@FreeBSD.org">
dec@FreeBSD.org">
deischen@FreeBSD.org">
demon@FreeBSD.org">
des@FreeBSD.org">
dfr@FreeBSD.org">
dg@FreeBSD.org">
dick@FreeBSD.org">
dillon@FreeBSD.org">
dinoex@FreeBSD.org">
dima@FreeBSD.org">
dirk@FreeBSD.org">
Dirk.vanGulik@jrc.it">
dmlb@FreeBSD.org">
DougB@FreeBSD.org">
dt@FreeBSD.org">
dufault@FreeBSD.org">
dwcjr@FreeBSD.org">
dwhite@FreeBSD.org">
dwmalone@FreeBSD.org">
dyson@FreeBSD.org">
eivind@FreeBSD.org">
ejc@FreeBSD.org">
eric@FreeBSD.org">
erich@FreeBSD.org">
faq@FreeBSD.org">
fenner@FreeBSD.org">
flathill@FreeBSD.org">
foxfair@FreeBSD.org">
fsmp@FreeBSD.org">
furuta@FreeBSD.org">
gad@FreeBSD.org">
gallatin@FreeBSD.org">
gclarkii@FreeBSD.org">
gena@NetVision.net.il">
ghelmer@cs.iastate.edu">
gibbs@FreeBSD.org">
gioria@FreeBSD.org">
gj@FreeBSD.org">
gpalmer@FreeBSD.org">
graichen@FreeBSD.org">
green@FreeBSD.org">
greid@FreeBSD.org">
grog@FreeBSD.org">
groudier@club-internet.fr">
gryphon@healer.com">
gshapiro@FreeBSD.org">
gsutter@FreeBSD.org">
guido@FreeBSD.org">
hanai@FreeBSD.org">
handy@sxt4.physics.montana.edu">
hrs@FreeBSD.org">
roger@freebsd.org">
helbig@FreeBSD.org">
hm@FreeBSD.org">
hoek@FreeBSD.org">
horikawa@FreeBSD.org">
hosokawa@FreeBSD.org">
hsu@FreeBSD.org">
iedowse@FreeBSD.org">
ijliao@FreeBSD.org">
imp@FreeBSD.org">
imura@FreeBSD.org">
issei@FreeBSD.org">
itojun@itojun.org">
iwasaki@FreeBSD.org">
jake@FreeBSD.org">
jasone@FreeBSD.org">
jayanth@FreeBSD.org">
jb@cimlogic.com.au">
jdp@FreeBSD.org">
jedgar@FreeBSD.org">
jeh@FreeBSD.org">
jehamby@lightside.com">
jesper@FreeBSD.org">
jesusr@FreeBSD.org">
jfieber@FreeBSD.org">
jfitz@FreeBSD.org">
jgreco@FreeBSD.org">
jhay@FreeBSD.org">
jhb@FreeBSD.org">
jhs@FreeBSD.org">
jim@FreeBSD.org">
jkh@FreeBSD.org">
jkoshy@FreeBSD.org">
jlemon@FreeBSD.org">
john@starfire.MN.ORG">
jlrobin@FreeBSD.org">
jmacd@FreeBSD.org">
jmas@FreeBSD.org">
jmb@FreeBSD.org">
jmg@FreeBSD.org">
jmz@FreeBSD.org">
joe@FreeBSD.org">
keichii@FreeBSD.org">
joerg@FreeBSD.org">
john@FreeBSD.org">
jon@FreeBSD.org">
jraynard@FreeBSD.org">
jseger@FreeBSD.org">
julian@FreeBSD.org">
jwd@FreeBSD.org">
jvh@FreeBSD.org">
karl@FreeBSD.org">
kato@FreeBSD.org">
kbyanc@FreeBSD.org">
keith@FreeBSD.org">
kelly@ad1440.net">
ken@FreeBSD.org">
kevlo@FreeBSD.org">
kiri@FreeBSD.org">
kjc@FreeBSD.org">
knu@FreeBSD.org">
kris@FreeBSD.org">
kuriyama@FreeBSD.org">
lars@FreeBSD.org">
lile@FreeBSD.org">
lioux@FreeBSD.org">
ljo@FreeBSD.org">
lkoeller@FreeBSD.org">
logo@blackened.com">
luigi@FreeBSD.org">
luoqi@FreeBSD.org">
marcel@FreeBSD.org">
markm@FreeBSD.org">
marko@FreeBSD.org">
markp@FreeBSD.org">
martin@FreeBSD.org">
max@FreeBSD.org">
mark@vmunix.com">
mb@FreeBSD.org">
mbarkah@FreeBSD.org">
mckay@FreeBSD.org">
mckusick@FreeBSD.org">
md@bsc.no">
winter@jurai.net">
mharo@FreeBSD.org">
mi@FreeBSD.org">
mikeh@FreeBSD.org">
mita@FreeBSD.org">
mjacob@FreeBSD.org">
mks@FreeBSD.org">
motoyuki@FreeBSD.org">
mph@FreeBSD.org">
mpp@FreeBSD.org">
msmith@FreeBSD.org">
mtaylor@FreeBSD.org">
murray@FreeBSD.org">
nakai@FreeBSD.org">
nate@FreeBSD.org">
nbm@FreeBSD.org">
nectar@FreeBSD.org">
newton@FreeBSD.org">
n_hibma@FreeBSD.org">
nik@FreeBSD.org">
non@FreeBSD.org">
nsayer@FreeBSD.org">
nsj@FreeBSD.org">
nsouch@FreeBSD.org">
nyan@FreeBSD.org">
obrien@FreeBSD.org">
okazaki@FreeBSD.org">
olah@FreeBSD.org">
olgeni@FreeBSD.org">
onoe@FreeBSD.org">
opsys@open-systems.net">
orion@FreeBSD.org">
patrick@FreeBSD.org">
paul@FreeBSD.org">
pb@fasterix.freenix.org">
pds@FreeBSD.org">
peter@FreeBSD.org">
phantom@FreeBSD.org">
phk@FreeBSD.org">
pho@FreeBSD.org">
piero@strider.inet.it">
pirzyk@FreeBSD.org">
pjchilds@imforei.apana.org.au">
proven@FreeBSD.org">
ps@FreeBSD.org">
pst@FreeBSD.org">
reg@FreeBSD.org">
rgrimes@FreeBSD.org">
rhuff@cybercom.net">
ricardag@ag.com.br">
rich@FreeBSD.org">
rnordier@FreeBSD.org">
roam@FreeBSD.org">
roberto@FreeBSD.org">
rse@FreeBSD.org">
ru@FreeBSD.org">
rv@FreeBSD.org">
rvb@FreeBSD.org">
rwatson@FreeBSD.org">
sada@FreeBSD.org">
sanpei@FreeBSD.org">
schweikh@FreeBSD.org">
scottl@FreeBSD.org">
scrappy@FreeBSD.org">
se@FreeBSD.org">
sef@FreeBSD.org">
semenu@FreeBSD.org">
seth.kingsley@windriver.com">
sf@FreeBSD.org">
shafeeq@FreeBSD.org">
sheldonh@FreeBSD.org">
shiba@FreeBSD.org">
shige@FreeBSD.org">
shin@FreeBSD.org">
silby@FreeBSD.org">
simokawa@FreeBSD.org">
smace@FreeBSD.org">
smpatel@FreeBSD.org">
sobomax@FreeBSD.org">
sos@FreeBSD.org">
adam@whizkidtech.net">
stark@FreeBSD.org">
stb@FreeBSD.org">
steve@FreeBSD.org">
sumikawa@FreeBSD.org">
swallace@FreeBSD.org">
tanimura@FreeBSD.org">
taoka@FreeBSD.org">
takawata@FreeBSD.org">
tedm@FreeBSD.org">
tegge@FreeBSD.org">
tg@FreeBSD.org">
thepish@FreeBSD.org">
tmm@FreeBSD.org">
tobez@FreeBSD.org">
tom@FreeBSD.org">
tomsoft@FreeBSD.org">
torstenb@FreeBSD.org">
toshi@FreeBSD.org">
trevor@FreeBSD.org">
truckman@FreeBSD.org">
tshiozak@FreeBSD.org">
uch@FreeBSD.org">
ue@FreeBSD.org">
ugen@FreeBSD.org">
uhclem@FreeBSD.org">
ulf@FreeBSD.org">
ume@FreeBSD.org">
unfurl@FreeBSD.org">
vanilla@FreeBSD.org">
wes@FreeBSD.org">
whiteside@acm.org">
wilko@FreeBSD.org">
will@FreeBSD.org">
wjv@FreeBSD.org">
wlloyd@mpd.ca">
wollman@FreeBSD.org">
wosch@FreeBSD.org">
wpaul@FreeBSD.org">
wsanchez@FreeBSD.org">
wylie@osd.bsdi.com">
yar@FreeBSD.org">
yokota@FreeBSD.org">