From owner-svn-doc-all@FreeBSD.ORG Wed May 14 14:16:01 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5819E7C0; Wed, 14 May 2014 14:16:01 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 435A82420; Wed, 14 May 2014 14:16:01 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s4EEG1kY060302; Wed, 14 May 2014 14:16:01 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s4EEG1oC060301; Wed, 14 May 2014 14:16:01 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201405141416.s4EEG1oC060301@svn.freebsd.org> From: Dru Lavigne Date: Wed, 14 May 2014 14:16:01 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r44829 - head/en_US.ISO8859-1/books/faq X-SVN-Group: doc-head 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.18 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: Wed, 14 May 2014 14:16:01 -0000 Author: dru Date: Wed May 14 14:16:00 2014 New Revision: 44829 URL: http://svnweb.freebsd.org/changeset/doc/44829 Log: Some more rewording around "you", more to come. Remove booting with NTloader and LILO entries. Sponsored by: iXsystems Modified: head/en_US.ISO8859-1/books/faq/book.xml Modified: head/en_US.ISO8859-1/books/faq/book.xml ============================================================================== --- head/en_US.ISO8859-1/books/faq/book.xml Wed May 14 13:11:28 2014 (r44828) +++ head/en_US.ISO8859-1/books/faq/book.xml Wed May 14 14:16:00 2014 (r44829) @@ -210,11 +210,10 @@ Collection. If an application is only - available on one operating system, you cannot just - replace that operating system. Chances are, there is a - very similar application on &os;, however. If you want a - solid office or Internet server, a reliable workstation, - or just the ability to do your job without interruptions, + available on one operating system, + that operating system cannot just be replaced. Chances are, there is a + very similar application on &os;, however. As a + solid office or Internet server or a reliable workstation, &os; will almost certainly do everything you need. Many computer users across the world, including both novices and experienced &unix; administrators, use &os; as their @@ -984,7 +983,7 @@ a general help channel with many users at any time. The conversations have been known to run off-topic for a while, but priority is given to users with &os; - questions. Other users can help you understand + questions. Other users can help with the basics, referring to the Handbook whenever possible and providing links for learning more about the topic you need help with. This is primarily an @@ -1714,8 +1713,8 @@ &os; supports SCSI changers using the &man.ch.4; device and the &man.chio.1; command. The details of how - you actually control the changer can be found in the - &man.chio.1; manual page. + to control the changer can be found in + &man.chio.1;. While AMANDA and some other products @@ -1749,10 +1748,8 @@ drive. See &man.burncd.8; for details. &os; also supports any SCSI CD-R or CD-RW drives. - Install and use cdrecord from the - ports or packages system, and make sure that you have - the pass device compiled in your - kernel. + Install the sysutils/cdrtools + port or package, then use cdrecord. @@ -1769,8 +1766,8 @@ - If you are using the default console driver, - &man.syscons.4;, you can use a mouse pointer in text + The default console driver, + &man.syscons.4;, provides the ability to use a mouse pointer in text consoles to cut & paste text. Run the mouse daemon, &man.moused.8;, and turn on the mouse pointer in the virtual console: @@ -1788,10 +1785,10 @@ the &man.moused.8; manual page for a list of supported protocol types. - If you have a PS/2 mouse, just add + For a PS/2 mouse, add moused_enable="YES" to /etc/rc.conf to start the mouse - daemon at boot-time. Additionally, if you would like to + daemon at boot time. Additionally, to use the mouse daemon on all virtual terminals instead of just the console, add allscreens_flags="-m on" to @@ -1813,9 +1810,9 @@ It is not possible to remove data using the mouse. - However, it is possible to copy and - paste. - Once you get the mouse daemon running as described in the previous question, hold down button 1 (left button) and move the mouse to select a region of text. Then, press button 2 (middle button) to @@ -1823,8 +1820,8 @@ button) will extend the selected region of text. - If your mouse does not have a middle button, you may - wish to emulate one or remap buttons using mouse daemon + If the mouse does not have a middle button, it is possible + to emulate one or remap buttons using mouse daemon options. See the &man.moused.8; manual page for details. @@ -1858,14 +1855,14 @@ For the Bourne Shell, add - the following lines to your .shrc. + the following lines to ~/.shrc. See &man.sh.1; and &man.editrc.5;. bind ^? ed-delete-next-char # for console bind ^[[3~ ed-delete-next-char # for xterm For the C Shell, add the - following lines to your .cshrc. + following lines to ~/.cshrc. See &man.csh.1;. bindkey ^? delete-char # for console @@ -1935,13 +1932,13 @@ bindkey ^[[3~ delete-char # for xterm

