From b1c0d8556483f7f1176cc1c4bf89fea4a928957b Mon Sep 17 00:00:00 2001 From: Michael Lucas Date: Thu, 12 May 2005 01:46:37 +0000 Subject: [PATCH] More 3.X removals. This concludes the easy and obvious 3.X removals. What's left requires something resembling conscious thought, and perhaps even actual decision-making. --- en_US.ISO8859-1/books/faq/book.sgml | 35 ++++++++++++++--------------- 1 file changed, 17 insertions(+), 18 deletions(-) diff --git a/en_US.ISO8859-1/books/faq/book.sgml b/en_US.ISO8859-1/books/faq/book.sgml index f5396ca148..9dad66093a 100644 --- a/en_US.ISO8859-1/books/faq/book.sgml +++ b/en_US.ISO8859-1/books/faq/book.sgml @@ -4412,8 +4412,7 @@ kern.timecounter.hardware: TSC -> i8254 - Static and dynamic ELF libraries (for use with - FreeBSD 3.0 and above). + Static and dynamic ELF libraries. @@ -5126,8 +5125,8 @@ kern.timecounter.hardware: TSC -> i8254 Chances are, you compiled your kernel in debug mode. Kernels built in debug mode contain many symbols that are used for debugging, thus - greatly increasing the size of the kernel. Note that if you - running a FreeBSD 3.0 or later system, there will be little + greatly increasing the size of the kernel. Note that + there will be little or no performance decrease from running a debug kernel, and it is useful to keep one around in case of a system panic. @@ -5150,7 +5149,7 @@ kern.timecounter.hardware: TSC -> i8254 - Both of the above situations will cause your kernel to + Either of the above settings will cause your kernel to be built in debug mode. As long as you make sure you follow the steps above, you can build your kernel normally, and you should notice a fairly large size decrease; most kernels @@ -6522,9 +6521,9 @@ perm /dev/acd0 0660 Yes, FreeBSD supports System V-style IPC, including - shared memory, messages and semaphores. Versions of - FreeBSD later than 3.2 support System V IPC in the GENERIC - kernel. In earlier versions of FreeBSD, enable this + shared memory, messages and semaphores, + in the GENERIC + kernel. In a custom kernel, enable this support by adding the following lines to your kernel config. @@ -6575,8 +6574,8 @@ options SYSVMSG # enable for messaging Do not panic! Restart the system, type - boot -s at the Boot: prompt (just - -s for FreeBSD releases before 3.2) to + boot -s at the Boot: prompt + to enter Single User mode. At the question about the shell to use, hit ENTER. You will be dropped to a &prompt.root; prompt. Enter mount -u / to remount your root filesystem @@ -6817,10 +6816,10 @@ options SYSVMSG # enable for messaging Long answer: FreeBSD derives its releases from one of two places. Major, dot-zero, releases, such as - 3.0-RELEASE and 4.0-RELEASE, are branched from the head of + 4.0-RELEASE and 5.0-RELEASE, are branched from the head of the development stream, commonly referred to as -CURRENT. Minor releases, such - as 3.1-RELEASE or 4.2-RELEASE, have been snapshots of the active + as 4.1-RELEASE or 5.2-RELEASE, have been snapshots of the active -STABLE branch. Starting with 4.3-RELEASE, each release also now has its own branch which can be tracked by people requiring an extremely conservative rate @@ -7453,14 +7452,14 @@ EndSection session, do AltF1. - The default FreeBSD installation has three virtual - consoles enabled (8 starting with 3.3-RELEASE), and + The default FreeBSD installation has eight virtual + consoles enabled. AltF1, AltF2, - and AltF3 + AltF3, and so on will switch between these virtual consoles. To enable more of them, edit @@ -8872,8 +8871,8 @@ Key F15 A A Menu Workplace Nop - FreeBSD 3.0 and later use a version of BIND - that uses a random high-numbered port for outgoing queries. If + BIND + uses a random high-numbered port for outgoing queries. If you want to use port 53 for outgoing queries, either to get past a firewall or to make yourself feel better, you can try the following in