Sync with head.
This commit is contained in:
John Fieber
parent
f7c869a24d
commit
4c0228d53f
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/branches/RELENG_2_1_0/; revision=120
33 changed files with 648 additions and 339 deletions
FAQ
handbook
Makefileauthors.sgmlbasics.sgmlbibliography.sgmlbooting.sgmlcontrib.sgmlctm.sgmlcurrent.sgmldialup.sgmldiskless.sgmleresources.sgmlglossary.sgmlhandbook.sgmlhistory.sgmlhw.sgmlinstall.sgmlkerberos.sgmlkerneldebug.sgmlmemoryuse.sgmlmirrors.sgmlnfs.sgmlnutshell.sgmlporting.sgmlports.sgmlppp.sgmlrelnotes.sgmlscsi.sgmlsections.sgmlslipc.sgmlsubmitters.sgmlsup.sgmltroubleshooting.sgml
|
|
@ -4,7 +4,7 @@
|
|||
|
||||
<title>Frequently Asked Questions for FreeBSD 2.X
|
||||
<author>The FreeBSD FAQ Team, <tt/FAQ@FreeBSD.ORG/
|
||||
<date> $Id: freebsd-faq.sgml,v 1.4.4.1 1995-09-17 11:19:07 davidg Exp $
|
||||
<date> $Id: freebsd-faq.sgml,v 1.4.4.2 1995-10-12 03:18:14 jfieber Exp $
|
||||
<abstract>
|
||||
This is the FAQ for FreeBSD systems version 2.X All entries are
|
||||
assumed to be relevant to FreeBSD 2.0.5+, unless otherwise noted.
|
||||
|
|
@ -952,6 +952,19 @@ options PSM_NO_RESET #don't reset mouse hardware (some laptops)
|
|||
phone +1(303)384-9999
|
||||
</descrip>
|
||||
|
||||
<sect1>
|
||||
<heading>Are there any Database systems for FreeBSD?</heading>
|
||||
<p>
|
||||
Yes! Conetic Software Systems has ported their C/base and C/books
|
||||
datebase systems to FreeBSD 2.0.5 and higher.
|
||||
|
||||
<descrip>
|
||||
<tag/For more information/
|
||||
<url url="http://www.conetic.com/" name="Conetic Software Systems">
|
||||
<tag/or mail/
|
||||
<url url="mailto:info@conetic.com" name="Information E-mail address">
|
||||
</descrip>
|
||||
|
||||
<sect1>
|
||||
<heading>Any other applications I might be interested in?</heading>
|
||||
|
||||
|
|
@ -1683,6 +1696,15 @@ disk fd1 at fdc0 drive 1
|
|||
<verb>
|
||||
mount -o -P linuxbox:/blah /mnt
|
||||
</verb>
|
||||
<sect1>
|
||||
<heading>Why can't I NFS-mount from a Sun box?</heading>
|
||||
|
||||
<p>
|
||||
Sun workstations running SunOS 4.X only accept mount requests
|
||||
from a priviledged port; try
|
||||
<verb>
|
||||
mount -o -P sunbox:/blah /mnt
|
||||
</verb>
|
||||
|
||||
<sect1>
|
||||
<heading>I want to enable IP multicast support on my FreeBSD box, how do I do it? (Alternatively: What the heck IS multicasting and what applications make use of it?)</heading>
|
||||
|
|
@ -1994,6 +2016,14 @@ vat_nv_record Recording tools for vat ftp.sics.se:archive/vat_nv_record.tar.Z
|
|||
cd /dev
|
||||
MAKEDEV cuaa0
|
||||
</verb>
|
||||
<p>
|
||||
Or use cu as root with the following command:
|
||||
<verb>
|
||||
cu -l``line'' -s``speed''
|
||||
</verb>
|
||||
with line being the serial port (e.g.<tt>/dev/cuaa0</tt>)
|
||||
and speed being the speed (e.g.<tt>57600</tt>).
|
||||
When you done entering the AT commands hit <tt>~.</tt> to exit.
|
||||
|
||||
<sect1>
|
||||
<heading>Why doesn't the <tt/@/ sign for the phone number capability work?</heading>
|
||||
|
|
@ -2160,7 +2190,7 @@ vat_nv_record Recording tools for vat ftp.sics.se:archive/vat_nv_record.tar.Z
|
|||
<tag/Ollivier Robert/
|
||||
FreeBSD FAQ maintenance man
|
||||
<tag/Gary Clark II/
|
||||
Ex-FreeBSD FAQ maintenance man
|
||||
FreeBSD Doc Team
|
||||
<tag/Jordan Hubbard/
|
||||
Janitorial services (I don't do windows)
|
||||
<tag/Garrett Wollman/
|
||||
|
|
|
|||
|
|
@ -1,12 +1,14 @@
|
|||
# $Id: Makefile,v 1.1 1995-09-08 19:34:26 jfieber Exp $
|
||||
# $Id: Makefile,v 1.1.2.1 1995-10-12 03:15:40 jfieber Exp $
|
||||
|
||||
SRCS= authors.sgml basics.sgml bibliography.sgml boothelp.sgml
|
||||
SRCS+= booting.sgml contrib.sgml ctm.sgml current.sgml dialup.sgml
|
||||
SRCS+= diskless.sgml eresources.sgml glossary.sgml handbook.sgml
|
||||
SRCS+= history.sgml hw.sgml install.sgml kerberos.sgml kerneldebug.sgml
|
||||
SRCS+= memoryuse.sgml mirrors.sgml nfs.sgml nutshell.sgml porting.sgml
|
||||
SRCS+= ports.sgml ppp.sgml relnotes.sgml scsi.sgml sections.sgml
|
||||
SRCS+= slipc.sgml slips.sgml submitters.sgml sup.sgml
|
||||
SRCS+= booting.sgml contrib.sgml crypt.sgml ctm.sgml current.sgml dialup.sgml
|
||||
SRCS+= diskless.sgml dma.sgml eresources.sgml esdi.sgml glossary.sgml
|
||||
SRCS+= handbook.sgml history.sgml hw.sgml install.sgml kerberos.sgml
|
||||
SRCS+= kernelconfig.sgml kerneldebug.sgml memoryuse.sgml
|
||||
SRCS+= mirrors.sgml nfs.sgml nutshell.sgml
|
||||
SRCS+= porting.sgml ports.sgml ppp.sgml printing.sgml relnotes.sgml
|
||||
SRCS+= routing.sgml scsi.sgml sections.sgml
|
||||
SRCS+= skey.sgml slipc.sgml slips.sgml submitters.sgml sup.sgml
|
||||
SRCS+= troubleshooting.sgml userppp.sgml
|
||||
|
||||
.include <bsd.sgml.mk>
|
||||
|
|
|
|||
|
|
@ -1,29 +1,112 @@
|
|||
<!-- $Id: authors.sgml,v 1.3.4.1 1995-09-17 11:19:21 davidg Exp $ -->
|
||||
<!-- $Id: authors.sgml,v 1.3.4.2 1995-10-12 03:15:42 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<!--
|
||||
Names and email address of contributing authors. Use these
|
||||
entities when referencing people.
|
||||
entities when referencing people. Please not the use of single
|
||||
and double quotes.
|
||||
-->
|
||||
|
||||
<!ENTITY a.asami "Satoshi Asami <tt><asami@FreeBSD.org></tt>">
|
||||
<!ENTITY a.awebster "Andrew Webster <tt><awebster@dataradio.com></tt>">
|
||||
<!ENTITY a.davidg "David Greenman <tt><davidg@Root.COM></tt>">
|
||||
<!ENTITY a.dufalt "Peter Dufault <tt><dufault@hda.com></tt>">
|
||||
<!ENTITY a.gclarkii "Gary Clark II <tt><gclarkii@FreeBSD.org></tt>">
|
||||
<!ENTITY a.gena "Gennady B. Sorokopud <tt><gena@NetVision.net.il></tt>">
|
||||
<!ENTITY a.ghelmer "Guy Helmer <tt><ghelmer@alpha.dsu.edu></tt>">
|
||||
<!ENTITY a.gpalmer "Gary Palmer <tt><gpalmer@FreeBSD.org></tt>">
|
||||
<!ENTITY a.jfieber "John Fieber <tt><jfieber@FreeBSD.org></tt>">
|
||||
<!ENTITY a.jkh "Jordan Hubbard <tt><jkh@FreeBSD.org></tt>">
|
||||
<!ENTITY a.joerg "Joerg Wunsch <tt><joerg_wunsch@uriah.heep.sax.de></tt>">
|
||||
<!ENTITY a.john "John Lind <tt><john@starfire.MN.ORG></tt>">
|
||||
<!ENTITY a.mark "Mark Murray <tt><mark@grondar.za></tt>">
|
||||
<!ENTITY a.martin "Martin Renters <tt><martin@innovus.com></tt>">
|
||||
<!ENTITY a.md "Mark Dapoz <tt><md@bsc.no></tt>">
|
||||
<!ENTITY a.nik "Nik Clayton <tt><nik@blueberry.co.uk></tt>">
|
||||
<!ENTITY a.phk "Poul-Henning Kamp <tt><phk@FreeBSD.org></tt>">
|
||||
<!ENTITY a.paul "Paul Richards <tt><paul@FreeBSD.org></tt>">
|
||||
<!ENTITY a.rgrimes "Rodney Grimes <tt><rgrimes@FreeBSD.org></tt>">
|
||||
<!ENTITY a.whiteside "Don Whiteside <tt><whiteside@acm.org></tt>">
|
||||
<!ENTITY a.wilko "Wilko Bulte <tt><wilko@yedi.iaf.nl></tt>">
|
||||
<!ENTITY a.asami "Satoshi Asami
|
||||
<tt><htmlurl url='mailto:asami@FreeBSD.org'
|
||||
name='<asami@FreeBSD.org>'></tt>">
|
||||
|
||||
<!ENTITY a.awebster "Andrew Webster
|
||||
<tt><htmlurl url='mailto:awebster@dataradio.com'
|
||||
name='<awebster@dataradio.com>'></tt>">
|
||||
|
||||
<!ENTITY a.davidg "David Greenman
|
||||
<tt><htmlurl url='mailto:davidg@Root.COM'
|
||||
name='<davidg@Root.COM>'></tt>">
|
||||
|
||||
<!ENTITY a.dufalt "Peter Dufault
|
||||
<tt><htmlurl url='mailto:dufault@hda.com'
|
||||
name='<dufault@hda.com>'></tt>">
|
||||
|
||||
<!ENTITY a.gclarkii "Gary Clark II
|
||||
<tt><htmlurl url='mailto:gclarkii@FreeBSD.org'
|
||||
name='<gclarkii@FreeBSD.org>'></tt>">
|
||||
|
||||
<!ENTITY a.gena "Gennady B. Sorokopud
|
||||
<tt><htmlurl url='mailto:gena@NetVision.net.il'
|
||||
name='<gena@NetVision.net.il>'></tt>">
|
||||
|
||||
<!ENTITY a.ghelmer "Guy Helmer
|
||||
<tt><htmlurl url='mailto:ghelmer@alpha.dsu.edu'
|
||||
name='<ghelmer@alpha.dsu.edu>'></tt>">
|
||||
|
||||
<!ENTITY a.gpalmer "Gary Palmer
|
||||
<tt><htmlurl url='mailto:gpalmer@FreeBSD.org'
|
||||
name='<gpalmer@FreeBSD.org>'></tt>">
|
||||
|
||||
<!ENTITY a.gryphon "Coranth Gryphon
|
||||
<tt><htmlurl url='mailto:gryphon@healer.com'
|
||||
name='<gryphon@healer.com>'></tt>">
|
||||
|
||||
<!ENTITY a.jehamby "Jake Hamby
|
||||
<tt><htmlurl url='mailto:jehamby@lightside.com'
|
||||
name='<jehamby@lightside.com>'></tt>">
|
||||
|
||||
<!ENTITY a.jfieber "John Fieber
|
||||
<tt><htmlurl url='mailto:jfieber@FreeBSD.org'
|
||||
name='<jfieber@FreeBSD.org>'></tt>">
|
||||
|
||||
<!ENTITY a.jkh "Jordan Hubbard
|
||||
<tt><htmlurl url='mailto:jkh@FreeBSD.org'
|
||||
name='<jkh@FreeBSD.org>'></tt>">
|
||||
|
||||
<!ENTITY a.joerg "Joerg Wunsch
|
||||
<tt><htmlurl url='mailto:joerg_wunsch@uriah.heep.sax.de'
|
||||
name='<joerg_wunsch@uriah.heep.sax.de>'></tt>">
|
||||
|
||||
<!ENTITY a.john "John Lind
|
||||
<tt><htmlurl url='mailto:john@starfire.MN.ORG'
|
||||
name='<john@starfire.MN.ORG>'></tt>">
|
||||
|
||||
<!ENTITY a.kelly "Sean Kelly
|
||||
<tt><htmlurl url='mailto:kelly@fsl.noaa.gov'
|
||||
name='<kelly@fsl.noaa.gov>'></tt>">
|
||||
|
||||
<!ENTITY a.mark "Mark Murray
|
||||
<tt><htmlurl url='mailto:mark@grondar.za'
|
||||
name='<mark@grondar.za>'></tt>">
|
||||
|
||||
<!ENTITY a.martin "Martin Renters
|
||||
<tt><htmlurl url='mailto:martin@innovus.com'
|
||||
name='<martin@innovus.com>'></tt>">
|
||||
|
||||
<!ENTITY a.md "Mark Dapoz
|
||||
<tt><htmlurl url='mailto:md@bsc.no'
|
||||
name='<md@bsc.no>'></tt>">
|
||||
|
||||
<!ENTITY a.nik "Nik Clayton
|
||||
<tt><htmlurl url='mailto:nik@blueberry.co.uk'
|
||||
name='<nik@blueberry.co.uk>'></tt>">
|
||||
|
||||
<!ENTITY a.phk "Poul-Henning Kamp
|
||||
<tt><htmlurl url='mailto:phk@FreeBSD.org'
|
||||
name='<phk@FreeBSD.org>'></tt>">
|
||||
|
||||
<!ENTITY a.paul "Paul Richards
|
||||
<tt><htmlurl url='mailto:paul@FreeBSD.org'
|
||||
name='<paul@FreeBSD.org>'></tt>">
|
||||
|
||||
<!ENTITY a.rgrimes "Rodney Grimes
|
||||
<tt><htmlurl url='mailto:rgrimes@FreeBSD.org'
|
||||
name='<rgrimes@FreeBSD.org>'></tt>">
|
||||
|
||||
<!ENTITY a.uhclem "Frank Durda IV
|
||||
<tt><htmlurl url='mailto:uhclem@nemesis.lonestar.org'
|
||||
name='<uhclem@nemesis.lonestar.org>'></tt>">
|
||||
|
||||
<!ENTITY a.whiteside "Don Whiteside
|
||||
<tt><htmlurl url='mailto:whiteside@acm.org'
|
||||
name='<whiteside@acm.org>'></tt>">
|
||||
|
||||
<!ENTITY a.wilko "Wilko Bulte
|
||||
<tt><htmlurl url='mailto:wilko@yedi.iaf.nl'
|
||||
name='<wilko@yedi.iaf.nl>'></tt>">
|
||||
|
||||
<!ENTITY a.wollman "Garrett Wollman
|
||||
<tt><htmlurl url='mailto:wollman@FreeBSD.org'
|
||||
name='<wollman@FreeBSD.org>'></tt>">
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
<!-- $Id: basics.sgml,v 1.1.1.1.4.1 1995-09-17 11:19:22 davidg Exp $ -->
|
||||
<!-- $Id: basics.sgml,v 1.1.1.1.4.2 1995-10-12 03:15:43 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<chapt><heading>Unix Basics<label id="basics"></heading>
|
||||
|
|
|
|||
|
|
@ -1,10 +1,10 @@
|
|||
<!-- $Id: bibliography.sgml,v 1.1.1.1.4.1 1995-09-17 11:19:23 davidg Exp $ -->
|
||||
<!-- $Id: bibliography.sgml,v 1.1.1.1.4.2 1995-10-12 03:15:45 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<chapt>
|
||||
<heading>Bibliography<label id="bibliography"></heading>
|
||||
|
||||
<p>While the manual pages provide the definative reference
|
||||
<p>While the manual pages provide the definitive reference
|
||||
for individual pieces of the FreeBSD operating system,
|
||||
they are notorious for not illustrating how to put the
|
||||
pieces together to make the whole operating system run
|
||||
|
|
@ -119,12 +119,12 @@
|
|||
<p><itemize>
|
||||
|
||||
<item>Stanley, Tom. <em>ISA System
|
||||
Architechure</em>. 3rd ed. Reading, Mass. :
|
||||
Architecture</em>. 3rd ed. Reading, Mass. :
|
||||
Addison-Wesley, 1995.
|
||||
<newline>ISBN 0201409968</item>
|
||||
|
||||
<item>Stanley, Tom. <em>PCI System
|
||||
Architechure</em>. 3rd ed. Reading, Mass. :
|
||||
Architecture</em>. 3rd ed. Reading, Mass. :
|
||||
Addison-Wesley, 1995. <newline>ISBN
|
||||
0201409933</item>
|
||||
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@
|
|||
|
||||
This conversion has been made by Ollivier Robert.
|
||||
|
||||
$Id: booting.sgml,v 1.2.4.1 1995-09-17 11:19:24 davidg Exp $
|
||||
$Id: booting.sgml,v 1.2.4.2 1995-10-12 03:15:47 jfieber Exp $
|
||||
|
||||
|
||||
<!DOCTYPE linuxdoc PUBLIC "-//FreeBSD//DTD linuxdoc//EN">
|
||||
|
|
@ -22,7 +22,7 @@
|
|||
<toc>
|
||||
-->
|
||||
|
||||
<chapt><heading>The FreeBSD Booting Process<label id="booting"></heading>
|
||||
<sect><heading>The FreeBSD Booting Process<label id="booting"></heading>
|
||||
|
||||
<p><em>Contributed by &a.phk;. v1.1, April 26th.</em>
|
||||
|
||||
|
|
@ -30,7 +30,7 @@
|
|||
determine the root filesystem and initialize user-land things. This
|
||||
leads to some interesting possibilities shown below.
|
||||
|
||||
<sect><heading>Loading a kernel</heading>
|
||||
<sect1><heading>Loading a kernel</heading>
|
||||
<p>
|
||||
We presently have three basic mechanisms for loading the
|
||||
kernel as described below:
|
||||
|
|
@ -67,7 +67,7 @@
|
|||
</descrip>
|
||||
|
||||
|
||||
<sect><heading>Determine the root filesystem</heading>
|
||||
<sect1><heading>Determine the root filesystem</heading>
|
||||
<p>
|
||||
Once the kernel is loaded and the boot-code jumps to it, the kernel
|
||||
will initialize itself, trying to determine what hardware is
|
||||
|
|
@ -104,7 +104,7 @@
|
|||
</descrip>
|
||||
|
||||
|
||||
<sect><heading>Initialize user-land things</heading>
|
||||
<sect1><heading>Initialize user-land things</heading>
|
||||
<p>
|
||||
To get the user-land going, when the kernel has finished
|
||||
initialization, it will create a with ``<tt/pid == 1/'' and execute
|
||||
|
|
@ -119,7 +119,7 @@
|
|||
1/''.
|
||||
|
||||
|
||||
<sect><heading>Interesting combinations</heading>
|
||||
<sect1><heading>Interesting combinations</heading>
|
||||
<p>
|
||||
Boot a kernel with a MFS in it with a special <tt>/sbin/init</tt>
|
||||
which...
|
||||
|
|
@ -133,7 +133,7 @@
|
|||
<tt>/rootfs/bin -> /bin</tt><newline>
|
||||
<tt>/rootfs/etc -> /etc</tt><newline>
|
||||
<tt>/rootfs/sbin -> /sbin</tt><newline>
|
||||
...<newline>
|
||||
(etc...)<newline>
|
||||
</itemize>
|
||||
|
||||
Now you run FreeBSD without repartitioning your hard disk...
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
<!-- $Id: contrib.sgml,v 1.15.2.1 1995-10-04 08:15:25 jkh Exp $ -->
|
||||
<!-- $Id: contrib.sgml,v 1.15.2.2 1995-10-12 03:15:48 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<chapt><heading>FreeBSD contributor list<label id="contrib"></heading>
|
||||
|
|
@ -19,7 +19,7 @@
|
|||
some occasionally rocky moments in relations between the
|
||||
two groups, we both want essentially the same thing: More
|
||||
BSD based operating systems on people's computers! We wish
|
||||
the NetBSD group every success in their endevors.
|
||||
the NetBSD group every success in their endeavors.
|
||||
|
||||
<sect><heading>Hardware contributors</heading>
|
||||
|
||||
|
|
@ -66,7 +66,7 @@
|
|||
|
||||
<p><descrip>
|
||||
<tag/President/ Jordan K. Hubbard <jkh@FreeBSD.org>
|
||||
<tag/Principle Architect/ David Greenman <davidg@FreeBSD.org>
|
||||
<tag/Principal Architect/ David Greenman <davidg@FreeBSD.org>
|
||||
<tag/Documentation/ John Fieber <jfieber@FreeBSD.org>
|
||||
<tag/Internationalization/ Andrey A. Chernov <ache@FreeBSD.org>
|
||||
<tag/Networking/ Garrett A. Wollman <wollman@FreeBSD.org>
|
||||
|
|
@ -87,8 +87,9 @@
|
|||
<itemize>
|
||||
<item>Adam David <adam@veda.is>
|
||||
<item>Adam Glass <glass@postgres.berkeley.edu>
|
||||
<item>Adrian T. Filipi-Martin <atf3r@agate.cs.virginia.edu>
|
||||
<item>Akito Fujita <fujita@zoo.ncl.omron.co.jp>
|
||||
<item>Alain Kalker <alain@Wit401402.student.utwente.nl>
|
||||
<item>Alain Kalker <A.C.P.M.Kalker@student.utwente.nl>
|
||||
<item>Andras Olah <olah@cs.utwente.nl>
|
||||
<item>Andreas Klemm <andreas@knobel.GUN.de>
|
||||
<item>Andrew Herbert <andrew@werple.apana.org.au>
|
||||
|
|
@ -100,15 +101,18 @@
|
|||
<item>Bob Wilcox <bob@obiwan.uucp>
|
||||
<item>Brian Tao <taob@gate.sinica.edu.tw>
|
||||
<item>Charles Hannum <mycroft@ai.mit.edu>
|
||||
<item>Chet Ramey <chet@odin.INS.CWRU.Edu>
|
||||
<item>Chris G. Demetriou <cgd@postgres.berkeley.edu>
|
||||
<item>Chris Provenzano <proven@athena.mit.edu>
|
||||
<item>Chris Stenton <jacs@gnome.co.uk>
|
||||
<item>Chris Torek <torek@ee.lbl.gov>
|
||||
<item>Christian Gusenbauer <cg@fimp01.fim.uni-linz.ac.at>
|
||||
<item>Christoph Robitschko <chmr@edvz.tu-graz.ac.at>
|
||||
<item>Chuck Hein <chein@cisco.com>
|
||||
<item>Chuck Robey <chuckr@Glue.umd.edu>
|
||||
<item>Cornelis van der Laan <nils@guru.ims.uni-stuttgart.de>
|
||||
<item>Craig Struble <cstruble@vt.edu>
|
||||
<item>Cristian Ferretti <cfs@riemann.mat.puc.cl>
|
||||
<item>Curt Mayer <curt@toad.com>
|
||||
<item>Danny J. Zerkel <dzerkel@feephi.phofarm.com>
|
||||
<item>Dave Burgess <burgess@hrd769.brooks.af.mil>
|
||||
|
|
@ -116,8 +120,10 @@
|
|||
<item>Dave Rivers <rivers@ponds.uucp>
|
||||
<item>David Dawes <dawes@physics.su.OZ.AU>
|
||||
<item>Dean Huxley <dean@fsa.ca>
|
||||
<item>Dirk Froemberg <dirk@hal.in-berlin.de>
|
||||
<item>Don Whiteside <dwhite@anshar.shadow.net>
|
||||
<item>Eric L. Hernes <erich@lodgenet.com>
|
||||
<item>Frank Bartels <knarf@nasim.cube.net>
|
||||
<item>Frank Durda IV <bsdmail@nemesis.lonestar.org>
|
||||
<item>Frank Maclachlan <fpm@crash.cts.com>
|
||||
<item>Frank Nobis <fn@trinity.radio-do.de>
|
||||
|
|
@ -127,6 +133,7 @@
|
|||
<item>Gene Stark <stark@cs.sunysb.edu>
|
||||
<item>Guido van Rooij <guido@gvr.win.tue.nl>
|
||||
<item>Havard Eidnes <Havard.Eidnes@runit.sintef.no>
|
||||
<item>Hideaki Ohmon <ohmon@sfc.keio.ac.jp>
|
||||
<item>Holger Veit <Holger.Veit@gmd.de>
|
||||
<item>Ishii Masahiro, R. Kym Horsell
|
||||
<item>J.T. Conklin <jtc@winsey.com>
|
||||
|
|
@ -134,9 +141,11 @@
|
|||
<item>James da Silva <jds@cs.umd.edu> et al
|
||||
<item>Janusz Kokot <janek@gaja.ipan.lublin.pl>
|
||||
<item>Javier Martin Rueda <jmrueda@diatel.upm.es>
|
||||
<item>Jean-Marc Zucconi <jmz@FreeBSD.ORG>
|
||||
<item>Jim Wilson <wilson@moria.cygnus.com>
|
||||
<item>Jonathan Bresler < jmb@FreeBSD.ORG>
|
||||
<item>Josh MacDonald <jmacd@uclink.berkeley.edu>
|
||||
<item>Juergen Lock <nox@jelal.hb.north.de>
|
||||
<item>Julian Elischer <julian@dialix.oz.au>
|
||||
<item>Julian Stacey <stacey@guug.de>
|
||||
(fallback: <julian@meepmeep.pcs.com>)
|
||||
|
|
@ -175,12 +184,14 @@
|
|||
<item>Rob Snow <rsnow@txdirect.net>
|
||||
<item>Rodney W. Grimes <rgrimes@FreeBSD.org>
|
||||
<item>Sascha Wildner <swildner@channelz.GUN.de>
|
||||
<item>Scott Blachowicz <scott@sabami.seaslug.org>
|
||||
<item>Scott Mace <smace@FreeBSD.org>
|
||||
<item>Sean Eric Fagan <sef@kithrup.com>
|
||||
<item>Serge V. Vakulenko <vak@zebub.msk.su>
|
||||
<item>Stefan Esser <se@MI.Uni-Koeln.DE>
|
||||
<item>Stephen McKay <syssgm@devetir.qld.gov.au>
|
||||
<item>Steve Gerakines <steve2@genesis.tiac.net>
|
||||
<item>Steve Passe <smp@csn.net>
|
||||
<item>Steven Wallace <swallace@ece.uci.edu>
|
||||
<item>Tatsumi Hosokawa <hosokawa@mt.cs.keio.ac.jp>
|
||||
<item>Terry Lee <terry@uivlsi.csl.uiuc.edu>
|
||||
|
|
@ -189,7 +200,7 @@
|
|||
<item>Tom Samplonius <tom@misery.sdf.com>
|
||||
<item>Torbjorn Granlund <tege@matematik.su.se>
|
||||
<item>Torsten Blum <torstenb@FreeBSD.ORG>
|
||||
<item>Ugen J.S.Antsilevich <ugen@NetVision.net.il>
|
||||
<item>Ugen J.S.Antsilevich <ugen@latte.WorldBank.org>
|
||||
<item>Werner Griessl <werner@btp1da.phy.uni-bayreuth.de>
|
||||
<item>Wolfgang Stanglmeier <wolf@kintaro.cologne.de>
|
||||
<item>Wolfram Schneider <wosch@cs.tu-berlin.de>
|
||||
|
|
@ -246,6 +257,7 @@
|
|||
<item>Joerg Lohse <lohse@tech7.informatik.uni-hamburg.de>
|
||||
<item>Jörg Wunsch <joerg_wunsch@uriah.heep.sax.de>
|
||||
<item>John Dyson - <formerly dyson@ref.tfs.com>
|
||||
<item>John Polstra <jdp@polstra.com>
|
||||
<item>John Woods <jfw@eddie.mit.edu>
|
||||
<item>Jordan K. Hubbard <jkh@whisker.hubbard.ie>
|
||||
<item>Julian Elischer <julian@dialix.oz.au>
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@
|
|||
#
|
||||
# Converted by Ollivier RObert <roberto@FreeBSD.ORG>
|
||||
#
|
||||
# $Id: ctm.sgml,v 1.1.1.1.4.1 1995-09-17 11:19:25 davidg Exp $
|
||||
# $Id: ctm.sgml,v 1.1.1.1.4.2 1995-10-12 03:15:50 jfieber Exp $
|
||||
#
|
||||
# ----------------------------------------------------------------------------
|
||||
# "THE BEER-WARE LICENSE" (Revision 42):
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
<!-- $Id: current.sgml,v 1.2.4.1 1995-09-17 11:19:26 davidg Exp $ -->
|
||||
<!-- $Id: current.sgml,v 1.2.4.2 1995-10-12 03:15:51 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
|
||||
|
|
@ -10,7 +10,7 @@
|
|||
|
||||
THE FREEBSD CURRENT POLICY
|
||||
|
||||
Last updated: $Date: 1995-09-17 11:19:26 $
|
||||
Last updated: $Date: 1995-10-12 03:15:51 $
|
||||
|
||||
This document attempts to explain the rationale behind FreeBSD-current,
|
||||
what you should expect should you decide to run it, and states some
|
||||
|
|
@ -67,7 +67,7 @@ too much time to do this as a general task.
|
|||
<item> In any way ``officially supported'' by us.
|
||||
|
||||
We do our best to help people genuinely in one of the 3
|
||||
``legitimate'' FreeBSD-current catagories, but we simply <em>do not
|
||||
``legitimate'' FreeBSD-current categories, but we simply <em>do not
|
||||
have the time</em> to help every person who jumps into FreeBSD-current
|
||||
with more enthusiasm than knowledge of how to deal with
|
||||
experimental system software. This is not because we're mean and
|
||||
|
|
@ -81,9 +81,9 @@ too much time to do this as a general task.
|
|||
|
||||
<sect><heading>Using FreeBSD-current</heading>
|
||||
|
||||
<p><enum> <item> Join the freebsd-hackers and freebsd-commit
|
||||
<p><enum> <item> Join the freebsd-current and cvs-all
|
||||
mailing lists. This is not just a good idea, it's
|
||||
<em>essential</em>. If you aren't on freebsd-hackers, you
|
||||
<em>essential</em>. If you aren't on freebsd-current, you
|
||||
won't read the comments that people are making about the
|
||||
current state of the system and thus will end up stumbling
|
||||
over a lot of problems that others have already found and
|
||||
|
|
@ -92,26 +92,26 @@ too much time to do this as a general task.
|
|||
Before you rebuild <tt>/usr/src</tt>, you <em>must</em>
|
||||
rebuild the kernel or your system will crash horribly!").
|
||||
|
||||
The freebsd-commit list will allow you to see the commit log
|
||||
entry for each change as its made. This can also contain
|
||||
The cvs-all mailing list will allow you to see the commit log
|
||||
entry for each change as it's made. This can also contain
|
||||
important information, and will let you know what parts of
|
||||
the system are being actively changed.
|
||||
|
||||
To join these lists, send mail to `majordomo@FreeBSD.ORG'
|
||||
and say:
|
||||
<verb>
|
||||
subscribe freebsd-hackers
|
||||
subscribe freebsd-commit
|
||||
subscribe current
|
||||
subscribe cvs-all
|
||||
</verb>
|
||||
In the body of your message. Optionally, you can also say `help'
|
||||
and MajorDomo will send you full help on how to subscribe and
|
||||
and Majordomo will send you full help on how to subscribe and
|
||||
unsubscribe to the various other mailing lists we support.
|
||||
|
||||
<item> Grab the sources from ftp.FreeBSD.ORG. You can do this in
|
||||
three ways:
|
||||
|
||||
<enum>
|
||||
<item> Using the CTM facility desribed below. Unless you
|
||||
<item> Using the CTM facility described below. Unless you
|
||||
have a good TCP/IP connection at a flat rate, this is
|
||||
the way to do it.
|
||||
|
||||
|
|
@ -173,7 +173,3 @@ commercial organizations won't even consider it) and I want to make
|
|||
sure that people at least come into this with their eyes open, and
|
||||
don't make the leap unless they're good at working without a net!
|
||||
-->
|
||||
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
<!-- This is an SGML document in the linuxdoc DTD of the Tutorial for
|
||||
Configuring a FreeBSD for Dialup Services by Guy Helmer.
|
||||
$Id: dialup.sgml,v 1.1.1.1.4.1 1995-09-17 11:19:26 davidg Exp $
|
||||
$Id: dialup.sgml,v 1.1.1.1.4.2 1995-10-12 03:15:53 jfieber Exp $
|
||||
|
||||
<!DOCTYPE linuxdoc PUBLIC "-//Linux//DTD linuxdoc//EN">
|
||||
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
<!-- $Id: diskless.sgml,v 1.1.1.1.4.1 1995-09-17 11:19:28 davidg Exp $ -->
|
||||
<!-- $Id: diskless.sgml,v 1.1.1.1.4.2 1995-10-12 03:15:54 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<sect><heading>Diskless operation<label id="diskless"></heading>
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
<!-- $Id: eresources.sgml,v 1.2.4.1 1995-09-17 11:19:28 davidg Exp $ -->
|
||||
<!-- $Id: eresources.sgml,v 1.2.4.2 1995-10-12 03:15:56 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<chapt>
|
||||
|
|
@ -21,10 +21,7 @@
|
|||
<sect>
|
||||
<heading>Mailing lists<label id="eresources:mail"></heading>
|
||||
|
||||
<p><em>Contributed by &a.dufalt;.<newline>
|
||||
20 Jun 1995.</em>
|
||||
|
||||
Though many of the FreeBSD development members read USENET, we cannot
|
||||
<p>Though many of the FreeBSD development members read USENET, we cannot
|
||||
always guarantee that we'll get to your questions in a timely fashion
|
||||
(or at all) if you post them only to one of the comp.unix.bsd.*
|
||||
groups. By addressing your questions to the appropriate mailing list
|
||||
|
|
@ -52,9 +49,10 @@ List Purpose
|
|||
freebsd-announce Important events / milestones
|
||||
freebsd-bugs Bug reports
|
||||
freebsd-chat Non technical items related to the community
|
||||
freebsd-current Discussions about the use of FreeBSD-current
|
||||
freebsd-isp Issues for ISP's using FreeBSD
|
||||
freebsd-policy Policy issues and suggestions
|
||||
freebsd-questions User questions
|
||||
freebsd-current Discussions about the use of FreeBSD-current
|
||||
</verb>
|
||||
|
||||
<bf>Technical lists:</bf> The following are the technical lists. You should
|
||||
|
|
@ -234,8 +232,12 @@ hardware that FreeBSD runs on, various problems and suggestions
|
|||
concerning what to buy or avoid.
|
||||
|
||||
<tag/FREEBSD-INSTALL/ <em>Installation discussion</em><newline>
|
||||
This is the mailing list for people discussing FreeBSD installation
|
||||
development for the 2.0 release.
|
||||
This mailing list is for discussing FreeBSD installation
|
||||
development for the future releases.
|
||||
|
||||
<tag/FREEBSD-ISP/ <em>Issues for Internet Service Providers</em><newline>
|
||||
This mailing list is for discussing topics relevant to Internet
|
||||
Serivce Providers (ISPs) using FreeBSD.
|
||||
|
||||
<tag/FREEBSD-MULTIMEDIA/ <em>Multimedia discussions</em><newline>
|
||||
This is a forum about multimedia applications using FreeBSD.
|
||||
|
|
@ -280,7 +282,7 @@ fixes, etc).
|
|||
|
||||
<tag/FREEBSD-USER-GROUPS/ <em>User Group Coordination List</em><newline>
|
||||
This is the mailing list for the coordinators from each of the
|
||||
local area Users Groups to dicuss matters with each other and a
|
||||
local area Users Groups to discuss matters with each other and a
|
||||
designated individual from the Core Team. This mail list should
|
||||
be limited to meeting synopsis and coordination of projects that span
|
||||
User Groups.
|
||||
|
|
@ -346,7 +348,7 @@ User Groups.
|
|||
</itemize>
|
||||
|
||||
<sect>
|
||||
<heading>Word Wide Web servers<label id="eresources:web"></heading>
|
||||
<heading>World Wide Web servers<label id="eresources:web"></heading>
|
||||
|
||||
<p><itemize>
|
||||
<item><url url="http://www.freebsd.org/"></item>
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
<!-- $Id: glossary.sgml,v 1.1.1.1.4.1 1995-09-17 11:19:30 davidg Exp $ -->
|
||||
<!-- $Id: glossary.sgml,v 1.1.1.1.4.2 1995-10-12 03:15:57 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<chapt><heading>* Glossary<label id="glossary"></heading>
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
<!-- $Id: handbook.sgml,v 1.7.4.1 1995-09-17 11:19:30 davidg Exp $ -->
|
||||
<!-- $Id: handbook.sgml,v 1.7.4.2 1995-10-12 03:15:59 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<!DOCTYPE linuxdoc PUBLIC "-//FreeBSD//DTD linuxdoc//EN" [
|
||||
|
|
@ -24,19 +24,22 @@
|
|||
<author>
|
||||
<name>The FreeBSD Documentation Project</name>
|
||||
</author>
|
||||
<date>August 31, 1995</date>
|
||||
<date>October 6, 1995</date>
|
||||
|
||||
<abstract>Welcome to FreeBSD! This handbook covers the
|
||||
installation and day to day use of <bf>FreeBSD Release
|
||||
2.0.5</bf>.
|
||||
|
||||
This manual is a <bf>work in progress</bf> and is the
|
||||
work of many individials. Many sections do not yet exist
|
||||
work of many individuals. Many sections do not yet exist
|
||||
and some of those that do exist need to be updated. If
|
||||
you are interested in helping with this project, send
|
||||
email to &a.jfieber; or to the FreeBSD Documentation
|
||||
email to the FreeBSD Documentation
|
||||
Project mailing list <tt><htmlurl url="mailto:doc@freebsd.org"
|
||||
name="<doc@freebsd.org>"></tt>.
|
||||
The latest version of this document is always available from
|
||||
the <url url="http://www.freebsd.org/" name="FreeBSD World Wide
|
||||
Web server">.
|
||||
</abstract>
|
||||
|
||||
<toc>
|
||||
|
|
@ -62,34 +65,23 @@ name="<doc@freebsd.org>"></tt>.
|
|||
|
||||
<part><heading>System Administration</heading>
|
||||
|
||||
<chapt><heading>Reconfiguring the Kernel<label id="kernelconfig"></heading>
|
||||
<p>This section is in progress. Please contact
|
||||
Deborah Bennett <htmlurl url="mailto:deborah@gallifrey.microunity.com"
|
||||
name="<deborah@gallifrey.microunity.com>"> for more information.
|
||||
In the meantime, please refer to
|
||||
Kernel Configuration section of the <url url="../FAQ/freebsd-faq.html"
|
||||
name="FreeBSD FAQ">.
|
||||
<!-- &kernelconfig; -->
|
||||
|
||||
&kernelconfig;
|
||||
<chapt><heading>Users, groups and security</heading>
|
||||
<sect><heading>* DES, MD5 and Crypt</heading>
|
||||
<sect><heading>* S/Key</heading>
|
||||
&crypt;
|
||||
&skey;
|
||||
&kerberos;
|
||||
<sect><heading>* Firewalls</heading>
|
||||
|
||||
<chapt><heading>Printing</heading>
|
||||
<p>This section is in progress. Please contact
|
||||
Sean Kelly <url url="mailto:kelly@fsl.noaa.gov"
|
||||
name="kelley@fsl.noaa.gov"> for more information.
|
||||
|
||||
&printing;
|
||||
<chapt><heading>The X-Window System</heading>
|
||||
<p>Pending the completion of this section, please refer to
|
||||
documentation supplied by the <url url="http://www.xfree86.org/"
|
||||
name="The XFree86 Project, Inc">.
|
||||
|
||||
<chapt><heading>Managing hardware</heading>
|
||||
&scsi;
|
||||
<sect><heading>* Adding and reconfiguring disks</heading>
|
||||
&scsi;
|
||||
&esdi;
|
||||
<sect><heading>* Tapes and backups</heading>
|
||||
<sect><heading>* Serial ports</heading>
|
||||
<sect><heading>* Sound cards</heading>
|
||||
|
|
@ -121,14 +113,16 @@ name="<doc@freebsd.org>"></tt>.
|
|||
&slips;
|
||||
|
||||
<chapt><heading>Advanced networking</heading>
|
||||
<!--
|
||||
<sect><heading>Gateways and routing</heading>
|
||||
<p>This section is in progress. Please contact
|
||||
Coranth Gryphon <htmlurl url="mailto:gryphon@healer.com"
|
||||
name="<gryphon@healer.com>"> for more information.
|
||||
|
||||
-->
|
||||
&routing;
|
||||
&nfs;
|
||||
<sect><heading>* Yellow Pages/NIS</heading>
|
||||
&diskless;
|
||||
<sect><heading>* Yellow Pages/NIS</heading>
|
||||
<sect><heading>* ISDN</heading>
|
||||
|
||||
<chapt><heading>* Mail</heading>
|
||||
|
|
@ -143,10 +137,9 @@ name="<doc@freebsd.org>"></tt>.
|
|||
⊃
|
||||
&kerneldebug;
|
||||
&submitters;
|
||||
&booting;
|
||||
&memoryuse;
|
||||
&troubleshooting;
|
||||
|
||||
|
||||
<!-- ************************************************************ -->
|
||||
|
||||
<part><heading>Appendices</heading>
|
||||
|
|
@ -154,8 +147,12 @@ name="<doc@freebsd.org>"></tt>.
|
|||
&bibliography;
|
||||
&eresources;
|
||||
&hw;
|
||||
<chapt><heading>Assorted technical topics</heading>
|
||||
&booting;
|
||||
&memoryuse;
|
||||
&dma;
|
||||
&contrib;
|
||||
&glossary;
|
||||
<!-- &glossary; -->
|
||||
|
||||
</book>
|
||||
</linuxdoc>
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
<!-- $Id: history.sgml,v 1.1.4.1 1995-09-17 11:19:31 davidg Exp $ -->
|
||||
<!-- $Id: history.sgml,v 1.1.4.2 1995-10-12 03:16:00 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<sect><heading>A brief history of FreeBSD<label id="history"></heading>
|
||||
|
|
@ -36,7 +36,7 @@ FreeBSD's distribution channels to those many unfortunates without
|
|||
easy access to the Internet. Walnut Creek CDROM not only supported
|
||||
the idea of distributing FreeBSD on CD but went so far as to provide
|
||||
the project with a machine to work on and a fast Internet connection.
|
||||
Without Walnut Creek CDROM's almost unprecidented degree of faith in
|
||||
Without Walnut Creek CDROM's almost unprecedented degree of faith in
|
||||
what was, at the time, a completely unknown project, it is in fact
|
||||
very unlikely that FreeBSD would have gotten as far, as fast, as it
|
||||
has today.
|
||||
|
|
@ -52,7 +52,7 @@ Around this time, some rather unexpected storm clouds formed on our
|
|||
horizon as Novell and U.C. Berkeley settled their long-running lawsuit
|
||||
over the legal status of the Berkeley Net/2 tape. A condition of that
|
||||
settlement was U.C. Berkeley's concession that large parts of Net/2
|
||||
was "encumbered" code and property of Novell, who had in turn aquired
|
||||
was "encumbered" code and property of Novell, who had in turn acquired
|
||||
it from AT&T some time previously. What Berkeley got in return was
|
||||
Novell's "blessing" that the 4.4 Lite release, when it was finally
|
||||
released, would be declared unencumbered and all existing Net/2 users
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
<!-- $Id: hw.sgml,v 1.6 1995-09-02 11:09:03 ats Exp $ -->
|
||||
<!-- $Id: hw.sgml,v 1.6.2.1 1995-10-12 03:16:02 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<!--
|
||||
|
|
@ -54,14 +54,14 @@
|
|||
known work around is to turn the cache
|
||||
off.
|
||||
|
||||
<tag>Saturn-I <em>(ie, 82424ZX at rev 0, 1 or
|
||||
2)</em>:</tag> write back cache coherency
|
||||
<tag>Saturn-I <em>(ie, 82424ZX at rev 0, 1 or 2)</em>:</tag>
|
||||
Write back cache coherency
|
||||
problems. Hardware flaw, only known work around
|
||||
is to set the external cache to write-through
|
||||
mode. Upgrade to Saturn-II.
|
||||
|
||||
<tag>Saturn-II <em>(ie, 82424ZX at rev 3 or
|
||||
4)</em>:</tag> Works fine, but many MB
|
||||
<tag>Saturn-II <em>(ie, 82424ZX at rev 3 or 4)</em>:</tag>
|
||||
Works fine, but many MB
|
||||
manufactures leave out the external dirty bit
|
||||
SRAM needed for write back operation. Work
|
||||
arounds are either run it in write through mode,
|
||||
|
|
@ -192,7 +192,7 @@ device sio1 at isa? port 0x100 tty flags 0x1005
|
|||
device sio2 at isa? port 0x108 tty flags 0x1005
|
||||
device sio3 at isa? port 0x110 tty flags 0x1005
|
||||
device sio4 at isa? port 0x118 tty flags 0x1005
|
||||
...
|
||||
[...]
|
||||
device sio15 at isa? port 0x170 tty flags 0x1005
|
||||
device sio16 at isa? port 0x178 tty flags 0x1005 irq 3 vector siointr
|
||||
</verb></tscreen>
|
||||
|
|
@ -272,12 +272,12 @@ sio16: type 16550A (multiport master)
|
|||
must be made using the <tt>/dev/MAKEDEV</tt>
|
||||
script. After becoming root:
|
||||
<tscreen>
|
||||
cd /dev<newline>
|
||||
./MAKEDEV tty1<newline>
|
||||
./MAKEDEV cua1<newline>
|
||||
<em>.. (everything inbetween)</em><newline>
|
||||
./MAKEDEV ttyg<newline>
|
||||
./MAKEDEV cuag
|
||||
# cd /dev<newline>
|
||||
# ./MAKEDEV tty1<newline>
|
||||
# ./MAKEDEV cua1<newline>
|
||||
<em>(everything in between)</em><newline>
|
||||
# ./MAKEDEV ttyg<newline>
|
||||
# ./MAKEDEV cuag
|
||||
</tscreen>
|
||||
|
||||
If you do not want or need callout devices for some
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
<!-- $Id: install.sgml,v 1.9 1995-08-29 01:42:39 jfieber Exp $ -->
|
||||
<!-- $Id: install.sgml,v 1.9.2.1 1995-10-12 03:16:03 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<!--
|
||||
|
|
@ -6,8 +6,154 @@
|
|||
-->
|
||||
<chapt><heading>Installing FreeBSD<label id="install"></heading>
|
||||
|
||||
<p>So, you would like to try out FreeBSD on your system?
|
||||
This section is a quick-start guide for what you need to
|
||||
do. FreeBSD can be installed from a variety of media
|
||||
including CD-ROM, floppy disk, magnetic tape, an MS-DOS
|
||||
partition, and if you have a network connection, via
|
||||
anonymous ftp or NFS.
|
||||
|
||||
Regardless of the installation media you choose, you can
|
||||
get started by downleading the <bf>installation disk</bf>
|
||||
as described below. Booting your computer with disk will
|
||||
provide important information about compatibility between
|
||||
FreeBSD and your hardware which could dictate which
|
||||
installation options are possible. It can also provide
|
||||
early clues to compatibilty problems that could prevent
|
||||
FreeBSD running on your system at all. If you plan on
|
||||
installing via anonymous FTP, then this installation disk
|
||||
is all you need to download.
|
||||
|
||||
For more information on obtaining the FreeBSD distribution
|
||||
itself, please see <ref id="mirrors" name="Obtaining
|
||||
FreeBSD"> in the Appendix.
|
||||
|
||||
So, to get the show on the road, follow these steps:
|
||||
<enum>
|
||||
|
||||
<item>Review the <ref id="install:hw" name="supported
|
||||
configurations"> section of this installation guide to
|
||||
be sure that your hardware is supported by FreeBSD. It
|
||||
may be helpful to make a list of any special cards you
|
||||
have installed, such as SCSI controllers, etherernet
|
||||
adapters or sound cards. This list should include
|
||||
relevant configuration parameters such as interrupts
|
||||
(IRQ) and IO port addresses. </item>
|
||||
|
||||
<item>Download the <url
|
||||
url="ftp://ftp.freebsd.org/pub/FreeBSD/2.0.5-RELEASE/UPDATES/boot.flp"
|
||||
name="installation boot disk image"> file to your hard
|
||||
drive, and be sure to tell your browser to
|
||||
<em>save</em> rather than <em>display</em>.
|
||||
<bf>Note:</bf> This disk image can be used for
|
||||
<em>both</em> 1.44 megabyte 3.5 inch floppy disks and
|
||||
1.2 megabyte 5.25 inch floppy disks.</item>
|
||||
|
||||
<item>Make the installation boot disk from the image file:
|
||||
<itemize>
|
||||
<item>If you are using MS-DOS download
|
||||
<url
|
||||
url="ftp://ftp.freebsd.org/pub/FreeBSD/tools/dos-tools/rawrite.exe"
|
||||
name="rawrite.exe"> (tell your browser to <em>save</em> rather than
|
||||
<em>display</em>!), then run it:
|
||||
<tscreen><verb>
|
||||
C:\> rawrite
|
||||
</verb></tscreen> The
|
||||
program will prompt you for the floppy drive
|
||||
containing the disk you want to write to (A: or
|
||||
B:) and the name of the file to put on disk (boot.flp).
|
||||
</item>
|
||||
|
||||
<item>If you are using a UNIX system:
|
||||
<tscreen>
|
||||
% dd if=boot.flp of=<em>disk_device</em> bs=18k
|
||||
</tscreen>
|
||||
where <em>disk_device</em> is the <tt>/dev</tt>
|
||||
entry for the floppy drive. On FreeBSD systems, this
|
||||
is <tt>/dev/rfd0</tt> for the A: drive and
|
||||
<tt>/dev/rfd1</tt> for the B: drive.
|
||||
</item>
|
||||
</itemize>
|
||||
|
||||
</item>
|
||||
|
||||
<item>With the installation disk in the A: drive, reboot your
|
||||
computer. You should get a boot prompt something like this:
|
||||
<tscreen>
|
||||
>> FreeBSD BOOT ...<newline>
|
||||
Use hd(1,a)/kernel to boot sd0 when wd0 is also installed.<newline>
|
||||
Usage: [[hd(1,a)]/kernel][-abcCdhrsv]<newline>
|
||||
Use ? for file list or press Enter for defaults<newline>
|
||||
Boot:
|
||||
</tscreen>
|
||||
If you do <em>not</em> type anything, FreeBSD will automatically boot
|
||||
with its default configuration after a delay of about
|
||||
five seconds. As FreeBSD boots, it probes your computer
|
||||
to determine what hardware is installed. The results of
|
||||
this probing is displayed on the screen.
|
||||
</item>
|
||||
|
||||
<item>When the booting process is finished, The main FreeBSD
|
||||
installation menu will be displayed.</item>
|
||||
|
||||
</enum>
|
||||
|
||||
<p><bf>If something goes wrong...</bf>
|
||||
|
||||
<p>Due to limitations of the PC architecture, it is
|
||||
impossible for probing to be 100 percent reliable. In the event
|
||||
that your hardware is incorrectly identified, or that the
|
||||
probing causes your computer to lock up, first check the
|
||||
<ref id="install:hw" name="supported
|
||||
configurations"> section of this installation guide to be
|
||||
sure that your hardware is indeed supported by FreeBSD.
|
||||
|
||||
<p>If your hardware is supported, reset the computer and when
|
||||
the <tt>Boot:</tt> prompt comes up, type <bf>-c</bf>. This puts
|
||||
FreeBSD into a configuration mode where you can supply
|
||||
hints about your hardware. The FreeBSD kernel on the
|
||||
installation disk is configured assuming that most hardware
|
||||
devices are in their factory default configuration in terms
|
||||
of IRQs, IO addresses and DMA channels. If your hardware
|
||||
has been reconfigured, you will most likely need to use the
|
||||
<bf>-c</bf> option at boot to tell FreeBSD where things are.
|
||||
|
||||
<p>It is also possible that a probe for a device not present
|
||||
will cause a later probe for another device that is present
|
||||
to fail. In that case, the probes for the conflicting
|
||||
driver(s) should be disabled.
|
||||
|
||||
<p>In the configuration mode, you can:
|
||||
|
||||
<itemize>
|
||||
<item>List the device drivers installed in the kernel.</item>
|
||||
<item>Disable device drivers for hardware not present in your
|
||||
system.</item>
|
||||
<item>Change the IRQ, DRQ, and IO port addresses used by a
|
||||
device driver.</item>
|
||||
</itemize>
|
||||
|
||||
<p>While at the <tt>config></tt> prompt, type
|
||||
<tt>help</tt> for more information on the available
|
||||
commands. After adjusting the kernel to match how you have
|
||||
your hardware configured, type <tt>quit</tt> at the
|
||||
<tt>config></tt> prompt to continue booting with the new
|
||||
settings.
|
||||
|
||||
After FreeBSD has been installed, changes made in the
|
||||
configuration mode will be permanent so you do not have
|
||||
to reconfigure every time you boot. Even so, it is likely
|
||||
that you will want to build a custom kernel to optimize the
|
||||
performance of your system. See <ref id="kernelconfig"
|
||||
name="Kernel configuration"> for more information on
|
||||
creating custom kernels.
|
||||
|
||||
<sect><heading>MS-DOS user's Questions and Answers</heading>
|
||||
|
||||
<p>Many FreeBSD users wish to install FreeBSD on PCs inhabited
|
||||
by MS-DOS. Here are some commonly asked questions about
|
||||
installing FreeBSD on such systems.
|
||||
|
||||
<p><bf>Help! I have no space! Do I need to delete
|
||||
everything first?</bf>
|
||||
|
||||
|
|
@ -219,7 +365,7 @@
|
|||
|
||||
<item>ARNET 8 port serial card using shared IRQ.
|
||||
|
||||
<item>BOCA ATIO66 6 port serial card using shared IRQ.
|
||||
<item>BOCA IOAT66 6 port serial card using shared IRQ.
|
||||
|
||||
<item>Cyclades Cyclom-y Serial Board.
|
||||
|
||||
|
|
@ -353,7 +499,7 @@ C> MD C:\FREEBSD
|
|||
C> XCOPY /S E:\FLOPPIES C:\FREEBSD\FLOPPIES\
|
||||
C> XCOPY /S E:\DISTS\BIN C:\FREEBSD\BIN\
|
||||
</verb></tscreen>
|
||||
asssuming that <tt>C:</tt> is where you have free space
|
||||
assuming that <tt>C:</tt> is where you have free space
|
||||
and <tt>E:</tt> is where your CDROM is mounted. Note
|
||||
that you need the <tt>FLOPPIES</tt> directory because
|
||||
the <tt>root.flp</tt> image is needed during an MS-DOS
|
||||
|
|
@ -375,7 +521,7 @@ C> XCOPY /S E:\DISTS C:\FREEBSD\
|
|||
|
||||
<p>Installing from tape is probably the easiest method,
|
||||
short of an on-line install using FTP or a CDROM
|
||||
instal. The installation program expects the files to
|
||||
install. The installation program expects the files to
|
||||
be simply tar'ed onto the tape, so after getting all of
|
||||
the files for distribution you're interested in, simply
|
||||
tar them onto the tape with a command like:
|
||||
|
|
@ -403,8 +549,9 @@ C> XCOPY /S E:\DISTS C:\FREEBSD\
|
|||
<p>You can do network installations over 3 types of
|
||||
communications links:
|
||||
<descrip>
|
||||
<tag>Serial port</tag> SLIP or PPP <tag>Parallel
|
||||
port</tag> PLIP (laplink cable) <tag>Ethernet</tag> A
|
||||
<tag>Serial port</tag> SLIP or PPP
|
||||
<tag>Parallel port</tag> PLIP (laplink cable)
|
||||
<tag>Ethernet</tag> A
|
||||
standard ethernet controller (includes some PCMCIA).
|
||||
</descrip>
|
||||
|
||||
|
|
@ -568,7 +715,7 @@ C> XCOPY /S E:\DISTS C:\FREEBSD\
|
|||
wish to proceed directly to the Language option and
|
||||
set your preferred language. This will bring up some
|
||||
of the documentation in that language instead of
|
||||
english.
|
||||
English.
|
||||
|
||||
<item>Select the Options item and set any special
|
||||
preferences you may have.
|
||||
|
|
@ -623,7 +770,7 @@ C> XCOPY /S E:\DISTS C:\FREEBSD\
|
|||
flags in the Label editor) and all selected
|
||||
distributions will be extracted.
|
||||
|
||||
<item>The Configure menu choice allows you to furthur
|
||||
<item>The Configure menu choice allows you to further
|
||||
configure your FreeBSD installation by giving you
|
||||
menu-driven access to various system defaults.
|
||||
Some items, like networking, may be especially
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
<!-- $Id: kerberos.sgml,v 1.2.4.1 1995-09-17 11:19:32 davidg Exp $ -->
|
||||
<!-- $Id: kerberos.sgml,v 1.2.4.2 1995-10-12 03:16:05 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<sect><heading>Kerberos<label id="kerberos"></heading>
|
||||
|
|
@ -226,7 +226,7 @@ grunt# mv grunt-new-srvtab srvtab
|
|||
|
||||
<p>If the file is for a client system, and the network is not
|
||||
deemed safe, then copy the <tt><client>-new-srvtab</tt> to
|
||||
removeable media and transport it by secure physical means. Be
|
||||
removable media and transport it by secure physical means. Be
|
||||
sure to rename it to <tt>srvtab</tt> in the client's
|
||||
<tt>/etc/kerberosIV</tt> directory, and make sure it is mode 600:
|
||||
|
||||
|
|
@ -325,7 +325,7 @@ Apr 30 11:23:22 Apr 30 19:23:22 krbtgt.GRONDAR.ZA@GRONDAR.ZA
|
|||
</verb></tscreen>
|
||||
|
||||
<p>Now try changing the password using <tt>passwd</tt> to check if the
|
||||
kpasswd daemon can get authorisation to the Kerberos database:
|
||||
kpasswd daemon can get authorization to the Kerberos database:
|
||||
|
||||
<tscreen><verb>
|
||||
grunt$ passwd
|
||||
|
|
@ -342,7 +342,7 @@ Password changed.
|
|||
|
||||
<p>Kerberos allows us to give <it>each</it> user who needs root
|
||||
privileges their own <it>separate</it> <tt>su</tt>password. We
|
||||
could now add an id which is authorised to <tt>su</tt> to <it>root</it>.
|
||||
could now add an id which is authorized to <tt>su</tt> to <it>root</it>.
|
||||
This is controlled by having an instance of <it>root</it> associated
|
||||
with a principal. Using <tt>kdb_edit</tt> we can create the entry
|
||||
<it>jane.root</it> in the Kerberos database:
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
<!-- $Id: kerneldebug.sgml,v 1.3 1995-07-31 01:18:46 jfieber Exp $ -->
|
||||
<!-- $Id: kerneldebug.sgml,v 1.3.2.1 1995-10-12 03:16:09 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<chapt><heading>Kernel Debugging<label id="kerneldebug"></heading>
|
||||
|
|
@ -44,7 +44,7 @@
|
|||
programs will drastically increase, and since
|
||||
the whole kernel is loaded entirely at boot time and cannot be
|
||||
swapped out later, several megabytes of
|
||||
physical RAM willl be wasted.
|
||||
physical RAM will be wasted.
|
||||
|
||||
If you are testing a new kernel, for example by typing the new
|
||||
kernel's name at the boot prompt, but need to boot a different
|
||||
|
|
@ -218,7 +218,7 @@
|
|||
the Makefile, there will be some other object files rebuild,
|
||||
for example <tt>trap.o</tt>. With a bit of luck, the added
|
||||
<tt>-g</tt> option won't change anything for the generated
|
||||
code, so you'll finally get a new kernel with similiar code to
|
||||
code, so you'll finally get a new kernel with similar code to
|
||||
the faulting one but some debugging symbols. You should at
|
||||
least verify the old and new sizes with the <tt>size(1)</tt> command. If
|
||||
there is a mismatch, you probably need to give up here.
|
||||
|
|
@ -243,7 +243,7 @@
|
|||
If you need to do low-level debugging on your kernel, there's
|
||||
an on- line debugger available called DDB. It allows to
|
||||
setting breakpoints, single-steping kernel functions, examining
|
||||
and changeing kernel variables, etc. However, it cannot not
|
||||
and changing kernel variables, etc. However, it cannot not
|
||||
access kernel source files, and only has access to the global
|
||||
and static symbols, not to the full debug information like
|
||||
<tt>kgdb</tt>.
|
||||
|
|
@ -354,7 +354,7 @@
|
|||
w/w 0xf0010030 0 0
|
||||
</verb></tscreen>
|
||||
The command modifier (<tt>b</tt>/<tt>h</tt>/<tt>w</tt>)
|
||||
specifies the size of the data to be writtten, the first
|
||||
specifies the size of the data to be written, the first
|
||||
following expression is the address to write to, the remainder
|
||||
is interpreted as data to write to successive memory locations.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!-- $Id: memoryuse.sgml,v 1.1.4.1 1995-09-17 11:19:33 davidg Exp $ -->
|
||||
<!-- $Id: memoryuse.sgml,v 1.1.4.2 1995-10-12 03:16:13 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<chapt><heading>PC memory utilization<label id="memoryuse"></heading>
|
||||
<sect><heading>PC memory utilization<label id="memoryuse"></heading>
|
||||
|
||||
<p><em>Contributed by &a.joerg;.<newline>
|
||||
16 Apr 1995.</em>
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
<!-- $Id: mirrors.sgml,v 1.1 1995-09-01 04:54:13 jfieber Exp $ -->
|
||||
<!-- $Id: mirrors.sgml,v 1.1.2.1 1995-10-12 03:16:17 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<!--
|
||||
|
|
@ -17,8 +17,8 @@ and on CD-ROM from Walnut Creek CDROM:
|
|||
Walnut Creek CDROM<newline>
|
||||
1547 Palos Verdes Mall, Suite 260<newline>
|
||||
Walnut Creek CA 94596 USA<newline>
|
||||
Phone: +1 510 647-0783<newline>
|
||||
Fax: +1 510 647-0821<newline>
|
||||
Phone: +1 510 674-0783<newline>
|
||||
Fax: +1 510 674-0821<newline>
|
||||
Email: <htmlurl url="mailto:info@cdrom.com" name="info@cdrom.com"><newline>
|
||||
WWW: <htmlurl url="http://www.cdrom.com/" name="http://www.cdrom.com/">
|
||||
</quote>
|
||||
|
|
@ -371,8 +371,8 @@ eBones (Kerberos) from one of the following foreign distribution sites:
|
|||
<itemize>
|
||||
|
||||
<item>
|
||||
<htmlurl url="ftp://skeleton.mikom.csir.co.za/pub/FreeBSD"
|
||||
name="ftp://skeleton.mikom.csir.co.za/pub/FreeBSD"><newline>
|
||||
<htmlurl url="ftp://ftp.internat.freebsd.org/pub/FreeBSD"
|
||||
name="ftp://ftp.internat.freebsd.org/pub/FreeBSD"><newline>
|
||||
Contact: Mark Murray <htmlurl url="mailto:mark@grondar.za"
|
||||
name="mark@grondar.za">.
|
||||
|
||||
|
|
@ -407,4 +407,4 @@ eBones (Kerberos) from one of the following foreign distribution sites:
|
|||
name="count@nic.funet.fi">.
|
||||
|
||||
</itemize>
|
||||
</descrip>
|
||||
</descrip>
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
<!-- $Id: nfs.sgml,v 1.1.1.1.4.1 1995-09-17 11:19:34 davidg Exp $ -->
|
||||
<!-- $Id: nfs.sgml,v 1.1.1.1.4.2 1995-10-12 03:16:20 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<sect><heading>NFS<label id="nfs"></heading>
|
||||
|
|
@ -36,7 +36,7 @@ a FreeBSD system with a lower-performance Ethernet adapter. Also,
|
|||
"/sharedfs" will be the exported NFS filesystem (see "man exports"), and
|
||||
"/project" will be the mount point on the client for the exported file
|
||||
system. In all cases, note that additional options, such as "hard" or
|
||||
"soft" and "bg" may be desireable in your application.
|
||||
"soft" and "bg" may be desirable in your application.
|
||||
|
||||
Examples for the FreeBSD system ("freebox") as the client:
|
||||
in /etc/fstab on freebox:
|
||||
|
|
@ -74,6 +74,6 @@ individually, avoiding the deadlock situation.
|
|||
|
||||
Overruns may still occur when a high-performance workstations is slamming
|
||||
data out to a PC system, but with the better cards, such overruns are
|
||||
not guarranteed on NFS "units". When an overrun occurs, the units affected
|
||||
not guaranteed on NFS "units". When an overrun occurs, the units affected
|
||||
will be retransmitted, and there will be a fair chance that they will be
|
||||
received, assembled, and acknowledged.
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
<!-- $Id: nutshell.sgml,v 1.1.4.1 1995-09-17 11:19:35 davidg Exp $ -->
|
||||
<!-- $Id: nutshell.sgml,v 1.1.4.2 1995-10-12 03:16:22 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<sect><heading>FreeBSD in a nutshell<label id="nutshell"></heading>
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
<!-- $Id: porting.sgml,v 1.2.4.1 1995-09-17 11:19:36 davidg Exp $ -->
|
||||
<!-- $Id: porting.sgml,v 1.2.4.2 1995-10-12 03:16:25 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<sect><heading>Porting applications<label id="porting"></heading>
|
||||
|
|
@ -22,7 +22,7 @@
|
|||
mentioned in this document. Most (if not all) are documented
|
||||
at the start of the <tt>bsd.port.mk</tt> file which can be
|
||||
found in <tt>/usr/share/mk</tt>. This file uses a non-standard tab
|
||||
setting. <tt>Emacs</tt> should recognise the setting on
|
||||
setting. <tt>Emacs</tt> should recognize the setting on
|
||||
loading the file. <tt>vi</tt> or <tt>ex</tt> can be set to
|
||||
using the correct value by typing `<tt>:set tabstop=4</tt>'
|
||||
once the file has been loaded.
|
||||
|
|
@ -120,23 +120,23 @@
|
|||
<p>The minimal <tt>Makefile</tt> would look something like this:
|
||||
|
||||
<tscreen><verb>
|
||||
# New ports collection makefile for: oneko
|
||||
# Version required: 1.1b
|
||||
# Date created: 5 December 1994
|
||||
# Whom: asami
|
||||
#
|
||||
# $Id: porting.sgml,v 1.2.4.1 1995-09-17 11:19:36 davidg Exp $
|
||||
#
|
||||
|
||||
DISTNAME= oneko-1.1b
|
||||
CATEGORIES+= games
|
||||
MASTER_SITES= ftp://ftp.cs.columbia.edu/archives/X11R5/contrib/
|
||||
|
||||
MAINTAINER= asami@FreeBSD.ORG
|
||||
|
||||
USE_IMAKE= yes
|
||||
|
||||
.include <bsd.port.mk>
|
||||
# New ports collection makefile for: oneko
|
||||
# Version required: 1.1b
|
||||
# Date created: 5 December 1994
|
||||
# Whom: asami
|
||||
#
|
||||
# $Id: porting.sgml,v 1.2.4.2 1995-10-12 03:16:25 jfieber Exp $
|
||||
#
|
||||
|
||||
DISTNAME= oneko-1.1b
|
||||
CATEGORIES+= games
|
||||
MASTER_SITES= ftp://ftp.cs.columbia.edu/archives/X11R5/contrib/
|
||||
|
||||
MAINTAINER= asami@FreeBSD.ORG
|
||||
|
||||
USE_IMAKE= yes
|
||||
|
||||
.include <bsd.port.mk>
|
||||
</verb></tscreen>
|
||||
|
||||
<p>See if you can figure it out. Don't worry about the contents
|
||||
|
|
@ -558,7 +558,7 @@ work/foozolix-1.0/
|
|||
|
||||
<sect2>
|
||||
<heading>Dependencies</heading>
|
||||
<p>Many ports depend on other ports. There are three
|
||||
<p>Many ports depend on other ports. There are five
|
||||
variables that you can use to ensure that all the required
|
||||
bits will be on the user's machine.
|
||||
<sect3>
|
||||
|
|
@ -579,22 +579,56 @@ LIB_DEPENDS= tcl\\.7\\.:${PORTSDIR}/lang/tcl
|
|||
to `<tt>ldconfig -r | grep</tt>', so periods should be
|
||||
escaped by two backslashes like in the example above.
|
||||
<sect3>
|
||||
<heading>EXEC_DEPENDS</heading>
|
||||
<p>This variable specifies executables this port depends
|
||||
on. It is a list of `<tt>exec:dir</tt>' pairs
|
||||
where <tt>exec</tt> is the name of the executable, and
|
||||
<tt>dir</tt> is the directory in which to find it in case
|
||||
it's not available. For example,
|
||||
<heading>RUN_DEPENDS</heading>
|
||||
<p>This variable specifies executables this port depends on
|
||||
during run-time. It is a list of `<tt>exec:dir</tt>'
|
||||
pairs where <tt>exec</tt> is the name of the executable,
|
||||
and <tt>dir</tt> is the directory in which to find it in
|
||||
case it's not available. For example,
|
||||
<tscreen><verb>
|
||||
EXEC_DEPENDS= wish:${PORTSDIR}/x11/tk
|
||||
RUN_DEPENDS= wish:${PORTSDIR}/x11/tk
|
||||
</verb></tscreen>
|
||||
will check for an executable called `<tt>wish</tt>', and
|
||||
descend into the <tt>x11/tk</tt> subdirectory of your
|
||||
ports tree to build and install it if it's not found.
|
||||
|
||||
The dependency is checked from within the <tt>install</tt>
|
||||
target. Also, the name of the dependency is put in to the
|
||||
package so that <tt>pkg_add</tt> will automatically
|
||||
install it if it is not on the user's system.
|
||||
<sect3>
|
||||
<heading>BUILD_DEPENDS</heading>
|
||||
<p>This variable specifies executables this port requires to
|
||||
build. Like <tt>RUN_DEPENDS</tt>, it is a list of
|
||||
`<tt>exec:dir</tt>' pairs. For example,
|
||||
<tscreen><verb>
|
||||
BUILD_DEPENDS= unzip:${PORTSDIR}/archivers/unzip
|
||||
</verb></tscreen>
|
||||
will check for an executable called `<tt>unzip</tt>', and
|
||||
descend into the <tt>archivers/unzip</tt> subdirectory of
|
||||
your ports tree to build and install it if it's not found.
|
||||
|
||||
Note that `build' here means everything from extracting to
|
||||
compilation. The dependency is checked from within the
|
||||
<tt>extract</tt> target.
|
||||
<sect3>
|
||||
<heading>FETCH_DEPENDS</heading>
|
||||
<p>This variable specifies executables this port requires to
|
||||
fetch. Like the previous two, it is a list of
|
||||
`<tt>exec:dir</tt>' pairs. For example,
|
||||
<tscreen><verb>
|
||||
FETCH_DEPENDS= ncftp2:${PORTSDIR}/net/ncftp2
|
||||
</verb></tscreen>
|
||||
will check for an executable called `<tt>ncftp2</tt>', and
|
||||
descend into the <tt>net/ncftp2</tt> subdirectory of
|
||||
your ports tree to build and install it if it's not found.
|
||||
|
||||
The dependency is checked from within the <tt>fetch</tt>
|
||||
target.
|
||||
<sect3>
|
||||
<heading>DEPENDS</heading>
|
||||
<p>If there is a dependency that doesn't fall into either of
|
||||
the above two categories, or your port requires to have
|
||||
the above four categories, or your port requires to have
|
||||
the source of the other port extracted (i.e., having them
|
||||
installed is not enough), then use this variable. This is
|
||||
just a list of directories, as there is nothing to check,
|
||||
|
|
@ -653,7 +687,7 @@ EXEC_DEPENDS= wish:${PORTSDIR}/x11/tk
|
|||
<p>Note: The GNU General Public License (GPL), both version 1
|
||||
and 2, shouldn't be a problem for ports.
|
||||
|
||||
<p>Note: If you are a commiter, make sure you update the
|
||||
<p>Note: If you are a committer, make sure you update the
|
||||
<tt>ports/LEGAL</tt> file too.
|
||||
|
||||
<sect1>
|
||||
|
|
@ -691,11 +725,11 @@ EXEC_DEPENDS= wish:${PORTSDIR}/x11/tk
|
|||
user can set in <tt>/etc/make.conf</tt> to disable man page
|
||||
compression. Here's an example:
|
||||
<tscreen><verb>
|
||||
post-install:
|
||||
strip ${PREFIX}/bin/xdl
|
||||
.if !defined(NOMANCOMPRESS)
|
||||
gzip -9nf ${PREFIX}/man/man1/xdl.1
|
||||
.endif
|
||||
post-install:
|
||||
strip ${PREFIX}/bin/xdl
|
||||
.if !defined(NOMANCOMPRESS)
|
||||
gzip -9nf ${PREFIX}/man/man1/xdl.1
|
||||
.endif
|
||||
</verb></tscreen>
|
||||
|
||||
<p>Use the <tt>file</tt> command on the installed executable
|
||||
|
|
@ -790,7 +824,7 @@ post-install:
|
|||
<heading>ldconfig</heading>
|
||||
<p>If your port installs a shared library, add a
|
||||
<tt>post-install</tt> target to your Makefile that runs
|
||||
`<tt>ldconfig -m</tt>' on the directory where the new
|
||||
`<tt>/sbin/ldconfig -m</tt>' on the directory where the new
|
||||
library is installed (usually <tt>${PREFIX}/lib</tt>)
|
||||
to register it into the shared library cache.
|
||||
|
||||
|
|
@ -801,7 +835,7 @@ post-install:
|
|||
as in:
|
||||
<tscreen><verb>
|
||||
lib/libtcl.so.7.3
|
||||
@exec ldconfig -m %D/%F
|
||||
@exec /sbin/ldconfig -m %D/lib
|
||||
</verb></tscreen>
|
||||
|
||||
<p>Note: the `-m' option is new since 2.0.5 and
|
||||
|
|
@ -840,75 +874,75 @@ lib/libtcl.so.7.3
|
|||
important information is easy to locate.
|
||||
|
||||
<tscreen><verb>
|
||||
[the header...just to make it easier for us to identify the ports]
|
||||
# New ports collection makefile for: xdvi
|
||||
# Version required: 2.2 [things like "1.5alpha" are fine here too]
|
||||
# Date created: 26 May 1995
|
||||
[this is the person who did the original port to FreeBSD, in particular, the
|
||||
person who wrote this Makefile]
|
||||
# Whom: Satoshi Asami <asami@FreeBSD.ORG>
|
||||
#
|
||||
# $Id: porting.sgml,v 1.2.4.1 1995-09-17 11:19:36 davidg Exp $
|
||||
[ ^^^^ don't worry about this...it will be automatically filled in by CVS when
|
||||
it is committed to our repository]
|
||||
#
|
||||
|
||||
[section to describe the package itself and main ftp site - DISTNAME
|
||||
is always first, followed by PKGNAME (if necessary), CATEGORIES,
|
||||
KEYWORDs (if necessary) and then MASTER_SITES, and optionally
|
||||
EXTRACT_SUFX or DISTFILES]
|
||||
DISTNAME= xdvi
|
||||
PKGNAME= xdvi-pl18
|
||||
CATEGORIES+= printing
|
||||
[don't forget the trailing slash ("/")!]
|
||||
MASTER_SITES= ftp://crl.dec.com/pub/X11/contrib/applications/
|
||||
[set this if the source is not in the standard ".tar.gz" form]
|
||||
EXTRACT_SUFX= .tar.Z
|
||||
|
||||
[section for distributed patches -- can be empty]
|
||||
PATCH_SITES= ftp://ftp.sra.co.jp/pub/X11/japanese/
|
||||
PATCHFILES= xdvi-18.patch1.gz xdvi-18.patch2.gz
|
||||
|
||||
[maintainer; *mandatory*! This is the person (preferably with commit
|
||||
privileges) who a user can contact for questions and bug reports - this
|
||||
person should be the porter or someone who can forward questions to the
|
||||
original porter reasonably promptly. If you really don't want to have your
|
||||
address here, set it to "ports@FreeBSD.ORG".]
|
||||
MAINTAINER= asami@FreeBSD.ORG
|
||||
|
||||
[dependencies -- can be empty]
|
||||
EXEC_DEPENDS= gs:${PORTSDIR}/print/ghostscript
|
||||
LIB_DEPENDS= Xpm\\.4\\.:${PORTSDIR}/graphics/xpm
|
||||
|
||||
[this section is for other standard bsd.port.mk variables that don't belong to
|
||||
any of the above]
|
||||
[If it extracts to a directory other than ${DISTNAME}...]
|
||||
WRKSRC= ${WRKDIR}/xdvi-new
|
||||
[If it asks questions during configure, build, install...]
|
||||
IS_INTERACTIVE= yes
|
||||
[If it requires "configure" in the distributed source directory to be run...]
|
||||
HAS_CONFIGURE= yes
|
||||
[If it requires GNU make, not /usr/bin/make, to build...]
|
||||
USE_GMAKE= yes
|
||||
[If it is an X application and requires "xmkmf -a" to be run...]
|
||||
USE_IMAKE= yes
|
||||
[et cetera.]
|
||||
|
||||
[non-standard variables to be used in the rules below]
|
||||
MY_FAVORITE_RESPONSE= "yeah, right"
|
||||
|
||||
[then the special rules, in the order they are called]
|
||||
pre-fetch:
|
||||
i go fetch something, yeah
|
||||
|
||||
post-patch:
|
||||
i need to do something after patch, great
|
||||
|
||||
pre-install:
|
||||
and then some more stuff before installing, wow
|
||||
|
||||
[and then the epilogue]
|
||||
.include <bsd.port.mk>
|
||||
[the header...just to make it easier for us to identify the ports]
|
||||
# New ports collection makefile for: xdvi
|
||||
# Version required: 2.2 [things like "1.5alpha" are fine here too]
|
||||
# Date created: 26 May 1995
|
||||
[this is the person who did the original port to FreeBSD, in particular, the
|
||||
person who wrote this Makefile]
|
||||
# Whom: Satoshi Asami <asami@FreeBSD.ORG>
|
||||
#
|
||||
# $Id: porting.sgml,v 1.2.4.2 1995-10-12 03:16:25 jfieber Exp $
|
||||
[ ^^^^ don't worry about this...it will be automatically filled in by CVS when
|
||||
it is committed to our repository]
|
||||
#
|
||||
|
||||
[section to describe the package itself and main ftp site - DISTNAME
|
||||
is always first, followed by PKGNAME (if necessary), CATEGORIES,
|
||||
KEYWORDs (if necessary) and then MASTER_SITES, and optionally
|
||||
EXTRACT_SUFX or DISTFILES]
|
||||
DISTNAME= xdvi
|
||||
PKGNAME= xdvi-pl18
|
||||
CATEGORIES+= printing
|
||||
[don't forget the trailing slash ("/")!]
|
||||
MASTER_SITES= ftp://crl.dec.com/pub/X11/contrib/applications/
|
||||
[set this if the source is not in the standard ".tar.gz" form]
|
||||
EXTRACT_SUFX= .tar.Z
|
||||
|
||||
[section for distributed patches -- can be empty]
|
||||
PATCH_SITES= ftp://ftp.sra.co.jp/pub/X11/japanese/
|
||||
PATCHFILES= xdvi-18.patch1.gz xdvi-18.patch2.gz
|
||||
|
||||
[maintainer; *mandatory*! This is the person (preferably with commit
|
||||
privileges) who a user can contact for questions and bug reports - this
|
||||
person should be the porter or someone who can forward questions to the
|
||||
original porter reasonably promptly. If you really don't want to have your
|
||||
address here, set it to "ports@FreeBSD.ORG".]
|
||||
MAINTAINER= asami@FreeBSD.ORG
|
||||
|
||||
[dependencies -- can be empty]
|
||||
RUN_DEPENDS= gs:${PORTSDIR}/print/ghostscript
|
||||
LIB_DEPENDS= Xpm\\.4\\.:${PORTSDIR}/graphics/xpm
|
||||
|
||||
[this section is for other standard bsd.port.mk variables that don't belong to
|
||||
any of the above]
|
||||
[If it extracts to a directory other than ${DISTNAME}...]
|
||||
WRKSRC= ${WRKDIR}/xdvi-new
|
||||
[If it asks questions during configure, build, install...]
|
||||
IS_INTERACTIVE= yes
|
||||
[If it requires "configure" in the distributed source directory to be run...]
|
||||
HAS_CONFIGURE= yes
|
||||
[If it requires GNU make, not /usr/bin/make, to build...]
|
||||
USE_GMAKE= yes
|
||||
[If it is an X application and requires "xmkmf -a" to be run...]
|
||||
USE_IMAKE= yes
|
||||
[et cetera.]
|
||||
|
||||
[non-standard variables to be used in the rules below]
|
||||
MY_FAVORITE_RESPONSE= "yeah, right"
|
||||
|
||||
[then the special rules, in the order they are called]
|
||||
pre-fetch:
|
||||
i go fetch something, yeah
|
||||
|
||||
post-patch:
|
||||
i need to do something after patch, great
|
||||
|
||||
pre-install:
|
||||
and then some more stuff before installing, wow
|
||||
|
||||
[and then the epilogue]
|
||||
.include <bsd.port.mk>
|
||||
</verb></tscreen>
|
||||
|
||||
<sect1>
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
<!-- $Id: ports.sgml,v 1.2.4.1 1995-09-17 11:19:38 davidg Exp $ -->
|
||||
<!-- $Id: ports.sgml,v 1.2.4.2 1995-10-12 03:16:27 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<sect><heading>The Ports collection<label id="ports"></heading>
|
||||
|
|
@ -85,12 +85,12 @@ FTP site as defined in the relevant Makefile (in the MASTER_SITES
|
|||
line), or some FreeBSD mirror site also carrying a set of distfiles,
|
||||
as does the master FTP site on ftp.FreeBSD.org (aka ftp.cdrom.com) in
|
||||
the directory <tt>/pub/FreeBSD/distfiles</tt>. Note that the files in
|
||||
that directory are not guarenteed to be kept up to date - this is a
|
||||
that directory are not guaranteed to be kept up to date - this is a
|
||||
volunteer project! We can't make any guarantees about the mirror
|
||||
sites either - they are obviously under independant control and don't
|
||||
sites either - they are obviously under independent control and don't
|
||||
even have to mirror the distfiles directory.
|
||||
|
||||
If you have a non-permanant link, you can fetch all the distfiles by
|
||||
If you have a non-permanent link, you can fetch all the distfiles by
|
||||
going to the top of the tree and typing ``make fetch''.
|
||||
|
||||
|
||||
|
|
@ -180,7 +180,7 @@ minute. The most up-to-date copy can be found in:
|
|||
If you find that you still need to go in there and alter things,
|
||||
by all means do so, and then send the diffs to ports@FreeBSD.org if
|
||||
you'd like them to be a part of the default distribution. Please also
|
||||
remember that any changes must respect backwards-compatability with
|
||||
remember that any changes must respect backwards-compatibility with
|
||||
any and all older Makefiles, unless you want a real nightmare of
|
||||
/usr/ports munging ahead of you! Large scale changes will generally
|
||||
not be warmly welcomed unless all the existing makefiles work without
|
||||
|
|
@ -208,7 +208,7 @@ This will print a summary of all ports in the tree.
|
|||
|
||||
<p> For various reasons, when using FTP over the Internet to obtain the
|
||||
source code, you may not always end up with the same copy of the code
|
||||
that the origional porter worked from, and this can lead to problems.
|
||||
that the original porter worked from, and this can lead to problems.
|
||||
So a simple checksumming system has been employed to try and highlight
|
||||
problems in this area.
|
||||
|
||||
|
|
@ -225,7 +225,7 @@ checksum routine. The same technique can be applied to a single port.
|
|||
for that port. Not all ports currently have checksums, but this should be
|
||||
cured soon.
|
||||
|
||||
Some older versions of the system don't recognise the ``checksum''
|
||||
Some older versions of the system don't recognize the ``checksum''
|
||||
target. In that case, try the command
|
||||
<verb>
|
||||
make check-md5
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
<!-- $Id: ppp.sgml,v 1.1.1.1.4.1 1995-09-17 11:19:39 davidg Exp $ -->
|
||||
<!-- $Id: ppp.sgml,v 1.1.1.1.4.2 1995-10-12 03:16:29 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<sect><heading>Setting up kernel PPP<label id="ppp"></heading>
|
||||
|
|
@ -92,7 +92,7 @@ pppd /dev/tty01 19200
|
|||
necessary authorization on the remote host.
|
||||
( Example of such script is attached to the end of this document )
|
||||
|
||||
Use the follwing /etc/ppp/pppdown script to disconnect the PPP line:
|
||||
Use the following /etc/ppp/pppdown script to disconnect the PPP line:
|
||||
<verb>
|
||||
#!/bin/sh
|
||||
pid=`ps ax |grep pppd |grep -v grep|awk '{print $1;}'`
|
||||
|
|
@ -246,7 +246,7 @@ exit
|
|||
This /etc/ppp/kermit.dial script is used for dialing and authorizing on remote host.
|
||||
You will need to customize it for your needs.
|
||||
Put your login and password in this script , also you'll need
|
||||
to change input statement depending on responces from your modem
|
||||
to change input statement depending on responses from your modem
|
||||
and remote host.
|
||||
<verb>
|
||||
;
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
<!-- $Id: relnotes.sgml,v 1.4 1995-08-29 01:42:43 jfieber Exp $ -->
|
||||
<!-- $Id: relnotes.sgml,v 1.4.2.1 1995-10-12 03:16:30 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<!--
|
||||
|
|
@ -176,8 +176,8 @@
|
|||
<tt>i386/isa/diskslice_machdep.c</tt> <tt>i386/isa/wd.c</tt>
|
||||
<tt>scsi/sd.c</tt> <tt>dev/vn/vn.c</tt>
|
||||
|
||||
<tag>Support for Ontrack Disk Manager Version
|
||||
6.0</tag> Support has been added for disks
|
||||
<tag>Support for Ontrack Disk Manager Version 6.0</tag>
|
||||
Support has been added for disks
|
||||
which use Ontrack Disk Manager. The fdisk
|
||||
program does <em>not</em> know about it
|
||||
however, so make all changes using the install
|
||||
|
|
@ -203,8 +203,8 @@
|
|||
|
||||
<p><descrip>
|
||||
|
||||
<tag>Matsushita/Panasonic (Creative) CD-ROM
|
||||
driver</tag> The Matsushita/Panasonic CR-562 and
|
||||
<tag>Matsushita/Panasonic (Creative) CD-ROM driver</tag>
|
||||
The Matsushita/Panasonic CR-562 and
|
||||
CR-563 drives are now supported when connected to
|
||||
a Sound Blaster or 100% compatible host adapter.
|
||||
Up to four host adapters are supported for a
|
||||
|
|
@ -236,8 +236,8 @@
|
|||
Sources involved: <tt>isa/aic7770.c</tt> <tt>pci/aic7870.c</tt>
|
||||
<tt>i386/scsi/*</tt> <tt>sys/dev/aic7xxx/*</tt>
|
||||
|
||||
<tag>NCR5380/NCR53400 SCSI (ProAudio Spectrum)
|
||||
driver</tag> Owner: core
|
||||
<tag>NCR5380/NCR53400 SCSI (ProAudio Spectrum) driver</tag>
|
||||
Owner: core
|
||||
|
||||
Submitted by: Serge Vakulenko (vak@cronyx.ru)
|
||||
|
||||
|
|
@ -255,8 +255,8 @@
|
|||
|
||||
<p><descrip>
|
||||
|
||||
<tag>SDL Communications Riscom/8 Serial Board
|
||||
Driver</tag> Owner: Andrey Chernov
|
||||
<tag>SDL Communications Riscom/8 Serial Board Driver</tag>
|
||||
Owner: Andrey Chernov
|
||||
(ache@FreeBSD.org)
|
||||
|
||||
Sources involved: <tt>isa/rc.c</tt> <tt>isa/rcreg.h</tt>
|
||||
|
|
@ -375,7 +375,7 @@
|
|||
|
||||
Sources involved: <tt>isa/joy.c</tt>
|
||||
|
||||
<tag>National Instruments "LabPC" driver</tag> Owner:
|
||||
<tag>National Instruments ``LabPC'' driver</tag> Owner:
|
||||
Peter Dufault (dufault@hda.com)
|
||||
|
||||
Sources involved: <tt>isa/labpc.c</tt>
|
||||
|
|
@ -398,8 +398,8 @@
|
|||
Sources involved: <tt>isa/sound/vat_audio.c</tt>
|
||||
<tt>isa/sound/vat_audioio.h</tt>
|
||||
|
||||
<tag>National Instruments AT-GPIB and AT-GPIB/TNT
|
||||
GPIB driver</tag> Owner: core
|
||||
<tag>National Instruments AT-GPIB and AT-GPIB/TNT GPIB driver</tag>
|
||||
Owner: core
|
||||
|
||||
Submitted by: Fred Cawthorne
|
||||
(fcawth@delphi.umd.edu)
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
<!-- $Id: scsi.sgml,v 1.1.1.1.4.1 1995-09-17 11:19:39 davidg Exp $ -->
|
||||
<!-- $Id: scsi.sgml,v 1.1.1.1.4.2 1995-10-12 03:16:32 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<!--
|
||||
|
|
@ -15,7 +15,7 @@
|
|||
-->
|
||||
<sect><heading>SCSI<label id="scsi"></heading>
|
||||
|
||||
<p><em>© 1995, &a.wilko;.<newline>3 September 1995.</em>
|
||||
<p><em>Copyright © 1995, &a.wilko;.<newline>3 September 1995.</em>
|
||||
|
||||
SCSI is an acronym for Small Computer Systems Interface. It is an
|
||||
ANSI standard that has become one of the leading I/O buses in the
|
||||
|
|
@ -26,7 +26,7 @@
|
|||
|
||||
After some time an industry effort was started to come to a more strict
|
||||
standard allowing devices from different vendors to work together.
|
||||
This effort was recognised in the ANSI SCSI-1 standard. The SCSI-1
|
||||
This effort was recognized in the ANSI SCSI-1 standard. The SCSI-1
|
||||
standard (approx 1985) is now more or less obsolete. The current
|
||||
standard is SCSI-2 (see <ref id="scsi:further-reading" name="Further
|
||||
reading">), with SCSI-3 on the drawing boards.
|
||||
|
|
@ -44,27 +44,27 @@
|
|||
variants. The oldest and most used is an 8 bit wide bus, with
|
||||
single-ended signals, carried on 50 wires. (If you don't know what
|
||||
single-ended means, don't worry, that is what this document is all
|
||||
about.) Modern designs also use 16 bit wides buses, with
|
||||
about.) Modern designs also use 16 bit wide buses, with
|
||||
differential signals. This allows transfer speeds of
|
||||
20Mbytes/second, on cables lengths of up to 25 meters. SCSI-2
|
||||
allows a maximum buswidth of 32 bits, using an additional cable.
|
||||
allows a maximum bus width of 32 bits, using an additional cable.
|
||||
|
||||
Of course the SCSI bus not only has data lines, but also a number
|
||||
of control signals. A very elaborate protocol is part of the
|
||||
standard to allow multiple devices to share the bus in an efficient
|
||||
manner. In SCSI-2, the data is always checked using a seperate
|
||||
manner. In SCSI-2, the data is always checked using a separate
|
||||
parity line. In pre-SCSI-2 designs parity was optional.
|
||||
|
||||
In SCSI-3 even faster bustypes are introduced, along with a serial
|
||||
In SCSI-3 even faster bus types are introduced, along with a serial
|
||||
SCSI bus that reduces the cabling overhead and allows a higher
|
||||
maximum buslength.
|
||||
maximum bus length.
|
||||
|
||||
As you could have guessed from the description above, SCSI devices
|
||||
are intelligent. They have to be to adhere to the SCSI standard
|
||||
(which is over 2 inches thick BTW). So, for a hard disk drive for
|
||||
instance you do not specify a head/cylinder/sector to address a
|
||||
particular block, but simply the number of the block you want.
|
||||
Elaborate caching schemes, automatic badblock replacement etc
|
||||
Elaborate caching schemes, automatic bad block replacement etc
|
||||
are all made possible by this 'intelligent device' approach.
|
||||
|
||||
On a SCSI bus, each possible pair of devices can communicate. If
|
||||
|
|
@ -78,7 +78,7 @@
|
|||
because it is not absolutely sure that the implementation of an old
|
||||
device follows the (old) standard closely enough to be acceptable
|
||||
on a new bus. Modern devices are usually more well-behaved,
|
||||
because the standardisation has become more strict and is better
|
||||
because the standardization has become more strict and is better
|
||||
adhered to by the device manufacturers. Generally speaking, the
|
||||
chances of getting a working set of devices on a single bus is
|
||||
better when all the devices are SCSI-2 or newer. This does not
|
||||
|
|
@ -149,11 +149,11 @@
|
|||
that on a narrow (8 bit) bus 10 Mbytes/sec are possible instead
|
||||
of 5 Mbytes/sec for 'slow' SCSI. More on this later.
|
||||
|
||||
It should be noted that the datalines > 8 are only used for
|
||||
datatransfers and device addressing. The transfers of commands
|
||||
It should be noted that the data lines > 8 are only used for
|
||||
data transfers and device addressing. The transfers of commands
|
||||
and status messages etc are only performed on the lowest 8
|
||||
datalines. The standard allows narrow devices to operate on
|
||||
a wide bus. The usable buswidth is negotiated
|
||||
data lines. The standard allows narrow devices to operate on
|
||||
a wide bus. The usable bus width is negotiated
|
||||
between the devices. You have to watch your device addressing
|
||||
closely when mixing wide and narrow.
|
||||
|
||||
|
|
@ -163,7 +163,7 @@
|
|||
0 Volts (indeed, TTL levels) and are relative to a COMMON
|
||||
ground reference. A singled ended 8 bit SCSI bus has
|
||||
approximately 25 ground lines, who are all tied to a single
|
||||
'rail' on all devices. A standard single ended bus has a
|
||||
`rail' on all devices. A standard single ended bus has a
|
||||
maximum length of 6 meters. If the same bus is used with
|
||||
fast-SCSI devices, the maximum length allowed drops to 3
|
||||
meters. Fast-SCSI means that instead of 5Mbytes/sec the bus
|
||||
|
|
@ -174,7 +174,7 @@
|
|||
bus must adhere to the length restrictions for fast buses!
|
||||
|
||||
It is obvious that with the newer fast-SCSI devices the
|
||||
buslength can become a real bottleneck. This is why the
|
||||
bus length can become a real bottleneck. This is why the
|
||||
differential SCSI bus was introduced in the SCSI-2 standard.
|
||||
|
||||
For connector pinning and connector types please refer to the
|
||||
|
|
@ -236,8 +236,8 @@
|
|||
reconfigure your SCSI bus. There is enough variation in even
|
||||
these simple tiny things to make finding the exact replacement
|
||||
a frustrating business. There are also SCSI devices that have
|
||||
a single jumper to enable or disable a builtin terminator.
|
||||
There are special terminators you can stick onto a flatcable
|
||||
a single jumper to enable or disable a built-in terminator.
|
||||
There are special terminators you can stick onto a flat cable
|
||||
bus. Others look like external connectors, so a connector hood
|
||||
without a cable. So, lots of choice as you can see.
|
||||
|
||||
|
|
@ -245,7 +245,7 @@
|
|||
from simple resistor (passive) terminators to active
|
||||
terminators. Active terminators contain more or less elaborate
|
||||
circuits to give more clean bus signals. The general consensus
|
||||
seems to be that the usefullnes of active termination increases
|
||||
seems to be that the usefulness of active termination increases
|
||||
when you have long buses and/or fast devices. If you ever have
|
||||
problems with your SCSI buses you might consider trying an
|
||||
active terminator. Try to borrow one first, they reputedly are
|
||||
|
|
@ -325,7 +325,7 @@
|
|||
|
||||
This is done by means of the SCSI or target ID. Each device has
|
||||
a unique target ID. You can select the ID to which a device
|
||||
must respond using a set of jumpers, or a dipswitch, or
|
||||
must respond using a set of jumpers, or a dip switch, or
|
||||
something similar. Consult the documentation of your device for
|
||||
more information.
|
||||
|
||||
|
|
@ -334,26 +334,26 @@
|
|||
|
||||
For an 8 bit bus, a maximum of 8 targets is possible. The
|
||||
maximum is 8 because the selection is done bitwise using the 8
|
||||
datalines on the bus. For wide this increases to the number of
|
||||
datalines.
|
||||
data lines on the bus. For wide this increases to the number of
|
||||
data lines.
|
||||
|
||||
The higher the SCSI target ID, the higher the priority the
|
||||
devices has. When it comes to arbitration between devices that
|
||||
want to use the bus at the same time, the device that has the
|
||||
highest SCSI ID will win. This also means that the SCSI
|
||||
hostadapter usually uses target ID 7 (for narrow buses).
|
||||
host adapter usually uses target ID 7 (for narrow buses).
|
||||
|
||||
For a further subdivision, the standard allows for Logical
|
||||
Units or LUNs for short. A single target ID may have multiple
|
||||
LUNs. For example, a tape device including a tape changer may
|
||||
have LUN 0 for the tape device itself, and LUN 1 for the
|
||||
tapechanger. In this way, the host system can address each of
|
||||
tape changer. In this way, the host system can address each of
|
||||
the parts of the tape unit as desired.
|
||||
|
||||
<sect2><heading>Bus layout</heading>
|
||||
<p>
|
||||
SCSI buses are linear. So, not shaped like Y-junctions, star
|
||||
topologies, cobwebbs or whatever else people might want to
|
||||
topologies, cobwebs or whatever else people might want to
|
||||
invent.
|
||||
|
||||
You might notice that the terminator issue discussed earlier
|
||||
|
|
@ -375,8 +375,8 @@
|
|||
When you want to use a SCSI disk on your PC as boot disk, you
|
||||
must aware of some quirks related to PC BIOSes. The PC BIOS in
|
||||
it's first incarnation used a low level physical interface to the
|
||||
harddisk. So, you had to tell the BIOS (using a setup tool or a
|
||||
BIOS builtin setup) how your disk physically looked like. This
|
||||
hard disk. So, you had to tell the BIOS (using a setup tool or a
|
||||
BIOS built-in setup) how your disk physically looked like. This
|
||||
involved stating number of heads, number of cylinders, number of
|
||||
sectors per track, obscure things like precompensation and
|
||||
reduced write current cylinder etc.
|
||||
|
|
@ -388,9 +388,9 @@
|
|||
|
||||
The SCSI host adapter or SCSI controller you have put in your
|
||||
AT/EISA/PCI/whatever bus to connect your disk therefore has it's
|
||||
own onboard BIOS. During system startup, the SCSI BIOS takes over
|
||||
the harddisk interface routines from the system BIOS. To fool the
|
||||
system BIOS, the system setup is normally set to No harddisk
|
||||
own on-board BIOS. During system startup, the SCSI BIOS takes over
|
||||
the hard disk interface routines from the system BIOS. To fool the
|
||||
system BIOS, the system setup is normally set to No hard disk
|
||||
present. Obvious, isn't it?
|
||||
|
||||
The SCSI BIOS itself presents to the system a so called
|
||||
|
|
@ -405,8 +405,8 @@
|
|||
|
||||
Right.. All is well now?! No, it isn't. The system BIOS has
|
||||
another quirk you might run into. The number of cylinders of a
|
||||
bootable harddisk cannot be greater than 1024. Using the
|
||||
translation above, this is a showstopper for disks greater than
|
||||
bootable hard disk cannot be greater than 1024. Using the
|
||||
translation above, this is a show-stopper for disks greater than
|
||||
1 Gb. With disk capacities going up all the time this is causing
|
||||
problems.
|
||||
|
||||
|
|
@ -424,7 +424,7 @@
|
|||
translated values your host adapter uses.
|
||||
|
||||
Failing to observe the translation issue might be un-bootable systems or
|
||||
operating systems overwriting eachothers partitions. Using fdisk
|
||||
operating systems overwriting each others partitions. Using fdisk
|
||||
you should be able to see all partitions.
|
||||
|
||||
As promised earlier: what is this talk about 'lying' devices? As
|
||||
|
|
@ -464,12 +464,12 @@ Feb 9 19:33:46 yedi /386bsd: sd0: 636MB (1303250 total sec), 1632 cyl, 15 head,
|
|||
|
||||
The multi level design allows a decoupling of low-level bit
|
||||
banging and more high level stuff. Adding support for another
|
||||
piece of hardware is a much more managable problem.
|
||||
piece of hardware is a much more manageable problem.
|
||||
|
||||
<sect2><heading>Kernel configuration</heading>
|
||||
<p>
|
||||
Dependent on your hardware, the kernel configuration file must
|
||||
contain one or more lines describing your hostadapter(s).
|
||||
contain one or more lines describing your host adapter(s).
|
||||
This includes I/O addresses, interrupts etc.
|
||||
Consult the man page for your
|
||||
adapter driver to get more info. Apart from that, check out
|
||||
|
|
@ -586,7 +586,7 @@ device cd0 #Only need one of these, the code dynamically grows &lsq
|
|||
above will work fine when you have only 2 SCSI disks.
|
||||
|
||||
Use <tt>man 4 scsi</tt> to check for the latest info on the SCSI
|
||||
subsystem. For more detailed info on hostadapter drivers use eg
|
||||
subsystem. For more detailed info on host adapter drivers use eg
|
||||
<tt>man 4 aha</tt> for info on the Adaptec 154x driver.
|
||||
|
||||
<sect2><heading>Tuning your SCSI kernel setup</heading>
|
||||
|
|
@ -598,13 +598,13 @@ device cd0 #Only need one of these, the code dynamically grows &lsq
|
|||
|
||||
To work around this problem, FreeBSD allows a tunable delay time before
|
||||
the SCSI devices are probed following a SCSI bus reset. You can set this
|
||||
delaytime in your kernel configuration file using a line like:
|
||||
delay time in your kernel configuration file using a line like:
|
||||
|
||||
<verb>
|
||||
options "SCSI_DELAY=15" #Be pessimistic about Joe SCSI device
|
||||
</verb>
|
||||
This line sets the delay time to 15 seconds. On my own system I had to
|
||||
use 3 seconds minimum to get my trusty old CDROM drive to be recognised.
|
||||
use 3 seconds minimum to get my trusty old CDROM drive to be recognized.
|
||||
Start with a high value (say 30 seconds or so) when you have problems
|
||||
with device recognition. If this helps, tune it back until it just stays
|
||||
working.
|
||||
|
|
@ -616,7 +616,7 @@ options "SCSI_DELAY=15" #Be pessimistic about Joe SCSI device
|
|||
Some vendors do a better job then others.
|
||||
|
||||
This is exactly where the 'rogue' devices come into view. Rogues are
|
||||
devices that are recognised by the FreeBSD kernel as behaving slightly
|
||||
devices that are recognized by the FreeBSD kernel as behaving slightly
|
||||
(...) non-standard. Rogue devices are reported by the kernel when
|
||||
booting. An example for two of my cartridge tape units:
|
||||
|
||||
|
|
@ -634,7 +634,7 @@ Mar 29 21:16:37 yedi /386bsd: st1: Archive Viper 150 is a known rogue
|
|||
believing that there are 8 LUNs at that particular target ID. The
|
||||
confusion this causes is left as an exercise to the user.
|
||||
|
||||
The SCSI subsystem of FreeBSD recognises devices with bad habits by
|
||||
The SCSI subsystem of FreeBSD recognizes devices with bad habits by
|
||||
looking at the INQUIRY response they send when probed. Because the
|
||||
INQUIRY response also includes the version number of the device
|
||||
firmware, it is even possible that for different firmware versions
|
||||
|
|
@ -655,7 +655,7 @@ Mar 29 21:16:37 yedi /386bsd: st1: Archive Viper 150 is a known rogue
|
|||
FreeBSD. It must be noted however that there might be some rough edges.
|
||||
|
||||
For instance an Adaptec 1542 controller can be set to use different
|
||||
transferspeeds on the host bus (ISA or AT in this case). The controller
|
||||
transfer speeds on the host bus (ISA or AT in this case). The controller
|
||||
is settable to different rates because not all motherboards can handle
|
||||
the higher speeds. Problems like hangups, bad data etc might be the
|
||||
result of using a higher data transfer rate then your motherboard
|
||||
|
|
@ -699,7 +699,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed
|
|||
<item>
|
||||
Make a minimal bus config with as little devices as possible.
|
||||
<item>
|
||||
If possible, configure your hostadapter to use slow bus speeds.
|
||||
If possible, configure your host adapter to use slow bus speeds.
|
||||
</itemize>
|
||||
|
||||
<sect1><heading>Further reading<label id="scsi:further-reading"></heading>
|
||||
|
|
@ -760,6 +760,6 @@ Suite 214, 1210 S. Bascom Ave., San Jose, CA 92128, (408) 293-0800
|
|||
are noteworthy places to look for more info. You can also
|
||||
find the SCSI-Faq there, which is posted periodically.
|
||||
|
||||
Most major SCSI device and hostadapter suppliers operate ftp sites
|
||||
Most major SCSI device and host adapter suppliers operate ftp sites
|
||||
and/or BBS systems. They may be valuable sources of information
|
||||
about the devices you own.
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
<!-- $Id: sections.sgml,v 1.1 1995-09-03 21:12:29 jfieber Exp $ -->
|
||||
<!-- $Id: sections.sgml,v 1.1.2.1 1995-10-12 03:16:34 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<!-- Entities containing all the pieces of the handbook are -->
|
||||
|
|
@ -10,9 +10,12 @@
|
|||
<!ENTITY contrib SYSTEM "contrib.sgml">
|
||||
<!ENTITY ctm SYSTEM "ctm.sgml">
|
||||
<!ENTITY current SYSTEM "current.sgml">
|
||||
<!ENTITY crypt SYSTEM "crypt.sgml">
|
||||
<!ENTITY dialup SYSTEM "dialup.sgml">
|
||||
<!ENTITY diskless SYSTEM "diskless.sgml">
|
||||
<!ENTITY dma SYSTEM "dma.sgml">
|
||||
<!ENTITY eresources SYSTEM "eresources.sgml">
|
||||
<!ENTITY esdi SYSTEM "esdi.sgml">
|
||||
<!ENTITY glossary SYSTEM "glossary.sgml">
|
||||
<!ENTITY history SYSTEM "history.sgml">
|
||||
<!ENTITY hw SYSTEM "hw.sgml">
|
||||
|
|
@ -27,8 +30,11 @@
|
|||
<!ENTITY porting SYSTEM "porting.sgml">
|
||||
<!ENTITY ports SYSTEM "ports.sgml">
|
||||
<!ENTITY ppp SYSTEM "ppp.sgml">
|
||||
<!ENTITY printing SYSTEM "printing.sgml">
|
||||
<!ENTITY relnotes SYSTEM "relnotes.sgml">
|
||||
<!ENTITY routing SYSTEM "routing.sgml">
|
||||
<!ENTITY scsi SYSTEM "scsi.sgml">
|
||||
<!ENTITY skey SYSTEM "skey.sgml">
|
||||
<!ENTITY slipc SYSTEM "slipc.sgml">
|
||||
<!ENTITY slips SYSTEM "slips.sgml">
|
||||
<!ENTITY submitters SYSTEM "submitters.sgml">
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
<!-- $Id: slipc.sgml,v 1.1.1.1.4.2 1995-09-17 11:19:41 davidg Exp $ -->
|
||||
<!-- $Id: slipc.sgml,v 1.1.1.1.4.3 1995-10-12 03:16:35 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<sect><heading>Setting up a SLIP client<label id="slipc"></heading>
|
||||
|
|
@ -17,10 +17,10 @@ mileage may vary.
|
|||
-->
|
||||
|
||||
First, determine which serial port your modem is connected to. I have
|
||||
a symbolic link /dev/modem -> cuaa1, and only use the modem name in my
|
||||
a symbolic link <tt>/dev/modem -> cuaa1</tt>, and only use the modem name in my
|
||||
configuration files. It can become quite cumbersome when you need to
|
||||
fix a bunch of files in /etc and .kermrc's all over the system! (Note
|
||||
that /dev/cuaa0 is COM1, cuaa1 is COM2, etc.)
|
||||
fix a bunch of files in <tt>/etc</tt> and <tt>.kermrc</tt>'s all over the system! (Note
|
||||
that <tt>/dev/cuaa0</tt> is COM1, <tt>cuaa1</tt> is COM2, etc.)
|
||||
|
||||
Make sure you have
|
||||
<verb>
|
||||
|
|
|
|||
|
|
@ -1,11 +1,11 @@
|
|||
<!-- $Id: submitters.sgml,v 1.2.4.1 1995-09-17 11:19:43 davidg Exp $ -->
|
||||
<!-- $Id: submitters.sgml,v 1.2.4.2 1995-10-12 03:16:37 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<chapt><heading>Contributing to FreeBSD<label id="submitters"></heading>
|
||||
|
||||
<p><em>Contributed by &a.jkh;.</em>
|
||||
|
||||
This guide is intended for those who are moderately familar with
|
||||
This guide is intended for those who are moderately familiar with
|
||||
FreeBSD and have reached a point where they have some locally
|
||||
developed customizations or fixes to the system which they'd like to
|
||||
incorporate back into the mainstream sources. Submitting something to
|
||||
|
|
@ -19,14 +19,14 @@ are also what FreeBSD lives and grows from, so your contributions are
|
|||
very important to the continued survival of this communal effort of
|
||||
ours---we're very glad to see you reading this document!
|
||||
|
||||
Submissions to FreeBSD can generally be classified into four catagories:
|
||||
Submissions to FreeBSD can generally be classified into four categories:
|
||||
<enum>
|
||||
<item>Ideas, general suggestions, bug reports.
|
||||
<item>Changes to existing sources.
|
||||
<item>Significant contribution of a large body of independant work.
|
||||
<item>Significant contribution of a large body of independent work.
|
||||
<item>Porting of freely available software.
|
||||
</enum>
|
||||
A submission in <em>any</em> of these catagories is highly welcomed as they
|
||||
A submission in <em>any</em> of these categories is highly welcomed as they
|
||||
are each, in their own way, quite significant to the project.
|
||||
|
||||
|
||||
|
|
@ -39,7 +39,7 @@ are each, in their own way, quite significant to the project.
|
|||
Likewise, people with an interest
|
||||
in such things (and a tolerance for a <em>high</em>
|
||||
volume of mail!) may
|
||||
subscribe to the hackers mailing list by sendimg mail to
|
||||
subscribe to the hackers mailing list by sending mail to
|
||||
<tt><majordomo@freebsd.org></tt>.
|
||||
See <ref id="eresources:mail" name="mailing lists">
|
||||
for more information about this and other mailing lists.
|
||||
|
|
@ -82,11 +82,11 @@ are each, in their own way, quite significant to the project.
|
|||
FreeBSD maintainers. This is done with the <tt>diff(1)</tt> command,
|
||||
with the `context diff' form being preferred. For example:
|
||||
<tscreen><verb>
|
||||
diff -c <oldfile> <newfile>
|
||||
diff -c oldfile newfile
|
||||
</verb></tscreen>
|
||||
or
|
||||
<tscreen><verb>
|
||||
diff -c -r <olddir> <newdir>
|
||||
diff -c -r olddir newdir
|
||||
</verb></tscreen>
|
||||
would generate such a set of context diffs for the given source file
|
||||
or directory hierarchy. See the man page for <tt>diff(1)</tt> for more
|
||||
|
|
@ -149,7 +149,7 @@ diff -c -r <olddir> <newdir>
|
|||
additional contributions under this license. Code under the GPL
|
||||
also goes into a different part of the tree, that being
|
||||
<tt>/sys/gnu</tt> or <tt>/usr/src/gnu</tt>, and is therefore
|
||||
easily identifable to anyone for whom the GPL presents a problem.
|
||||
easily identifiable to anyone for whom the GPL presents a problem.
|
||||
</enum>
|
||||
|
||||
<p>Contributions coming under any other type of copyright must be
|
||||
|
|
@ -193,7 +193,7 @@ 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: submitters.sgml,v 1.2.4.1 1995-09-17 11:19:43 davidg Exp $
|
||||
$Id: submitters.sgml,v 1.2.4.2 1995-10-12 03:16:37 jfieber Exp $
|
||||
</verb></tscreen>
|
||||
For your convenience, a copy of this text can be found in
|
||||
<tt>/usr/share/examples/etc/bsd-style-copyright</tt>.
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
<!-- $Id: sup.sgml,v 1.2.4.2 1995-09-17 11:19:44 davidg Exp $ -->
|
||||
<!-- $Id: sup.sgml,v 1.2.4.3 1995-10-12 03:16:39 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
|
||||
|
|
@ -17,15 +17,15 @@ way of doing this is to grab the sup.tgz package from:
|
|||
ftp://ftp.FreeBSD.ORG:/pub/FreeBSD/packages/sup.tgz
|
||||
</verb>
|
||||
Install the sup package using pkg_add and add the following line to
|
||||
your /etc/services file:
|
||||
your /etc/services file (if it doesn't already exist):
|
||||
<verb>
|
||||
sup 871/tcp #sup
|
||||
supfilesrv 871/tcp # for SUP
|
||||
</verb>
|
||||
|
||||
SUP gets the information it needs to run from a configuration file
|
||||
called a supfile. This file tells sup what collections it will be updating
|
||||
and/or installing and where they go. The supfile in this directory will
|
||||
sup both the source and ports collection - look for the blank line seperating
|
||||
sup both the source and ports collection - look for the blank line separating
|
||||
the two collections; if you don't want ports, you can simply delete all the
|
||||
ports entries. If you're inside the United States, you may also uncomment
|
||||
the `secure' collection line to grab the DES code. If you're outside the
|
||||
|
|
@ -35,7 +35,7 @@ collection and then go look on braae.ru.ac.za, where it's available for
|
|||
anonymous ftp for those outside the U.S.
|
||||
|
||||
Any other distributions you do not wish to receive can be commented out
|
||||
with a # at the begining of the distribution line.
|
||||
with a # at the beginning of the distribution line.
|
||||
|
||||
Once this is setup, you're ready to go. To start sup type:
|
||||
<verb>
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
<!-- $Id: troubleshooting.sgml,v 1.1.1.1.4.1 1995-09-17 11:19:45 davidg Exp $ -->
|
||||
<!-- $Id: troubleshooting.sgml,v 1.1.1.1.4.2 1995-10-12 03:16:40 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<chapt><heading>Troubleshooting<label id="troubleshooting"></heading>
|
||||
|
|
|
|||
Loading…
Reference in a new issue