diff options
| author | Jordan K. Hubbard <jkh@FreeBSD.org> | 1997-10-04 11:16:57 +0000 |
|---|---|---|
| committer | Jordan K. Hubbard <jkh@FreeBSD.org> | 1997-10-04 11:16:57 +0000 |
| commit | 68799f0e1fd3a7416f2f967dc808513d0e073fe2 (patch) | |
| tree | 56d759fbf93fe8b7c16cc1a49e5fe3cd7396c37a /FAQ/FAQ.sgml | |
| parent | 63197b569e80727dcff1930e537101ef9b46eac2 (diff) | |
Update to reflect a more current state of affairs.
Notes
svn path=/head/; revision=2030
Diffstat (limited to 'FAQ/FAQ.sgml')
| -rw-r--r-- | FAQ/FAQ.sgml | 733 |
1 files changed, 360 insertions, 373 deletions
diff --git a/FAQ/FAQ.sgml b/FAQ/FAQ.sgml index 1bbecc5689..a495a294aa 100644 --- a/FAQ/FAQ.sgml +++ b/FAQ/FAQ.sgml @@ -1,16 +1,16 @@ <!DOCTYPE linuxdoc PUBLIC "-//FreeBSD//DTD linuxdoc//EN"> -<!-- $Id: FAQ.sgml,v 1.80 1997-10-04 00:19:58 brian Exp $ --> +<!-- $Id: FAQ.sgml,v 1.81 1997-10-04 11:16:57 jkh Exp $ --> <article> <title>Frequently Asked Questions for FreeBSD 2.X -<author>Maintainer: Peter da Silva <tt><htmlurl url='mailto:peter@taronga.com' - name='<peter@taronga.com>'></tt> -<date>$Date: 1997-10-04 00:19:58 $</date> +<author>Please send submissions to <tt><htmlurl url='mailto:faq@freebsd.org' + name='<faq@freebsd.org>'></tt> +<date>$Date: 1997-10-04 11:16:57 $</date> <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. +assumed to be relevant to FreeBSD 2.0.5 and later, unless otherwise noted. Any entries with a <XXX> are under construction. @@ -118,7 +118,7 @@ Any entries with a <XXX> are under construction. down its branch and been better shaken-out. <sect1> - <heading>What is FreeBSD-current?</heading> + <heading>What is FreeBSD-current?<label id="current"></heading> <p> <url url="../handbook/current.html" name="FreeBSD-current"> is the development version of the operating system, which will in due @@ -128,79 +128,88 @@ Any entries with a <XXX> are under construction. in the <url url="../handbook/handbook.html" name="handbook"> for details on running -current. - <sect1> - <heading> What are ``snapshots''?<label id="snapshots"></heading> - <p> - Every now and again, a <url url="../releases/snapshots.html" - name="snapshot"> is taken of the development code and prepared - more or less as if it were an official release; recently, - CDROMs have even been cut from the snapshots. The intention is to:- + <p>Every now and again, a <url url="../releases/snapshots.html" + name="snapshot"> release is also made of this -current development + code, CDROM distributions of the occasional snapshot even now being + made available. The goals behind each snapshot release are: <itemize> - <item>Test the latest version of the installation software. - <item>Allow people who would like to run -current, but who don't + <item>To test the latest version of the installation software. + + <item>To give people who would like to run -current but who don't have the time and/or bandwidth to follow it on a day-to-day - basis, an easy way to bootstrap it onto their systems. - <item> - Preserve a fixed reference point for the code in question, - in case we really break something badly later. + basis an easy way of bootstrapping it onto their systems. - <item>Ensure that a new feature in need of testing has the + <item>To preserve a fixed reference point for the code in question, + just in case we break something really badly later. :) + + <item>To ensure that any new features in need of testing have the greatest possible number of potential testers. </itemize> - No claim is made that a snapshot is regarded as being of - ``production quality'' for any purpose. For that, you will - have to stick to full releases. + No claims are made that any snapshot can be considered + ``production quality'' for any purpose. For stability + and tested mettle, you will have to stick to full releases. + + <p>Snapshot releases are directly available from <url + url="ftp://current.freebsd.org/pub/FreeBSD/"> and are generated, + on the average, once a day for both the 3.0-current and 2.2-stable + branches. <sect1> - <heading> What about FreeBSD-stable?</heading> + <heading> What is the FreeBSD-stable concept?</heading> <p> - Back when FreeBSD 2.0.5 was released, we branched FreeBSD - development into two parts. One branch was named <url + Back when FreeBSD 2.0.5 was released, we decided to branch FreeBSD + development into two parts. One branch was named <url url="../handbook/stable.html" name="-stable">, with the intention that only well-tested bug fixes and small incremental enhancements would be made to it (for Internet Service Providers and other commercial enterprises for whom sudden shifts or experimental features are quite undesirable). The other branch was 3.0-current, which essentially has been one unbroken line leading - towards 3.0-RELEASE since 2.0 was released. If a little ASCII art - would help, this is how it looks: + towards 3.0-RELEASE (and beyond) since 2.0 was released. If a + little ASCII art would help, this is how it looks: <verb> - 2.0 - | - | - | - 2.0.5 -> 2.1 -> 2.1.5 -> 2.1.6 -> 2.1.7 [2.1-stable ends] - | (Feb 1997) - | - [3.0-current] 2.2-SNAPs - | - | - 2.2-ALPHA -> -BETA -> -GAMMA -> 2.2-RELEASE -> [2.2-stable] - | (Mar 1997) - | - 3.0-SNAPs (Q1 1997) - | - | - \|/ - + - - [future 3.x releases] + 2.0 + | + | + | [2.1-stable] + *BRANCH* 2.0.5 -> 2.1 -> 2.1.5 -> 2.1.6 -> 2.1.7.1 [2.1-stable ends] + | (Mar 1997) + | + | + | [2.2-stable] + *BRANCH* 2.2.1 -> 2.2.2-RELEASE -> 2.2.5-RELEASE -> ... + | (Mar 1997) (Nov 1997) + | + | + 3.0-SNAPs (started Q1 1997) + | + | + 3.0.0-RELEASE (Q1 1998) + | + \|/ + + + [future 3.x releases] </verb> <p> The -current branch is slowly progressing towards 3.0 and beyond, - whereas the existing -stable branch was terminated by the - release of 2.2, resurrecting itself as 2.2-stable. + whereas the existing 2.1-stable branch was superseded by the + release of 2.2.0, the "stability branch" resurrecting itself as + 2.2-stable. 3.0-current will continue to be where the active + development takes place, up until the actual release of 3.0. + At that point, 3.0 will become yet another branch and 3.1-current + will become the next "current branch". + <sect1> - <heading>Why is the -stable branch ending with 2.1.7? </heading> + <heading>Why is the 2.1-stable branch ending with 2.1.7.1? </heading> <p> - While we'd certainly like to be able to continue both branches of + While we'd certainly like to be able to continue 3 branches of development, we've found that the version control tools available to us are not particularly well-suited for this; in fact, they quickly result in a maintenance nightmare for any branch which lives much - beyond 2-3 months. The -stable branch has, by contrast, lasted for + beyond 2-3 months. The 2.1-stable branch has, by contrast, lasted for well over a year and what little sanity the FreeBSD developers have left would be in serious jeopardy if we continued in this way. Perhaps in the future we'll figure out another model which gives @@ -228,58 +237,6 @@ Any entries with a <XXX> are under construction. leading up to a release. <sect1> - <heading>How do I make my own custom release?<label id="custrel"></heading> - <p> - To make a release you need to do three things: First, you need to - be running a kernel with the <tt/vn/ driver configured in. Add - this to your kernel config file and build a new kernel: - - <verb> -pseudo-device vn #Vnode driver (turns a file into a device) - </verb> - - Second, you have to have the whole CVS repository at hand. - To get this you can use - <url url="../handbook/cvsup.html" name="CVSUP"> - but your tag value, if any, should be `.' and your release name - should be cvs: - - <verb> -*default prefix=/home/ncvs base=/a host=cvsup.FreeBSD.org release=cvs delete compress use-rel=suffix - -## Main Source Tree -src-all -src-eBones -src-secure - -# Other stuff -ports-all -www - </verb> - - Then run <tt/cvsup -g supfile/ to suck all the good bits into your - box... - - Finally, you need a chunk of empty space to build into. Let's - say it's in <tt>/some/big/filesystem</tt>, and from the example - above you've got the CVS repository in <tt>/home/ncvs</tt>: - - <verb> -setenv CVSROOT /home/ncvs # or export CVSROOT=/home/ncvs -cd /usr/src/release -make release BUILDNAME=3.0-MY-SNAP CHROOTDIR=/some/big/filesystem/release - </verb> - - An entire release will be built in - <tt>/some/big/filesystem/release</tt> - and you will have a full FTP-type installation in - <tt>/some/big/filesystem/release/R/ftp</tt> - when you're done. If you want to build your SNAP along some other - branch than -current, you can also add <tt/RELEASETAG=SOMETAG/ to - the make release command line above, e.g. <tt/RELEASETAG=RELENG_2_2/ - would build an up-to-the- minute 2.2 GAMMA snapshot. - - <sect1> <heading> Is FreeBSD only available for PCs?</heading> <p> At present, yes, though a port to the DEC Alpha architecture @@ -300,32 +257,41 @@ make release BUILDNAME=3.0-MY-SNAP CHROOTDIR=/some/big/filesystem/release FreeBSD source tree. <p> However, most non-trivial changes are discussed in advance in the - mailing lists, and there are no restrictions on who may take part + <ref id="mailing" name="mailing lists">, and there are no restrictions on who may take part in the discussion. <sect1> <heading>Where can I get FreeBSD?<label id="where-get"></heading> <p> - The distribution is available via anonymous ftp from: - <url url="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/" name="the FreeBSD FTP site"> - - For the current stable release, 2.1.7.1R, look in: + Every significant release of FreeBSD is available via anonymous ftp from the + <url url="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/" name="FreeBSD FTP site">: + <itemize> + <item> + For the current 2.1-stable release, 2.1.7.1R, see the <url url="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/2.1.7.1-RELEASE/" - name="FreeBSD 2.1.7.1-RELEASE"> + name="2.1.7.1-RELEASE"> directory. - For the current 2.2 branch release, 2.2.2R, look in: + <item> + For the current 2.2-stable release, 2.2.2R, see the <url url="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/2.2.2-RELEASE/" - name="FreeBSD 2.2.2-RELEASE"> + name="2.2.2-RELEASE"> directory. - <url url="ftp://releng22.freebsd.org/pub/FreeBSD/" name="SNAPshot releases"> - are also made once a day along the RELENG_2_2 branch (2.2.2 -> 2.2.x) - as it winds its way towards the next point release on the 2.2 branch - (2.2.3, possibly, or maybe 2.2.5 depending on the change delta). With - the occasional exception of accidental breakage, the RELENG_2_2 - branch is being carefully maintained (no experimental changes, fixes only - after testing in -current) and these snapshots of it may be considered - "2.2.2+" for all intents and purposes and more desirable than 2.2.2 for new - installations. + <item> + <url url="ftp://releng22.freebsd.org/pub/FreeBSD/" name="2.2 Snapshot"> + releases are made once a day along the RELENG_2_2 branch + (2.2.2 -> 2.2.x) as it winds its way towards the next point + release on the 2.2 branch, 2.2.5. With the occasional + exception of accidental breakage, the RELENG_2_2 branch is + being carefully maintained (no experimental changes, fixes made + only after testing in -current). + + <item> + <url url="ftp://current.freebsd.org/pub/FreeBSD/" name="3.0 Snapshot"> + releases are also made once a day for the <ref id="current" + name="-current"> branch, these being of service purely to + bleeding-edge testers and developers. + + </itemize> FreeBSD is also available via CDROM, from the following place(s): @@ -368,9 +334,8 @@ make release BUILDNAME=3.0-MY-SNAP CHROOTDIR=/some/big/filesystem/release (Do not dial the leading zero if calling from outside the UK). - <sect1> - <heading>Where do I find info on the mailing lists?</heading> + <heading>Where do I find info on the FreeBSD mailing lists?<label id="mailing"></heading> <p> You can find full information in the <url url="../handbook/eresources:mail.html" @@ -402,7 +367,7 @@ make release BUILDNAME=3.0-MY-SNAP CHROOTDIR=/some/big/filesystem/release from Walnut Creek and ships with the 2.1.7 CDROM. There is also a larger book entitled ``The Complete FreeBSD'', which comes with additional printed manpages amd includes the 2.1.7 CDROM set. It - should be available in most good bookshops now. + should be available in most good book shops now. There is a FreeBSD Documentation Project which you may contact (or even better, join) on the <tt>doc</tt> mailing list: @@ -472,15 +437,15 @@ make release BUILDNAME=3.0-MY-SNAP CHROOTDIR=/some/big/filesystem/release FreeBSD CDROM often has newer versions). <sect1> - <heading>I have heard about the Problem Report database. - Is there an easy way to access it ?</heading> + <heading>How do I access your Problem Report database?</heading> <p> - The Problem Report database, filled with all the problems, bugs - and changes requested by users with help of the <url - url="http://www.freebsd.org/send-pr.html" name="send-pr"> - command can be reached at + The Problem Report database of all open user change requests + may be queried (or submitted to) by using our web-based PR + <url url="http://www.freebsd.org/send-pr.html" name="submission"> + and <url url="http://www.freebsd.org/cgi-bin/query-pr-summary.cgi" - name="PR Database Summary"> + name="query"> interfaces. The <em>send-pr(1)</em> command + can also be used to submit change requests via electronic mail. <sect1> <heading>Other sources of information.</heading> @@ -494,17 +459,36 @@ make release BUILDNAME=3.0-MY-SNAP CHROOTDIR=/some/big/filesystem/release <item><url url="comp.unix.bsd.misc" name="comp.unix.bsd.misc"> </itemize> - If you have WWW access, please visit <url url="http://www.freebsd.org/" - name="the FreeBSD home page">. - - The FreeBSD handbook has a pretty complete - <url url="../handbook/bibliography.html" name="Bibliography"> + <p> + Web resources: - <label id="pao">There's also a wealth of information about using - FreeBSD on laptops at + <itemize> + <item> + The <url url="http://www.freebsd.org/" name="FreeBSD Home Page">. + <item> + <label id="pao">If you have a laptop, be sure and see <url url="http://www.jp.FreeBSD.org/PAO/" name="Tatsumi Hosokawa's Mobile Computing page"> in Japan. + <item> + <label id="smp">For information on SMP (Symmetric MultiProcessing), + please see the <url url="http://www.freebsd.org/~fsmp/SMP/SMP.html" + name="SMP support page">. + + <item> + <label id="multimedia">For information on FreeBSD multimedia + applications, please see the <url + url="http://www.freebsd.org/~faulkner/multimedia/mm.html" + name="multimedia">page. If you're interested specifically in + the <url url="http://www.freebsd.org/~ahasty/Bt848.html" + name="Bt848"> video capture chip, then follow that link. + </itemize> + + The FreeBSD handbook also has a fairly complete + <url url="../handbook/bibliography.html" name="bibliography"> + section which is worth reading if you're looking for actual + books to buy. + <sect> <heading>Installation</heading> <p> @@ -767,7 +751,7 @@ make release BUILDNAME=3.0-MY-SNAP CHROOTDIR=/some/big/filesystem/release <sect1><heading>What about disk managers? My BIOS doesn't support large drives!</heading> <p> - FreeBSD recognises the Ontrack Disk Manager and makes allowances + FreeBSD recognizes the Ontrack Disk Manager and makes allowances for it. Other disk managers are not supported. If you just want to use the disk with FreeBSD you don't need a @@ -784,7 +768,7 @@ make release BUILDNAME=3.0-MY-SNAP CHROOTDIR=/some/big/filesystem/release reasonably careful, a 20 megabyte boot partition should be plenty. <sect1> - <heading>When I boot FreeBSD I get ``Missing Operating System''.<label id="missing_os"></heading> + <heading>When I boot FreeBSD I get ``Missing Operating System''<label id="missing_os"></heading> <p> This is classically a case of FreeBSD and DOS or some other OS conflicting over their ideas of disk <ref id="geometry" @@ -840,19 +824,27 @@ make release BUILDNAME=3.0-MY-SNAP CHROOTDIR=/some/big/filesystem/release them will make it much easier for you to upgrade to future releases of FreeBSD. + To actually select a subset of the sources, use the Custom + menu item when you are in the Distributions menu of the + system installation tool. The <tt>src/install.sh</tt> script + will also install partial pieces of the source distribution, + depending on the arguments you pass it. + <sect1> - <heading>Do I need to build a kernel</heading> + <heading>Do I need to build a kernel?</heading> - <p> Originally building a new kernel was pretty much a required - step in a FreeBSD installation, but recent releases have an - excellent user configuration tool. When presented with the - FreeBSD boot prompt, enter "-c" and you will be dropped into - a visual configuration screen that allows you to configure the - settings for all the most common drivers. + <p>Building a new kernel was originally pretty much a required + step in a FreeBSD installation, but more recent releases have + benefited from the introduction of a much friendlier kernel + configuration tool. When at the FreeBSD boot prompt (boot:), + use the "-c" flag and you will be dropped into a visual + configuration screen which allows you to configure the kernel's + settings for most common ISA cards. - <p> It's still recommended that you build a new kernel with just - the drivers you need, just to save a bit of RAM, but it's no - longer required for most systems. + <p> It's still recommended that you eventually build a new + kernel containing just the drivers that you need, just to save a + bit of RAM, but it's no longer a strict requirement for most + systems. <sect1> <heading>I live outside the US. Can I use DES encryption?</heading> @@ -901,7 +893,7 @@ make release BUILDNAME=3.0-MY-SNAP CHROOTDIR=/some/big/filesystem/release current versions can generally be obtained by anonymous FTP from <tt>braae.ru.ac.za</tt>. - There is a mailing list for the discussion of non-US encryption + There is also a <ref id="mailing" name="mailing list"> for the discussion of non-US encryption software. For more information, send an email message with a single line saying ``<tt/help/'' in the body of your message to <tt><majordomo@braae.ru.ac.za></tt>. @@ -913,7 +905,7 @@ make release BUILDNAME=3.0-MY-SNAP CHROOTDIR=/some/big/filesystem/release <heading>Hardware compatibility <label id="hardware"></heading> <p> <sect1> - <heading>What kind of hard drives does FreeBSD run on?</heading> + <heading>What kind of hard drives does FreeBSD support?</heading> <p> FreeBSD supports EIDE and SCSI drives (with a compatible @@ -924,7 +916,7 @@ make release BUILDNAME=3.0-MY-SNAP CHROOTDIR=/some/big/filesystem/release and clones. <sect1> - <heading>What SCSI controllers are supported?</heading> + <heading>Which SCSI controllers are supported?</heading> <p> FreeBSD supports the following SCSI controllers: @@ -971,7 +963,7 @@ make release BUILDNAME=3.0-MY-SNAP CHROOTDIR=/some/big/filesystem/release </descrip> <sect1> - <heading>What CD-ROM drives are supported by FreeBSD?</heading> + <heading>Which CD-ROM drives are supported by FreeBSD?</heading> <p> Any SCSI drive connected to a supported controller. @@ -991,7 +983,7 @@ make release BUILDNAME=3.0-MY-SNAP CHROOTDIR=/some/big/filesystem/release directly from the CD. <sect1> - <heading>How about ZIP drives?</heading> + <heading>Does FreeBSD support ZIP drives?</heading> <p> FreeBSD supports the SCSI ZIP drive out of the box, of course. The @@ -1015,7 +1007,7 @@ make release BUILDNAME=3.0-MY-SNAP CHROOTDIR=/some/big/filesystem/release and <ref id="disklabel" name="this note on 'formatting'">. <sect1> - <heading>And how about JAZ, EZ, and other removable drives?</heading> + <heading>Does FreeBSD support JAZ, EZ and other removable drives?</heading> <p> Apart from the IDE version of the EZ drive, these are all SCSI @@ -1031,7 +1023,7 @@ make release BUILDNAME=3.0-MY-SNAP CHROOTDIR=/some/big/filesystem/release See <ref id="disklabel" name="this note on 'formatting'">. <sect1> - <heading>What multi-port serial cards are supported by FreeBSD?</heading> + <heading>Which multi-port serial cards are supported by FreeBSD?</heading> <p>There is a list of these in <htmlurl url="../handbook/handbook11.html" @@ -1058,8 +1050,15 @@ make release BUILDNAME=3.0-MY-SNAP CHROOTDIR=/some/big/filesystem/release <sect1> <heading>I have a PS/2 mouse (``keyboard'' mouse) How do I use it?<label id="ps2mouse"></heading> <p> - You'll have to add the following lines to your kernel - configuration file and recompile: + If you're running a relatively recent version of FreeBSD then you + can simply enable it in the kernel configuration menu + at installation time, otherwise later with -c at the boot: + prompt. It is disabled by default, so you will need to enable + it explicitly. + + <p>If you're running an older version of FreeBSD then you'll + have to add the following lines to your kernel + configuration file and compile a new kernel: <verb> device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr # Options for psm: @@ -1071,12 +1070,6 @@ options PSM_CHECKSYNC #checks the header byte for sync. name="Handbook entry on configuring the kernel"> if you've no experience with building kernels. - If you're running FreeBSD 2.1.6 or later, the psm0 device - line is already there, but it's disabled. Remove the keyword - <tt/disable/ from the device line to enable it, or if you - don't want to compile a kernel just boot with the "-c" flag - and enable it from there. - Once you have a kernel detecting psm0 correctly at boot time, make sure that an entry for psm0 exists in /dev. You can do this by typing: @@ -1106,7 +1099,7 @@ options PSM_CHECKSYNC #checks the header byte for sync. </sect1> <sect1> - <heading>How about tape changers?</heading> + <heading>Does FreeBSD support tape changers?</heading> <p>FreeBSD 2.2 supports SCSI changers using the <tt/ch/ device and the <tt/chio/ command. The details of how you actually control the @@ -1122,7 +1115,7 @@ options PSM_CHECKSYNC #checks the header byte for sync. </sect1> <sect1> - <heading>What sound cards are supported by FreeBSD?</heading> + <heading>Which sound cards are supported by FreeBSD?</heading> <p> FreeBSD supports the SoundBlaster, SoundBlaster Pro, SoundBlaster @@ -1137,13 +1130,13 @@ options PSM_CHECKSYNC #checks the header byte for sync. CDROMS are supported, but you can't boot off this device. <sect1> - <heading>What network cards does FreeBSD support?</heading> + <heading>Which network cards does FreeBSD support?</heading> <p>See <htmlurl url="../handbook/handbook10.html" name="Section 2.1.2 of the handbook"> for a more complete list. Since it doesn't list the drivers you need to use for each of the cards, this incomplete - list wil have to do. + list will have to do. <descrip> <tag/``de'' driver/ @@ -1203,7 +1196,7 @@ options PSM_CHECKSYNC #checks the header byte for sync. require a full power cycle. <sect1> - <heading>I don't have a math co-processor.</heading> + <heading>I don't have a math co-processor - is that bad?</heading> <p> <tt /Note/ This will only affect 386/486SX/486SLC owners - other @@ -1224,8 +1217,8 @@ options PSM_CHECKSYNC #checks the header byte for sync. <heading>What other devices does 2.X support?</heading> <p> - Here is a listing of drivers that do not fit into any of the - above areas. + Here is a listing of drivers which do not fit into any of the + earlier categories. <descrip> <tag><tt/b004.c/</tag> @@ -1258,16 +1251,59 @@ options PSM_CHECKSYNC #checks the header byte for sync. <p> See the <url url="../handbook/hw.html" name="hardware section"> - of the handbook. + of the handbook for general tips if you're going to build it + yourself, otherwise see the + FreeBSD <url url="http://www.freebsd.org/commercial/hardware.html" + name="Hardware vendors"> page for various companies who offer + FreeBSD compatible systems. + --> <sect1> - <heading>I have a laptop with power management.</heading> + <heading>Does FreeBSD support power management on my laptop?</heading> <p> FreeBSD supports APM on certain machines. Please look in the - <tt/LINT/ kernel config file under <tt/APM/. + <tt/LINT/ kernel config file, searching for the <tt/APM/ keyword. + <sect> + <heading>Troubleshooting</heading> + <p> <sect1> - <heading>FreeBSD does not recognise my Bustek 742a EISA SCSI.</heading> + <heading>I have bad blocks on my hard drive!<label id="awre"></heading> + <p> + With SCSI drives, the drive should be capable of re-mapping + these automatically. However, many drives are shipped with + this feature disabled, for some mysterious reason... + + To enable this, you'll need to edit the first device page mode, + which can be done on FreeBSD by giving the command (as root) + +<verb> + scsi -f /dev/rsd0c -m 1 -e -P 3 +</verb> + + and changing the values of AWRE and ARRE from 0 to 1:- +<verb> + AWRE (Auto Write Reallocation Enbld): 1 + ARRE (Auto Read Reallocation Enbld): 1 +</verb> + + For other drive types, you are dependent on support from the + operating system. Unfortunately, the ``bad144'' command that + FreeBSD supplies for this purpose needs a considerable amount + of work done on it. In other words, it doesn't work. If you're + lucky, you can create a file that contains the bad blocks and + stuff it away with a name like ".BADBLOCKS". This is how I got + 386BSD Patchkit 24 completed. <tt/NOTE/: don't do this unless + your time is effectively free. + + IDE drives are <em/supposed/ to come with built-in bad-block + remapping; if you have documentation for your drive, you may want + to see if this feature has been disabled on your drive. However, + ESDI, RLL, and ST-506 drives normally do not do this. + + + <sect1> + <heading>FreeBSD does not recognize my Bustek 742a EISA SCSI!</heading> <p> This info is specific to the 742a but may also cover other Buslogic cards. (Bustek = Buslogic) @@ -1310,7 +1346,7 @@ options PSM_CHECKSYNC #checks the header byte for sync. problem that occurs with the Vesa-Local Buslogic SCSI cards. <sect1> - <heading>FreeBSD does not recognise my on-board AIC-7xxx EISA SCSI in an HP Netserver</heading> + <heading>FreeBSD does not recognize my on-board AIC-7xxx EISA SCSI in an HP Netserver!</heading> <p> This is basically a known problem. The EISA on-board SCSI controller in the HP Netserver machines occupies EISA slot number 11, so all @@ -1363,44 +1399,6 @@ quit build a new kernel with <tt/options "CMD640"/ enabled. This is the default for 2.2.5 and later. - <sect> - <heading>Troubleshooting</heading> - <p> - <sect1> - <heading>I have bad blocks on my hard drive!<label id="awre"></heading> - <p> - With SCSI drives, the drive should be capable of re-mapping - these automatically. However, many drives are shipped with - this feature disabled, for some mysterious reason... - - To enable this, you'll need to edit the first device page mode, - which can be done on FreeBSD by giving the command (as root) - -<verb> - scsi -f /dev/rsd0c -m 1 -e -P 3 -</verb> - - and changing the values of AWRE and ARRE from 0 to 1:- -<verb> - AWRE (Auto Write Reallocation Enbld): 1 - ARRE (Auto Read Reallocation Enbld): 1 -</verb> - - For other drive types, you are dependent on support from the - operating system. Unfortunately, the ``bad144'' command that - FreeBSD supplies for this purpose needs a considerable amount - of work done on it. In other words, it doesn't work. If you're - lucky, you can create a file that contains the bad blocks and - stuff it away with a name like ".BADBLOCKS". This is how I got - 386BSD Patchkit 24 completed. <tt/NOTE/: don't do this unless - your time is effectively free. - - IDE drives are <em/supposed/ to come with built-in bad-block - remapping; if you have documentation for your drive, you may want - to see if this feature has been disabled on your drive. However, - ESDI, RLL, and ST-506 drives normally do not do this. - - <sect1> <heading>I keep seeing messages like ``<tt/ed1: timeout/''.</heading> <p> @@ -1487,7 +1485,7 @@ quit though every memory testing program you try will report your memory as being fine, it's possible for slightly marginal memory to pass all memory tests, yet fail under operating conditions - (such as during busmastering DMA from a SCSI controller like the + (such as during bus mastering DMA from a SCSI controller like the Adaptec 1542, when you're beating on memory by compiling a kernel, or just when the system's running particularly hot). @@ -1732,34 +1730,60 @@ quit <url url="http://www.sleepycat.com/" name = "Sleepycat Software">. </descrip> + <sect> + <heading>User Applications</heading> <sect1> - <heading>Any other applications I might be interested in?</heading> + <heading>So, where are all the user applications?</heading> - <p> - RenderMorphics, Ltd. sells a high-speed 3D rendering package for - FreeBSD called ``Reality Lab'' (tm). + <p> + Please take a look at <url + url="http://www.FreeBSD.ORG/ports/" name="the ports page"> + for info on software packages ported to FreeBSD. The list currently + tops 1000 and is growing daily, so come back to check often + or subscribe to the <tt/freebsd-announce/ <ref id="mailing" + name="mailing list"> for periodic updates on new entries. - Send email to <url url="mailto:info@render.com" - name="info@render.com"> + Most ports should be available for both the 2.2 and 3.0 + branches, and many of them should work on 2.1.x systems as + well. Each time a FreeBSD release is made, a snapshot of the + ports tree at the time of release in also included in the + <tt>ports/</tt> directory. - or call: +44(0)71-251-4411 / FAX: +44(0)71-251-0939 + We also support the concept of a ``package'', essentially no + more than a gzipped binary distribution with a little extra + intelligence embedded in it for doing whatever custom installation + work is required. A package can installed and uninstalled + again easily without having to know the gory details of which + files it includes. - This package is also for FreeBSD 1.1.5 but has been tested and - shown to run under FreeBSD 2.0 with the ``<tt/compat1xdist/'' - installed. + Use the package installation menu in <tt>/stand/sysinstall</tt> + (under the post-configuration menu item) or invoke the + <em>pkg_add(1)</em> command on the specific package files you're + interested in installing. Package files can usually be identified by + their <em>.tgz</em> suffix and CDROM distribution people will have + a <tt>packages/All</tt> directory on their CD which contains such + files. They can also be downloaded over the net for various versions + of FreeBSD at the following locations: - Thanks must be extended to all of these companies for showing - enough faith in FreeBSD to port their products to it. While we - get no direct benefit from the sales of these products, the - indirect benefits of FreeBSD proving itself to be a successful - platform for such commercial interests will be immense! We wish - these companies every measure of success, and can only hope that - others are encouraged to follow suit. + <descrip> + <tag>for 2.1.x-release</tag> + <url url="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/packages-2.1.7/" + name="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/packages-2.1.7/"> + <tag>for 2.2.2-release/2.2-stable</tag> + <url url="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/packages-2.2/" + name="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/packages-2.2/"> + <tag>for 3.0-current</tag> + <url url="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/packages-3.0/" + name="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/packages-3.0/"> + </descrip> - </sect1> + or your nearest local mirror site. - <sect> - <heading>User Applications</heading> + Note that all ports may not be available as packages since + new ones are constantly being added. It is always a good + idea to check back periodically to see which packages are available + at the <url url="ftp://ftp.freebsd.org/pub/FreeBSD/" + name="ftp.freebsd.org"> master site. <sect1> <heading>ghostscript gives lots of errors with my 386/486SX.<label id="emul"></heading> @@ -1778,48 +1802,6 @@ quit option when you do this. <sect1> - <heading>Is there an easy way to get hold of applications?</heading> - - <p> - Yes. Please take a look at <url - url="http://www.FreeBSD.ORG/ports/" name="the ports page"> - for software ported to FreeBSD. The list is growing daily, - so come back to check often. All ports here should work for - systems on either the 2.2 or 3.0 branch, and most of them - work for 2.1.x systems as well. CDROM people will have a - snapshot of this tree at the time of release in the - <tt>ports/</tt> directory on the CD. - - We also support the concept of a ``package'', which is - essentially a gzipped binary distribution with a little extra - intelligence embedded in it for doing any custom installation - work required. Packages can also be installed or uninstalled - again easily without having to know the gory details. CDROM - people will have a <tt>packages/</tt> directory on their CD, - others can get the currently available packages from: - - <descrip> - <tag>for 2.1.x-release</tag> - <url url="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/packages-2.1.7/" - name="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/packages-2.1.7/"> - <tag>for 2.2.2-release/2.2-stable</tag> - <url url="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/packages-2.2/" - name="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/packages-2.2/"> - <tag>for 3.0-current</tag> - <url url="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/packages-3.0/" - name="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/packages-3.0/"> - </descrip> - - or your nearest mirror site. - - Note that all ports may not be available as packages, and that - new packages are constantly being added. It is always a good - idea to check periodically to see which packages are available. - A <tt/README/ file in the packages directory provides more - details on the care and feeding of the package software, so no - explicit details will be given here. - - <sect1> <heading>Where do I find libc.so.3.0?</heading> <p> You are trying to run a package for 2.2/3.0 on a 2.1.x @@ -2102,9 +2084,9 @@ disk fd1 at fdc0 drive 1 name="disklabel"> before you can run <htmlurl url="http://www.freebsd.org/cgi/man.cgi?newfs" name="newfs">/. This means doing the math for partitions - yourself. This is rumoured to be easy :-) See if you can obtain a + yourself. This is rumored to be easy :-) See if you can obtain a skeletal label with ''<tt>disklabel -r <diskname></tt>'' - <em>(eg. </em>''<tt>disklabel -r /dev/rwd0s2</tt>''<em>, assuming + <em>(e.g. </em>''<tt>disklabel -r /dev/rwd0s2</tt>''<em>, assuming that your new disk is wd0, the first IDE drive, and the FreeBSD slice is the second one, s2)</em>. You should see something like:- @@ -2194,7 +2176,7 @@ drivedata: 0 disk at boot time. Editing this label continues as described above. <p> - You're done! Time to initialise the filesystems with something + You're done! Time to initialize the filesystems with something like:- <verb> @@ -2265,7 +2247,7 @@ drivedata: 0 <p> Whether it's a removable drive like a ZIP or an EZ drive (or even a floppy, if you want to use it that way), or a new hard - disk, once it's installed and recognised by the system, and + disk, once it's installed and recognized by the system, and you have your cartridge/floppy/whatever slotted in, things are pretty much the same for all devices. @@ -2443,7 +2425,7 @@ drivedata: 0 <heading>Will a ``dangerously dedicated'' disk endanger my health?</heading> <p><label id="dedicate"> The installation procedure allows you to chose two different - modi how to partition your harddisk(s). The default way makes + methods in partitioning your harddisk(s). The default way makes it compatible with other operating systems on the same machine, by using fdisk table entries (called ``slices'' in FreeBSD), with a FreeBSD slice that employs partitions of its own. @@ -2487,8 +2469,8 @@ drivedata: 0 <p> The advantages of this mode are: FreeBSD owns the entire - disk, no need to waste several ficticuous `tracks' for just - nothing but a 1980-aged simplicistic partitioning model + disk, no need to waste several fictitious `tracks' for just + nothing but a 1980-aged simplistic partitioning model enforcing some artificial and now rather nonsensical constraints on how this partitioning needs to be done. These constraints often lead to what might be the biggest @@ -2531,17 +2513,17 @@ drivedata: 0 <p>The best way is to increase the size of your swap partition, or take advantage of this convenient excuse to add another disk (and see <ref id="swap" name="this note"> if you do). - <p>Adding swap onto a seperate disk makes things faster than + <p>Adding swap onto a separate disk makes things faster than simply adding swap onto the same disk. As an example, if you are compiling source located on one disk, and the swap is on another disk, this is much faster than both swap and compile on the same disk. This is true for SCSI disks specifically. <p> IDE drives are not able to allow access to both drives on the same channel at the same time. I would still suggest putting - your swap on a seperate drive however. The drives are so cheap, + your swap on a separate drive however. The drives are so cheap, it is not worth worrying about. <p>It is a really bad idea to locate your swap file over NFS - unless you are running in a fast networking enviroment, with + unless you are running in a fast networking environment, with a good server. If you can afford fast ethernet, you will not need my advice anyway. @@ -2831,16 +2813,16 @@ vnconfig -ce /dev/vn0c /usr/swap0 swap As you can see, this is part of a real-life file. The first three lines handle special cases where domain-addressed mail should not be sent out to the default route, but instead to - some UUCP neighbour in order to ``shortcut'' the delivery + some UUCP neighbor in order to ``shortcut'' the delivery path. The next line handles mail to the local Ethernet domain that can be delivered using SMTP. Finally, the UUCP - neighbours are mentioned in the .UUCP pseudo-domain notation, - to allow for a ``uucp-neighbour!recipient'' override of the + neighbors are mentioned in the .UUCP pseudo-domain notation, + to allow for a ``uucp-neighbor!recipient'' override of the default rules. The last line is always a single dot, matching - everything else, with UUCP delivery to a UUCP neighbour that + everything else, with UUCP delivery to a UUCP neighbor that serves as your universal mail gateway to the world. All of the node names behind the <tt>uucp-dom:</tt> keyword must - be valid UUCP neighbours, as you can verify using the + be valid UUCP neighbors, as you can verify using the command <tt>uuname</tt>. <p> @@ -2950,7 +2932,7 @@ vnconfig -ce /dev/vn0c /usr/swap0 swap <sect1> - <heading>What is a virtual console?</heading> + <heading>What is a virtual console and how do I make more?</heading> <p> Virtual consoles, put simply, enable you to have several simultaneous sessions on the same machine without doing anything @@ -2973,26 +2955,10 @@ vnconfig -ce /dev/vn0c /usr/swap0 swap enabled, and Alt-F1, Alt-F2, and Alt-F3 will switch between these virtual consoles. - <sect1> - <heading>How do I access the virtual consoles from X?</heading> - <p> - If the console is currently displaying X Window, you can use - Ctrl-Alt-F1, etc. to switch to a virtual console. Note, however, - that once you've switched away from X Window to a virtual - terminal, you use only the Alt- function key to switch to another - virtual terminal or back to X Window. You do not also press the - Ctrl key; the Ctrl-Alt-function key combination is used only when - switching from X Window to a virtual terminal. If you insist on - using the control key to switch back to X you can find your - text console stuck in ``control-lock'' mode. Tap the control - key to wake it up again. - - <sect1> - <heading>How do I increase the number of virtual consoles?</heading> - <p> - Edit <tt>/etc/ttys</tt> and add entries for ``<tt/ttyv4/'' to - ``<tt/ttyvc/'' after the comment on ``Virtual terminals'' (delete - the leading whitespace in the following example): + To enable more of them, edit <tt>/etc/ttys</tt> and add + entries for ``<tt/ttyv4/'' to ``<tt/ttyvc/'' after the + comment on ``Virtual terminals'' (delete the leading + whitespace in the following example): <verb> # Edit the existing entry for ttyv3 in /etc/ttys and change @@ -3013,18 +2979,17 @@ vnconfig -ce /dev/vn0c /usr/swap0 swap if you have 8MB RAM or less. You may also want to change the ``<tt/secure/'' to ``<tt/insecure/''. - <bf/IMPORTANT NOTE/ if you want to run X Window, you <bf/MUST/ - leave a virtual terminal unused (or turned off). For example, if - you want to attach a virtual terminal to all of your twelve - Alt-function keys, you can only attach virtual terminals to - eleven of them. The last must be left unused, because - X Window System - will use it, and you will use the last Alt-function key to switch - back to X Window (after you have switched from X Window to a - virtual console via a Ctrl-Alt-function key). The easiest way to - do this is to disable a console by turning it off. For example, - if you have a keyboard with twelve function keys, you would - change settings for virtual terminal 12 from: + <bf/IMPORTANT NOTE/ if you want to run an X server you <bf/MUST/ + leave at least one virtual terminal unused (or turned off) for it + to use. That is to say that if you want to have a login + prompt pop up for all twelve of your Alt-function keys, + you're out of luck - you can only do this for eleven of them + if you also want to run an X server on the same machine. + + The easiest way to disable a console is by turning it off. For + example, if you had the full 12 terminal allocation mentioned + above and you wanted to run X, you would change settings for + virtual terminal 12 from: <verb> ttyvb "/usr/libexec/getty Pc" cons25 on secure @@ -3064,6 +3029,20 @@ vnconfig -ce /dev/vn0c /usr/swap0 swap command. <sect1> + <heading>How do I access the virtual consoles from X?</heading> + <p> + If the console is currently displaying X Window, you can use + Ctrl-Alt-F1, etc. to switch to a virtual console. Note, however, + that once you've switched away from X Window to a virtual + terminal, you use only the Alt- function key to switch to another + virtual terminal or back to X Window. You do not also press the + Ctrl key; the Ctrl-Alt-function key combination is used only when + switching from X Window to a virtual terminal. If you insist on + using the control key to switch back to X you can find your + text console stuck in ``control-lock'' mode. Tap the control + key to wake it up again. + + <sect1> <heading>How do I start XDM from the <tt>/etc/ttys</tt> file ?</heading> <p> Starting xdm via /etc/ttys is a Bad Thing. I don't know why this @@ -3520,7 +3499,7 @@ MYADDR: <p> You can now disable dialing under these circumstances. Usually, - this sort of problem arrises due to DNS lookups. To prevent + this sort of problem arises due to DNS lookups. To prevent DNS lookups from establishing a connection (this will <bf/not/ prevent <tt/ppp/ from passing the packets through an established connection), use the following: @@ -3734,7 +3713,7 @@ Zynx ZX342 as <tt>mumble.foo.bar.edu</tt>, or it will be searched for in the root domain. <p> - This is different from the previous behaviour, where the + This is different from the previous behavior, where the search continued across <tt>mumble.bar.edu</tt>, and <tt>mumble.edu</tt>. Have a look at RFC 1535 for why this was considered bad practice, or even a security hole. @@ -4456,48 +4435,57 @@ domain foo.bar.edu The <bf/2.1-stable/ branch, <bf/RELENG_2_1_0/,departed -current in September of 1994. - <itemize> - <item><bf/Fine, so what are SNAPshots?/ + <sect1> + <heading>How do I make my own custom release?<label id="custrel"></heading> + <p> + To make a release you need to do three things: First, you need to + be running a kernel with the <tt/vn/ driver configured in. Add + this to your kernel config file and build a new kernel: - <p>"SNAPs" are made from -current, that is to say 3.0, and they happen - infrequently, basically whenever I feel like doing one (e.g. I or - someone else wants something tested), and this generally doesn't - happen more than 3-4 times a year.</item> + <verb> +pseudo-device vn #Vnode driver (turns a file into a device) + </verb> - <item><bf/And what constitutes a full "RELEASE" then?/ + Second, you have to have the whole CVS repository at hand. + To get this you can use + <url url="../handbook/cvsup.html" name="CVSUP"> + but your tag value, if any, should be `.' and your release name + should be cvs: - <p>A full release generally occurs along a branch, divorced from - the <bf/-current/ mainline and its associated instabilities as people - work on new mechanisms or generally do renovation on FreeBSD. A - release, unless it's perhaps the very first one on a new branch, - is meant to be of slightly better and more tested stuff, and the - release date is chosen to coincide with a point in time when the - sources are the most stable, following ALPHA and BETA test periods - along the branch (during which time the addition of new functionality - is discouraged and the testing of existing functionality strongly - encouraged). </item> + <verb> +*default prefix=/home/ncvs base=/a host=cvsup.FreeBSD.org release=cvs delete compress use-rel=suffix - <item><bf/Makes sense so far - so, what's a "RELENG?" release?/ +## Main Source Tree +src-all +src-eBones +src-secure - <p>The RELENG releases are a new thing, sort of a "release of the day" - mechanism which is automated and set to run along a given branch, - in the current case that being <bf/RELENG_2_2/. +# Other stuff +ports-all +www + </verb> - The URL <url url="ftp://releng22.freebsd.org/pub/FreeBSD" - name="ftp://releng22.freebsd.org/pub/FreeBSD"> points to a machine - which builds a full 2.2 branch release <em/every day/ from wherever - the RELENG_2_2 tag happens to be pointing at 3am. If the new - build succeeds, the release is moved into the anonymous FTP area - for transfer by others. If it fails, jkh gets a mail telling him - "Hey, somebody broke the 2.2 branch! Bad hacker, no caffeine!" - and he goes off to investigate. The 2.2 branch is not supposed to - break since people are only supposed to be committing bug fixes and - well-tested enhancements to that branch, nothing experimental - or untried (sometimes they do anyway, but hey - this is a - volunteer-driven project and we try to take that in stride :-). - </item> - </itemize> - </sect1> + Then run <tt/cvsup -g supfile/ to suck all the good bits into your + box... + + Finally, you need a chunk of empty space to build into. Let's + say it's in <tt>/some/big/filesystem</tt>, and from the example + above you've got the CVS repository in <tt>/home/ncvs</tt>: + + <verb> +setenv CVSROOT /home/ncvs # or export CVSROOT=/home/ncvs +cd /usr/src/release +make release BUILDNAME=3.0-MY-SNAP CHROOTDIR=/some/big/filesystem/release + </verb> + + An entire release will be built in + <tt>/some/big/filesystem/release</tt> + and you will have a full FTP-type installation in + <tt>/some/big/filesystem/release/R/ftp</tt> + when you're done. If you want to build your SNAP along some other + branch than -current, you can also add <tt/RELEASETAG=SOMETAG/ to + the make release command line above, e.g. <tt/RELEASETAG=RELENG_2_2/ + would build an up-to-the- minute 2.2 GAMMA snapshot. <sect1> <heading>How do I create customized installation disks?</heading> @@ -4630,7 +4618,7 @@ domain foo.bar.edu This info is then combined with info from any ECU files on the hard disk or wired into the MLB BIOS. The ECU and BIOS PnP support for hardware on the MLB is usually synthetic, and the - peripherals don't really do geniune PnP. However by examining + peripherals don't really do genuine PnP. However by examining the BIOS info plus the ECU info, the probe routines can cause the devices that are PnP to avoid those devices the probe code cannot relocate. @@ -4658,10 +4646,11 @@ domain foo.bar.edu <p> Several different groups have expressed interest in working on - multi-architecture support for FreeBSD. If you are interested in - doing so, please contact the developers at - <tt><platforms@FreeBSD.ORG></tt> for more information on our - strategy for porting. + multi-architecture support for FreeBSD and some people are + currently working on a port of FreeBSD to the ALPHA, with the + cooperation of DEC. For general discussion on new architectures, + use the <tt><platforms@FreeBSD.ORG></tt> + <ref id="mailing" name="mailing list">. <sect1> <heading>I need a major number for a device driver I've written.</heading> @@ -4692,10 +4681,8 @@ domain foo.bar.edu </verb> <descrip> - <tag/Gary Clark II/ - FreeBSD Doc Team <tag/Jordan Hubbard/ - Janitorial services (I don't do windows) + Occasional fits of FAQ-reshuffling and updating. <tag/Doug White/ Services above and beyond the call of duty on freebsd-questions <tag/Joerg Wunsch/ |