From owner-freebsd-bugs@FreeBSD.ORG Mon Sep 5 19:40:01 2011 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AA4EC1065676 for ; Mon, 5 Sep 2011 19:40:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 7FFC68FC18 for ; Mon, 5 Sep 2011 19:40:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p85Je1lM041800 for ; Mon, 5 Sep 2011 19:40:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p85Je1W5041799; Mon, 5 Sep 2011 19:40:01 GMT (envelope-from gnats) Resent-Date: Mon, 5 Sep 2011 19:40:01 GMT Resent-Message-Id: <201109051940.p85Je1W5041799@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-bugs@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Eitan Adler Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D996A106566B for ; Mon, 5 Sep 2011 19:38:42 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from red.freebsd.org (red.freebsd.org [IPv6:2001:4f8:fff6::22]) by mx1.freebsd.org (Postfix) with ESMTP id C7FB68FC16 for ; Mon, 5 Sep 2011 19:38:42 +0000 (UTC) Received: from red.freebsd.org (localhost [127.0.0.1]) by red.freebsd.org (8.14.4/8.14.4) with ESMTP id p85Jcgcx069249 for ; Mon, 5 Sep 2011 19:38:42 GMT (envelope-from nobody@red.freebsd.org) Received: (from nobody@localhost) by red.freebsd.org (8.14.4/8.14.4/Submit) id p85Jcgpn069248; Mon, 5 Sep 2011 19:38:42 GMT (envelope-from nobody) Message-Id: <201109051938.p85Jcgpn069248@red.freebsd.org> Date: Mon, 5 Sep 2011 19:38:42 GMT From: Eitan Adler To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Cc: Subject: misc/160491: [patch] reaper of the dead: remove ancient FAQ entries X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Sep 2011 19:40:01 -0000 >Number: 160491 >Category: misc >Synopsis: [patch] reaper of the dead: remove ancient FAQ entries >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Sep 05 19:40:01 UTC 2011 >Closed-Date: >Last-Modified: >Originator: Eitan Adler >Release: >Organization: graveyard >Environment: >Description: The attached patch is an incomplete mass removal of outdated FAQ questions. I removed whichever questions I knew to be no longer relevant, but left ones I was not 100% certain about about. We need to strip the FAQ to the bare bones and build it back up. >How-To-Repeat: >Fix: Index: book.sgml =================================================================== RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/faq/book.sgml,v retrieving revision 1.1140 diff -u -r1.1140 book.sgml --- book.sgml 29 Aug 2011 05:16:37 -0000 1.1140 +++ book.sgml 5 Sep 2011 19:37:12 -0000 @@ -46,7 +46,6 @@ &tm-attrib.ibm; &tm-attrib.ieee; &tm-attrib.intel; - &tm-attrib.iomega; &tm-attrib.linux; &tm-attrib.microsoft; &tm-attrib.mips; @@ -65,7 +64,7 @@ This is the FAQ for &os; versions 6.X, 7.X and 8.X. All entries are assumed to be - relevant to &os; 6.X and later, + relevant to &os; 7.X and later, unless otherwise noted. If you are interested in helping with this project, send email to the &a.doc;. The latest version of this document is always available from the Introduction Welcome to the &os; - 6.X-, 7.X- and - 8.X FAQ! + 7.X-, 8.X- and + 9.X FAQ! As is usual with Usenet FAQs, this document aims to cover the most frequently asked questions concerning the &os; operating @@ -1141,107 +1140,6 @@ Installation - - - Which file do I download to get &os;? - - - - You need three floppy images: - floppies/boot.flp, - floppies/kern1.flp, and - floppies/kern2.flp. These images need - to be copied onto floppies by tools like - fdimage or &man.dd.1;. - - If you need to download the distributions yourself (for - a DOS file system install, for instance), below are some - recommendations for distributions to grab: - - - - base/ - - - - manpages/ - - - - compat*/ - - - - doc/ - - - - src/ssys.* - - - - Full instructions on this procedure and a little bit - more about installation issues in general can be found in - the Handbook entry on installing &os;. - - - - - - - What do I do if the floppy images does not fit on a - single floppy? - - - - A 3.5 inch (1.44 MB) floppy can accommodate - 1,474,560 bytes of data. The boot image is exactly - 1,474,560 bytes in size. - - Common mistakes when preparing the boot floppy - are: - - - - Not downloading the floppy image in - binary mode when using - FTP. - - Some FTP clients default their transfer mode to - ascii and attempt to change any - end-of-line characters received to match the conventions - used by the client's system. This will almost - invariably corrupt the boot image. Check the size of - the downloaded boot image: if it is not - exactly that on the server, then - the download process is suspect. - - To workaround: type binary at - the FTP command prompt after getting connected to the - server and before starting the download of the - image. - - - - Using the DOS copy command (or - equivalent GUI tool) to transfer the boot image to - floppy. - - Programs like copy will not work - as the boot image has been created to be booted into - directly. The image has the complete content of the - floppy, track for track, and is not meant to be placed - on the floppy as a regular file. You have to transfer - it to the floppy raw, using the low-level - tools (e.g. fdimage or - rawrite) described in the installation guide to &os;. - - - - - @@ -1585,15 +1483,6 @@ at least once!) - - If you are using &windows; 95 or - &windows; 98 did you run fdimage - or rawrite in pure DOS mode? These - operating systems can interfere with programs that write - directly to hardware, which the disk creation program - does; even running it inside a DOS shell in the GUI can - cause this problem. - There have also been reports of &netscape; causing @@ -1829,27 +1718,6 @@ - - Do I need to build a kernel? - - - - Building a new kernel was originally pretty much a - required step in a &os; installation, but more recent releases - have benefited from the introduction of much friendlier - kernel configuration methods. It is very easy to configure - the kernel's configuration by much more flexible - hints which can be set at the loader - prompt. - - It may still be worthwhile building a new kernel - containing just the drivers that you need, just to save a - bit of RAM, but it is no longer necessary for most - systems. - - - - Should I use DES, Blowfish, or MD5 passwords and how do I specify which form my users receive? @@ -1876,21 +1744,6 @@ - - Why does the boot floppy start, but hang at the - Probing Devices... screen? - - - - If you have a IDE &iomegazip; or &jaz; drive installed, - remove it and try again. The boot floppy can get confused by - the drives. After the system is installed you can reconnect - the drive. Hopefully this will be fixed in a later - release. - - - - Why do I get a panic: can't mount root error when rebooting the system after @@ -3228,82 +3081,6 @@ - - Why does &os; only use 64 MB of RAM when my system - has 128 MB of RAM installed? - - - - Due to the manner in which &os; gets the memory size - from the BIOS, it can only detect 16 bits worth of - Kbytes in size (65535 Kbytes = 64 MB) (or less... - some BIOSes peg the memory size to 16 MB). If you have - more than 64 MB, &os; will attempt to detect it; - however, the attempt may fail. - - To work around this problem, you need to use the kernel - option specified below. There is a way to get complete - memory information from the BIOS, but we do not have room in - the bootblocks to do it. Someday when lack of room in the - bootblocks is fixed, we will use the extended BIOS functions - to get the full memory information... but for now we are - stuck with the kernel option. - - options MAXMEM=n - - Where n is your memory in - Kilobytes. For a 128 MB machine, you would want to use - 131072. - - - - - - My system has more than 1 GB of RAM, and I'm - getting panics with kmem_map too small - messages. What is wrong? - - - - Normally, &os; determines a number of kernel parameters, - such as as the maximum number of files that can be open - concurrently, from the amount of memory installed in the - system. On systems with one gigabyte of RAM or more, this - auto sizing mechanism may choose values that - are too high: while starting up, the kernel allocates - various tables and other structures that fill up most of the - available kernel memory. Later on, while the system is - running, the kernel has no more space left for dynamic - memory allocations, and panics. - - Compile your own kernel, and add the - to your kernel - configuration file, increasing the maximum size to - 400 MB (). 400 MB appears - to be sufficient for machines with up to 6 GB of - memory. - - - - - - My system does not have 1 GB of RAM, and &os; still - panics with kmem_map too - small! - - - - The panic indicates that the system ran out of virtual - memory for network buffers (specifically, mbuf clusters). - You can increase the amount of VM available for mbuf - clusters by following the instructions in the Network Limits - section of the Handbook. - - - - Why do I get the error kernel: proc: table is full? @@ -3314,12 +3091,11 @@ processes to exist at one time. The number is based on the kern.maxusers &man.sysctl.8; variable. kern.maxusers also affects various other - in-kernel limits, such as network buffers (see this earlier - question). If your machine is heavily loaded, you probably - want to increase kern.maxusers. This - will increase these other system limits in addition to the - maximum number of processes. + in-kernel limits, such as network buffers. If your machine + is heavily loaded, you probably want to increase + kern.maxusers. This will increase these + other system limits in addition to the maximum number + of processes. To adjust your kern.maxusers value, see the - - for 6.X-RELEASE/6-STABLE - - - ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-6-stable - - - for 7.X-RELEASE/7-STABLE @@ -5477,78 +5244,6 @@ - - I have a new removable drive, how do I use it? - - - - Whether it is a removable drive like a &iomegazip; or an - EZ drive (or even a floppy, if you want to use it that way), - or a new hard disk, once it is installed and recognized by - the system, and you have your cartridge/floppy/whatever - slotted in, things are pretty much the same for all - devices. - - (this section is based on Mark Mayo's ZIP FAQ) - - - If it is a ZIP drive or a floppy, you have already got a - DOS file system on it, you can use a command like this: - - &prompt.root; mount -t msdosfs /dev/fd0c /floppy - - if it is a floppy, or this: - - &prompt.root; mount -t msdosfs /dev/da2s4 /zip - - for a ZIP disk with the factory configuration. - - For other disks, see how they are laid out using - &man.fdisk.8; or &man.sysinstall.8;. - - The rest of the examples will be for a ZIP drive on - da2, the third SCSI disk. - - Unless it is a floppy, or a removable you plan on - sharing with other people, it is probably a better idea to - stick a BSD file system on it. You will get long filename - support, at least a 2X improvement in performance, and a lot - more stability. First, you need to redo the DOS-level - partitions/file systems. You can either use &man.fdisk.8; - or &man.sysinstall.8;, or for a small drive that you do not - want to bother with multiple operating system support on, - just blow away the whole FAT partition table (slices) and - just use the BSD partitioning: - - &prompt.root; dd if=/dev/zero of=/dev/rda2 count=2 -&prompt.root; disklabel -Brw da2 auto - - You can use &man.disklabel.8; or &man.sysinstall.8; to - create multiple BSD partitions. You will certainly want to - do this if you are adding swap space on a fixed disk, but it - is probably irrelevant on a removable drive like a - ZIP. - - Finally, create a new file system, this one is on our - ZIP drive using the whole disk: - - &prompt.root; newfs /dev/rda2c - - and mount it: - - &prompt.root; mount /dev/da2c /zip - - and it is probably a good idea to add a line like this - to /etc/fstab (see &man.fstab.5;) so - you can just type mount /zip in the - future: - - /dev/da2c /zip ffs rw,noauto 0 0 - - - - Why do I get Incorrect super block when mounting a CD-ROM? @@ -6841,22 +6536,6 @@ - - Why did &os; choose to go with the &xorg; ports by - default? - - - - The &xorg; developers claimed that their goal is to - release more often and incorporate new features more - quickly. If they are able to do so, this will be very - attractive. Also, their software still uses the traditional - X license, while &xfree86; is using their modified - one. - - - - I want to run X, how do I go about it? @@ -9533,78 +9212,6 @@ - - - Why do &macos; and &windows; 98 connections freeze - when running PPPoE on the gateway? - - - - Thanks to Michael Wozniak - mwozniak@netcom.ca for figuring this out and - Dan Flemming danflemming@mac.com for the Mac - solution: - - This is due to what is called a Black - Hole router. &macos; and &windows; 98 (and maybe - other µsoft; OSs) send TCP packets with a requested - segment size too big to fit into a PPPoE frame (MTU is - 1500 by default for Ethernet) - and have the do not - fragment bit set (default of TCP) and the Telco - router is not sending ICMP must fragment back - to the WWW site you are trying to load. (Alternatively, the - router is sending the ICMP packet correctly, but the - firewall at the WWW site is dropping it.) When the www - server is sending you frames that do not fit into the PPPoE - pipe the Telco router drops them on the floor and your page - does not load (some pages/graphics do as they are smaller - than a MSS). This seems to be the default of most Telco - PPPoE configurations. - - One fix is to use regedit on - your 95/98 system to add the following registry entry: - - HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\NetTrans\0000\MaxMTU - - It should be a string with a value - 1436, as some ADSL routers are reported - to be unable to deal with packets larger than this. This - registry key has been changed to - Tcpip\Parameters\Interfaces\ID for - adapter\MTU in &windows; 2000 - and becomes a DWORD. - - Refer to the Microsoft Knowledge Base documents Q158474 - Windows TCPIP Registry Entries - and Q120642 - TCPIP & NBT Configuration Parameters for &windowsnt; - for more information on changing &windows; MTU to work with - a NAT router. - - Another regedit possibility under &windows; 2000 to - set the Tcpip\Parameters\Interfaces\ID - for adapter\EnablePMTUBHDetect - DWORD to 1 as - mentioned in the Microsoft document 120642 mentioned - above. - - Unfortunately, &macos; does not provide an interface for - changing TCP/IP settings. However, there are several commercial - programs available that will allow users to customize TCP/IP - settings. &macos; NAT users should search for their MTU - settings and enter 1450 instead of - 1500. - - The &man.ppp.8; has an enable - tcpmssfixup command that will automatically adjust - the MSS to an appropriate value. This facility is enabled - by default. If you are stuck with an older version of - &man.ppp.8;, you may want to look at the net/tcpmssd port. - - - None of this helps — I am desperate! What can I @@ -10570,7 +10177,10 @@ somewhere? And then I was enlightened - :-) + :-) + + 1 to remove the documentation that has been outdated + five minutes later &a.tabthorpe; says: None, real &os; hackers are not afraid of the @@ -10803,24 +10413,6 @@ - - How did you split the distribution into 1392 KB - files? - - - - Newer BSD based systems have a - option to &man.split.1; that allows them to split files on - arbitrary byte boundaries. - - Here is an example from - /usr/src/release/Makefile. - - ZIPNSPLIT= gzip --no-name -9 -c | split -b 1392k - - - - - I have written a kernel extension, who do I send it to? @@ -10924,20 +10516,6 @@ - - Can you assign a major number for a device driver I have - written? - - - - &os; releases after February 2003 has a facility for - dynamically and automatically allocating major numbers for - device drivers at runtime (see &man.devfs.5;), so there is - no need for this. - - - - What about alternative layout policies for directories? >Release-Note: >Audit-Trail: >Unformatted: