From owner-svn-doc-all@FreeBSD.ORG Sun Nov 4 22:40:54 2012 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8B385BC0; Sun, 4 Nov 2012 22:40:54 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 6AD928FC0A; Sun, 4 Nov 2012 22:40:54 +0000 (UTC) Received: from svn.freebsd.org (localhost [127.0.0.1]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id qA4MesGm070202; Sun, 4 Nov 2012 22:40:54 GMT (envelope-from gjb@svn.freebsd.org) Received: (from gjb@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id qA4MesWE070189; Sun, 4 Nov 2012 22:40:54 GMT (envelope-from gjb@svn.freebsd.org) Message-Id: <201211042240.qA4MesWE070189@svn.freebsd.org> From: Glen Barber Date: Sun, 4 Nov 2012 22:40:54 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-translations@freebsd.org Subject: svn commit: r39940 - in translations/en_US.ISO8859-1: articles/committers-guide articles/contributing articles/contributing-ports articles/contributors articles/java-tomcat articles/linux-users art... X-SVN-Group: doc-translations MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Nov 2012 22:40:54 -0000 Author: gjb Date: Sun Nov 4 22:40:53 2012 New Revision: 39940 URL: http://svnweb.freebsd.org/changeset/doc/39940 Log: Merge r39770 through r39936 from head/ into translations/ Added: translations/en_US.ISO8859-1/books/handbook/jails/Makefile - copied unchanged from r39936, head/en_US.ISO8859-1/books/handbook/jails/Makefile Deleted: translations/en_US.ISO8859-1/articles/java-tomcat/ translations/en_US.ISO8859-1/articles/programming-tools/ translations/en_US.ISO8859-1/articles/smp/ translations/en_US.ISO8859-1/books/developers-handbook/boot/ translations/en_US.ISO8859-1/books/developers-handbook/dma/ translations/en_US.ISO8859-1/books/developers-handbook/driverbasics/ translations/en_US.ISO8859-1/books/developers-handbook/isa/ translations/en_US.ISO8859-1/books/developers-handbook/jail/ translations/en_US.ISO8859-1/books/developers-handbook/kobj/ translations/en_US.ISO8859-1/books/developers-handbook/locking/ translations/en_US.ISO8859-1/books/developers-handbook/mac/ translations/en_US.ISO8859-1/books/developers-handbook/newbus/ translations/en_US.ISO8859-1/books/developers-handbook/pccard/ translations/en_US.ISO8859-1/books/developers-handbook/pci/ translations/en_US.ISO8859-1/books/developers-handbook/scsi/ translations/en_US.ISO8859-1/books/developers-handbook/sound/ translations/en_US.ISO8859-1/books/developers-handbook/sysinit/ translations/en_US.ISO8859-1/books/developers-handbook/usb/ translations/en_US.ISO8859-1/books/developers-handbook/vm/ translations/en_US.ISO8859-1/books/ppp-primer/ translations/en_US.ISO8859-1/htdocs/alpha/ translations/en_US.ISO8859-1/htdocs/conspectus/ translations/en_US.ISO8859-1/htdocs/gallery/ translations/en_US.ISO8859-1/htdocs/gnome/images/team/ translations/en_US.ISO8859-1/htdocs/gnome/patches/ translations/en_US.ISO8859-1/htdocs/platforms/amd64/ translations/en_US.ISO8859-1/htdocs/projects/dingo/ translations/en_US.ISO8859-1/htdocs/projects/nanobsd/ translations/en_US.ISO8859-1/htdocs/releases/2.0.5A/ translations/en_US.ISO8859-1/htdocs/releases/2.0A/ translations/en_US.ISO8859-1/htdocs/releases/4.6.1R/ translations/en_US.ISO8859-1/share/images/ Modified: translations/en_US.ISO8859-1/articles/committers-guide/article.xml translations/en_US.ISO8859-1/articles/contributing-ports/article.xml translations/en_US.ISO8859-1/articles/contributing/article.xml translations/en_US.ISO8859-1/articles/contributors/contrib.additional.xml translations/en_US.ISO8859-1/articles/contributors/contrib.committers.xml translations/en_US.ISO8859-1/articles/contributors/contrib.portmgralumni.xml translations/en_US.ISO8859-1/articles/linux-users/article.xml translations/en_US.ISO8859-1/articles/portbuild/article.xml translations/en_US.ISO8859-1/articles/rc-scripting/article.xml translations/en_US.ISO8859-1/books/dev-model/book.xml translations/en_US.ISO8859-1/books/faq/book.xml translations/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml translations/en_US.ISO8859-1/books/handbook/audit/chapter.xml translations/en_US.ISO8859-1/books/handbook/basics/chapter.xml translations/en_US.ISO8859-1/books/handbook/boot/chapter.xml translations/en_US.ISO8859-1/books/handbook/bsdinstall/chapter.xml translations/en_US.ISO8859-1/books/handbook/colophon.xml translations/en_US.ISO8859-1/books/handbook/config/chapter.xml translations/en_US.ISO8859-1/books/handbook/desktop/chapter.xml translations/en_US.ISO8859-1/books/handbook/disks/chapter.xml translations/en_US.ISO8859-1/books/handbook/dtrace/chapter.xml translations/en_US.ISO8859-1/books/handbook/geom/chapter.xml translations/en_US.ISO8859-1/books/porters-handbook/book.xml translations/en_US.ISO8859-1/htdocs/administration.xml translations/en_US.ISO8859-1/htdocs/cgi/man.cgi translations/en_US.ISO8859-1/htdocs/internal/Makefile translations/en_US.ISO8859-1/htdocs/multimedia/multimedia-input.xml translations/en_US.ISO8859-1/htdocs/privacy.xml translations/en_US.ISO8859-1/htdocs/releases/9.1R/schedule.xml translations/en_US.ISO8859-1/share/xml/release.l10n.ent Directory Properties: translations/en_US.ISO8859-1/ (props changed) Modified: translations/en_US.ISO8859-1/articles/committers-guide/article.xml ============================================================================== --- translations/en_US.ISO8859-1/articles/committers-guide/article.xml Sun Nov 4 22:17:58 2012 (r39939) +++ translations/en_US.ISO8859-1/articles/committers-guide/article.xml Sun Nov 4 22:40:53 2012 (r39940) @@ -2189,8 +2189,8 @@ U stable/9/share/man/man4/netmap.4 - (For committers only:) - If you subscribe to &a.svn-src-all.name; or the &a.cvsall;, + If you subscribe to &a.svn-src-all.name;, + &a.svn-ports-all.name; or &a.svn-doc-all.name;, you will probably want to unsubscribe to avoid receiving duplicate copies of commit messages and their followups. Modified: translations/en_US.ISO8859-1/articles/contributing-ports/article.xml ============================================================================== --- translations/en_US.ISO8859-1/articles/contributing-ports/article.xml Sun Nov 4 22:17:58 2012 (r39939) +++ translations/en_US.ISO8859-1/articles/contributing-ports/article.xml Sun Nov 4 22:40:53 2012 (r39940) @@ -465,7 +465,7 @@ Regularly check the automated ports building cluster, pointyhat, - and the distfiles + and the distfiles scanner to see if any of the ports you maintain are failing to build or fetch (see resources for more @@ -797,7 +797,7 @@ build status of your ports. As a contributor you can use it to find broken and unmaintained ports that need to be fixed. - The FreeBSD Ports + The FreeBSD Ports distfile scanner can show you ports for which the distfiles are not fetchable. You can check on your own ports or use it to find ports that need their Modified: translations/en_US.ISO8859-1/articles/contributing/article.xml ============================================================================== --- translations/en_US.ISO8859-1/articles/contributing/article.xml Sun Nov 4 22:17:58 2012 (r39939) +++ translations/en_US.ISO8859-1/articles/contributing/article.xml Sun Nov 4 22:40:53 2012 (r39940) @@ -88,7 +88,7 @@ Read through the FAQ and Handbook periodically. If anything is badly explained, out of date or even just completely wrong, let us know. Even better, send us a fix - (SGML is not difficult to learn, but there is no objection + (Docbook is not difficult to learn, but there is no objection to ASCII submissions). @@ -565,16 +565,6 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE PO Donations Liaison Office. - - - Donating Internet Access - - We can always use new mirror sites for FTP, WWW or - cvsup. If you would like to be such a - mirror, please see the - Mirroring - FreeBSD article for more information. - Modified: translations/en_US.ISO8859-1/articles/contributors/contrib.additional.xml ============================================================================== --- translations/en_US.ISO8859-1/articles/contributors/contrib.additional.xml Sun Nov 4 22:17:58 2012 (r39939) +++ translations/en_US.ISO8859-1/articles/contributors/contrib.additional.xml Sun Nov 4 22:40:53 2012 (r39940) @@ -3595,11 +3595,6 @@ - Grzegorz Blach - magik@roorback.net - - - Guillaume Paquet amyfoub@videotron.ca @@ -4433,6 +4428,11 @@ + Jean Benoit + jean@unistra.fr + + + Jean-Sebastien Roy js@jeannot.org @@ -6018,6 +6018,11 @@ + Manuel Creach + manuel.creach@me.com + + + Manuel Rabade Garcia mig@mig-29.net @@ -8325,6 +8330,11 @@ + Pierre David + pdagog@gmail.com + + + Pierre Y. Dampure pierre.dampure@k2c.co.uk @@ -9347,11 +9357,6 @@ - Simon J Gerraty - sjg@juniper.net - - - Simon Lang simon@lang-clan.de Modified: translations/en_US.ISO8859-1/articles/contributors/contrib.committers.xml ============================================================================== --- translations/en_US.ISO8859-1/articles/contributors/contrib.committers.xml Sun Nov 4 22:17:58 2012 (r39939) +++ translations/en_US.ISO8859-1/articles/contributors/contrib.committers.xml Sun Nov 4 22:40:53 2012 (r39940) @@ -116,6 +116,10 @@ + &a.gblach; + + + &a.mbr; @@ -448,6 +452,10 @@ + &a.sjg; + + + &a.gibbs; Modified: translations/en_US.ISO8859-1/articles/contributors/contrib.portmgralumni.xml ============================================================================== --- translations/en_US.ISO8859-1/articles/contributors/contrib.portmgralumni.xml Sun Nov 4 22:17:58 2012 (r39939) +++ translations/en_US.ISO8859-1/articles/contributors/contrib.portmgralumni.xml Sun Nov 4 22:40:53 2012 (r39940) @@ -3,6 +3,10 @@ + &a.pav; (2006 - 2012) + + + &a.flz; (2008 - 2012) Modified: translations/en_US.ISO8859-1/articles/linux-users/article.xml ============================================================================== --- translations/en_US.ISO8859-1/articles/linux-users/article.xml Sun Nov 4 22:17:58 2012 (r39939) +++ translations/en_US.ISO8859-1/articles/linux-users/article.xml Sun Nov 4 22:40:53 2012 (r39940) @@ -407,7 +407,7 @@ ifconfig_em0="DHCP" Updating from source is the most involved update method, but offers the greatest amount of flexibility. The process involves synchronizing a local copy of the FreeBSD source code with the &os; - CVS (Concurrent Versioning System) servers. + Subversion servers. Once the local source code is up to date you can build new versions of the kernel and userland. For more information on source updates see the chapter on updating Modified: translations/en_US.ISO8859-1/articles/portbuild/article.xml ============================================================================== --- translations/en_US.ISO8859-1/articles/portbuild/article.xml Sun Nov 4 22:17:58 2012 (r39939) +++ translations/en_US.ISO8859-1/articles/portbuild/article.xml Sun Nov 4 22:40:53 2012 (r39940) @@ -703,7 +703,7 @@ PKG_BIN=/usr/local/sbin/pkg dopackages.wrapper sparc64 7 -finish - Hint: it us usually best to run the dopackages + Hint: it is usually best to run the dopackages command inside of screen(1). Modified: translations/en_US.ISO8859-1/articles/rc-scripting/article.xml ============================================================================== --- translations/en_US.ISO8859-1/articles/rc-scripting/article.xml Sun Nov 4 22:17:58 2012 (r39939) +++ translations/en_US.ISO8859-1/articles/rc-scripting/article.xml Sun Nov 4 22:40:53 2012 (r39940) @@ -400,8 +400,8 @@ start_cmd="${name}_start" stop_cmd=":" load_rc_config $name -eval "${rcvar}=\${${rcvar}:-'NO'}" -dummy_msg=${dummy_msg:-"Nothing started."} +: ${dummy_enable:=no} +: ${dummy_msg="Nothing started."} dummy_start() { @@ -448,7 +448,7 @@ run_rc_command "$1" system, you should add a default setting for the knob to /etc/defaults/rc.conf and document it in &man.rc.conf.5;. Otherwise it is your script that - should provide a default setting for the knob. A portable + should provide a default setting for the knob. The canonical approach to the latter case is shown in the example. @@ -479,7 +479,7 @@ run_rc_command "$1" The names of all &man.rc.conf.5; variables used exclusively by our script must - have the same prefix: ${name}. For + have the same prefix: ${name}_. For example: dummy_mode, dummy_state_file, and so on. @@ -487,19 +487,10 @@ run_rc_command "$1" While it is possible to use a shorter name internally, e.g., just msg, adding the unique prefix - ${name} to all global names introduced by + ${name}_ to all global names introduced by our script will save us from possible collisions with the &man.rc.subr.8; namespace. - As long as an &man.rc.conf.5; variable and its - internal equivalent are the same, we can use a more - compact expression to set the default value: - - : ${dummy_msg:="Nothing started."} - - The current style is to use the more verbose form - though. - As a rule, rc.d scripts of the base system need not provide defaults for their &man.rc.conf.5; variables because the defaults should @@ -512,7 +503,11 @@ run_rc_command "$1" Here we use dummy_msg to actually - control our script, i.e., to emit a variable message. + control our script, i.e., to emit a variable message. + Use of a shell function is overkill here, since it only + runs a single command; an equally valid alternative is: + + start_cmd="echo \"$dummy_msg\"" Modified: translations/en_US.ISO8859-1/books/dev-model/book.xml ============================================================================== --- translations/en_US.ISO8859-1/books/dev-model/book.xml Sun Nov 4 22:17:58 2012 (r39939) +++ translations/en_US.ISO8859-1/books/dev-model/book.xml Sun Nov 4 22:40:53 2012 (r39940) @@ -46,7 +46,13 @@ 2002-2005 Niklas Saers - + + + 1.3 + October, 2012 + Remove hats held by specific people, these + are documented elsewhere. + 1.2 April, 2005 @@ -884,8 +890,6 @@ - - Hat held by: The DocEng team doceng@FreeBSD.org. The @@ -959,8 +963,6 @@ Hat held by: the Release Engineering team re@FreeBSD.org. - The current Release Engineer is - Ken Smith kensmith@FreeBSD.org. The Release Engineering Charter. @@ -1018,16 +1020,6 @@ Officer Team security-team@FreeBSD.org to help do the work. - - Hat held by: - the Security Officer security-officer@FreeBSD.org, - currently headed by - Colin Percival cperciva@FreeBSD.org. - The - - Security Officer and The Security Officer Team's - charter. -
@@ -1044,8 +1036,7 @@ Hat held by: - the Source Repository Manager cvs@FreeBSD.org, - currently headed by Peter Wemm peter@FreeBSD.org. + the Source Repository Manager cvs@FreeBSD.org.
@@ -1171,10 +1162,7 @@ Hat held by: - the Donations Liaison Office donations@FreeBSD.org, - currently headed by - Michael W. Lucas mwlucas@FreeBSD.org. - + the Donations Liaison Office donations@FreeBSD.org. Modified: translations/en_US.ISO8859-1/books/faq/book.xml ============================================================================== --- translations/en_US.ISO8859-1/books/faq/book.xml Sun Nov 4 22:17:58 2012 (r39939) +++ translations/en_US.ISO8859-1/books/faq/book.xml Sun Nov 4 22:40:53 2012 (r39940) @@ -59,7 +59,6 @@ &tm-attrib.freebsd; - &tm-attrib.3com; &tm-attrib.adobe; &tm-attrib.creative; &tm-attrib.ibm; @@ -1165,44 +1164,83 @@ Installation + + + + Which platform should I download? I have a 64 + bit capable &intel; CPU, + but I only see amd64. + + + + &arch.amd64; is the term &os; uses for 64-bit + compatible x86 architectures. Most modern computers + should use &arch.amd64;. Older hardware should use + &arch.i386;. If you are installing on a + non-x86-compatible architecture select the platform + which best matches the architecture you are + using. + + + 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;. + On the + Get &os; page + select [iso] next to the + architecture you want to use. - If you need to download the distributions yourself (for - a DOS file system install, for instance), below are some - recommendations for distributions to grab: + Any of the following can be used: - - - base/ - + + + + + file + description + + - - manpages/ - + + + disc1.iso + Contains enough to install &os; and + a minimal set of packages. + - - compat*/ - + + dvd1.iso + Similar to disc1.iso + but with addtional packages. + - - doc/ - + + memstick.iso + A bootable image sufficient for copying to a + USB stick. + - - src/ssys.* - - + + bootonly.iso + A minimal image that requires network + access during installation to completely + install &os;. + + + + + + &arch.pc98; users require three floppy images: + floppies/boot.flp, + floppies/kern1.flp, and + floppies/kern2.flp. These images + need + to be copied onto floppies by tools like + &man.dd.1;. Full instructions on this procedure and a little bit more about installation issues in general can be found in @@ -1214,21 +1252,17 @@ - What do I do if the floppy images does not fit on a - single floppy? + What do I do if the images do not fit on a + single disk? - 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 + Common mistakes when preparing the boot media are: - Not downloading the floppy image in + Not downloading the image in binary mode when using FTP. @@ -1236,7 +1270,8 @@ 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 + invariably corrupt the boot image. Check the SHA-256 + of the downloaded boot image: if it is not exactly that on the server, then the download process is suspect. @@ -1258,7 +1293,7 @@ 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 + tools (e.g., fdimage or rawrite) described in the installation guide to &os;. @@ -1313,7 +1348,8 @@ - Install &windows; first, then &os;. &os;'s boot manager + If &windows; is installed first, then yes. + &os;'s boot manager will then manage to boot &windows; and &os;. If you install &windows; second, it will boorishly overwrite your boot manager without even asking. If that happens, see the next @@ -1351,7 +1387,7 @@ Partition. Select the drive which used to contain your boot manager (likely the first one) and when you come to the partition editor for - it, as the very first thing (e.g. do not make any + it, as the very first thing (e.g., do not make any changes) press W. This will ask for confirmation, select &gui.yes;, and when you get the Boot Manager selection prompt, be sure to select the @@ -1383,166 +1419,6 @@ - - My A, T, or X series IBM Thinkpad locks up when I first - booted up my &os; installation. How can I solve - this? - - - - A bug in early revisions of IBM's BIOS on these machines - mistakenly identifies the &os; partition as a potential FAT - suspend-to-disk partition. When the BIOS tries to parse the - &os; partition it hangs. - - According to IBM - In an email from Keith Frechette - kfrechet@us.ibm.com., - the following model/BIOS release numbers incorporate the - fix. - - - - - - Model - - BIOS revision - - - - - - T20 - - IYET49WW or later - - - - T21 - - KZET22WW or later - - - - A20p - - IVET62WW or later - - - - A20m - - IWET54WW or later - - - - A21p - - KYET27WW or later - - - - A21m - - KXET24WW or later - - - - A21e - - KUET30WW - - - - - - It has been reported that later IBM BIOS revisions may - have reintroduced the bug. This message - from &a.nectar; to the &a.mobile; describes a procedure - which may work if your newer IBM laptop does not boot &os; - properly, and you can upgrade or downgrade the BIOS. - - If you have an earlier BIOS, and upgrading is not an - option, a workaround is to install &os;, change the partition - ID &os; uses, and install new boot blocks that can handle - the different partition ID. - - First, you will need 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 - &os; 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 is there, you can delete the &os; - 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 &os; - installation. - - - - Download boot1 and - boot2 from . - Put these files somewhere you will be able to retrieve - them later. - - - - Install &os; 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 (AltF4) - or start a fixit shell. - - - - Use &man.fdisk.8; to change the &os; partition ID - from 165 to 166 - (this is the type used by OpenBSD). - - - - Bring the boot1 and - boot2 files to the local file - system. - - - - Use &man.disklabel.8; to write - boot1 and boot2 - to your &os; slice. - - &prompt.root; disklabel -B -b boot1 -s boot2 ad0sn - - n is the number of the - slice where you installed &os;. - - - - Reboot. At the boot prompt you will be given the - option of booting OpenBSD. This will - actually boot &os;. - - - - Getting this to work in the case where you want to dual - boot OpenBSD and &os; on the same laptop is left as an - exercise for the reader. - - - - Can I install on a disk with bad blocks? @@ -2063,6 +1939,21 @@ shows up before loader is started. + + + + Is there a tool to perform post-installation + configuration tasks? + + + + Yes, &rel.head.releng; users can set + WITH_BSDCONFIG in + /etc/src.conf. Users of &rel.relx; + and higher may also install + sysutils/bsdconfig. + + @@ -2196,8 +2087,8 @@ - Yes. &os; currently runs on the Intel x86 and the - AMD64 architectures. The Intel EM64T, IA-64, &arm;, + Yes. &os; currently runs on the &intel; x86 and the + AMD64 architectures. The &intel; EM64T, IA-64, &arm;, &powerpc;, and &sparc64; architectures are also supported. Upcoming platforms are &mips; and &s390;, join the &a.mips; for more information about ongoing work on @@ -2725,48 +2616,6 @@ bindkey ^[[3~ delete-char # for xterm

 - - - - Why does my Micron system hang at boot time? - - - - Certain Micron motherboards have a non-conforming PCI - BIOS implementation that causes grief when &os; boots - because PCI devices do not get configured at their - reported addresses. - - Disable the Plug and Play Operating - System flag in the BIOS to work around this - problem. - - - - - - The boot floppy hangs on a system with an ASUS K7V - motherboard. How do I fix this? - - - - Go into the BIOS setup and disable the boot - virus protection. - - - - - - Why does my &tm.3com; PCI network card not work with my - Micron computer? - - - - See the previous answer. - - - @@ -2927,19 +2776,6 @@ quit - - Why did my &tm.3com; 3C509 card stop working for no - apparent reason? - - - - This card has a bad habit of losing its configuration - information. Refresh your card's settings with the DOS - utility 3c5x9.exe. - - - - Why do my programs occasionally die with Signal 11 errors? @@ -3011,8 +2847,8 @@ quit on the processor might have died. In either case you need to ensure that you have hardware running at what it is specified to run at, at least while trying to solve - this problem. i.e. Clock it back to the default - settings. + this problem (in other words, clock it back to the default + settings.) If you are overclocking then note that it is far cheaper to have a slow system than a fried system that @@ -3141,36 +2977,6 @@ quit - - 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 @@ -3179,7 +2985,7 @@ quit Normally, &os; determines a number of kernel parameters, - such as as the maximum number of files that can be open + such 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 @@ -3641,7 +3447,7 @@ chip1@pci0:31:5: class=0x040100 c Break the warnings by changing the value of MAX_STRAY_LOG from 5 to 0 in your - platform's (e.g. &i386;) + platform's (e.g., &i386;) intr_machdep.c file and rebuild the new kernel and all the warnings will be suppressed. @@ -3984,11 +3790,7 @@ kern.timecounter.hardware: TSC -> i82 url="http://www.openoffice.org">OpenOffice.org and LibreOffice - office suites work natively on &os;. The &linux; version of - Oracle Open Office, - the value-added closed-source version of OpenOffice.org, - also works on &os;. + office suites work natively on &os;. &os; also includes a variety of text editors, spreadsheets, and drawing programs in the Ports @@ -4178,9 +3980,7 @@ kern.timecounter.hardware: TSC -> i82 can be installed and uninstalled again easily without having to know the gory details of which files it includes. - Use the Packages package - installation menu in &man.sysinstall.8; (under the - Configure menu item) or invoke + Invoke the &man.pkg.add.1; command on the specific package files you are interested in installing. Package files can usually be identified by their .tbz suffix and @@ -4322,38 +4122,12 @@ kern.timecounter.hardware: TSC -> i82 - First, always make sure that you have a completely + First, always make sure that you have a complete up-to-date Ports Collection. Errors that affect building INDEX from an up-to-date copy of the Ports Collection are high-visibility and are thus almost always fixed immediately. - However, if you are up-to-date, perhaps you are seeing - another problem. make index - has a known bug in dealing with incomplete copies of the - Ports Collection. It assumes that you have a local copy of - every single port that every other port that you have a - local copy of depends on. To explain, if you have a copy of - foo/bar on your disk, and - foo/bar depends on - baz/quux, then you must also have a - copy of baz/quux on your disk, and the - ports baz/quux depends on, and so on. - Otherwise, make index - has insufficient information to create its dependency - tree. - - This is particularly a problem for &os; users who - utilize &man.csup.1; to track the Ports - Collection but choose not to install certain categories by - specifying them in refuse. In theory, - one should be able to refuse categories, but in practice - there are too many ports that depend on ports in other - categories. Until someone comes up with a solution for this - problem, the general rule is that if you want to build - INDEX, you must have a complete copy of - the Ports Collection. - There are rare cases where INDEX will not build due to odd cases involving WITH_* or @@ -4680,27 +4454,12 @@ device sio5 at isa? port 0x2b8 tty flags - Check for the existence of the - kern.sched.quantum sysctl. If you have - it, you should see something like this: - - &prompt.user; sysctl kern.sched.quantum -kern.sched.quantum: 99960 - - If the kern.sched.quantum sysctl - exists, you are using the 4BSD scheduler (&man.sched.4bsd.4;). - If not, you will get an error printed by &man.sysctl.8; - (which you can safely ignore): - - &prompt.user; sysctl kern.sched.quantum -sysctl: unknown oid 'kern.sched.quantum' - The name of the scheduler currently being used is directly available as the value of the kern.sched.name sysctl: &prompt.user; sysctl kern.sched.name -kern.sched.name: 4BSD +kern.sched.name: ULE @@ -4867,11 +4626,8 @@ kern.sched.name: 4BSD they are getting in contact with such a disk, or even worse, they might damage the BSD bootstrap without even asking or notifying you. In addition, the dangerously - dedicated disk's layout is known to confuse many - BIOSes, including those from AWARD (e.g. as found in HP - Netserver and Micronics systems as well as many others) and - Symbios/NCR (for the popular 53C8xx range of SCSI - controllers). This is not a complete list, there are more. + dedicated disk's layout is known to confuse some + BIOSes. Symptoms of this confusion include the read error message printed by the &os; bootstrap when it cannot find itself, as well as system lockups when @@ -4912,7 +4668,7 @@ kern.sched.name: 4BSD &os; lists your disks, first IDE, then SCSI. When you are slicing up your disk, check that the disk - geometry displayed in the FDISK screen is correct (ie. it + geometry displayed in the FDISK screen is correct (i.e., it matches the BIOS numbers); if it is wrong, use the G key to fix it. You may have to do this if there is absolutely nothing on the disk, or if the disk @@ -5102,11 +4858,10 @@ use "disklabel -r" to install initial la NTFS - &os; includes a read-only NTFS driver. For more - information, see &man.mount.ntfs.8;. A port of ntfs-3g - supports write operations on NTFS (see sysutils/fusefs-ntfs). + FUSE based NTFS support is available as a port + (sysutils/fusefs-ntfs). + For more information see ntfs-3g. @@ -5287,7 +5042,7 @@ C:\="DOS" following to your configuration file /boot/grub/menu.lst (or /boot/grub/grub.conf in some systems, - e.g. Red Hat Linux and its derivatives). + e.g., Red Hat Linux and its derivatives). title &os; 6.1 root (hd0,a) @@ -5523,85 +5278,39 @@ C:\="DOS" - How do I let ordinary users mount floppies, CD-ROMs and - other removable media? + How do I let ordinary users mount CD-ROMs, DVDs, + USB drives, and other removable media? - Ordinary users can be permitted to mount devices. Here - is how: - - - - As root set the sysctl variable - vfs.usermount to - 1. *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***