From cf1b475fc253cf547c861f49054037329ff1f782 Mon Sep 17 00:00:00 2001 From: "David E. O'Brien" Date: Thu, 8 Mar 2001 11:01:25 +0000 Subject: [PATCH] Fix formatting -- people this thing is not indented. --- en_US.ISO8859-1/books/faq/book.sgml | 605 ++++++++++++++------------- en_US.ISO_8859-1/books/faq/book.sgml | 605 ++++++++++++++------------- 2 files changed, 606 insertions(+), 604 deletions(-) diff --git a/en_US.ISO8859-1/books/faq/book.sgml b/en_US.ISO8859-1/books/faq/book.sgml index 58561cb8c9..5d7ecc0329 100644 --- a/en_US.ISO8859-1/books/faq/book.sgml +++ b/en_US.ISO8859-1/books/faq/book.sgml @@ -11,7 +11,7 @@ The FreeBSD Documentation Project - $FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.148 2001/03/07 20:00:49 hrs Exp $ + $FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.149 2001/03/08 10:55:14 obrien Exp $ This is the FAQ for FreeBSD versions 2.X, 3.X, and 4.X. @@ -428,41 +428,41 @@ place(s):
BSDi -4041 Pike Lane, Suite F -Concord, CA -94520 -USA + 4041 Pike Lane, Suite F + Concord, CA + 94520 + USA -Orders: +1 800 786-9907 -Questions: +1 925 674-0783 -FAX: +1 925 674-0821 -email: BSDi Orders address -WWW: BSDi Home page
+ Orders: +1 800 786-9907 + Questions: +1 925 674-0783 + FAX: +1 925 674-0821 + email: BSDi Orders address + WWW: BSDi Home page In Australia, you may find it at:
Advanced Multimedia Distributors -Factory 1/1 Ovata Drive -Tullamarine, Melbourne -Victoria -Australia -Voice: +61 3 9338 6777 + Factory 1/1 Ovata Drive + Tullamarine, Melbourne + Victoria + Australia + Voice: +61 3 9338 6777 -CDROM Support BBS -17 Irvine St -Peppermint Grove, WA -6011 -Voice: +61 9 385-3793 -Fax: +61 9 385-2360
+ CDROM Support BBS + 17 Irvine St + Peppermint Grove, WA + 6011 + Voice: +61 9 385-3793 + Fax: +61 9 385-2360 And in the UK:
The Public Domain & Shareware Library -Winscombe House, Beacon Rd -Crowborough -Sussex. TN6 1UL -Voice: +44 1892 663-298 -Fax: +44 1892 667-473
+ Winscombe House, Beacon Rd + Crowborough + Sussex. TN6 1UL + Voice: +44 1892 663-298 + Fax: +44 1892 667-473 @@ -585,7 +585,8 @@ The definitive printed guide on FreeBSD is The Complete FreeBSD, written by Greg Lehey and - published by BSDi (formerly Walnut Creek CDROM) Books. Now in its second + published by BSDi (formerly Walnut Creek CDROM) Books. + Now in its second edition, the book contains 1,750 pages of install & system administration guidance, program setup help, and manual pages. The book (and current FreeBSD release) can be ordered from @@ -813,7 +814,7 @@ html-split A collection of small, linked, HTML - files. + files. @@ -1422,146 +1423,146 @@ File: +DESC (ignored) - - I have an IBM Thinkpad in the A, T, or X series that FreeBSD - installs on, but then the machine locks up on next boot. How can I - solve this? - + + I have an IBM Thinkpad in the A, T, or X series that FreeBSD + installs on, but then the machine locks up on next boot. How can I + solve this? + - - A bug in early revisions of IBM's BIOS on these machines - mistakenly identifies the FreeBSD partition as a potential FAT - suspend-to-disk partition. When the BIOS tries to parse the - FreeBSD partition it hangs. + + A bug in early revisions of IBM's BIOS on these machines + mistakenly identifies the FreeBSD partition as a potential FAT + suspend-to-disk partition. When the BIOS tries to parse the + FreeBSD partition it hangs. - According to IBM In an e-mail from Keith - Frechette - kfrechet@us.ibm.com., the - following model/BIOS release numbers incorporate the fix. + According to IBM In an e-mail from Keith + Frechette + kfrechet@us.ibm.com., the + following model/BIOS release numbers incorporate the fix. - - - - - Model - BIOS revision - - - - - - T20 - IYET49WW or later - + + + + + Model + BIOS revision + + + + + + T20 + IYET49WW or later + - - T21 - KZET22WW or later - + + T21 + KZET22WW or later + - - A20p - IVET62WW or later - + + A20p + IVET62WW or later + - - A20m - IWET54WW or later - + + A20m + IWET54WW or later + - - A21p - KYET27WW or later - + + A21p + KYET27WW or later + - - A21m - KXET24WW or later - + + A21m + KXET24WW or later + - - A21e - KUET30WW - - - - + + A21e + KUET30WW + + + + - If you have an earlier BIOS, and upgrading is not an option a - workaround is to install FreeBSD, change the partition ID FreeBSD - uses, and install new boot blocks that can handle the different - partition ID. + If you have an earlier BIOS, and upgrading is not an option a + workaround is to install FreeBSD, change the partition ID FreeBSD + uses, and install new boot blocks that can handle the different + partition ID. - First, you'll need to to restore the machine to a state where - it can get through its self-test screen. Doing this requires - powering up the machine without letting it find a FreeBSD - partition on its primary disk. One way is to remove the hard disk - and temporarily move it to an older ThinkPad (such as a ThinkPad - 600) or a desktop PC with an appropriate conversion cable. Once - it's there, you can delete the FreeBSD partition and move the hard - disk back. The ThinkPad should now be in a bootable state - again. + First, you'll need to to restore the machine to a state where + it can get through its self-test screen. Doing this requires + powering up the machine without letting it find a FreeBSD + partition on its primary disk. One way is to remove the hard disk + and temporarily move it to an older ThinkPad (such as a ThinkPad + 600) or a desktop PC with an appropriate conversion cable. Once + it's there, you can delete the FreeBSD partition and move the hard + disk back. The ThinkPad should now be in a bootable state + again. - With the machine functional again, you can use the workaround - procedure described here to get a working FreeBSD - installation. + With the machine functional again, you can use the workaround + procedure described here to get a working FreeBSD + installation. - - - Download boot1 and - boot2 from + + Download boot1 and + boot2 from http://people.freebsd.org/~bmah/ThinkPad/. - Put these files somewhere you will be able to retrieve them - later. - + Put these files somewhere you will be able to retrieve them + later. + - - Install FreeBSD as normal on to the ThinkPad. - Do not use Dangerously - Dedicated mode. Do not - reboot when the install has finished. - + + Install FreeBSD as normal on to the ThinkPad. + Do not use Dangerously + Dedicated mode. Do not + reboot when the install has finished. + - - Either switch to the Emergency Holographic - Shell (ALT - F4) or start a - fixit shell. - + + Either switch to the Emergency Holographic + Shell (ALT + F4) or start a + fixit shell. + - - Use &man.fdisk.8; to change the FreeBSD partition ID from - 165 to 166 (this is the - type used by OpenBSD). - + + Use &man.fdisk.8; to change the FreeBSD partition ID from + 165 to 166 (this is the + type used by OpenBSD). + - - Bring the boot1 and - boot2 files to the local - filesystem. - + + Bring the boot1 and + boot2 files to the local + filesystem. + - - Use &man.disklabel.8; to write boot1 - and boot2 to your FreeBSD slice. + + Use &man.disklabel.8; to write boot1 + and boot2 to your FreeBSD slice. - &prompt.root; disklabel -B -b boot1 -s boot2 ad0sn + &prompt.root; disklabel -B -b boot1 -s boot2 ad0sn - n is the number of the slice - where you installed FreeBSD. - + n is the number of the slice + where you installed FreeBSD. + - - Reboot. At the boot prompt you will be given the option - of booting OpenBSD. This will actually - boot FreeBSD. - - + + Reboot. At the boot prompt you will be given the option + of booting OpenBSD. This will actually + boot FreeBSD. + + - Getting this to work in the case where you want to dual boot - OpenBSD and FreeBSD on the same laptop is left as an exercise for - the reader. - + Getting this to work in the case where you want to dual boot + OpenBSD and FreeBSD on the same laptop is left as an exercise for + the reader. + @@ -1879,13 +1880,13 @@ BUSY - - By the geometry of a disk, we mean the - number of cylinders, heads and sectors/track on a disk - I'll - refer to this as C/H/S for convenience. This is how the PC's - BIOS works out which area on a disk to read/write from. - - + + By the geometry of a disk, we mean the + number of cylinders, heads and sectors/track on a disk - I'll + refer to this as C/H/S for convenience. This is how the PC's + BIOS works out which area on a disk to read/write from. + + This seems to cause a lot of confusion for some reason. First of all, the physical geometry of a @@ -2373,7 +2374,7 @@ Filesystem 1024-blocks Used Avail Capacity Mounted on 1+0 records out 1 bytes transferred in 0.000187 secs (5346 bytes/sec) -rw-r--r-- 1 bde bin 8796093022207 Sep 7 16:04 z -32 z +32 z Filesystem 1024-blocks Used Avail Capacity Mounted on /dev/da0a 64479 27734 31587 47% / @@ -4226,7 +4227,7 @@ IO range check 0x00 activate 0x01 I get the error nlist failed when - running, for example, top or + running, for example, top or systat. @@ -4238,13 +4239,13 @@ IO range check 0x00 activate 0x01 Your kernel and userland are not synchronized (i.e., you - built a new kernel but did not do an - installworld, or vice versa), and - thus the symbol table is different from what the user - application thinks it is. If this is the case, simply - complete the upgrade process (see - /usr/src/UPDATING for the correct - sequence). + built a new kernel but did not do an + installworld, or vice versa), and + thus the symbol table is different from what the user + application thinks it is. If this is the case, simply + complete the upgrade process (see + /usr/src/UPDATING for the correct + sequence). @@ -5013,7 +5014,7 @@ device sio5 at isa? port 0x2b8 tty flags 0x501 vector siointr Every kernel I try to build fails to compile; even GENERIC. - + There are a number of possible causes for this problem. They are, in no particular order: @@ -5249,19 +5250,19 @@ device sio5 at isa? port 0x2b8 tty flags 0x501 vector siointr If this is what you did, the extra crontab is simply a copy of /etc/crontab in the wrong format it. Delete it with the command: - - &prompt.root; crontab -r - Next time, when you edit - /etc/crontab, you should not do - anything to inform &man.cron.8; of the changes, since it - will notice them automatically. + &prompt.root; crontab -r + + Next time, when you edit + /etc/crontab, you should not do + anything to inform &man.cron.8; of the changes, since it + will notice them automatically. - If you want something to be run once per day, week, or - month, it's probably better to add shell scripts - /usr/local/etc/periodic, and let the - &man.periodic.8; command run from the system cron schedule - it with the other periodic system tasks. + If you want something to be run once per day, week, or + month, it's probably better to add shell scripts + /usr/local/etc/periodic, and let the + &man.periodic.8; command run from the system cron schedule + it with the other periodic system tasks. The actual reason for the error is that the system crontab has an extra field, specifying which user to run the @@ -5278,7 +5279,7 @@ device sio5 at isa? port 0x2b8 tty flags 0x501 vector siointr I made a mistake in rc.conf, - or another startup file, and + or another startup file, and now I can't edit it because the filesystem is read-only. What should I do? @@ -5884,16 +5885,16 @@ C:\="DOS" I get messages like: unknown: <PNP0303> can't - assign resources on boot + assign resources on boot These indicate Plug-and-Play devices that the current - kernel doesn't have drivers for. They're harmless. + kernel doesn't have drivers for. They're harmless. - If you dislike these messages, the FreeBSD Project - will happily accept driver contributions via send-pr. - + If you dislike these messages, the FreeBSD Project + will happily accept driver contributions via send-pr. + @@ -5913,34 +5914,34 @@ C:\="DOS" Put the quota file on the file system that the quotas are to be enforced on. ie: - - - - - Filesystem - Quota file - - + + + + + Filesystem + Quota file + + - - - /usr - /usr/admin/quotas - + + + /usr + /usr/admin/quotas + - - /home - /home/admin/quotas - + + /home + /home/admin/quotas + - - … - … - - - - - + + … + … + + + + + @@ -6384,8 +6385,8 @@ define(`confDELIVERY_MODE',`deferred')dnl &prompt.root; ./install.sh Alternately, you can remove all "MAKE_KERBEROS" - options from /etc/make.conf and rebuild - world. + options from /etc/make.conf and rebuild + world. @@ -6604,12 +6605,12 @@ define(`confDELIVERY_MODE',`deferred')dnl &prompt.root; chmod 640 /dev/cd0c - - Finally, add the line - vfs.usermount=1 to the file - /etc/sysctl.conf so that it is reset - at system boot time. - + + Finally, add the line + vfs.usermount=1 to the file + /etc/sysctl.conf so that it is reset + at system boot time. + All users can now mount the floppy @@ -6633,7 +6634,7 @@ define(`confDELIVERY_MODE',`deferred')dnl Enabling vfs.usermount, however, has negative security implications. A better way to access MSDOS formatted media is to use the mtools package in the ports collection. + URL="http://www.freebsd.org/cgi/ports.cgi?query=%5Emtools-&stype=name">mtools package in the ports collection. @@ -6776,52 +6777,52 @@ define(`confDELIVERY_MODE',`deferred')dnl I tried to install a new kernel, and the chflags failed. - How do I get around this? + How do I get around this? Short answer: You're probably at security level - greater than 0. Reboot directly to single user mode to - install the kernel. + greater than 0. Reboot directly to single user mode to + install the kernel. Long answer: FreeBSD disallows changing system flags - at security levels greater than 0. You can check your - security level with the command: + at security levels greater than 0. You can check your + security level with the command: - &prompt.root; sysctl kern.securelevel + &prompt.root; sysctl kern.securelevel - You cannot lower the security level; you have to boot - to single mode to install the kernel, or change the - security in /etc/rc.conf then reboot. See - the &man.init.8; man page for details on securelevel, and - see /etc/defaults/rc.conf and the - &man.rc.conf.5; man page for more information on rc.conf. + You cannot lower the security level; you have to boot + to single mode to install the kernel, or change the + security in /etc/rc.conf then reboot. See + the &man.init.8; man page for details on securelevel, and + see /etc/defaults/rc.conf and the + &man.rc.conf.5; man page for more information on rc.conf. I can't change the time on my system by more than one second! - How do I get around this? + How do I get around this? Short answer: You're probably at security level - greater than 1. Reboot directly to single user mode to - change the date. + greater than 1. Reboot directly to single user mode to + change the date. Long answer: FreeBSD disallows changing the time by more that one second at security levels greater than 1. You can check your security level with the command: - &prompt.root; sysctl kern.securelevel + &prompt.root; sysctl kern.securelevel - You cannot lower the security level; you have to boot - to single mode to change the date, or change the security - level in /etc/rc.conf then reboot. See - the &man.init.8; man page for details on securelevel, and - see /etc/defaults/rc.conf and the - &man.rc.conf.5; man page for more information on rc.conf. + You cannot lower the security level; you have to boot + to single mode to change the date, or change the security + level in /etc/rc.conf then reboot. See + the &man.init.8; man page for details on securelevel, and + see /etc/defaults/rc.conf and the + &man.rc.conf.5; man page for more information on rc.conf. @@ -6880,24 +6881,24 @@ define(`confDELIVERY_MODE',`deferred')dnl I tried to run X, but I get an - KDENABIO failed (Operation not permitted) - error when I type startx. What do I do - now? + KDENABIO failed (Operation not permitted) + error when I type startx. What do I do + now? Your system is running at a raised securelevel, isn't - it? It is, indeed, impossible to start X at a raised - securelevel. To see why, look at the &man.init.8; man - page. - + it? It is, indeed, impossible to start X at a raised + securelevel. To see why, look at the &man.init.8; man + page. + So the question is what else you should do instead, and you basically have two choices: set your securelevel back down to zero (usually from /etc/rc.conf), or run &man.xdm.1; at boot time (before the securelevel is raised). - See for more information about + See for more information about running &man.xdm.1; at boot time. @@ -7226,7 +7227,7 @@ ttyvb "/usr/libexec/getty Pc" cons25 on secure want to change the secure to insecure. - + If you want to run an X server you must leave at least one virtual @@ -7236,8 +7237,8 @@ ttyvb "/usr/libexec/getty Pc" cons25 on secure 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 @@ -7287,34 +7288,34 @@ ttyvb "/usr/libexec/getty Pc" cons25 off secure How do I access the virtual consoles from X? - - Use - Ctrl - Alt - Fn - to switch back to a virtual console. - - Ctrl - Alt - F1 - would return you to the first virtual console. + + Use + Ctrl + Alt + Fn + to switch back to a virtual console. + + Ctrl + Alt + F1 + would return you to the first virtual console. - Once you are back to a text console, you can then use - - Alt - Fn - as normal to move between them. - - To return to the X session, you must switch to the virtual - console running X. If you invoked X from the command line, (e.g., - using startx) then the X session will attach to - the next unused virtual console, not the text console from which - it was invoked. If you have eight active virtual terminals then X - will be running on the ninth, and you would use - - Alt - F9 - to return. + Once you are back to a text console, you can then use + + Alt + Fn + as normal to move between them. + + To return to the X session, you must switch to the virtual + console running X. If you invoked X from the command line, (e.g., + using startx) then the X session will attach to + the next unused virtual console, not the text console from which + it was invoked. If you have eight active virtual terminals then X + will be running on the ninth, and you would use + + Alt + F9 + to return. @@ -7536,8 +7537,8 @@ UserConfig> quit + set_mouse_resolution(sc->kbdc, PSMD_RES_HIGH); + #if 0 - set_mouse_scaling(sc->kbdc); /* 1:1 scaling */ - set_mouse_mode(sc->kbdc); /* stream mode */ + set_mouse_scaling(sc->kbdc); /* 1:1 scaling */ + set_mouse_mode(sc->kbdc); /* stream mode */ In versions 2.2.6 or later, specify the flags 0x04 to the PS/2 mouse driver to put the mouse into the high @@ -8061,15 +8062,15 @@ Key F15 A A Menu Workplace Nop passage from the &man.exports.5 manual page correctly: -
- Each line in the file (other than comment - lines that begin with a #) specifies the mount point(s) - and export flags within one local server filesystem for - one or more hosts. A host may be specified only once - for each local filesystem on the server and there may be - only one default entry for each server filesystem that - applies to all other hosts. -
+
+ Each line in the file (other than comment + lines that begin with a #) specifies the mount point(s) + and export flags within one local server filesystem for + one or more hosts. A host may be specified only once + for each local filesystem on the server and there may be + only one default entry for each server filesystem that + applies to all other hosts. +
This is made more clear by an example of a common mistake. If everything above /usr is @@ -8402,7 +8403,7 @@ Znyx (2.2.x) ZX312, ZX314, ZX342, ZX345, ZX346, ZX348 utilize it. Add this to your kernel config file and build a new kernel: - pseudo-device bpfilter # Berkeley Packet Filter + pseudo-device bpfilter # Berkeley Packet Filter Secondly, after rebooting you will have to create the device node. This can be accomplished by a change to the @@ -8523,7 +8524,7 @@ Znyx (2.2.x) ZX312, ZX314, ZX342, ZX345, ZX346, ZX348 /etc/syslog.conf contains the lines !ppp -*.* /var/log/ppp.log +*.* /var/log/ppp.log and that the file /var/log/ppp.log exists. You can now find out a lot about what's going on @@ -9570,8 +9571,8 @@ ATDT1234567 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 + sending the ICMP packet correctly, but the firewall at the www + site is dropping it.) When the www server is sending you frames that don't fit into the PPPoE pipe the Telco router drops them on the floor and your page doesn't load (some pages/graphics do as they are smaller than a MSS.) This seems @@ -9590,13 +9591,13 @@ ATDT1234567 packets into a PPPoE frame perfectly but the 1450 gives you a margin of error for other IP protocols you may encounter). This registry key is reported to - have moved to - Tcpip\Parameters\Interfaces\ID for adapter\MTU - in Windows 2000. + have moved to + Tcpip\Parameters\Interfaces\ID for adapter\MTU + in Windows 2000. Refer to Microsoft Knowledge - Base documents Q158474 - Windows TCPIP Registry + URL="http://search.support.microsoft.com/kb">Microsoft Knowledge + Base documents Q158474 - Windows TCPIP Registry Entries and Q120642 - TCPIP & NBT Configuration Parameters for Windows NT for more information on changing Windoze MTU to work with a FreeBSD/NAT/PPPoE @@ -10098,9 +10099,9 @@ device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointr file. For example: tip115200|Dial any phone number at 115200 bps:\ - :dv=/dev/cuaa0:br#115200:at=hayes:pa=none:du: + :dv=/dev/cuaa0:br#115200:at=hayes:pa=none:du: tip57600|Dial any phone number at 57600 bps:\ - :dv=/dev/cuaa0:br#57600:at=hayes:pa=none:du: + :dv=/dev/cuaa0:br#57600:at=hayes:pa=none:du: Then you can do something like tip -115200 5551234. If you prefer : pain|pain.deep13.com|Forrester's machine:\ - :cm=CONNECT pain\n:tc=deep13: + :cm=CONNECT pain\n:tc=deep13: muffin|muffin.deep13.com|Frank's machine:\ - :cm=CONNECT muffin\n:tc=deep13: + :cm=CONNECT muffin\n:tc=deep13: deep13:Gizmonics Institute terminal server:\ - :dv=/dev/cuaa2:br#38400:at=hayes:du:pa=none:pn=5551234: + :dv=/dev/cuaa2:br#38400:at=hayes:du:pa=none:pn=5551234: will let you type tip pain or tip muffin to connect to the hosts @@ -10179,9 +10180,9 @@ deep13:Gizmonics Institute terminal server:\ the pn capability: big-university:\ - :pn=\@:tc=dialout + :pn=\@:tc=dialout dialout:\ - :dv=/dev/cuaa3:br#9600:at=courier:du:pa=none: + :dv=/dev/cuaa3:br#9600:at=courier:du:pa=none: Then, list the phone numbers for the university in @@ -11388,8 +11389,8 @@ ${RELEASEDIR}/tarballs/bindist/bin_tgz.) mailing list if you are interested in joining that project. Most recent additions to the list of upcoming plaforms are IA-64 and PowerPC, join the - freebsd-ia64@FreeBSD.org or/and - freebsd-ppc@FreeBSD.org freebsd-ia64@FreeBSD.org or/and + freebsd-ppc@FreeBSD.org mailing lists for more information. For general discussion on new architectures, join the freebsd-platforms@FreeBSD.org diff --git a/en_US.ISO_8859-1/books/faq/book.sgml b/en_US.ISO_8859-1/books/faq/book.sgml index 58561cb8c9..5d7ecc0329 100644 --- a/en_US.ISO_8859-1/books/faq/book.sgml +++ b/en_US.ISO_8859-1/books/faq/book.sgml @@ -11,7 +11,7 @@ The FreeBSD Documentation Project - $FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.148 2001/03/07 20:00:49 hrs Exp $ + $FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.149 2001/03/08 10:55:14 obrien Exp $ This is the FAQ for FreeBSD versions 2.X, 3.X, and 4.X. @@ -428,41 +428,41 @@ place(s):
BSDi -4041 Pike Lane, Suite F -Concord, CA -94520 -USA + 4041 Pike Lane, Suite F + Concord, CA + 94520 + USA -Orders: +1 800 786-9907 -Questions: +1 925 674-0783 -FAX: +1 925 674-0821 -email: BSDi Orders address -WWW: BSDi Home page
+ Orders: +1 800 786-9907 + Questions: +1 925 674-0783 + FAX: +1 925 674-0821 + email: BSDi Orders address + WWW: BSDi Home page In Australia, you may find it at:
Advanced Multimedia Distributors -Factory 1/1 Ovata Drive -Tullamarine, Melbourne -Victoria -Australia -Voice: +61 3 9338 6777 + Factory 1/1 Ovata Drive + Tullamarine, Melbourne + Victoria + Australia + Voice: +61 3 9338 6777 -CDROM Support BBS -17 Irvine St -Peppermint Grove, WA -6011 -Voice: +61 9 385-3793 -Fax: +61 9 385-2360
+ CDROM Support BBS + 17 Irvine St + Peppermint Grove, WA + 6011 + Voice: +61 9 385-3793 + Fax: +61 9 385-2360 And in the UK:
The Public Domain & Shareware Library -Winscombe House, Beacon Rd -Crowborough -Sussex. TN6 1UL -Voice: +44 1892 663-298 -Fax: +44 1892 667-473
+ Winscombe House, Beacon Rd + Crowborough + Sussex. TN6 1UL + Voice: +44 1892 663-298 + Fax: +44 1892 667-473 @@ -585,7 +585,8 @@ The definitive printed guide on FreeBSD is The Complete FreeBSD, written by Greg Lehey and - published by BSDi (formerly Walnut Creek CDROM) Books. Now in its second + published by BSDi (formerly Walnut Creek CDROM) Books. + Now in its second edition, the book contains 1,750 pages of install & system administration guidance, program setup help, and manual pages. The book (and current FreeBSD release) can be ordered from @@ -813,7 +814,7 @@ html-split A collection of small, linked, HTML - files. + files. @@ -1422,146 +1423,146 @@ File: +DESC (ignored) - - I have an IBM Thinkpad in the A, T, or X series that FreeBSD - installs on, but then the machine locks up on next boot. How can I - solve this? - + + I have an IBM Thinkpad in the A, T, or X series that FreeBSD + installs on, but then the machine locks up on next boot. How can I + solve this? + - - A bug in early revisions of IBM's BIOS on these machines - mistakenly identifies the FreeBSD partition as a potential FAT - suspend-to-disk partition. When the BIOS tries to parse the - FreeBSD partition it hangs. + + A bug in early revisions of IBM's BIOS on these machines + mistakenly identifies the FreeBSD partition as a potential FAT + suspend-to-disk partition. When the BIOS tries to parse the + FreeBSD partition it hangs. - According to IBM In an e-mail from Keith - Frechette - kfrechet@us.ibm.com., the - following model/BIOS release numbers incorporate the fix. + According to IBM In an e-mail from Keith + Frechette + kfrechet@us.ibm.com., the + following model/BIOS release numbers incorporate the fix. - - - - - Model - BIOS revision - - - - - - T20 - IYET49WW or later - + + + + + Model + BIOS revision + + + + + + T20 + IYET49WW or later + - - T21 - KZET22WW or later - + + T21 + KZET22WW or later + - - A20p - IVET62WW or later - + + A20p + IVET62WW or later + - - A20m - IWET54WW or later - + + A20m + IWET54WW or later + - - A21p - KYET27WW or later - + + A21p + KYET27WW or later + - - A21m - KXET24WW or later - + + A21m + KXET24WW or later + - - A21e - KUET30WW - - - - + + A21e + KUET30WW + + + + - If you have an earlier BIOS, and upgrading is not an option a - workaround is to install FreeBSD, change the partition ID FreeBSD - uses, and install new boot blocks that can handle the different - partition ID. + If you have an earlier BIOS, and upgrading is not an option a + workaround is to install FreeBSD, change the partition ID FreeBSD + uses, and install new boot blocks that can handle the different + partition ID. - First, you'll need to to restore the machine to a state where - it can get through its self-test screen. Doing this requires - powering up the machine without letting it find a FreeBSD - partition on its primary disk. One way is to remove the hard disk - and temporarily move it to an older ThinkPad (such as a ThinkPad - 600) or a desktop PC with an appropriate conversion cable. Once - it's there, you can delete the FreeBSD partition and move the hard - disk back. The ThinkPad should now be in a bootable state - again. + First, you'll need to to restore the machine to a state where + it can get through its self-test screen. Doing this requires + powering up the machine without letting it find a FreeBSD + partition on its primary disk. One way is to remove the hard disk + and temporarily move it to an older ThinkPad (such as a ThinkPad + 600) or a desktop PC with an appropriate conversion cable. Once + it's there, you can delete the FreeBSD partition and move the hard + disk back. The ThinkPad should now be in a bootable state + again. - With the machine functional again, you can use the workaround - procedure described here to get a working FreeBSD - installation. + With the machine functional again, you can use the workaround + procedure described here to get a working FreeBSD + installation. - - - Download boot1 and - boot2 from + + Download boot1 and + boot2 from http://people.freebsd.org/~bmah/ThinkPad/. - Put these files somewhere you will be able to retrieve them - later. - + Put these files somewhere you will be able to retrieve them + later. + - - Install FreeBSD as normal on to the ThinkPad. - Do not use Dangerously - Dedicated mode. Do not - reboot when the install has finished. - + + Install FreeBSD as normal on to the ThinkPad. + Do not use Dangerously + Dedicated mode. Do not + reboot when the install has finished. + - - Either switch to the Emergency Holographic - Shell (ALT - F4) or start a - fixit shell. - + + Either switch to the Emergency Holographic + Shell (ALT + F4) or start a + fixit shell. + - - Use &man.fdisk.8; to change the FreeBSD partition ID from - 165 to 166 (this is the - type used by OpenBSD). - + + Use &man.fdisk.8; to change the FreeBSD partition ID from + 165 to 166 (this is the + type used by OpenBSD). + - - Bring the boot1 and - boot2 files to the local - filesystem. - + + Bring the boot1 and + boot2 files to the local + filesystem. + - - Use &man.disklabel.8; to write boot1 - and boot2 to your FreeBSD slice. + + Use &man.disklabel.8; to write boot1 + and boot2 to your FreeBSD slice. - &prompt.root; disklabel -B -b boot1 -s boot2 ad0sn + &prompt.root; disklabel -B -b boot1 -s boot2 ad0sn - n is the number of the slice - where you installed FreeBSD. - + n is the number of the slice + where you installed FreeBSD. + - - Reboot. At the boot prompt you will be given the option - of booting OpenBSD. This will actually - boot FreeBSD. - - + + Reboot. At the boot prompt you will be given the option + of booting OpenBSD. This will actually + boot FreeBSD. + + - Getting this to work in the case where you want to dual boot - OpenBSD and FreeBSD on the same laptop is left as an exercise for - the reader. - + Getting this to work in the case where you want to dual boot + OpenBSD and FreeBSD on the same laptop is left as an exercise for + the reader. + @@ -1879,13 +1880,13 @@ BUSY - - By the geometry of a disk, we mean the - number of cylinders, heads and sectors/track on a disk - I'll - refer to this as C/H/S for convenience. This is how the PC's - BIOS works out which area on a disk to read/write from. - - + + By the geometry of a disk, we mean the + number of cylinders, heads and sectors/track on a disk - I'll + refer to this as C/H/S for convenience. This is how the PC's + BIOS works out which area on a disk to read/write from. + + This seems to cause a lot of confusion for some reason. First of all, the physical geometry of a @@ -2373,7 +2374,7 @@ Filesystem 1024-blocks Used Avail Capacity Mounted on 1+0 records out 1 bytes transferred in 0.000187 secs (5346 bytes/sec) -rw-r--r-- 1 bde bin 8796093022207 Sep 7 16:04 z -32 z +32 z Filesystem 1024-blocks Used Avail Capacity Mounted on /dev/da0a 64479 27734 31587 47% / @@ -4226,7 +4227,7 @@ IO range check 0x00 activate 0x01 I get the error nlist failed when - running, for example, top or + running, for example, top or systat. @@ -4238,13 +4239,13 @@ IO range check 0x00 activate 0x01 Your kernel and userland are not synchronized (i.e., you - built a new kernel but did not do an - installworld, or vice versa), and - thus the symbol table is different from what the user - application thinks it is. If this is the case, simply - complete the upgrade process (see - /usr/src/UPDATING for the correct - sequence). + built a new kernel but did not do an + installworld, or vice versa), and + thus the symbol table is different from what the user + application thinks it is. If this is the case, simply + complete the upgrade process (see + /usr/src/UPDATING for the correct + sequence). @@ -5013,7 +5014,7 @@ device sio5 at isa? port 0x2b8 tty flags 0x501 vector siointr Every kernel I try to build fails to compile; even GENERIC. - + There are a number of possible causes for this problem. They are, in no particular order: @@ -5249,19 +5250,19 @@ device sio5 at isa? port 0x2b8 tty flags 0x501 vector siointr If this is what you did, the extra crontab is simply a copy of /etc/crontab in the wrong format it. Delete it with the command: - - &prompt.root; crontab -r - Next time, when you edit - /etc/crontab, you should not do - anything to inform &man.cron.8; of the changes, since it - will notice them automatically. + &prompt.root; crontab -r + + Next time, when you edit + /etc/crontab, you should not do + anything to inform &man.cron.8; of the changes, since it + will notice them automatically. - If you want something to be run once per day, week, or - month, it's probably better to add shell scripts - /usr/local/etc/periodic, and let the - &man.periodic.8; command run from the system cron schedule - it with the other periodic system tasks. + If you want something to be run once per day, week, or + month, it's probably better to add shell scripts + /usr/local/etc/periodic, and let the + &man.periodic.8; command run from the system cron schedule + it with the other periodic system tasks. The actual reason for the error is that the system crontab has an extra field, specifying which user to run the @@ -5278,7 +5279,7 @@ device sio5 at isa? port 0x2b8 tty flags 0x501 vector siointr I made a mistake in rc.conf, - or another startup file, and + or another startup file, and now I can't edit it because the filesystem is read-only. What should I do? @@ -5884,16 +5885,16 @@ C:\="DOS" I get messages like: unknown: <PNP0303> can't - assign resources on boot + assign resources on boot These indicate Plug-and-Play devices that the current - kernel doesn't have drivers for. They're harmless. + kernel doesn't have drivers for. They're harmless. - If you dislike these messages, the FreeBSD Project - will happily accept driver contributions via send-pr. - + If you dislike these messages, the FreeBSD Project + will happily accept driver contributions via send-pr. + @@ -5913,34 +5914,34 @@ C:\="DOS" Put the quota file on the file system that the quotas are to be enforced on. ie: - - - - - Filesystem - Quota file - - + + + + + Filesystem + Quota file + + - - - /usr - /usr/admin/quotas - + + + /usr + /usr/admin/quotas + - - /home - /home/admin/quotas - + + /home + /home/admin/quotas + - - … - … - - - - - + + … + … + + + + + @@ -6384,8 +6385,8 @@ define(`confDELIVERY_MODE',`deferred')dnl &prompt.root; ./install.sh Alternately, you can remove all "MAKE_KERBEROS" - options from /etc/make.conf and rebuild - world. + options from /etc/make.conf and rebuild + world. @@ -6604,12 +6605,12 @@ define(`confDELIVERY_MODE',`deferred')dnl &prompt.root; chmod 640 /dev/cd0c - - Finally, add the line - vfs.usermount=1 to the file - /etc/sysctl.conf so that it is reset - at system boot time. - + + Finally, add the line + vfs.usermount=1 to the file + /etc/sysctl.conf so that it is reset + at system boot time. + All users can now mount the floppy @@ -6633,7 +6634,7 @@ define(`confDELIVERY_MODE',`deferred')dnl Enabling vfs.usermount, however, has negative security implications. A better way to access MSDOS formatted media is to use the mtools package in the ports collection. + URL="http://www.freebsd.org/cgi/ports.cgi?query=%5Emtools-&stype=name">mtools package in the ports collection. @@ -6776,52 +6777,52 @@ define(`confDELIVERY_MODE',`deferred')dnl I tried to install a new kernel, and the chflags failed. - How do I get around this? + How do I get around this? Short answer: You're probably at security level - greater than 0. Reboot directly to single user mode to - install the kernel. + greater than 0. Reboot directly to single user mode to + install the kernel. Long answer: FreeBSD disallows changing system flags - at security levels greater than 0. You can check your - security level with the command: + at security levels greater than 0. You can check your + security level with the command: - &prompt.root; sysctl kern.securelevel + &prompt.root; sysctl kern.securelevel - You cannot lower the security level; you have to boot - to single mode to install the kernel, or change the - security in /etc/rc.conf then reboot. See - the &man.init.8; man page for details on securelevel, and - see /etc/defaults/rc.conf and the - &man.rc.conf.5; man page for more information on rc.conf. + You cannot lower the security level; you have to boot + to single mode to install the kernel, or change the + security in /etc/rc.conf then reboot. See + the &man.init.8; man page for details on securelevel, and + see /etc/defaults/rc.conf and the + &man.rc.conf.5; man page for more information on rc.conf. I can't change the time on my system by more than one second! - How do I get around this? + How do I get around this? Short answer: You're probably at security level - greater than 1. Reboot directly to single user mode to - change the date. + greater than 1. Reboot directly to single user mode to + change the date. Long answer: FreeBSD disallows changing the time by more that one second at security levels greater than 1. You can check your security level with the command: - &prompt.root; sysctl kern.securelevel + &prompt.root; sysctl kern.securelevel - You cannot lower the security level; you have to boot - to single mode to change the date, or change the security - level in /etc/rc.conf then reboot. See - the &man.init.8; man page for details on securelevel, and - see /etc/defaults/rc.conf and the - &man.rc.conf.5; man page for more information on rc.conf. + You cannot lower the security level; you have to boot + to single mode to change the date, or change the security + level in /etc/rc.conf then reboot. See + the &man.init.8; man page for details on securelevel, and + see /etc/defaults/rc.conf and the + &man.rc.conf.5; man page for more information on rc.conf. @@ -6880,24 +6881,24 @@ define(`confDELIVERY_MODE',`deferred')dnl I tried to run X, but I get an - KDENABIO failed (Operation not permitted) - error when I type startx. What do I do - now? + KDENABIO failed (Operation not permitted) + error when I type startx. What do I do + now? Your system is running at a raised securelevel, isn't - it? It is, indeed, impossible to start X at a raised - securelevel. To see why, look at the &man.init.8; man - page. - + it? It is, indeed, impossible to start X at a raised + securelevel. To see why, look at the &man.init.8; man + page. + So the question is what else you should do instead, and you basically have two choices: set your securelevel back down to zero (usually from /etc/rc.conf), or run &man.xdm.1; at boot time (before the securelevel is raised). - See for more information about + See for more information about running &man.xdm.1; at boot time. @@ -7226,7 +7227,7 @@ ttyvb "/usr/libexec/getty Pc" cons25 on secure want to change the secure to insecure. - + If you want to run an X server you must leave at least one virtual @@ -7236,8 +7237,8 @@ ttyvb "/usr/libexec/getty Pc" cons25 on secure 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 @@ -7287,34 +7288,34 @@ ttyvb "/usr/libexec/getty Pc" cons25 off secure How do I access the virtual consoles from X? - - Use - Ctrl - Alt - Fn - to switch back to a virtual console. - - Ctrl - Alt - F1 - would return you to the first virtual console. + + Use + Ctrl + Alt + Fn + to switch back to a virtual console. + + Ctrl + Alt + F1 + would return you to the first virtual console. - Once you are back to a text console, you can then use - - Alt - Fn - as normal to move between them. - - To return to the X session, you must switch to the virtual - console running X. If you invoked X from the command line, (e.g., - using startx) then the X session will attach to - the next unused virtual console, not the text console from which - it was invoked. If you have eight active virtual terminals then X - will be running on the ninth, and you would use - - Alt - F9 - to return. + Once you are back to a text console, you can then use + + Alt + Fn + as normal to move between them. + + To return to the X session, you must switch to the virtual + console running X. If you invoked X from the command line, (e.g., + using startx) then the X session will attach to + the next unused virtual console, not the text console from which + it was invoked. If you have eight active virtual terminals then X + will be running on the ninth, and you would use + + Alt + F9 + to return. @@ -7536,8 +7537,8 @@ UserConfig> quit + set_mouse_resolution(sc->kbdc, PSMD_RES_HIGH); + #if 0 - set_mouse_scaling(sc->kbdc); /* 1:1 scaling */ - set_mouse_mode(sc->kbdc); /* stream mode */ + set_mouse_scaling(sc->kbdc); /* 1:1 scaling */ + set_mouse_mode(sc->kbdc); /* stream mode */ In versions 2.2.6 or later, specify the flags 0x04 to the PS/2 mouse driver to put the mouse into the high @@ -8061,15 +8062,15 @@ Key F15 A A Menu Workplace Nop passage from the &man.exports.5 manual page correctly: -
- Each line in the file (other than comment - lines that begin with a #) specifies the mount point(s) - and export flags within one local server filesystem for - one or more hosts. A host may be specified only once - for each local filesystem on the server and there may be - only one default entry for each server filesystem that - applies to all other hosts. -
+
+ Each line in the file (other than comment + lines that begin with a #) specifies the mount point(s) + and export flags within one local server filesystem for + one or more hosts. A host may be specified only once + for each local filesystem on the server and there may be + only one default entry for each server filesystem that + applies to all other hosts. +
This is made more clear by an example of a common mistake. If everything above /usr is @@ -8402,7 +8403,7 @@ Znyx (2.2.x) ZX312, ZX314, ZX342, ZX345, ZX346, ZX348 utilize it. Add this to your kernel config file and build a new kernel: - pseudo-device bpfilter # Berkeley Packet Filter + pseudo-device bpfilter # Berkeley Packet Filter Secondly, after rebooting you will have to create the device node. This can be accomplished by a change to the @@ -8523,7 +8524,7 @@ Znyx (2.2.x) ZX312, ZX314, ZX342, ZX345, ZX346, ZX348 /etc/syslog.conf contains the lines !ppp -*.* /var/log/ppp.log +*.* /var/log/ppp.log and that the file /var/log/ppp.log exists. You can now find out a lot about what's going on @@ -9570,8 +9571,8 @@ ATDT1234567 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 + sending the ICMP packet correctly, but the firewall at the www + site is dropping it.) When the www server is sending you frames that don't fit into the PPPoE pipe the Telco router drops them on the floor and your page doesn't load (some pages/graphics do as they are smaller than a MSS.) This seems @@ -9590,13 +9591,13 @@ ATDT1234567 packets into a PPPoE frame perfectly but the 1450 gives you a margin of error for other IP protocols you may encounter). This registry key is reported to - have moved to - Tcpip\Parameters\Interfaces\ID for adapter\MTU - in Windows 2000. + have moved to + Tcpip\Parameters\Interfaces\ID for adapter\MTU + in Windows 2000. Refer to Microsoft Knowledge - Base documents Q158474 - Windows TCPIP Registry + URL="http://search.support.microsoft.com/kb">Microsoft Knowledge + Base documents Q158474 - Windows TCPIP Registry Entries and Q120642 - TCPIP & NBT Configuration Parameters for Windows NT for more information on changing Windoze MTU to work with a FreeBSD/NAT/PPPoE @@ -10098,9 +10099,9 @@ device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointr file. For example: tip115200|Dial any phone number at 115200 bps:\ - :dv=/dev/cuaa0:br#115200:at=hayes:pa=none:du: + :dv=/dev/cuaa0:br#115200:at=hayes:pa=none:du: tip57600|Dial any phone number at 57600 bps:\ - :dv=/dev/cuaa0:br#57600:at=hayes:pa=none:du: + :dv=/dev/cuaa0:br#57600:at=hayes:pa=none:du: Then you can do something like tip -115200 5551234. If you prefer : pain|pain.deep13.com|Forrester's machine:\ - :cm=CONNECT pain\n:tc=deep13: + :cm=CONNECT pain\n:tc=deep13: muffin|muffin.deep13.com|Frank's machine:\ - :cm=CONNECT muffin\n:tc=deep13: + :cm=CONNECT muffin\n:tc=deep13: deep13:Gizmonics Institute terminal server:\ - :dv=/dev/cuaa2:br#38400:at=hayes:du:pa=none:pn=5551234: + :dv=/dev/cuaa2:br#38400:at=hayes:du:pa=none:pn=5551234: will let you type tip pain or tip muffin to connect to the hosts @@ -10179,9 +10180,9 @@ deep13:Gizmonics Institute terminal server:\ the pn capability: big-university:\ - :pn=\@:tc=dialout + :pn=\@:tc=dialout dialout:\ - :dv=/dev/cuaa3:br#9600:at=courier:du:pa=none: + :dv=/dev/cuaa3:br#9600:at=courier:du:pa=none: Then, list the phone numbers for the university in @@ -11388,8 +11389,8 @@ ${RELEASEDIR}/tarballs/bindist/bin_tgz.) mailing list if you are interested in joining that project. Most recent additions to the list of upcoming plaforms are IA-64 and PowerPC, join the - freebsd-ia64@FreeBSD.org or/and - freebsd-ppc@FreeBSD.org freebsd-ia64@FreeBSD.org or/and + freebsd-ppc@FreeBSD.org mailing lists for more information. For general discussion on new architectures, join the freebsd-platforms@FreeBSD.org