From b90ea8b776ff7793229407c861ab8df06ddc5093 Mon Sep 17 00:00:00 2001 From: Nik Clayton Date: Sun, 14 Nov 1999 18:07:39 +0000 Subject: [PATCH] * Add reference to 3.X in and <abstract> * -stable -> -STABLE * -current -> -CURRENT * Update 3.0/3.2 entries to 3.3 or 3.X as appropriate * .x -> .X (i.e., 3.x -> 3.X) * Update entries to correspond to new directory structure on ftp site * Removed reference to RELENG_2_ snapshots, which no longer exist * Add reference to allscreens_flags="-m on" for moused * Note that 3.3-RELEASE has 8 virtual terminals by default Submitter sent the original PR, Jim Mock added to it, I cleaned up a couple of bits and pieces. PR: docs/13949 Submitted by: Chris D. Faulhaber <jedgar@fxp.org>, jim --- en_US.ISO8859-1/books/faq/book.sgml | 147 ++++++++++++++------------- en_US.ISO_8859-1/books/faq/book.sgml | 147 ++++++++++++++------------- 2 files changed, 156 insertions(+), 138 deletions(-) diff --git a/en_US.ISO8859-1/books/faq/book.sgml b/en_US.ISO8859-1/books/faq/book.sgml index b26379a6b0..2920262983 100644 --- a/en_US.ISO8859-1/books/faq/book.sgml +++ b/en_US.ISO8859-1/books/faq/book.sgml @@ -2,7 +2,7 @@ <book> <bookinfo> -<title>Frequently Asked Questions for FreeBSD 2.X +Frequently Asked Questions for FreeBSD 2.X and 3.X @@ -10,9 +10,9 @@ -$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.22 1999/11/12 04:36:42 chris Exp $ +$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.23 1999/11/13 00:25:00 jim Exp $ - This is the FAQ for FreeBSD systems version 2.X All entries are + This is the FAQ for FreeBSD versions 2.X and 3.X. All entries are assumed to be relevant to FreeBSD 2.0.5 and later, unless otherwise noted. Any entries with a <XXX> are under construction. If you are interested in helping with this project, send @@ -25,7 +25,7 @@ Preface -Welcome to the FreeBSD 2.X FAQ! +Welcome to the FreeBSD 2.X-3.X FAQ! As is usual with Usenet FAQs, this document aims to cover the most frequently asked questions concerning the FreeBSD operating system @@ -122,45 +122,45 @@ really can do whatever you like with it. What is the latest version of FreeBSD? -Version 3.2 is the latest stable version; it was released -in May, 1999. This is also the latest release version. +Version 3.3 is the latest stable version; it was released +in September, 1999. This is also the latest release version. -Briefly explained, -stable is aimed at the ISP or other +Briefly explained, -STABLE is aimed at the ISP or other corporate user who wants stability and a low change count over -the wizzy new features of the latest -current snapshot. +the wizzy new features of the latest -CURRENT snapshot. Releases can come from either "branch," but you should only use --current if you're sure that you're prepared for its -increased volatility (relative to -stable, that is). +-CURRENT if you're sure that you're prepared for its +increased volatility (relative to -STABLE, that is). Releases are only made every few months. While many people stay more up-to-date with the -FreeBSD sources (see the questions on FreeBSD-current and FreeBSD-stable) than that, doing so is more of a +FreeBSD sources (see the questions on FreeBSD-CURRENT and FreeBSD-STABLE) than that, doing so is more of a commitment, as the sources are a moving target. -What is FreeBSD-current? +What is FreeBSD-CURRENT? -FreeBSD-current is the +FreeBSD-CURRENT is the development version of the operating system, which will in due course become 4.0-RELEASE. As such, it is really only of interest to developers working on the system and die-hard hobbyists. See the relevant section in the handbook for -details on running -current. +details on running -CURRENT. If you are not familiar with the operating system or are not capable of identifying the difference between a real problem and -a temporary problem, you should not use FreeBSD-current. This +a temporary problem, you should not use FreeBSD-CURRENT. This branch sometimes evolves quite quickly and can be un-buildable -for a number of days at a time. People that use FreeBSD-current +for a number of days at a time. People that use FreeBSD-CURRENT are expected to be able to analyze any problems and only report them if they are deemed to be mistakes rather than ``glitches''. Questions such as ``make world produces some error about groups'' on the --current mailing list are sometimes treated with contempt. +-CURRENT mailing list are sometimes treated with contempt. -Every now and again, a snapshot release is also made of this -current development +Every now and again, a 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: @@ -173,7 +173,7 @@ made available. The goals behind each snapshot release are: -To give people who would like to run -current but who don't +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 of bootstrapping it onto their systems. @@ -199,22 +199,22 @@ greatest possible number of potential testers. and tested mettle, you will have to stick to full releases. Snapshot releases are directly available from ftp://current.FreeBSD.org/pub/FreeBSD/ and are generated, -on the average, once a day for both the 4.0-current and 3.0-stable +on the average, once a day for both the 4.0-CURRENT and 3.0-STABLE branches. -What is the FreeBSD-stable concept? +What is the FreeBSD-STABLE concept? Back when FreeBSD 2.0.5 was released, we decided to branch FreeBSD -development into two parts. One branch was named -stable, with the +development into two parts. One branch was named -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 --current, which +-CURRENT, which essentially has been one unbroken line leading towards 4.0-RELEASE (and beyond) since 2.0 was released. If a little ASCII art would help, this is how it looks: @@ -223,12 +223,12 @@ help, this is how it looks: 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] + | [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] + | [2.2-STABLE] *BRANCH* 2.2.1 -> 2.2.2-RELEASE -> 2.2.5 -> 2.2.6 -> 2.2.7 -> 2.2.8 [end] | (Mar 1997) (Oct 97) (Apr 98) (Jul 98) (Dec 98) | @@ -238,19 +238,19 @@ help, this is how it looks: | 3.0.0-RELEASE (Oct 1998) | - | [3.0-stable] + | [3.0-STABLE] *BRANCH* 3.1 (Feb 1999) -> 3.2 -> ... future 3.x releases ... | (May 1999) | \|/ + - [4.0-current continues] + [4.0-CURRENT continues] -The -current branch is slowly progressing towards 4.0 and beyond, -the previous 2.2-stable branch having just retired with the release -of 2.2.8. 3.0-stable has now replaced it, the next release coming -up with 3.3 in Q3 1999. 4.0-current is now the "current branch", +The -CURRENT branch is slowly progressing towards 4.0 and beyond, +the previous 2.2-STABLE branch having been retired with the release +of 2.2.8. 3.3-STABLE has now replaced it, with 3.3-RELEASE being released +in mid-September 1999. 4.0-CURRENT is now the "current branch", with the first 4.0 releases appearing in Q1 2000. @@ -315,14 +315,14 @@ from the FreeBSD FTP site -For the current 2.2-stable release, 2.2.8R, see the -2.2.8-RELEASE directory. +For the current 2.2-STABLE release, 2.2.8R, see the +2.2.8-RELEASE directory. -For the current 3.0-stable release, 3.0-RELEASE, see the -3.0-RELEASE directory. +For the current 3.X-STABLE release, 3.3-RELEASE, see the +3.3-RELEASE directory. @@ -337,15 +337,15 @@ are now made. -3.0 Snapshot releases are also made once a day along the -RELENG_3 branch (post 3.0-release) as it continues on its way -towards 3.2-RELEASE. +3.X Snapshot releases are also made once a day along the +RELENG_3 branch (post 3.0-RELEASE) as it continues on its way +towards 3.4-RELEASE. 4.0 Snapshot releases are made once a day for the --current branch, these being of service +-CURRENT branch, these being of service purely to bleeding-edge testers and developers. @@ -704,7 +704,7 @@ prefix=/usr/local/www/data/www.FreeBSD.org delete old use-rel-suffix Using ftp mirror: You can download the FTP server's copy of the web site using your favorite ftp mirror tool. Simply start at -ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-current/www. +ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-CURRENT/www. @@ -1557,7 +1557,7 @@ filesystems with 4 terabytes are possible (and exist). maxfilesize ---------------------------------- 2.2.7 3.0 -fs block size -stable -current works should-work +fs block size -STABLE -CURRENT works should-work ------------- ------- -------- ----- ----------- 4K 4T-1 4T-1 4T-1 4+T 8K 32+G 8T-1 32+G 16T-1 @@ -1577,10 +1577,10 @@ unreachable when the fs block size is 4K. For block sizes of 8K and larger, everything should be limited by the 2G-1 limit on fs block numbers, but is actually limited by the -1G-1 limit on fs block numbers, except under -stable triple indirect +1G-1 limit on fs block numbers, except under -STABLE triple indirect blocks are unreachable, so the limit is the maxiumum fs block number that can be represented using double indirect blocks -(approx. (blocksize/4)^2 + (blocksize/4)), and under -current +(approx. (blocksize/4)^2 + (blocksize/4)), and under -CURRENT exceeding this limit may cause problems. Using the correct limit of 2G-1 blocks does cause problems. @@ -1859,6 +1859,15 @@ system starts. In version 2.2.1, set the following variables in +In addition, if you would like to be able to use the mouse +daemon on all virtual terminals instead of just console at boot-time, +add the following to /etc/rc.conf. + + + allscreens_flags="-m on" + + + Staring from FreeBSD 2.2.6, the mouse daemon is capable of determining the correct protocol type automatically unless the mouse is a relatively old serial mouse model. Specify ``auto'' as @@ -3014,7 +3023,7 @@ of FreeBSD at the following locations: -for 2.2.8-release/2.2.8-stable +for 2.2.8-RELEASE/2.2.8-STABLE ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-2.2.8/ @@ -3023,7 +3032,7 @@ of FreeBSD at the following locations: -for 3.2-release/3.2-stable +for 3.X-RELEASE/3.X-STABLE ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-3-stable/ @@ -3033,7 +3042,7 @@ of FreeBSD at the following locations: -for 4.0-current +for 4.0-CURRENT ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-4-current/ @@ -3110,7 +3119,7 @@ crw-rw-rw- 1 root wheel 41, 1 Oct 15 22:14 spx You just need socksys to go to /dev/null -to fake the open & close. The code in -current will handle the +to fake the open & close. The code in -CURRENT will handle the rest. This is much cleaner than the way it was done before. If you want the spx driver for a local socket X connection, define SPX_HACK when you compile the system. @@ -3142,15 +3151,15 @@ in the ports tree. -Why can't I build this port on my 3.x-stable machine? +Why can't I build this port on my 3.X-STABLE machine? If you're running a FreeBSD version that lags significantly behind --current or -stable, you may need a ports upgrade kit from +-CURRENT or -STABLE, you may need a ports upgrade kit from http://www.FreeBSD.org/ports/. If you are up to date, then someone might have committed a change to the port which works for --current but which broke the port for -stable. Please submit a bug +-CURRENT but which broke the port for -STABLE. Please submit a bug report on this with the send-pr(1) command, since the ports -collection is supposed to work for both the -current and -stable +collection is supposed to work for both the -CURRENT and -STABLE branches. @@ -3260,11 +3269,11 @@ write to through a special program to manage it called ``ft'' - see the man page on ft for further details. -Versions previous to also had some trouble dealing +Versions previous to also had some trouble dealing with bad tape media; if you have trouble where ft seems to go back and forth over the same spot, try grabbing the latest version of ft from /usr/src/sbin/ft in - and try that. + and try that. @@ -4711,8 +4720,8 @@ waiting for you on the second ``virtual console''! When you want to go back to the original session, do Alt-F1. The default FreeBSD installation has three virtual consoles -enabled, and Alt-F1, Alt-F2, and Alt-F3 will switch between -these virtual consoles. +enabled (8 starting with 3.3-RELEASE), and Alt-F1, Alt-F2, and +Alt-F3 will switch between these virtual consoles. To enable more of them, edit /etc/ttys and add entries for ``ttyv4'' to ``ttyvc'' after the @@ -7510,7 +7519,7 @@ back when. One thousand, one hundred and seventy-two: -Twenty-three to complain to -current about the lights being +Twenty-three to complain to -CURRENT about the lights being out; Four to claim that it is a configuration problem, and that @@ -7533,7 +7542,7 @@ have cvsupped at a bad time; One to post a patch for a new lightbulb to -hackers; One to complain that he had patches for this three years ago, -but when he sent them to -current they were just ignored, and he +but when he sent them to -CURRENT they were just ignored, and he has had bad experiences with the PR system; besides, the proposed new lightbulb is non-reflexive; @@ -7622,15 +7631,15 @@ id="hackers"> -RELENG_2_2 AKA 2.2-stable AKA "2.2 branch" +RELENG_2_2 AKA 2.2-STABLE AKA "2.2 branch" -RELENG_3 AKA 3.x-stable AKA "3.0 branch" +RELENG_3 AKA 3.X-STABLE AKA "3.0 branch" -HEAD AKA AKA 4.0-current +HEAD AKA AKA 4.0-CURRENT @@ -7639,16 +7648,16 @@ id="hackers"> HEAD is not an actual branch tag, like the other two, it's simply a symbolic constant for "the current, non-branched development stream" which we simply -refer to as . +refer to as . -Right now, is the 4.0 development stream and the -3.0-stable branch, RELENG_3, forked off from - in Jan 1999. +Right now, is the 4.0 development stream and the +3.0-STABLE branch, RELENG_3, forked off from + in Jan 1999. -The 2.2-stable branch, RELENG_2_2, departed -current in +The 2.2-STABLE branch, RELENG_2_2, departed -CURRENT in November 1996. -The 2.1-stable branch, RELENG_2_1_0, departed -current in +The 2.1-STABLE branch, RELENG_2_1_0, departed -CURRENT in September of 1994. This branch has been fully retired. @@ -7709,7 +7718,7 @@ above you've got the CVS repository in /home/ncvs: /some/big/filesystem/release and you will have a full FTP-type installation in /some/big/filesystem/release/R/ftp when you're done. If you want to build your SNAP along some other branch than --current, you can also add RELEASETAG=SOMETAG to +-CURRENT, you can also add RELEASETAG=SOMETAG to the make release command line above, e.g. RELEASETAG=RELENG_2_2 would build an up-to-the- minute 2.2-STABLE snapshot. @@ -8032,7 +8041,7 @@ instruction pointer with a function in the kernel symbol table. The best way to track down the cause of a panic is by capturing a crash dump, then using gdb(1) to to a stack trace on the crash dump. Of course, this depends on gdb(1) -in -current working correctly, which I can't guarantee (I recall +in -CURRENT working correctly, which I can't guarantee (I recall somebody saying that the new ELF-ized gdb(1) didn't handle kernel crash dumps correctly: somebody should check this before 3.0 goes out of beta or there'll be a lot of red faces after the diff --git a/en_US.ISO_8859-1/books/faq/book.sgml b/en_US.ISO_8859-1/books/faq/book.sgml index b26379a6b0..2920262983 100644 --- a/en_US.ISO_8859-1/books/faq/book.sgml +++ b/en_US.ISO_8859-1/books/faq/book.sgml @@ -2,7 +2,7 @@ -Frequently Asked Questions for FreeBSD 2.X +Frequently Asked Questions for FreeBSD 2.X and 3.X @@ -10,9 +10,9 @@ -$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.22 1999/11/12 04:36:42 chris Exp $ +$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.23 1999/11/13 00:25:00 jim Exp $ - This is the FAQ for FreeBSD systems version 2.X All entries are + This is the FAQ for FreeBSD versions 2.X and 3.X. All entries are assumed to be relevant to FreeBSD 2.0.5 and later, unless otherwise noted. Any entries with a <XXX> are under construction. If you are interested in helping with this project, send @@ -25,7 +25,7 @@ Preface -Welcome to the FreeBSD 2.X FAQ! +Welcome to the FreeBSD 2.X-3.X FAQ! As is usual with Usenet FAQs, this document aims to cover the most frequently asked questions concerning the FreeBSD operating system @@ -122,45 +122,45 @@ really can do whatever you like with it. What is the latest version of FreeBSD? -Version 3.2 is the latest stable version; it was released -in May, 1999. This is also the latest release version. +Version 3.3 is the latest stable version; it was released +in September, 1999. This is also the latest release version. -Briefly explained, -stable is aimed at the ISP or other +Briefly explained, -STABLE is aimed at the ISP or other corporate user who wants stability and a low change count over -the wizzy new features of the latest -current snapshot. +the wizzy new features of the latest -CURRENT snapshot. Releases can come from either "branch," but you should only use --current if you're sure that you're prepared for its -increased volatility (relative to -stable, that is). +-CURRENT if you're sure that you're prepared for its +increased volatility (relative to -STABLE, that is). Releases are only made every few months. While many people stay more up-to-date with the -FreeBSD sources (see the questions on FreeBSD-current and FreeBSD-stable) than that, doing so is more of a +FreeBSD sources (see the questions on FreeBSD-CURRENT and FreeBSD-STABLE) than that, doing so is more of a commitment, as the sources are a moving target. -What is FreeBSD-current? +What is FreeBSD-CURRENT? -FreeBSD-current is the +FreeBSD-CURRENT is the development version of the operating system, which will in due course become 4.0-RELEASE. As such, it is really only of interest to developers working on the system and die-hard hobbyists. See the relevant section in the handbook for -details on running -current. +details on running -CURRENT. If you are not familiar with the operating system or are not capable of identifying the difference between a real problem and -a temporary problem, you should not use FreeBSD-current. This +a temporary problem, you should not use FreeBSD-CURRENT. This branch sometimes evolves quite quickly and can be un-buildable -for a number of days at a time. People that use FreeBSD-current +for a number of days at a time. People that use FreeBSD-CURRENT are expected to be able to analyze any problems and only report them if they are deemed to be mistakes rather than ``glitches''. Questions such as ``make world produces some error about groups'' on the --current mailing list are sometimes treated with contempt. +-CURRENT mailing list are sometimes treated with contempt. -Every now and again, a snapshot release is also made of this -current development +Every now and again, a 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: @@ -173,7 +173,7 @@ made available. The goals behind each snapshot release are: -To give people who would like to run -current but who don't +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 of bootstrapping it onto their systems. @@ -199,22 +199,22 @@ greatest possible number of potential testers. and tested mettle, you will have to stick to full releases. Snapshot releases are directly available from ftp://current.FreeBSD.org/pub/FreeBSD/ and are generated, -on the average, once a day for both the 4.0-current and 3.0-stable +on the average, once a day for both the 4.0-CURRENT and 3.0-STABLE branches. -What is the FreeBSD-stable concept? +What is the FreeBSD-STABLE concept? Back when FreeBSD 2.0.5 was released, we decided to branch FreeBSD -development into two parts. One branch was named -stable, with the +development into two parts. One branch was named -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 --current, which +-CURRENT, which essentially has been one unbroken line leading towards 4.0-RELEASE (and beyond) since 2.0 was released. If a little ASCII art would help, this is how it looks: @@ -223,12 +223,12 @@ help, this is how it looks: 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] + | [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] + | [2.2-STABLE] *BRANCH* 2.2.1 -> 2.2.2-RELEASE -> 2.2.5 -> 2.2.6 -> 2.2.7 -> 2.2.8 [end] | (Mar 1997) (Oct 97) (Apr 98) (Jul 98) (Dec 98) | @@ -238,19 +238,19 @@ help, this is how it looks: | 3.0.0-RELEASE (Oct 1998) | - | [3.0-stable] + | [3.0-STABLE] *BRANCH* 3.1 (Feb 1999) -> 3.2 -> ... future 3.x releases ... | (May 1999) | \|/ + - [4.0-current continues] + [4.0-CURRENT continues] -The -current branch is slowly progressing towards 4.0 and beyond, -the previous 2.2-stable branch having just retired with the release -of 2.2.8. 3.0-stable has now replaced it, the next release coming -up with 3.3 in Q3 1999. 4.0-current is now the "current branch", +The -CURRENT branch is slowly progressing towards 4.0 and beyond, +the previous 2.2-STABLE branch having been retired with the release +of 2.2.8. 3.3-STABLE has now replaced it, with 3.3-RELEASE being released +in mid-September 1999. 4.0-CURRENT is now the "current branch", with the first 4.0 releases appearing in Q1 2000. @@ -315,14 +315,14 @@ from the FreeBSD FTP site -For the current 2.2-stable release, 2.2.8R, see the -2.2.8-RELEASE directory. +For the current 2.2-STABLE release, 2.2.8R, see the +2.2.8-RELEASE directory. -For the current 3.0-stable release, 3.0-RELEASE, see the -3.0-RELEASE directory. +For the current 3.X-STABLE release, 3.3-RELEASE, see the +3.3-RELEASE directory. @@ -337,15 +337,15 @@ are now made. -3.0 Snapshot releases are also made once a day along the -RELENG_3 branch (post 3.0-release) as it continues on its way -towards 3.2-RELEASE. +3.X Snapshot releases are also made once a day along the +RELENG_3 branch (post 3.0-RELEASE) as it continues on its way +towards 3.4-RELEASE. 4.0 Snapshot releases are made once a day for the --current branch, these being of service +-CURRENT branch, these being of service purely to bleeding-edge testers and developers. @@ -704,7 +704,7 @@ prefix=/usr/local/www/data/www.FreeBSD.org delete old use-rel-suffix Using ftp mirror: You can download the FTP server's copy of the web site using your favorite ftp mirror tool. Simply start at -ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-current/www. +ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-CURRENT/www. @@ -1557,7 +1557,7 @@ filesystems with 4 terabytes are possible (and exist). maxfilesize ---------------------------------- 2.2.7 3.0 -fs block size -stable -current works should-work +fs block size -STABLE -CURRENT works should-work ------------- ------- -------- ----- ----------- 4K 4T-1 4T-1 4T-1 4+T 8K 32+G 8T-1 32+G 16T-1 @@ -1577,10 +1577,10 @@ unreachable when the fs block size is 4K. For block sizes of 8K and larger, everything should be limited by the 2G-1 limit on fs block numbers, but is actually limited by the -1G-1 limit on fs block numbers, except under -stable triple indirect +1G-1 limit on fs block numbers, except under -STABLE triple indirect blocks are unreachable, so the limit is the maxiumum fs block number that can be represented using double indirect blocks -(approx. (blocksize/4)^2 + (blocksize/4)), and under -current +(approx. (blocksize/4)^2 + (blocksize/4)), and under -CURRENT exceeding this limit may cause problems. Using the correct limit of 2G-1 blocks does cause problems. @@ -1859,6 +1859,15 @@ system starts. In version 2.2.1, set the following variables in +In addition, if you would like to be able to use the mouse +daemon on all virtual terminals instead of just console at boot-time, +add the following to /etc/rc.conf. + + + allscreens_flags="-m on" + + + Staring from FreeBSD 2.2.6, the mouse daemon is capable of determining the correct protocol type automatically unless the mouse is a relatively old serial mouse model. Specify ``auto'' as @@ -3014,7 +3023,7 @@ of FreeBSD at the following locations: -for 2.2.8-release/2.2.8-stable +for 2.2.8-RELEASE/2.2.8-STABLE ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-2.2.8/ @@ -3023,7 +3032,7 @@ of FreeBSD at the following locations: -for 3.2-release/3.2-stable +for 3.X-RELEASE/3.X-STABLE ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-3-stable/ @@ -3033,7 +3042,7 @@ of FreeBSD at the following locations: -for 4.0-current +for 4.0-CURRENT ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-4-current/ @@ -3110,7 +3119,7 @@ crw-rw-rw- 1 root wheel 41, 1 Oct 15 22:14 spx You just need socksys to go to /dev/null -to fake the open & close. The code in -current will handle the +to fake the open & close. The code in -CURRENT will handle the rest. This is much cleaner than the way it was done before. If you want the spx driver for a local socket X connection, define SPX_HACK when you compile the system. @@ -3142,15 +3151,15 @@ in the ports tree. -Why can't I build this port on my 3.x-stable machine? +Why can't I build this port on my 3.X-STABLE machine? If you're running a FreeBSD version that lags significantly behind --current or -stable, you may need a ports upgrade kit from +-CURRENT or -STABLE, you may need a ports upgrade kit from http://www.FreeBSD.org/ports/. If you are up to date, then someone might have committed a change to the port which works for --current but which broke the port for -stable. Please submit a bug +-CURRENT but which broke the port for -STABLE. Please submit a bug report on this with the send-pr(1) command, since the ports -collection is supposed to work for both the -current and -stable +collection is supposed to work for both the -CURRENT and -STABLE branches. @@ -3260,11 +3269,11 @@ write to through a special program to manage it called ``ft'' - see the man page on ft for further details. -Versions previous to also had some trouble dealing +Versions previous to also had some trouble dealing with bad tape media; if you have trouble where ft seems to go back and forth over the same spot, try grabbing the latest version of ft from /usr/src/sbin/ft in - and try that. + and try that. @@ -4711,8 +4720,8 @@ waiting for you on the second ``virtual console''! When you want to go back to the original session, do Alt-F1. The default FreeBSD installation has three virtual consoles -enabled, and Alt-F1, Alt-F2, and Alt-F3 will switch between -these virtual consoles. +enabled (8 starting with 3.3-RELEASE), and Alt-F1, Alt-F2, and +Alt-F3 will switch between these virtual consoles. To enable more of them, edit /etc/ttys and add entries for ``ttyv4'' to ``ttyvc'' after the @@ -7510,7 +7519,7 @@ back when. One thousand, one hundred and seventy-two: -Twenty-three to complain to -current about the lights being +Twenty-three to complain to -CURRENT about the lights being out; Four to claim that it is a configuration problem, and that @@ -7533,7 +7542,7 @@ have cvsupped at a bad time; One to post a patch for a new lightbulb to -hackers; One to complain that he had patches for this three years ago, -but when he sent them to -current they were just ignored, and he +but when he sent them to -CURRENT they were just ignored, and he has had bad experiences with the PR system; besides, the proposed new lightbulb is non-reflexive; @@ -7622,15 +7631,15 @@ id="hackers"> -RELENG_2_2 AKA 2.2-stable AKA "2.2 branch" +RELENG_2_2 AKA 2.2-STABLE AKA "2.2 branch" -RELENG_3 AKA 3.x-stable AKA "3.0 branch" +RELENG_3 AKA 3.X-STABLE AKA "3.0 branch" -HEAD AKA AKA 4.0-current +HEAD AKA AKA 4.0-CURRENT @@ -7639,16 +7648,16 @@ id="hackers"> HEAD is not an actual branch tag, like the other two, it's simply a symbolic constant for "the current, non-branched development stream" which we simply -refer to as . +refer to as . -Right now, is the 4.0 development stream and the -3.0-stable branch, RELENG_3, forked off from - in Jan 1999. +Right now, is the 4.0 development stream and the +3.0-STABLE branch, RELENG_3, forked off from + in Jan 1999. -The 2.2-stable branch, RELENG_2_2, departed -current in +The 2.2-STABLE branch, RELENG_2_2, departed -CURRENT in November 1996. -The 2.1-stable branch, RELENG_2_1_0, departed -current in +The 2.1-STABLE branch, RELENG_2_1_0, departed -CURRENT in September of 1994. This branch has been fully retired. @@ -7709,7 +7718,7 @@ above you've got the CVS repository in /home/ncvs: /some/big/filesystem/release and you will have a full FTP-type installation in /some/big/filesystem/release/R/ftp when you're done. If you want to build your SNAP along some other branch than --current, you can also add RELEASETAG=SOMETAG to +-CURRENT, you can also add RELEASETAG=SOMETAG to the make release command line above, e.g. RELEASETAG=RELENG_2_2 would build an up-to-the- minute 2.2-STABLE snapshot. @@ -8032,7 +8041,7 @@ instruction pointer with a function in the kernel symbol table. The best way to track down the cause of a panic is by capturing a crash dump, then using gdb(1) to to a stack trace on the crash dump. Of course, this depends on gdb(1) -in -current working correctly, which I can't guarantee (I recall +in -CURRENT working correctly, which I can't guarantee (I recall somebody saying that the new ELF-ized gdb(1) didn't handle kernel crash dumps correctly: somebody should check this before 3.0 goes out of beta or there'll be a lot of red faces after the