What happens to the memory that should appear in that - location is dependent on your hardware. Unfortunately, + location is hardware dependent. Unfortunately, some hardware does nothing and the ability to use that last 500 MB of RAM is entirely lost. Luckily, most hardware remaps the memory to a higher location so that it can still be used. However, this can - cause some confusion if you watch the boot + cause some confusion when watching the boot messages. On a 32-bit version of &os;, the memory appears lost, @@ -1971,11 +1968,11 @@ bindkey ^[[3~ delete-char # for xterm

- Signal 11 errors are caused when your process has + Signal 11 errors are caused when a process has attempted to access memory which the operating system has not granted it access to. If something like this is - happening at seemingly random intervals then you need to - start investigating things very carefully. + happening at seemingly random intervals, + start investigating the cause. These problems can usually be attributed to either: @@ -1983,8 +1980,8 @@ bindkey ^[[3~ delete-char # for xterm

If the problem is occurring only in a specific - application that you are developing yourself it is - probably a bug in your code. + custom application, it is + probably a bug in the code. @@ -1996,103 +1993,97 @@ bindkey ^[[3~ delete-char # for xterm

- In particular, a dead giveaway that this is - not a &os; bug is if you see the - problem when you are compiling a program, but the activity + It is probably + not a &os; bug if the + problem occurs compiling a program, but the activity that the compiler is carrying out changes each time. - For example, suppose you are running make - buildworld, and the compile fails while trying + For example, if make + buildworld fails while trying to compile ls.c into - ls.o. If you then run make - buildworld again, and the compile fails in the - same place then this is a broken build — try - updating your sources and try again. If the compile fails - elsewhere then this is almost certainly hardware. - - What you should do: + ls.o and, when run again, it fails in the + same place, this is a broken build. Try + updating source and try again. If the compile fails + elsewhere, it is almost certainly due to hardware. - In the first case you can use a debugger e.g., + In the first case, use a debugger such as &man.gdb.1; to find the point in the program which is - attempting to access a bogus address and then fix + attempting to access a bogus address and fix it. - In the second case you need to verify that it is not - your hardware at fault. + In the second case, verify which piece of + hardware is at fault. Common causes of this include: - Your hard disks might be overheating: Check the - fans in your case are still working, as your disk (and - perhaps other hardware might be overheating). + The hard disks might be overheating: Check that the + fans are still working, as the disk and + other hardware might be overheating. The processor running is overheating: This might be because the processor has been overclocked, or the - fan on the processor might have died. In either case - you need to ensure that you have hardware running at + fan on the processor might have died. In either case, + ensure that the hardware is running at what it is specified to run at, at least while trying - to solve this problem (in other words, clock it back + to solve this problem. If it is not, clock it back to the default settings.) - If you are overclocking then note that it is far + Regarding overclocking, it is far cheaper to have a slow system than a fried system that - needs replacing! Also the wider community is not - often sympathetic to problems on overclocked systems, - whether you believe it is safe or not. + needs replacing! Also the community is not + sympathetic to problems on overclocked systems. - Dodgy memory: If you have multiple memory - SIMMS/DIMMS installed then pull them all out and try + Dodgy memory: if multiple memory + SIMMS/DIMMS are installed, pull them all out and try running the machine with each SIMM or DIMM - individually and narrow the problem down to either the + individually to narrow the problem down to either the problematic DIMM/SIMM or perhaps even a combination. - Over-optimistic Motherboard settings: In your BIOS - settings, and some motherboard jumpers you have - options to set various timings, mostly the defaults - will be sufficient, but sometimes, setting the wait + Over-optimistic motherboard settings: the BIOS + settings, and some motherboard jumpers, provide + options to set various timings. The defaults + are often sufficient, but sometimes setting the wait states on RAM too low, or setting the RAM - Speed: Turbo option, or similar in the BIOS + Speed: Turbo option will cause strange behavior. A possible idea is to - set to BIOS defaults, but it might be worth noting - down your settings first! + set to BIOS defaults, after noting + the current settings first. Unclean or insufficient power to the motherboard. - If you have any unused I/O boards, hard disks, or - CD-ROMs in your system, try temporarily removing them - or disconnecting the power cable from them, to see if - your power supply can manage a smaller load. Or try + Remove any unused I/O boards, hard disks, or + CD-ROMs, + or disconnect the power cable from them, to see if + the power supply can manage a smaller load. Or try another power supply, preferably one with a little - more power (for instance, if your current power supply - is rated at 250 Watts try one rated at - 300 Watts). + more power. For instance, if the current power supply + is rated at 250 Watts, try one rated at + 300 Watts. - You should also read the SIG11 FAQ (listed below) - which has excellent explanations of all these problems, - albeit from a &linux; viewpoint. It also discusses how + Read the section on Signal 11 + for a further explanation and a discussion on how memory testing software or hardware can still pass faulty - memory. - - Finally, if none of this has helped it is possible - that you have just found a bug in &os;, and you should - follow the instructions to send a problem report. - - There is an extensive FAQ on this at FAQ on this at the SIG11 problem FAQ. + + Finally, if none of this has helped, it is possibly + a bug in &os;. + Follow these instructions + to send a problem report. @@ -2105,21 +2096,21 @@ bindkey ^[[3~ delete-char # for xterm

- The &os; developers are very interested in these - errors, but need some more information than just the error - you see. Copy your full crash message. Then consult the + The &os; developers are interested in these + errors, but need more information than just the error + message. Copy the full crash message. Then consult the FAQ section on kernel panics, build a debugging kernel, and get a - backtrace. This might sound difficult, but you do not - need any programming skills; you just have to follow the + backtrace. This might sound difficult, but does not require + any programming skills. Just follow the instructions. - Why do I get the error maxproc limit + What is the meaning of the error maxproc limit exceeded by uid %i, please see tuning(7) and login.conf(5)? @@ -2130,31 +2121,30 @@ bindkey ^[[3~ delete-char # for xterm

kern.maxusers &man.sysctl.8; variable. kern.maxusers also affects various other in-kernel limits, such as network buffers. - If your machine is heavily loaded, you probably want to + If the machine is heavily loaded, increase kern.maxusers. This will increase these other system limits in addition to the maximum number of processes. - To adjust your kern.maxusers value, + To adjust the kern.maxusers value, see the File/Process - Limits section of the Handbook. (While that + Limits section of the Handbook. While that section refers to open files, the same limits apply to - processes.) + processes. - If the machine is lightly loaded and you are - running a very large number of processes, you can adjust - this with the kern.maxproc tunable. If - this tunable needs adjustment it needs to be defined in + If the machine is lightly loaded but + running a very large number of processes, adjust + the kern.maxproc tunable by defining it in /boot/loader.conf. The tunable will not get adjusted until the system is rebooted. For more information about tuning tunables, see &man.loader.conf.5;. If these processes are being run by - a single user, you will also need to adjust + a single user, adjust kern.maxprocperuid to be one less than - your new kern.maxproc value. (It must + the new kern.maxproc value. It must be at least one less because one system program, - &man.init.8;, must always be running.) + &man.init.8;, must always be running. @@ -2196,7 +2186,7 @@ to /etc/mail/sendmail.cf. - The remote machine may be setting your terminal type + The remote machine may be setting the terminal type to something other than the cons25 terminal type required by the &os; console. @@ -2215,9 +2205,9 @@ to /etc/mail/sendmail.cf. Use a VT100 emulator like screen at the &os; console. - screen offers you the + screen provides the ability to run multiple concurrent sessions from one - terminal, and is a neat program in its own right. + terminal. Each screen window behaves like a VT100 terminal, so the TERM variable at the remote end should be set to @@ -2228,8 +2218,8 @@ to /etc/mail/sendmail.cf.Install the cons25 terminal database entry on the remote machine. The way to do this depends on the operating system on the remote - machine. The system administration manuals for the - remote system should be able to help you here. + machine. Refer to the system administration manuals for the + remote system. @@ -2267,29 +2257,28 @@ to /etc/mail/sendmail.cf. - The remedy: if the problem occurs whenever you connect - from your computer (the client) to any server, the problem - is with the client; likewise, if the problem only occurs - when someone connects to your computer (the server) the + The remedy: if the problem occurs whenever connecting + the client computer to any server, the problem + is with the client. If the problem only occurs + when someone connects to the server computer, the problem is with the server. If the problem is with the client, the only remedy is to fix the DNS so the server can resolve it. If this is on a local network, consider it a server problem and keep - reading; conversely, if this is on the global Internet, - you will most likely need to contact your ISP and ask them - to fix it for you. - - If the problem is with the server, and this is on a - local network, you need to configure the server to be able - to resolve address-to-hostname queries for your local - address range. See the &man.hosts.5; and &man.named.8; - manual pages for more information. If this is on the - global Internet, the problem may be that your server's + reading. If this is on the Internet, + contact your ISP. + + If the problem is with the server on a + local network, configure the server + to resolve address-to-hostname queries for the local + address range. See &man.hosts.5; and &man.named.8; + for more information. If this is on the + Internet, the problem may be that the local server's resolver is not functioning correctly. To check, try to - look up another host — say, + look up another host such as www.yahoo.com. If it does not - work, that is your problem. + work, that is the problem. Following a fresh install of &os;, it is also possible that domain and name server information is missing from @@ -2298,7 +2287,7 @@ to /etc/mail/sendmail.cf.UseDNS is set to yes by default in /etc/ssh/sshd_config. If this is - causing the problem, you will either need to fill in the + causing the problem, either fill in the missing information in /etc/resolv.conf or set UseDNS to no in @@ -2314,8 +2303,8 @@ to /etc/mail/sendmail.cf. - This error message indicates you have exhausted the - number of available file descriptors on your system. + This error message indicates that the + number of available file descriptors have been exhausted on the system. Refer to the kern.maxfiles section of the /var/log/messages and in the output - of dmesg. Otherwise, check your cables + of dmesg. Otherwise, check the cables and connections. @@ -2434,8 +2423,8 @@ kern.timecounter.hardware: TSC -> i82 &man.witness.4; is conservative. A true positive report does not mean that a system is dead-locked; instead it should be understood as a warning - of the form if you were unlucky, a deadlock would - have happened here. + that a deadlock could + have happened here. Problematic LORs tend to get @@ -2493,7 +2482,7 @@ kern.timecounter.hardware: TSC -> i82 This error does not mean that the &man.touch.1; utility is missing. The error is instead probably due to the dates of the files being set sometime in the future. - If your CMOS-clock is set to local time, run + If the CMOS clock is set to local time, run adjkerntz -i to adjust the kernel clock when booting into single-user mode. @@ -2526,21 +2515,11 @@ kern.timecounter.hardware: TSC -> i82 of release in also included in the ports/ directory. - We also support the concept of a - package, essentially no more than a - compressed binary distribution with a little extra - intelligence embedded in it for doing whatever custom - installation work is required. A package can be installed - and uninstalled again easily without having to know the - gory details of which files it includes. - - Use &man.pkg.7; on the specific package files you are - interested in installing. Package files can usually be - identified by their .txz suffix and - CD-ROM distribution people will have a - packages/All directory on their CD - which contains such files. They can also be downloaded - over the net for various versions of &os;. + &os; supports + packages, which provide a + compressed binary distribution. Package can be installed + and uninstalled again easily. On &os;, + &man.pkg.7; to install packages. @@ -2555,20 +2534,24 @@ kern.timecounter.hardware: TSC -> i82 - Use portsnap for most use cases. - - - Use SVN directly if you need custom patches to the - ports tree. - - - Use CTM if you prefer getting patches by email - (this is a rarer use case). + Use portsnap for most use cases. Refer to Using + the Ports Collection for instructions on how to + use this tool. + + + Use SVN if custom patches to the + ports tree are needed. Refer to Using + Subversion for details. + + + Use CTM, as described in Using + CTM to receive patches by + email over an unreliable Internet connection. - - Any other method should be considered a legacy method. - If you do not already use them, do not start. @@ -2592,14 +2575,13 @@ kern.timecounter.hardware: TSC -> i82 - If you are running a &os; version that lags + If the installed &os; version lags significantly behind -CURRENT or - -STABLE, you may need to update your - Ports Collection; see the Keeping - Up section of the Porter's Handbook for further - information on how to do this. If you are up to date, - then someone might have committed a change to the port + -STABLE, update the + Ports Collection using the instructions in Using + the Ports Collection. If the system is up-to-date, + someone might have committed a change to the port which works for -CURRENT but which broke the port for -STABLE. Submit a bug report with the &man.send-pr.1; @@ -2616,8 +2598,8 @@ kern.timecounter.hardware: TSC -> i82 - First, always make sure that you have a complete - up-to-date Ports Collection. Errors that affect building + First, make sure that the + Ports Collection is up-to-date. 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. @@ -2656,11 +2638,10 @@ kern.timecounter.hardware: TSC -> i82 - By all means! While a recent system will run with - software compiled under an older release, you will end up - with things randomly crashing and failing to work once you - start installing other ports or updating a portion of what - you already have. + Yes! While a recent system will run with + software compiled under an older release, + things will randomly crash and fail to work once + other ports are installed or updated. When the system is upgraded, various shared libraries, loadable modules, and other parts of the system will be @@ -2717,10 +2698,10 @@ kern.timecounter.hardware: TSC -> i82 shells have. That is why other more featureful shells like bash, scsh, &man.tcsh.1;, and zsh are available. - (You can compare for yourself the memory utilization of - all these shells by looking at the VSZ and + You can compare the memory utilization of + these shells by looking at the VSZ and RSS columns in a ps -u - listing.) + listing. @@ -2772,13 +2753,12 @@ kern.timecounter.hardware: TSC -> i82 - Short answer: it is not possible. + Short answer: no. - Longer answer: if you have made any changes using - pkg converting back is non-trivial and + Longer answer: converting back is non-trivial and requires lots of manual editing of internal package - database files. However, if you have just run - pkg2ng then you may remove + database files. However, if + pkg2ng has just been run, remove /var/db/pkg/local.sqlite and extract /var/backups/pkgdb.bak.tbz. @@ -2806,9 +2786,9 @@ kern.timecounter.hardware: TSC -> i82 installed to the /boot/kernel directory along with its modules, while the old kernel and its modules will be moved to the - /boot/kernel.old directory, so if - you make a mistake the next time you play with your - configuration you can boot the previous version of your + /boot/kernel.old directory. If + a mistake is made in the + configuration, simply boot the previous version of the kernel. @@ -2829,12 +2809,12 @@ kern.timecounter.hardware: TSC -> i82 running a debug kernel, and it is useful to keep one around in case of a system panic. - However, if you are running low on disk space, there + However, when running low on disk space, there are different options to reduce the size of /boot/kernel/. - If you do not want the symbol files to be installed, - make sure you have the following line present in + To not install the symbol files, + make sure the following line exists in /etc/src.conf: WITHOUT_KERNEL_SYMBOLS=yes @@ -2846,44 +2826,42 @@ kern.timecounter.hardware: TSC -> i82 - You do not have a line in your kernel - configuration file that reads: + This line does not exist in the kernel + configuration file: makeoptions DEBUG=-g - You are not running &man.config.8; with + Do not run &man.config.8; with . - Either of the above settings will cause your kernel to - be built in debug mode. As long as you make sure you - follow the steps above, you can build your kernel - normally. + Either of the above settings will cause the kernel to + be built in debug mode. - If you want only the modules you use to be built and - installed, make sure you have a line like below in + To build and install only the specified modules, list + them in /etc/make.conf: MODULES_OVERRIDE= accf_http ipfw Replace accf_httpd ipfw with a - list of modules you need. Only these modules will be - built. This does not only reduce the size of the kernel - directory but also decreases the amount of time needed to - build your kernel. For more information see + list of needed modules. Only the listed modules will be + built. This reduces the size of the kernel + directory and decreases the amount of time needed to + build the kernel. For more information, read /usr/share/examples/etc/make.conf. - You can also remove unneeded devices from your kernel + Unneeded devices can be removed from the kernel to further reduce the size. See for more information. - To put any of these options into effect you will have + To put any of these options into effect, follow the instructions to build - and install your new kernel. + and install the new kernel. Most kernels (/boot/kernel/kernel) tend to be @@ -2899,45 +2877,38 @@ kern.timecounter.hardware: TSC -> i82 There are a number of possible causes for this - problem. They are, in no particular order: + problem: - You are not using the make - buildkernel and make - installkernel targets, and your source + The source tree is different from the one used to build the - currently running system (e.g., you are compiling - &rel.current;-RELEASE on a &rel2.current;-RELEASE - system). If you are attempting an upgrade, + currently running system. When attempting an upgrade, read /usr/src/UPDATING, paying particular attention to the COMMON ITEMS section at the end. - You are using the make - buildkernel and make - installkernel targets, but you failed to - assert the completion of the make - buildworld target. The make + The make + buildkernel command did not complete + successfuly. The make buildkernel target relies on files generated by the make buildworld target to complete its job correctly. - Even if you are trying to build Even when building &os;-STABLE, it is possible - that you fetched the source tree at a time when it was - either being modified, or broken for other reasons; - only releases are absolutely guaranteed to be + that the source tree was fetched at a time when it was + either being modified or it was broken. + Only releases are guaranteed to be buildable, although &os;-STABLE builds fine the - majority of the time. If you have not already done - so, try re-fetching the source tree and see if the - problem goes away. Try using a different server in - case the one you are using is having problems. + majority of the time. Try re-fetching the source tree and see if the + problem goes away. Try using a different mirror in + case the previous one is having problems. @@ -2945,7 +2916,7 @@ kern.timecounter.hardware: TSC -> i82 - How can I verify which scheduler is in use on a + Which scheduler is in use on a running system? @@ -2997,38 +2968,37 @@ kern.sched.name: ULE - The best way is to reinstall the OS on the new disk, + The best way is to reinstall the operating system on the new disk, then move the user data over. This is highly recommended - if you have been tracking -STABLE for - more than one release, or have updated a release instead - of installing a new one. You can install booteasy on both - disks with &man.boot0cfg.8;, and dual boot them until you + when tracking -STABLE for + more than one release or when updating a release instead + of installing a new one. Install booteasy on both + disks with &man.boot0cfg.8; and dual boot until you are happy with the new configuration. Skip the next paragraph to find out how to move the data after doing this. Alternatively, partition and label the new disk with either &man.sade.8; or &man.gpart.8;. If the disks are - MBR-formatted, you can also install booteasy on both disks - with &man.boot0cfg.8;, so that you can dual boot to the + MBR-formatted, booteasy can be installed on both disks + with &man.boot0cfg.8; so that the computer can dual boot to the old or new system after the copying is done. - Now you have the new disk set up, and are ready to - move the data. Unfortunately, you cannot just blindly - copy the data. Things like device files (in - /dev), flags, and links tend to screw - that up. You need to use tools that understand these - things, which means &man.dump.8;. Although it is - suggested that you move the data in single-user mode, it + Once the new disk set up, + the data cannot just be copied. Instead, use tools that + understand device files and syste flags, such as + &man.dump.8;. Although it is recommended + to move the data while in single-user mode, it is not required. - You should never use anything but &man.dump.8; and - &man.restore.8; to move the root file system. The - &man.tar.1; command may work — then again, it may - not. You should also use &man.dump.8; and &man.restore.8; - if you are moving a single partition to another empty + When the disks are formatted with + UFS, never use anything but &man.dump.8; and + &man.restore.8; to move the root file system. These + commands should also be used when + moving a single partition to another empty partition. The sequence of steps to use - dump to move a partitions data to a new + dump to move the data from one + UFS partitions to a new partition is: @@ -3051,17 +3021,16 @@ kern.sched.name: ULE - For example, if you are going to move root to - /dev/ada1s1a, with - /mnt as the temporary mount point, it - is: + For example, to move + /dev/ada1s1a with + /mnt as the temporary mount point, type: &prompt.root; newfs /dev/ada1s1a &prompt.root; mount /dev/ada1s1a /mnt &prompt.root; cd /mnt &prompt.root; dump 0af - / | restore rf - - Rearranging your partitions with + Rearranging partitions with dump takes a bit more work. To merge a partition like /var into its parent, create the new partition large enough for both, move the @@ -3105,7 +3074,7 @@ kern.sched.name: ULE - Short answer: you can usually use Soft Updates safely + Short answer: Soft Updates can usually be safely used on all partitions. Long answer: Soft Updates has two characteristics @@ -3119,17 +3088,15 @@ kern.sched.name: ULE thirty seconds to write changes to the physical disk. When a large file is deleted the file still resides on disk until the kernel actually performs the deletion. - This can cause a very simple race condition. Suppose you - delete one large file and immediately create another large - file. The first large file is not yet actually removed + This can cause a very simple race condition. Suppose + one large file is deleted and another large file is immediately created. + The first large file is not yet actually removed from the physical disk, so the disk might not have enough - room for the second large file. You get an error that the - partition does not have enough space, although you know - perfectly well that you just released a large chunk of - space! When you try again mere seconds later, the file - creation works as you expect. This has left more than one - user scratching his head and doubting his sanity, the &os; - file system, or both. + room for the second large file. This will produce an error that the + partition does not have enough space, even though + a large chunk of + space has just been released. A few seconds later, the file + creation works as expected. If a system should crash after the kernel accepts a chunk of data for writing to disk, but before that data is @@ -3143,15 +3110,14 @@ kern.sched.name: ULE rarely. If the system crashed during the thirty-second window after such a change is made, it is possible that data could be lost. This risk is negligible for most - applications, but you should be aware that it exists. If - your system cannot tolerate this much risk, do not use + applications, but be aware that it exists. If + the system cannot tolerate this much risk, do not use Soft Updates on the root file system! / is traditionally one of the - smallest partitions. If you put the - /tmp directory on - / and you have a busy - /tmp, you might see intermittent + smallest partitions. If + /tmp is on + /, there may be intermittent space problems. Symlinking /tmp to /var/tmp will solve this problem. @@ -3241,10 +3207,10 @@ kern.sched.name: ULE The secondary DOS partitions are found after all the primary partitions. For - example, if you have an E partition as the + example, if E is the second DOS partition on the second SCSI drive, there will be a device file for slice 5 in - /dev, so mount it: + /dev. To mount it: &prompt.root; mount -t msdosfs /dev/da1s5 /dos/e @@ -3256,8 +3222,8 @@ kern.sched.name: ULE - Yes. You can use either &man.gbde.8; or &man.geli.8;, - see the Yes, &man.gbde.8; and &man.geli.8;. + See the Encrypting Disk Partitions section of the &os; Handbook. @@ -3265,116 +3231,6 @@ kern.sched.name: ULE - - How can I use the &windowsnt; loader to boot - &os;? - - - - The general idea is that you copy the first sector of - your native root &os; partition into a file in the - DOS/&windowsnt; partition. Assuming you name that file - something like c:\bootsect.bsd - (inspired by c:\bootsect.dos), you - can then edit c:\boot.ini to come up - with something like this: - - [boot loader] -timeout=30 -default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS -[operating systems] -multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows NT" -C:\BOOTSECT.BSD="&os;" -C:\="DOS" - - If &os; is installed on the same disk as the - &windowsnt; boot partition, copy - /boot/boot1 to - C:\BOOTSECT.BSD. However, if &os; is - installed on a different disk - /boot/boot1 will not work, *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***