Date: Mon, 12 May 2014 18:42:03 +0000 (UTC) From: Dru Lavigne <dru@FreeBSD.org> To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r44817 - head/en_US.ISO8859-1/books/faq Message-ID: <201405121842.s4CIg3x2091889@svn.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: dru Date: Mon May 12 18:42:03 2014 New Revision: 44817 URL: http://svnweb.freebsd.org/changeset/doc/44817 Log: White space fix only. Translators can ignore. 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 Mon May 12 15:15:44 2014 (r44816) +++ head/en_US.ISO8859-1/books/faq/book.xml Mon May 12 18:42:03 2014 (r44817) @@ -2895,8 +2895,9 @@ kern.timecounter.hardware: TSC -> i82 xlink:href="&url.books.handbook;/kernelconfig-building.html">build and install</link> your new kernel.</para> - <para>Most kernels (<filename>/boot/kernel/kernel</filename>) - tend to be around 12 MB to 16 MB.</para> + <para>Most kernels + (<filename>/boot/kernel/kernel</filename>) tend to be + around 12 MB to 16 MB.</para> </answer> </qandaentry> @@ -2907,48 +2908,46 @@ kern.timecounter.hardware: TSC -> i82 </question> <answer> - <para>There are a number of possible causes for this problem. - They are, in no particular order:</para> + <para>There are a number of possible causes for this + problem. They are, in no particular order:</para> <itemizedlist> <listitem> - <para>You are not using the - <command>make buildkernel</command> and - <command>make installkernel</command> - targets, and your 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, please read - <filename>/usr/src/UPDATING</filename>, paying - particular attention to the <quote>COMMON ITEMS</quote> - section at the end.</para> + <para>You are not using the <command>make + buildkernel</command> and <command>make + installkernel</command> targets, and your 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, please + read <filename>/usr/src/UPDATING</filename>, paying + particular attention to the <quote>COMMON + ITEMS</quote> section at the end.</para> </listitem> <listitem> - <para>You are using the - <command>make buildkernel</command> - and - <command>make installkernel</command> - targets, but you failed to assert the completion of the - <command>make buildworld</command> - target. The - <command>make buildkernel</command> - target relies on files generated by the - <command>make buildworld</command> + <para>You are using the <command>make + buildkernel</command> and <command>make + installkernel</command> targets, but you failed to + assert the completion of the <command>make + buildworld</command> target. The <command>make + buildkernel</command> target relies on files + generated by the <command>make buildworld</command> target to complete its job correctly.</para> </listitem> <listitem> - <para>Even if you are trying to build <link linkend="stable">&os;-STABLE</link>, 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 buildable, - although <link linkend="stable">&os;-STABLE</link> - 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.</para> + <para>Even if you are trying to build <link + linkend="stable">&os;-STABLE</link>, 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 + buildable, although <link + linkend="stable">&os;-STABLE</link> 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.</para> </listitem> </itemizedlist> </answer> @@ -2956,8 +2955,8 @@ kern.timecounter.hardware: TSC -> i82 <qandaentry> <question xml:id="scheduler-in-use"> - <para>How can I verify which scheduler is in use on a running - system?</para> + <para>How can I verify which scheduler is in use on a + running system?</para> </question> <answer> @@ -2990,53 +2989,57 @@ kern.sched.name: ULE</screen> <qandaset> <qandaentry> <question xml:id="adding-disks"> - <para>How can I add my new hard disk to my &os; system?</para> + <para>How can I add my new hard disk to my &os; + system?</para> </question> <answer> - <para>See the <link xlink:href="&url.books.handbook;/disks-adding.html">Adding Disks</link> - section in the &os; Handbook.</para> + <para>See the <link + xlink:href="&url.books.handbook;/disks-adding.html">Adding + Disks</link> section in the &os; Handbook.</para> </answer> </qandaentry> <qandaentry> <question xml:id="new-huge-disk"> - <para>How do I move my system over to my huge new disk?</para> + <para>How do I move my system over to my huge new + disk?</para> </question> <answer> <para>The best way is to reinstall the OS on the new disk, - then move the user data over. This is highly recommended if - you have been tracking <emphasis>-STABLE</emphasis> for more - than one release, or have updated a release instead of - installing a new one. You can install booteasy on both + then move the user data over. This is highly recommended + if you have been tracking <emphasis>-STABLE</emphasis> 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 are happy with the new configuration. Skip the next paragraph to find out how to move the data after doing this.</para> - <para>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 old or - new system after the copying is done.</para> - - <para>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 + <para>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 + old or new system after the copying is done.</para> + + <para>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 <filename>/dev</filename>), 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 is not - required.</para> + things, which means &man.dump.8;. Although it is + suggested that you move the data in single user mode, it + is not required.</para> <para>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 partition. - The sequence of steps to use <command>dump</command> to move - a partitions data to a new partition is:</para> + &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 + partition. The sequence of steps to use + <command>dump</command> to move a partitions data to a new + partition is:</para> <procedure> <step> @@ -3059,21 +3062,22 @@ kern.sched.name: ULE</screen> </procedure> <para>For example, if you are going to move root to - <filename>/dev/ada1s1a</filename>, - with <filename>/mnt</filename> as - the temporary mount point, it is:</para> + <filename>/dev/ada1s1a</filename>, with + <filename>/mnt</filename> as the temporary mount point, it + is:</para> <screen>&prompt.root; <userinput>newfs /dev/ada1s1a</userinput> &prompt.root; <userinput>mount /dev/ada1s1a /mnt</userinput> &prompt.root; <userinput>cd /mnt</userinput> &prompt.root; <userinput>dump 0af - / | restore rf -</userinput></screen> - <para>Rearranging your partitions with <command>dump</command> - takes a bit more work. To merge a partition like - <filename>/var</filename> into its parent, create the new - partition large enough for both, move the parent partition - as described above, then move the child partition into the - empty directory that the first move created:</para> + <para>Rearranging your partitions with + <command>dump</command> takes a bit more work. To merge a + partition like <filename>/var</filename> into its parent, + create the new partition large enough for both, move the + parent partition as described above, then move the child + partition into the empty directory that the first move + created:</para> <screen>&prompt.root; <userinput>newfs /dev/ada1s1a</userinput> &prompt.root; <userinput>mount /dev/ada1s1a /mnt</userinput> @@ -3096,72 +3100,69 @@ kern.sched.name: ULE</screen> &prompt.root; <userinput>cd /mnt</userinput> &prompt.root; <userinput>dump 0af - / | restore rf -</userinput></screen> - <para>You might prefer &man.cpio.1;, &man.pax.1;, &man.tar.1; - to &man.dump.8; for user data. At the time of this writing, - these are known to lose file flag information, so use them - with caution.</para> + <para>You might prefer &man.cpio.1;, &man.pax.1;, + &man.tar.1; to &man.dump.8; for user data. At the time of + this writing, these are known to lose file flag + information, so use them with caution.</para> </answer> </qandaentry> <qandaentry> <question xml:id="safe-softupdates"> <para>Which partitions can safely use Soft Updates? I have - heard that Soft Updates on <filename>/</filename> can cause - problems. What about Journaled Soft Updates?</para> + heard that Soft Updates on <filename>/</filename> can + cause problems. What about Journaled Soft Updates?</para> </question> <answer> - <para>Short answer: you can usually use Soft Updates safely on - all partitions.</para> + <para>Short answer: you can usually use Soft Updates safely + on all partitions.</para> - <para>Long answer: Soft Updates has two - characteristics that may be undesirable on certain - partitions. First, a Soft Updates - partition has a small chance of losing data during a system - crash. (The partition will not be corrupted; the data will - simply be lost.) Second, Soft Updates can cause temporary - space shortages.</para> + <para>Long answer: Soft Updates has two characteristics + that may be undesirable on certain partitions. First, a + Soft Updates partition has a small chance of losing data + during a system crash. (The partition will not be + corrupted; the data will simply be lost.) Second, Soft + Updates can cause temporary space shortages.</para> <para>When using Soft Updates, the kernel can take up to - 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 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.</para> + 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 + 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.</para> <para>If a system should crash after the kernel accepts a chunk of data for writing to disk, but before that data is - actually written out, data could be lost. This - risk is extremely small, but generally manageable.</para> + actually written out, data could be lost. This risk is + extremely small, but generally manageable.</para> <para>These issues affect all partitions using Soft Updates. So, what does this mean for the root partition?</para> <para>Vital information on the root partition changes very - 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 Soft Updates on the root - file system!</para> + 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 + Soft Updates on the root file system!</para> <para><filename>/</filename> is traditionally one of the smallest partitions. If you put the <filename>/tmp</filename> directory on <filename>/</filename> and you have a busy - <filename>/tmp</filename>, you might see intermittent space - problems. Symlinking <filename>/tmp</filename> to + <filename>/tmp</filename>, you might see intermittent + space problems. Symlinking <filename>/tmp</filename> to <filename>/var/tmp</filename> will solve this problem.</para> @@ -3188,8 +3189,8 @@ kern.sched.name: ULE</screen> <para>UFS CD-ROMs can be mounted directly on &os;. Mounting disk partitions from Digital UNIX and other systems that support UFS may be more complex, - depending on the details of the disk partitioning for - the operating system in question.</para> + depending on the details of the disk partitioning + for the operating system in question.</para> </listitem> </varlistentry> @@ -3208,8 +3209,9 @@ kern.sched.name: ULE</screen> <listitem> <para>FUSE based NTFS support is available as a port - (<package>sysutils/fusefs-ntfs</package>). - For more information see <link xlink:href="http://www.tuxera.com/community/ntfs-3g-manual/"><application>ntfs-3g</application></link>.</para>; + (<package>sysutils/fusefs-ntfs</package>). For more + information see <link + xlink:href="http://www.tuxera.com/community/ntfs-3g-manual/"><application>ntfs-3g</application></link>.</para>; </listitem> </varlistentry> @@ -3226,19 +3228,20 @@ kern.sched.name: ULE</screen> <term>ZFS</term> <listitem> - <para>&os; includes a port of - &sun;'s ZFS driver. The current recommendation is to - use it only on &arch.amd64; platforms with sufficient - memory. For more information, see &man.zfs.8;.</para> + <para>&os; includes a port of &sun;'s ZFS driver. The + current recommendation is to use it only on + &arch.amd64; platforms with sufficient memory. For + more information, see &man.zfs.8;.</para> </listitem> </varlistentry> </variablelist> - <para>&os; also supports network file systems such as NFS (see - &man.mount.nfs.8;), NetWare (see &man.mount.nwfs.8;), and - Microsoft-style SMB file systems (see &man.mount.smbfs.8;). - You can find ports based on FUSE (<package>sysutils/fusefs-kmod</package>) for many - other file systems.</para> + <para>&os; also supports network file systems such as NFS + (see &man.mount.nfs.8;), NetWare (see &man.mount.nwfs.8;), + and Microsoft-style SMB file systems (see + &man.mount.smbfs.8;). You can find ports based on FUSE + (<package>sysutils/fusefs-kmod</package>) for many other + file systems.</para> </answer> </qandaentry> @@ -3251,8 +3254,8 @@ kern.sched.name: ULE</screen> <para>The secondary DOS partitions are found after <emphasis>all</emphasis> the primary partitions. For example, if you have an <quote>E</quote> partition as the - second DOS partition on the second SCSI drive, there will be - a device file for <quote>slice 5</quote> in + second DOS partition on the second SCSI drive, there will + be a device file for <quote>slice 5</quote> in <filename>/dev</filename>, so simply mount it:</para> <screen>&prompt.root; <userinput>mount -t msdosfs /dev/da1s5 /dos/e</userinput></screen> @@ -3266,8 +3269,10 @@ kern.sched.name: ULE</screen> <answer> <para>Yes. You can use either &man.gbde.8; or &man.geli.8;, - see the <link xlink:href="&url.books.handbook;/disks-encrypting.html">Encrypting Disk Partitions</link> - section of the &os; Handbook.</para> + see the <link + xlink:href="&url.books.handbook;/disks-encrypting.html">Encrypting + Disk Partitions</link> section of the &os; + Handbook.</para> </answer> </qandaentry> @@ -3282,9 +3287,9 @@ kern.sched.name: ULE</screen> your native root &os; partition into a file in the DOS/&windowsnt; partition. Assuming you name that file something like <filename>c:\bootsect.bsd</filename> - (inspired by <filename>c:\bootsect.dos</filename>), you can - then edit <filename>c:\boot.ini</filename> to come - up with something like this:</para> + (inspired by <filename>c:\bootsect.dos</filename>), you + can then edit <filename>c:\boot.ini</filename> to come up + with something like this:</para> <programlisting>[boot loader] timeout=30 @@ -3294,20 +3299,22 @@ multi(0)disk(0)rdisk(0)partition(1)\WIND C:\BOOTSECT.BSD="&os;" C:\="DOS"</programlisting> - <para>If &os; is installed on the same disk as the &windowsnt; - boot partition simply copy <filename>/boot/boot1</filename> to + <para>If &os; is installed on the same disk as the + &windowsnt; boot partition simply copy + <filename>/boot/boot1</filename> to <filename>C:\BOOTSECT.BSD</filename>. However, if &os; is installed on a different disk <filename>/boot/boot1</filename> will not work, <filename>/boot/boot0</filename> is needed.</para> <para><filename>/boot/boot0</filename> needs to be installed - using &man.sysinstall.8; by selecting the &os; boot manager - on the screen which asks if you wish to use a boot manager. - This is because <filename>/boot/boot0</filename> has the - partition table area filled with NULL characters but - &man.sysinstall.8; copies the partition table before copying - <filename>/boot/boot0</filename> to the MBR.</para> + using &man.sysinstall.8; by selecting the &os; boot + manager on the screen which asks if you wish to use a boot + manager. This is because <filename>/boot/boot0</filename> + has the partition table area filled with NULL characters + but &man.sysinstall.8; copies the partition table before + copying <filename>/boot/boot0</filename> to the + MBR.</para> <warning> <para><emphasis>Do not simply copy @@ -3322,9 +3329,9 @@ C:\="DOS"</programlisting> entry for that OS and then writes the whole 512-bytes of itself back to the MBR so if you just copy <filename>/boot/boot0</filename> to - <filename>C:\BOOTSECT.BSD</filename> then it writes an empty - partition table, with the active flag set on one entry, to - the MBR.</para> + <filename>C:\BOOTSECT.BSD</filename> then it writes an + empty partition table, with the active flag set on one + entry, to the MBR.</para> </answer> </qandaentry> @@ -3349,7 +3356,8 @@ C:\="DOS"</programlisting> <para>(the above assumes that your &os; slice is known to &linux; as <filename>/dev/hda2</filename>; tailor to suit your setup). Then, run <command>lilo</command> as - <systemitem class="username">root</systemitem> and you should be done.</para> + <systemitem class="username">root</systemitem> and you + should be done.</para> <para>If &os; resides on another disk, you need to add <literal>loader=/boot/chain.b</literal> to the LILO entry. @@ -3361,19 +3369,20 @@ C:\="DOS"</programlisting> label=&os;</programlisting> <para>In some cases you may need to specify the BIOS drive - number to the &os; boot loader to successfully boot off the - second disk. For example, if your &os; SCSI disk is probed - by BIOS as BIOS disk 1, at the &os; boot loader prompt you - need to specify:</para> + number to the &os; boot loader to successfully boot off + the second disk. For example, if your &os; SCSI disk is + probed by BIOS as BIOS disk 1, at the &os; boot loader + prompt you need to specify:</para> <screen>Boot: <userinput>1:da(0,a)/boot/kernel/kernel</userinput></screen> - <para>You can configure &man.boot.8; to automatically do this - for you at boot time.</para> + <para>You can configure &man.boot.8; to automatically do + this for you at boot time.</para> - <para>The <link xlink:href="http://tldp.org/HOWTO/Linux+FreeBSD.html">&linux;+&os; mini-HOWTO</link> - is a good reference for &os; and &linux; interoperability - issues.</para> + <para>The <link + xlink:href="http://tldp.org/HOWTO/Linux+FreeBSD.html">&linux;+&os; + mini-HOWTO</link> is a good reference for &os; and + &linux; interoperability issues.</para> </answer> </qandaentry> @@ -3397,8 +3406,8 @@ C:\="DOS"</programlisting> root partition on the first disk. If you need to specify which slice number should be used, use something like this <replaceable>(hd0,2,a)</replaceable>. By default, if the - slice number is omitted, GRUB searches the first slice which - has <literal>a</literal> partition.</para> + slice number is omitted, GRUB searches the first slice + which has <literal>a</literal> partition.</para> </answer> </qandaentry> @@ -3409,29 +3418,31 @@ C:\="DOS"</programlisting> </question> <answer> - <para>Install LILO at the start of your &linux; boot partition - instead of in the Master Boot Record. You can then boot - LILO from <application>BootEasy</application>.</para> + <para>Install LILO at the start of your &linux; boot + partition instead of in the Master Boot Record. You can + then boot LILO from + <application>BootEasy</application>.</para> <para>If you are running &windows; and &linux; this is - recommended anyway, to make it simpler to get &linux; booting - again if you should need to reinstall &windows; (which is a - Jealous Operating System, and will bear no other Operating - Systems in the Master Boot Record).</para> + recommended anyway, to make it simpler to get &linux; + booting again if you should need to reinstall &windows; + (which is a Jealous Operating System, and will bear no + other Operating Systems in the Master Boot Record).</para> </answer> </qandaentry> <qandaentry> <question xml:id="changing-bootprompt"> <para>How do I change the boot prompt from - <literal>???</literal> to something more meaningful?</para> + <literal>???</literal> to something more + meaningful?</para> </question> <answer> <para>You can not do that with the standard boot manager without rewriting it. There are a number of other boot - managers in the <filename>sysutils</filename> ports category - that provide this functionality.</para> + managers in the <filename>sysutils</filename> ports + category that provide this functionality.</para> </answer> </qandaentry> @@ -3441,19 +3452,17 @@ C:\="DOS"</programlisting> </question> <answer> - <para>If the drive already has a - file system on it, you can use a command like this:</para> + <para>If the drive already has a file system on it, you can + use a command like this:</para> <screen>&prompt.root; <userinput>mount -t msdosfs /dev/da0s1 /mnt</userinput></screen> - <para>If the drive will only be used with &os; - systems it is better idea to - stick a BSD file system on it, like UFS or ZFS. - You will get long filename - support, at least a 2X improvement in performance, - and a lot more stability. If the drive will be - used by other operating systems a more portable - choice, such as msdosfs, is better.</para> + <para>If the drive will only be used with &os; systems it is + better idea to stick a BSD file system on it, like UFS or + ZFS. You will get long filename support, at least a 2X + improvement in performance, and a lot more stability. If + the drive will be used by other operating systems a more + portable choice, such as msdosfs, is better.</para> <screen>&prompt.root; <userinput>dd if=/dev/zero of=/dev/da0 count=2</userinput> &prompt.root; <userinput>gpart create -s GPT /dev/da0</userinput> @@ -3467,9 +3476,9 @@ C:\="DOS"</programlisting> <screen>&prompt.root; <userinput>mount /dev/da0s1 /mnt</userinput></screen> - <para>It is a good idea to add a line - to <filename>/etc/fstab</filename> (see &man.fstab.5;) so - you can just type <command>mount /mnt</command> in the + <para>It is a good idea to add a line to + <filename>/etc/fstab</filename> (see &man.fstab.5;) so you + can just type <command>mount /mnt</command> in the future:</para> <programlisting>/dev/da0p1 /mnt ufs rw,noauto 0 0</programlisting> @@ -3484,8 +3493,12 @@ C:\="DOS"</programlisting> <answer> <para>You have to tell &man.mount.8; the type of the device - that you want to mount. This is described in the <link xlink:href="&url.books.handbook;/creating-cds.html"> Handbook section on optical media</link>, - specifically the section <link xlink:href="&url.books.handbook;/creating-cds.html#mounting-cd">Using Data CDs</link>.</para> + that you want to mount. This is described in the <link + xlink:href="&url.books.handbook;/creating-cds.html">Handbook + section on optical media</link>, specifically the + section <link + xlink:href="&url.books.handbook;/creating-cds.html#mounting-cd">Using + Data CDs</link>.</para> </answer> </qandaentry> @@ -3498,9 +3511,10 @@ C:\="DOS"</programlisting> <answer> <para>This generally means that there is no CD-ROM in the CD-ROM drive, or the drive is not visible on the bus. - Please see the <link xlink:href="&url.books.handbook;/creating-cds.html#mounting-cd">Using Data CDs</link> - section of the Handbook for a detailed discussion of this - issue.</para> + Please see the <link + xlink:href="&url.books.handbook;/creating-cds.html#mounting-cd">Using + Data CDs</link> section of the Handbook for a detailed + discussion of this issue.</para> </answer> </qandaentry> @@ -3514,22 +3528,30 @@ C:\="DOS"</programlisting> <para>Your CD-ROM probably uses the <quote>Joliet</quote> extension for storing information about files and directories. This is discussed in the Handbook chapter on - <link xlink:href="&url.books.handbook;/creating-cds.html">creating and using CD-ROMs</link>, - specifically the section on <link xlink:href="&url.books.handbook;/creating-cds.html#mounting-cd">Using Data CD-ROMs</link>.</para> + <link + xlink:href="&url.books.handbook;/creating-cds.html">creating + and using CD-ROMs</link>, specifically the section on + <link + xlink:href="&url.books.handbook;/creating-cds.html#mounting-cd">Using + Data CD-ROMs</link>.</para> </answer> </qandaentry> <qandaentry> <question xml:id="burncd-isofs"> - <para>I burned a CD under &os; and now I can not read it under - any other operating system. Why?</para> + <para>I burned a CD under &os; and now I can not read it + under any other operating system. Why?</para> </question> <answer> <para>You most likely burned a raw file to your CD, rather - than creating an ISO 9660 file system. Take a look at - the <link xlink:href="&url.books.handbook;/creating-cds.html">Handbook chapter on creating CD-ROMs</link>, - particularly the section on <link xlink:href="&url.books.handbook;/creating-cds.html#mounting-cd">Using Data <acronym>CD</acronym>s</link>.</para> + than creating an ISO 9660 file system. Take a look + at the <link + xlink:href="&url.books.handbook;/creating-cds.html">Handbook + chapter on creating CD-ROMs</link>, particularly the + section on <link + xlink:href="&url.books.handbook;/creating-cds.html#mounting-cd">Using + Data <acronym>CD</acronym>s</link>.</para> </answer> </qandaentry> @@ -3539,9 +3561,13 @@ C:\="DOS"</programlisting> </question> <answer> - <para>This is discussed in the Handbook section on <link xlink:href="&url.books.handbook;/creating-cds.html#mkisofs">Writing Data to an <acronym>ISO</acronym> File System</link>. - For more on working with CD-ROMs, see the <link xlink:href="&url.books.handbook;/creating-cds.html">Creating CDs Section</link> - in the Storage chapter in the Handbook.</para> + <para>This is discussed in the Handbook section on <link + xlink:href="&url.books.handbook;/creating-cds.html#mkisofs">Writing + Data to an <acronym>ISO</acronym> File System</link>. + For more on working with CD-ROMs, see the <link + xlink:href="&url.books.handbook;/creating-cds.html">Creating + CDs Section</link> in the Storage chapter in the + Handbook.</para> </answer> </qandaentry> @@ -3554,10 +3580,11 @@ C:\="DOS"</programlisting> <answer> <para>If you try to mount an audio CD, you will get an error like <errorname>cd9660: /dev/acd0c: Invalid - argument</errorname>. This is because - <command>mount</command> only works on file systems. Audio - CDs do not have file systems; they just have data. You need - a program that reads audio CDs, such as the <package>audio/xmcd</package> port.</para> + argument</errorname>. This is because + <command>mount</command> only works on file systems. + Audio CDs do not have file systems; they just have data. + You need a program that reads audio CDs, such as the + <package>audio/xmcd</package> port.</para> </answer> </qandaentry> @@ -3568,11 +3595,11 @@ C:\="DOS"</programlisting> </question> <answer> - <para>By default, &man.mount.8; will attempt to mount the last - data track (session) of a CD. If you would like to load an - earlier session, you must use the <option>-s</option> - command line argument. Please see &man.mount.cd9660.8; for - specific examples.</para> + <para>By default, &man.mount.8; will attempt to mount the + last data track (session) of a CD. If you would like to + load an earlier session, you must use the + <option>-s</option> command line argument. Please see + &man.mount.cd9660.8; for specific examples.</para> </answer> </qandaentry> @@ -3583,16 +3610,16 @@ C:\="DOS"</programlisting> </question> <answer> - <para>As <systemitem class="username">root</systemitem> set the sysctl variable - <varname>vfs.usermount</varname> to + <para>As <systemitem class="username">root</systemitem> set + the sysctl variable <varname>vfs.usermount</varname> to <literal>1</literal>.</para> <screen>&prompt.root; <userinput>sysctl vfs.usermount=1</userinput></screen> <para>To make this persist across reboots, add the line <literal>vfs.usermount=1</literal> to - <filename>/etc/sysctl.conf</filename> so that - it is reset at system boot time.</para> + <filename>/etc/sysctl.conf</filename> so that it is reset + at system boot time.</para> <para>Users can only mount devices they have read permissions to. To allow users to mount a device @@ -3606,8 +3633,8 @@ C:\="DOS"</programlisting> own /dev/da0 root:operator perm /dev/da0 0666</programlisting> - <para>All users can now mount devices they could read - onto a directory that they own:</para> + <para>All users can now mount devices they could read onto a + directory that they own:</para> <screen>&prompt.user; <userinput>mkdir ~/my-mount-point</userinput> &prompt.user; <userinput>mount -t msdosfs /dev/da0 ~/my-mount-point</userinput></screen> @@ -3616,14 +3643,15 @@ C:\="DOS"</programlisting> <screen>&prompt.user; <userinput>umount ~/my-mount-point</userinput></screen> - <para>Enabling <varname>vfs.usermount</varname>, however, has - negative security implications. A better way to access - &ms-dos; formatted media is to use the <package>emulators/mtools</package> package in the - Ports Collection.</para> + <para>Enabling <varname>vfs.usermount</varname>, however, + has negative security implications. A better way to + access &ms-dos; formatted media is to use the + <package>emulators/mtools</package> package in the Ports + Collection.</para> <note> - <para>The device name used in the previous examples must be - changed according to your configuration.</para> + <para>The device name used in the previous examples must + be changed according to your configuration.</para> </note> </answer> </qandaentry> @@ -3637,19 +3665,19 @@ C:\="DOS"</programlisting> <answer> <para>You need to understand what <command>du</command> and - <command>df</command> really do. <command>du</command> goes - through the directory tree, measures how large each file is, - and presents the totals. <command>df</command> just asks - the file system how much space it has left. They seem to be - the same thing, but a file without a directory entry will - affect <command>df</command> but not + <command>df</command> really do. <command>du</command> + goes through the directory tree, measures how large each + file is, and presents the totals. <command>df</command> + just asks the file system how much space it has left. + They seem to be the same thing, but a file without a + directory entry will affect <command>df</command> but not <command>du</command>.</para> - <para>When a program is using a file, and you delete the file, - the file is not really removed from the file system until - the program stops using it. The file is immediately deleted - from the directory listing, however. You can see this - easily enough with a program such as + <para>When a program is using a file, and you delete the + file, the file is not really removed from the file system + until the program stops using it. The file is immediately + deleted from the directory listing, however. You can see + this easily enough with a program such as <command>more</command>. Assume you have a file large enough that its presence affects the output of <command>du</command> and <command>df</command>. (Since @@ -3657,21 +3685,22 @@ C:\="DOS"</programlisting> <emphasis>very</emphasis> large file!) If you delete this file while using <command>more</command> on it, <command>more</command> does not immediately choke and - complain that it cannot view the file. The entry is simply - removed from the directory so no other program or user can - access it. <command>du</command> shows that it is gone - — it has walked the directory tree and the file is not - listed. <command>df</command> shows that it is still there, - as the file system knows that <command>more</command> is - still using that space. Once you end the - <command>more</command> session, <command>du</command> and - <command>df</command> will agree.</para> + complain that it cannot view the file. The entry is + simply removed from the directory so no other program or + user can access it. <command>du</command> shows that it + is gone — it has walked the directory tree and the + file is not listed. <command>df</command> shows that it + is still there, as the file system knows that + <command>more</command> is still using that space. Once + you end the <command>more</command> session, + <command>du</command> and <command>df</command> will + agree.</para> <para>This situation is common on web servers. Many people - set up a &os; web server and forget to rotate the log files. - The access log fills up <filename>/var</filename>. The new - administrator deletes the file, but the system still - complains that the partition is full. Stopping and + set up a &os; web server and forget to rotate the log + files. The access log fills up <filename>/var</filename>. + The new administrator deletes the file, but the system + still complains that the partition is full. Stopping and restarting the web server program would free the file, allowing the system to release the disk space. To prevent this from happening, set up &man.newsyslog.8;.</para> @@ -3688,8 +3717,11 @@ C:\="DOS"</programlisting> </question> <answer> - <para>In the <link xlink:href="&url.books.handbook;/config-tuning.html">Configuration and Tuning</link> - section of the Handbook, you will find a <link xlink:href="&url.books.handbook;/adding-swap-space.html">section</link> + <para>In the <link + xlink:href="&url.books.handbook;/config-tuning.html">Configuration + and Tuning</link> section of the Handbook, you will find + a <link + xlink:href="&url.books.handbook;/adding-swap-space.html">section</link> describing how to do this.</para> </answer> </qandaentry> @@ -3705,32 +3737,34 @@ C:\="DOS"</programlisting> bytes each, whereas &os; calculates them as 1,073,741,824 bytes each. This explains why, for example, &os;'s boot messages will report a disk that - supposedly has 80 GB as holding 76,319 MB.</para> + supposedly has 80 GB as holding + 76,319 MB.</para> - <para>Also note that &os; will (by default) <link linkend="disk-more-than-full">reserve</link> 8% of the disk - space.</para> + <para>Also note that &os; will (by default) <link + linkend="disk-more-than-full">reserve</link> 8% of the + disk space.</para> </answer> </qandaentry> <qandaentry> <question xml:id="disk-more-than-full"> - <para>How is it possible for a partition to be more than 100% - full?</para> + <para>How is it possible for a partition to be more than + 100% full?</para> </question> <answer> <para>A portion of each UFS partition (8%, by default) is reserved for use by the operating system and the - <systemitem class="username">root</systemitem> user. &man.df.1; does not count - that space when calculating the <literal>Capacity</literal> - column, so it can exceed 100%. Also, you will notice that - the <literal>Blocks</literal> column is always greater than - the sum of the <literal>Used</literal> and - <literal>Avail</literal> columns, usually by a factor of - 8%.</para> + <systemitem class="username">root</systemitem> user. + &man.df.1; does not count that space when calculating the + <literal>Capacity</literal> column, so it can exceed 100%. + Also, you will notice that the <literal>Blocks</literal> + column is always greater than the sum of the + <literal>Used</literal> and <literal>Avail</literal> + columns, usually by a factor of 8%.</para> - <para>For more details, look up <option>-m</option> - in &man.tunefs.8;.</para> + <para>For more details, look up <option>-m</option> in + &man.tunefs.8;.</para> </answer> </qandaentry> @@ -3744,10 +3778,9 @@ C:\="DOS"</programlisting> <para>&os; does a short memory test early in the boot process. This test usually only takes several seconds, however if the system has many 10s or 100s of gigabytes - of memory it can take up to a few minutes. This test - can be disabled by setting - <literal>hw.memtest.tests</literal> to - <literal>0</literal> in + of memory it can take up to a few minutes. This test can + be disabled by setting <literal>hw.memtest.tests</literal> + to <literal>0</literal> in <filename>/boot/loader.conf</filename>.</para> <para>For more details, see &man.loader.conf.5;.</para> @@ -3780,16 +3813,16 @@ C:\="DOS"</programlisting> <para>The <acronym>ZIL</acronym> ((<acronym>ZFS</acronym> intent log) is a write log used to implement posix write commitment semantics across crashes. Normally writes - are bundled up into transaction groups - and written to disk when filled (<quote>Transaction Group + are bundled up into transaction groups and written to + disk when filled (<quote>Transaction Group Commit</quote>). However syscalls like &man.fsync.2; require a commitment that the data is written to stable - storage before returning. - The ZIL is needed for writes that have been acknowledged - as written but which are not yet on disk as part of a - transaction. The transaction groups are timestamped. - In the event of a crash the last valid timestamp is - found and missing data is merged in from the ZIL.</para> + storage before returning. The ZIL is needed for writes + that have been acknowledged as written but which are not + yet on disk as part of a transaction. The transaction + groups are timestamped. In the event of a crash the + last valid timestamp is found and missing data is merged + in from the ZIL.</para> </answer> </qandaentry> @@ -3816,17 +3849,16 @@ C:\="DOS"</programlisting> <answer> <para>The <acronym>L2ARC</acronym> is a read cache stored on a fast device such as an <acronym>SSD</acronym>. - This cache is not persistent across - reboots. Note that RAM is used as the first layer - of cache and the L2ARC is only needed if there is - insufficient RAM.</para> + This cache is not persistent across reboots. Note that + RAM is used as the first layer of cache and the L2ARC is + only needed if there is insufficient RAM.</para> <para>L2ARC needs space in the ARC to index it. So, perversely, a working set that fits perfectly in the ARC will not fit perfectly any more if a L2ARC is used because part of the ARC is holding the L2ARC index, - pushing part of the working set into the - L2ARC which is slower than RAM.</para> + pushing part of the working set into the L2ARC which is + slower than RAM.</para> </answer> </qandaentry> @@ -3838,20 +3870,20 @@ C:\="DOS"</programlisting> <answer> <para>Generally speaking, no.</para> - <para>Deduplication takes up a significant amount - of RAM and may slow down read and write - disk access times. Unless one is storing data that is - very heavily duplicated (such as virtual machine images, - or user backups) it is possible that deduplication will - do more harm than good. Another consideration is the - inability to revert deduplication status. If data is - written when deduplication is enabled, disabling dedup - will not cause those blocks which were deduplicated to - be replicated until they are next modified.</para> + <para>Deduplication takes up a significant amount of RAM + and may slow down read and write disk access times. + Unless one is storing data that is very heavily + duplicated (such as virtual machine images, or user + backups) it is possible that deduplication will do more + harm than good. Another consideration is the inability + to revert deduplication status. If data is written when + deduplication is enabled, disabling dedup will not cause + those blocks which were deduplicated to be replicated + until they are next modified.</para> <para>Deduplication can also lead to some unexpected - situations. In particular deleting files may become much - slower.</para> + situations. In particular deleting files may become + much slower.</para> </answer> </qandaentry> @@ -3863,20 +3895,20 @@ C:\="DOS"</programlisting> <answer> <para>This could happen because the pool is 100% full. - ZFS requires space on the disk to write - transaction metadata. To restore the pool *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201405121842.s4CIg3x2091889>