Date: Tue, 13 May 2014 03:34:52 +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: r44818 - head/en_US.ISO8859-1/books/faq Message-ID: <201405130334.s4D3YqK1028153@svn.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: dru Date: Tue May 13 03:34:52 2014 New Revision: 44818 URL: http://svnweb.freebsd.org/changeset/doc/44818 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 18:42:03 2014 (r44817) +++ head/en_US.ISO8859-1/books/faq/book.xml Tue May 13 03:34:52 2014 (r44818) @@ -4247,32 +4247,36 @@ options SYSVMSG # enable for </question> <answer> - <para>The <link xlink:href="http://www.sendmail.org/"><application>sendmail</application></link>; - server is the default mail-server software for &os;, but you - can easily replace it with one of the other MTA (for + <para>The <link + xlink:href="http://www.sendmail.org/"><application>sendmail</application></link>; + server is the default mail-server software for &os;, but + you can easily replace it with one of the other MTA (for instance, an MTA installed from the ports).</para> <para>There are various alternative MTAs in the ports tree already, with <package>mail/exim</package>, - <package>mail/postfix</package>, <package>mail/qmail</package>, and <package>mail/zmailer</package> being some of the - most popular choices.</para> + <package>mail/postfix</package>, + <package>mail/qmail</package>, and + <package>mail/zmailer</package> being some of the most + popular choices.</para> <para>Diversity is nice, and the fact that you have many different mail-servers to chose from is considered a good thing; therefore try to avoid asking questions like <quote>Is <application>sendmail</application> better than <application>qmail</application>?</quote> in the mailing - lists. If you do feel like asking, first check the mailing - list archives. The advantages and disadvantages of each and - every one of the available MTAs have already been discussed - a few times.</para> + lists. If you do feel like asking, first check the + mailing list archives. The advantages and disadvantages + of each and every one of the available MTAs have already + been discussed a few times.</para> </answer> </qandaentry> <qandaentry> <question xml:id="forgot-root-pw"> - <para>I have forgotten the <systemitem class="username">root</systemitem> password! - What do I do?</para> + <para>I have forgotten the <systemitem + class="username">root</systemitem> password! What do I + do?</para> </question> <answer> @@ -4281,27 +4285,29 @@ options SYSVMSG # enable for <literal>Boot:</literal> prompt to enter Single User mode. At the question about the shell to use, hit <keycap>Enter</keycap>. You will be dropped to a - &prompt.root; prompt. Enter <command>mount -urw /</command> - to remount your root file system read/write, then run - <command>mount -a</command> to remount all the file systems. - Run <command>passwd root</command> to change the - <systemitem class="username">root</systemitem> password then run &man.exit.1; to - continue booting.</para> + &prompt.root; prompt. Enter <command>mount + -urw /</command> to remount your root file system + read/write, then run <command>mount -a</command> to + remount all the file systems. Run <command>passwd + root</command> to change the <systemitem + class="username">root</systemitem> password then run + &man.exit.1; to continue booting.</para> <note> - <para>If you are still prompted to give the - <systemitem class="username">root</systemitem> password when entering the - Single User mode, it means that the console has been - marked as <literal>insecure</literal> in + <para>If you are still prompted to give the <systemitem + class="username">root</systemitem> password when + entering the Single User mode, it means that the console + has been marked as <literal>insecure</literal> in <filename>/etc/ttys</filename>. In this case it will be required to boot from a &os; installation disk, choose the <guimenuitem>Live CD</guimenuitem> or - <guimenuitem>Shell</guimenuitem> at the beginning of the install - process and issue the commands mentioned above. You will need to - mount the specific partition in this case and then chroot to it, - i.e., replace <command>mount -urw /</command> by - <command>mount /dev/ada0p1 /mnt; chroot /mnt</command> for - a system on <replaceable>ada0p1</replaceable>.</para> + <guimenuitem>Shell</guimenuitem> at the beginning of the + install process and issue the commands mentioned above. + You will need to mount the specific partition in this + case and then chroot to it, i.e., replace <command>mount + -urw /</command> by <command>mount /dev/ada0p1 /mnt; + chroot /mnt</command> for a system on + <replaceable>ada0p1</replaceable>.</para> </note> <note> @@ -4310,21 +4316,23 @@ options SYSVMSG # enable for encrypted and it is impossible to mount them without the access keys. Your chances depend on the chosen implementation. For more information see the section - about encrypted disks in the &os; <link xlink:href="&url.books.handbook;/disks-encrypting.html">Handbook</link>.</para> + about encrypted disks in the &os; <link + xlink:href="&url.books.handbook;/disks-encrypting.html">Handbook</link>.</para> </note> </answer> </qandaentry> <qandaentry> <question xml:id="CAD-reboot"> - <para>How do I keep <keycombo action="simul"><keycap>Control</keycap><keycap>Alt</keycap><keycap>Delete</keycap></keycombo> + <para>How do I keep <keycombo + action="simul"><keycap>Control</keycap><keycap>Alt</keycap><keycap>Delete</keycap></keycombo> from rebooting the system?</para> </question> <answer> <para>If you are using &man.syscons.4; (the default console - driver) build and install a new kernel with the line in the - configuration file:</para> + driver) build and install a new kernel with the line in + the configuration file:</para> <programlisting>options SC_DISABLE_REBOOT</programlisting> @@ -4335,16 +4343,18 @@ options SYSVMSG # enable for <screen>&prompt.root; <userinput>sysctl hw.syscons.kbd_reboot=0</userinput></screen> <note> - <para>The above two methods are exclusive: The &man.sysctl.8; - does not exist if you compile your kernel with the - <literal>SC_DISABLE_REBOOT</literal> option.</para> + <para>The above two methods are exclusive: The + &man.sysctl.8; does not exist if you compile your kernel + with the <literal>SC_DISABLE_REBOOT</literal> + option.</para> </note> </answer> </qandaentry> <qandaentry> <question xml:id="dos-to-unix-txt"> - <para>How do I reformat DOS text files to &unix; ones?</para> + <para>How do I reformat DOS text files to &unix; + ones?</para> </question> <answer> @@ -4352,25 +4362,26 @@ options SYSVMSG # enable for <screen>&prompt.user; <userinput>perl -i.bak -npe 's/\r\n/\n/g' file(s)</userinput></screen> - <para>where <replaceable>file(s)</replaceable> is one or more - files to process. The modification is done in-place, with the - original file stored with a <filename>.bak</filename> - extension.</para> + <para>where <replaceable>file(s)</replaceable> is one or + more files to process. The modification is done in-place, + with the original file stored with a + <filename>.bak</filename> extension.</para> - <para>Alternatively you can use the &man.tr.1; command:</para> + <para>Alternatively you can use the &man.tr.1; + command:</para> <screen>&prompt.user; <userinput>tr -d '\r' < dos-text-file > unix-file</userinput></screen> <para><replaceable>dos-text-file</replaceable> is the file containing DOS text while <replaceable>unix-file</replaceable> will contain the - converted output. This can be quite a bit faster than using - <command>perl</command>.</para> + converted output. This can be quite a bit faster than + using <command>perl</command>.</para> - <para>Yet another way to reformat DOS text files is to use the - <package>converters/dosunix</package> port - from the Ports Collection. Consult its documentation about - the details.</para> + <para>Yet another way to reformat DOS text files is to use + the <package>converters/dosunix</package> port from the + Ports Collection. Consult its documentation about the + details.</para> </answer> </qandaentry> @@ -4411,73 +4422,77 @@ options SYSVMSG # enable for <emphasis>-STABLE</emphasis>, but got <emphasis>-BETA<replaceable>x</replaceable></emphasis>, <emphasis>-RC</emphasis> or - <emphasis>-PRERELEASE</emphasis>! What is going on?</para> + <emphasis>-PRERELEASE</emphasis>! What is going + on?</para> </question> <answer> <para>Short answer: it is just a name. <emphasis>RC</emphasis> stands for <quote>Release - Candidate</quote>. It signifies that a release is imminent. - In &os;, <emphasis>-PRERELEASE</emphasis> is typically - synonymous with the code freeze before a release. (For some - releases, the <emphasis>-BETA</emphasis> label was used in - the same way as <emphasis>-PRERELEASE</emphasis>.)</para> + Candidate</quote>. It signifies that a release is + imminent. In &os;, <emphasis>-PRERELEASE</emphasis> is + typically synonymous with the code freeze before a + release. (For some releases, the + <emphasis>-BETA</emphasis> label was used in the same way + as <emphasis>-PRERELEASE</emphasis>.)</para> <para>Long answer: &os; derives its releases from one of two places. Major, dot-zero, releases, such as 9.0-RELEASE - are branched from the head of the development - stream, commonly referred to as <link linkend="current">-CURRENT</link>. Minor releases, such as - 6.3-RELEASE or 5.2-RELEASE, have been snapshots of the + are branched from the head of the development stream, + commonly referred to as <link + linkend="current">-CURRENT</link>. Minor releases, such + as 6.3-RELEASE or 5.2-RELEASE, have been snapshots of the active <link linkend="stable">-STABLE</link> branch. - Starting with 4.3-RELEASE, each release also now has its own - branch which can be tracked by people requiring an extremely - conservative rate of development (typically only security - advisories).</para> + Starting with 4.3-RELEASE, each release also now has its + own branch which can be tracked by people requiring an + extremely conservative rate of development (typically only + security advisories).</para> <para>When a release is about to be made, the branch from which it will be derived from has to undergo a certain process. Part of this process is a code freeze. When a - code freeze is initiated, the name of the branch is changed - to reflect that it is about to become a release. For - example, if the branch used to be called 6.2-STABLE, its - name will be changed to 6.3-PRERELEASE to signify the code - freeze and signify that extra pre-release testing should be - happening. Bug fixes can still be committed to be part of - the release. When the source code is in shape for the - release the name will be changed to 6.3-RC to signify that a - release is about to be made from it. Once in the RC stage, - only the most critical bugs found can be fixed. Once the - release (6.3-RELEASE in this example) and release branch - have been made, the branch will be renamed to - 6.3-STABLE.</para> - - <para>For more information on version numbers and the various - Subversion branches, refer to the <link xlink:href="&url.articles.releng;/article.html">Release Engineering</link> - article.</para> + code freeze is initiated, the name of the branch is + changed to reflect that it is about to become a release. + For example, if the branch used to be called 6.2-STABLE, + its name will be changed to 6.3-PRERELEASE to signify the + code freeze and signify that extra pre-release testing + should be happening. Bug fixes can still be committed to + be part of the release. When the source code is in shape + for the release the name will be changed to 6.3-RC to + signify that a release is about to be made from it. Once + in the RC stage, only the most critical bugs found can be + fixed. Once the release (6.3-RELEASE in this example) and + release branch have been made, the branch will be renamed + to 6.3-STABLE.</para> + + <para>For more information on version numbers and the + various Subversion branches, refer to the <link + xlink:href="&url.articles.releng;/article.html">Release + Engineering</link> article.</para> </answer> </qandaentry> <qandaentry> <question xml:id="kernel-chflag-failure"> - <para>I tried to install a new kernel, and the &man.chflags.1; - failed. How do I get around this?</para> + <para>I tried to install a new kernel, and the + &man.chflags.1; failed. How do I get around this?</para> </question> <answer> - <para>Short answer: You are probably at security level greater - than 0. Reboot directly to Single User mode to install the - kernel.</para> + <para>Short answer: You are probably at security level + greater than 0. Reboot directly to Single User mode to + install the kernel.</para> <para>Long answer: &os; disallows changing system flags at - security levels greater than 0. You can check your security - level with the command:</para> + security levels greater than 0. You can check your + security level with the command:</para> <screen>&prompt.root; <userinput>sysctl kern.securelevel</userinput></screen> - <para>You cannot lower the security level; you have to boot to - Single Mode to install the kernel, or change the security - level in <filename>/etc/rc.conf</filename> then reboot. See - the &man.init.8; manual page for details on + <para>You cannot lower the security level; you have to boot + to Single Mode to install the kernel, or change the + security level in <filename>/etc/rc.conf</filename> then + reboot. See the &man.init.8; manual page for details on <literal>securelevel</literal>, and see <filename>/etc/defaults/rc.conf</filename> and the &man.rc.conf.5; manual page for more information on @@ -4492,20 +4507,20 @@ options SYSVMSG # enable for </question> <answer> - <para>Short answer: You are probably at security level greater - than 1. Reboot directly to Single User mode to change the - date.</para> + <para>Short answer: You are probably at security level + greater than 1. Reboot directly to Single User mode to + change the date.</para> <para>Long answer: &os; disallows changing the time by more - that one second at security levels greater than 1. You can - check your security level with the command:</para> + that one second at security levels greater than 1. You + can check your security level with the command:</para> <screen>&prompt.root; <userinput>sysctl kern.securelevel</userinput></screen> - <para>You cannot lower the security level; you have to boot to - Single User mode to change the date, or change the security - level in <filename>/etc/rc.conf</filename> then reboot. See - the &man.init.8; manual page for details on + <para>You cannot lower the security level; you have to boot + to Single User mode to change the date, or change the + security level in <filename>/etc/rc.conf</filename> then + reboot. See the &man.init.8; manual page for details on <literal>securelevel</literal>, and see <filename>/etc/defaults/rc.conf</filename> and the &man.rc.conf.5; manual page for more information on @@ -4515,8 +4530,8 @@ options SYSVMSG # enable for <qandaentry> <question xml:id="statd-mem-leak"> - <para>Why is <command>rpc.statd</command> using 256 MB of - memory?</para> + <para>Why is <command>rpc.statd</command> using 256 MB + of memory?</para> </question> <answer> @@ -4524,17 +4539,17 @@ options SYSVMSG # enable for 256 MB of memory. For convenience, <command>rpc.statd</command> maps an obscene amount of memory into its address space. There is nothing terribly - wrong with this from a technical standpoint; it just throws - off things like &man.top.1; and &man.ps.1;.</para> + wrong with this from a technical standpoint; it just + throws off things like &man.top.1; and &man.ps.1;.</para> <para>&man.rpc.statd.8; maps its status file (resident on <filename>/var</filename>) into its address space; to save - worrying about remapping it later when it needs to grow, it - maps it with a generous size. This is very evident from the - source code, where one can see that the length argument to - &man.mmap.2; is <literal>0x10000000</literal>, or one - sixteenth of the address space on an IA32, or exactly - 256 MB.</para> + worrying about remapping it later when it needs to grow, + it maps it with a generous size. This is very evident + from the source code, where one can see that the length + argument to &man.mmap.2; is <literal>0x10000000</literal>, + or one sixteenth of the address space on an IA32, or + exactly 256 MB.</para> </answer> </qandaentry> @@ -4546,9 +4561,9 @@ options SYSVMSG # enable for <answer> <para>You are running at an elevated (i.e., greater than 0) - securelevel. Lower the securelevel and try again. For more - information, see <link linkend="securelevel">the FAQ entry - on securelevel</link> and the &man.init.8; manual + securelevel. Lower the securelevel and try again. For + more information, see <link linkend="securelevel">the FAQ + entry on securelevel</link> and the &man.init.8; manual page.</para> </answer> </qandaentry> @@ -4556,17 +4571,17 @@ options SYSVMSG # enable for <qandaentry> <question xml:id="ssh-shosts"> <para>Why does <application>SSH</application> authentication - through <filename>.shosts</filename> not work by default in - recent versions of &os;?</para> + through <filename>.shosts</filename> not work by default + in recent versions of &os;?</para> </question> <answer> <para>The reason why <filename>.shosts</filename> authentication does not work by default in more recent versions of &os; is because &man.ssh.1; is not installed - suid <systemitem class="username">root</systemitem> by default. To - <quote>fix</quote> this, you can do one of the - following:</para> + suid <systemitem class="username">root</systemitem> by + default. To <quote>fix</quote> this, you can do one of + the following:</para> <itemizedlist> <listitem> @@ -4580,9 +4595,9 @@ options SYSVMSG # enable for <listitem> <para>As a temporary fix, change the mode on <filename>/usr/bin/ssh</filename> to - <literal>4555</literal> by running - <command>chmod 4555 /usr/bin/ssh</command> as - <systemitem class="username">root</systemitem>.</para> + <literal>4555</literal> by running <command>chmod 4555 + /usr/bin/ssh</command> as <systemitem + class="username">root</systemitem>.</para> </listitem> </itemizedlist> </answer> @@ -4595,10 +4610,10 @@ options SYSVMSG # enable for <answer> <para><literal>vnlru</literal> flushes and frees vnodes when - the system hits the <varname>kern.maxvnodes</varname> limit. - This kernel thread sits mostly idle, and only activates if - you have a huge amount of RAM and are accessing tens of - thousands of tiny files.</para> + the system hits the <varname>kern.maxvnodes</varname> + limit. This kernel thread sits mostly idle, and only + activates if you have a huge amount of RAM and are + accessing tens of thousands of tiny files.</para> </answer> </qandaentry> @@ -4624,49 +4639,51 @@ options SYSVMSG # enable for <listitem> <para><literal>Cache</literal>: (most often) pages that have percolated from inactive to a status where they - maintain their data, but can often be immediately reused - (either with their old association, or reused with a new - association). There can be certain immediate transitions - from <literal>active</literal> to - <literal>cache</literal> state if the page is known to - be clean (unmodified), but that transition is a matter - of policy, depending upon the algorithm choice of the VM - system maintainer.</para> + maintain their data, but can often be immediately + reused (either with their old association, or reused + with a new association). There can be certain + immediate transitions from <literal>active</literal> + to <literal>cache</literal> state if the page is known + to be clean (unmodified), but that transition is a + matter of policy, depending upon the algorithm choice + of the VM system maintainer.</para> </listitem> <listitem> - <para><literal>Free</literal>: pages without data content, - and can be immediately used in certain circumstances - where cache pages might be ineligible. Free pages can - be reused at interrupt or process + <para><literal>Free</literal>: pages without data + content, and can be immediately used in certain + circumstances where cache pages might be ineligible. + Free pages can be reused at interrupt or process state.</para> </listitem> <listitem> - <para><literal>Wired</literal>: pages that are fixed into - memory, usually for kernel purposes, but also sometimes - for special use in processes.</para> + <para><literal>Wired</literal>: pages that are fixed + into memory, usually for kernel purposes, but also + sometimes for special use in processes.</para> </listitem> </itemizedlist> - <para>Pages are most often written to disk (sort of a VM sync) - when they are in the inactive state, but active pages can - also be synced. This depends upon the CPU tracking of the - modified bit being available, and in certain situations - there can be an advantage for a block of VM pages to be - synced, whether they are active or inactive. In most common - cases, it is best to think of the inactive queue to be a - queue of relatively unused pages that might or might not be - in the process of being written to disk. Cached pages are - already synced, not mapped, but available for immediate - process use with their old association or with a new - association. Free pages are available at interrupt level, - but cached or free pages can be used at process state for - reuse. Cache pages are not adequately locked to be - available at interrupt level.</para> + <para>Pages are most often written to disk (sort of a VM + sync) when they are in the inactive state, but active + pages can also be synced. This depends upon the CPU + tracking of the modified bit being available, and in + certain situations there can be an advantage for a block + of VM pages to be synced, whether they are active or + inactive. In most common cases, it is best to think of + the inactive queue to be a queue of relatively unused + pages that might or might not be in the process of being + written to disk. Cached pages are already synced, not + mapped, but available for immediate process use with their + old association or with a new association. Free pages are + available at interrupt level, but cached or free pages can + be used at process state for reuse. Cache pages are not + adequately locked to be available at interrupt + level.</para> <para>There are some other flags (e.g., busy flag or busy - count) that might modify some of the described rules.</para> + count) that might modify some of the described + rules.</para> </answer> </qandaentry> @@ -4680,16 +4697,16 @@ options SYSVMSG # enable for <para>There are a couple of kinds of <quote>free memory</quote>. One kind is the amount of memory immediately available without paging anything else out. - That is approximately the size of cache queue + size of free - queue (with a derating factor, depending upon system - tuning). Another kind of <quote>free memory</quote> is the - total amount of <acronym>VM</acronym> space. That can be - complex, but is dependent upon the amount of swap space and - memory. Other kinds of <quote>free memory</quote> - descriptions are also possible, but it is relatively useless - to define these, but rather it is important to make sure - that the paging rate is kept low, and to avoid running out - of swap space.</para> + That is approximately the size of cache queue + size of + free queue (with a derating factor, depending upon system + tuning). Another kind of <quote>free memory</quote> is + the total amount of <acronym>VM</acronym> space. That can + be complex, but is dependent upon the amount of swap space + and memory. Other kinds of <quote>free memory</quote> + descriptions are also possible, but it is relatively + useless to define these, but rather it is important to + make sure that the paging rate is kept low, and to avoid + running out of swap space.</para> </answer> </qandaentry> @@ -4700,24 +4717,26 @@ options SYSVMSG # enable for </question> <answer> - <para><filename>/var/empty</filename> is a directory that the - &man.sshd.8; program uses when performing privilege separation. - The <filename>/var/empty</filename> directory is empty, owned by - <systemitem class="username">root</systemitem> and has the <literal>schg</literal> - flag set.</para> - - <para>Although it is not recommended to delete this directory, to - do so you will need to unset the <literal>schg</literal> flag - first. See the &man.chflags.1; manual page for more information - (and bear in mind the answer to - <link linkend="unsetting-schg">the question on unsetting the schg flag</link>).</para> + <para><filename>/var/empty</filename> is a directory that + the &man.sshd.8; program uses when performing privilege + separation. The <filename>/var/empty</filename> + directory is empty, owned by <systemitem + class="username">root</systemitem> and has the + <literal>schg</literal> flag set.</para> + + <para>Although it is not recommended to delete this + directory, to do so you will need to unset the + <literal>schg</literal> flag first. See the + &man.chflags.1; manual page for more information (and bear + in mind the answer to <link linkend="unsetting-schg">the + question on unsetting the schg flag</link>).</para> </answer> </qandaentry> <qandaentry> <question xml:id="newsyslog-expectations"> <para>I just changed - <filename>/etc/newsyslog.conf</filename>. How can I check + <filename>/etc/newsyslog.conf</filename>. How can I check if it does what I expect?</para> </question> @@ -4752,14 +4771,16 @@ options SYSVMSG # enable for </question> <answer> - <para>The X Window System (commonly <literal>X11</literal>) is - the most widely available windowing system capable of running - on &unix; or &unix; like systems, including &os;. - <link xlink:href="http://www.x.org/wiki/">The X.Org Foundation</link> - administers the <link xlink:href="http://en.wikipedia.org/wiki/X_Window_System_core_protocol">X protocol standards</link>, - with the current reference implementation, version 11 - release &xorg.version;, so you will often see references - shortened to <literal>X11</literal>.</para> + <para>The X Window System (commonly <literal>X11</literal>) + is the most widely available windowing system capable of + running on &unix; or &unix; like systems, including + &os;. <link xlink:href="http://www.x.org/wiki/">The X.Org + Foundation</link> administers the <link + xlink:href="http://en.wikipedia.org/wiki/X_Window_System_core_protocol">X + protocol standards</link>, with the current reference + implementation, version 11 release &xorg.version;, so you + will often see references shortened to + <literal>X11</literal>.</para> <para>Many implementations are available for different architectures and operating systems. An implementation of @@ -4787,13 +4808,16 @@ options SYSVMSG # enable for <screen><userinput>&prompt.root; pkg_add -r xorg</userinput></screen> - <para>or on systems using <application>pkg</application>:</para> + <para>or on systems using + <application>pkg</application>:</para> <screen><userinput>&prompt.root; pkg install xorg</userinput></screen> - <para>After the installation of &xorg;, follow - the instructions from the <link xlink:href="&url.books.handbook;/x-config.html">X11 Configuration</link> section of - the &os; Handbook.</para> + <para>After the installation of &xorg;, follow the + instructions from the <link + xlink:href="&url.books.handbook;/x-config.html">X11 + Configuration</link> section of the &os; + Handbook.</para> </answer> </qandaentry> @@ -4801,27 +4825,24 @@ options SYSVMSG # enable for <question xml:id="running-X-securelevels"> <para>I <emphasis>tried</emphasis> to run X, but I get a <errorname>No devices detected.</errorname> error when I - type - <command>startx</command>. What do I do now?</para> + type <command>startx</command>. What do I do now?</para> </question> <answer> <para>Your system is probably running at a raised - <literal>securelevel</literal>. It is not possible to start X - at a raised <literal>securelevel</literal> because X - requires write access to &man.io.4;. For more information, - see at the &man.init.8; manual page.</para> + <literal>securelevel</literal>. It is not possible to + start X at a raised <literal>securelevel</literal> because + X requires write access to &man.io.4;. For more + information, see at the &man.init.8; manual page.</para> - <para>There are two solutions to the problem: - Set your + <para>There are two solutions to the problem: Set your <literal>securelevel</literal> back down to zero (usually in <filename>/etc/rc.conf</filename>), or run &man.xdm.1; - (or an alternative display manager) - at boot time (before the <literal>securelevel</literal> is - raised).</para> + (or an alternative display manager) at boot time (before + the <literal>securelevel</literal> is raised).</para> - <para>See <xref linkend="xdm-boot"/> for more information about - running &man.xdm.1; at boot time.</para> + <para>See <xref linkend="xdm-boot"/> for more information + about running &man.xdm.1; at boot time.</para> </answer> </qandaentry> @@ -4832,14 +4853,15 @@ options SYSVMSG # enable for <answer> <para>If you are using &man.syscons.4; (the default console - driver), you can configure &os; to support a mouse pointer on - each virtual screen. To avoid conflicting with X, + driver), you can configure &os; to support a mouse pointer + on each virtual screen. To avoid conflicting with X, &man.syscons.4; supports a virtual device called <filename>/dev/sysmouse</filename>. All mouse events received from the real mouse device are written to the &man.sysmouse.4; device via &man.moused.8;. To use your mouse on one or more virtual consoles, - <emphasis>and</emphasis> use X, see <xref linkend="moused" remap="another section"/> and set up + <emphasis>and</emphasis> use X, see <xref + linkend="moused" remap="another section"/> and set up &man.moused.8;.</para> <para>Then edit <filename>/etc/X11/xorg.conf</filename> and @@ -4853,9 +4875,9 @@ options SYSVMSG # enable for <para>Starting with &xorg; version 7.4, the <literal>InputDevice</literal> sections in <filename>xorg.conf</filename> are ignored in favor of - autodetected devices. To restore the old behavior, add the - following line to the <literal>ServerLayout</literal> or - <literal>ServerFlags</literal> section:</para> + autodetected devices. To restore the old behavior, add + the following line to the <literal>ServerLayout</literal> + or <literal>ServerFlags</literal> section:</para> <programlisting>Option "AutoAddDevices" "false"</programlisting> @@ -4870,8 +4892,8 @@ options SYSVMSG # enable for <programlisting>link sysmouse mouse</programlisting> <para>This link can be created by restarting &man.devfs.5; - with the following command (as - <systemitem class="username">root</systemitem>):</para> + with the following command (as <systemitem + class="username">root</systemitem>):</para> <screen>&prompt.root; <userinput>service devfs restart</userinput></screen> </answer> @@ -4890,12 +4912,12 @@ options SYSVMSG # enable for and <literal>ZAxisMapping 4 5</literal> to the <quote>InputDevice</quote> section of <filename>/etc/X11/xorg.conf</filename>. For example, you - might have the following <quote>InputDevice</quote> section - in <filename>/etc/X11/xorg.conf</filename>.</para> + might have the following <quote>InputDevice</quote> + section in <filename>/etc/X11/xorg.conf</filename>.</para> <example> - <title><quote>InputDevice</quote> Section for Wheeled Mouse - in &xorg; Configuration File</title> + <title><quote>InputDevice</quote> Section for Wheeled + Mouse in &xorg; Configuration File</title> <programlisting>Section "InputDevice" Identifier "Mouse1" @@ -4920,18 +4942,18 @@ EndSection</programlisting> <qandaentry> <question xml:id="x-and-synaptic"> - <para>My laptop has a Synaptics touchpad. Can I use - it in X?</para> + <para>My laptop has a Synaptics touchpad. Can I use it in + X?</para> </question> <answer> - <para>Yes, you will have to configure a few things to - make it work.</para> + <para>Yes, you will have to configure a few things to make + it work.</para> <para>If you plan to use the Xorg synaptics driver you <emphasis>must</emphasis> remove moused_enable from - <filename>rc.conf</filename>. Xorg can not use - the synaptics mouse if the moused already sits on + <filename>rc.conf</filename>. Xorg can not use the + synaptics mouse if the moused already sits on <filename>/dev/psm0</filename>.</para> <para>To enable synaptics in the &man.psm.4; driver you need @@ -4976,35 +4998,43 @@ EndSection</programlisting> <qandaentry> <question xml:id="virtual-console"> - <para>What is a virtual console and how do I make more?</para> + <para>What is a virtual console and how do I make + more?</para> </question> <answer> - <para>Virtual consoles, put simply, enable you to have several - simultaneous sessions on the same machine without doing - anything complicated like setting up a network or running - X.</para> + <para>Virtual consoles, put simply, enable you to have + several simultaneous sessions on the same machine without + doing anything complicated like setting up a network or + running X.</para> <para>When the system starts, it will display a login prompt - on the monitor after displaying all the boot messages. You - can then type in your login name and password and start - working (or playing!) on the first virtual console.</para> + on the monitor after displaying all the boot messages. + You can then type in your login name and password and + start working (or playing!) on the first virtual + console.</para> <para>At some point, you will probably wish to start another - session, perhaps to look at documentation for a program you - are running or to read your mail while waiting for an FTP - transfer to finish. Just do <keycombo action="simul"><keycap>Alt</keycap><keycap>F2</keycap></keycombo> + session, perhaps to look at documentation for a program + you are running or to read your mail while waiting for an + FTP transfer to finish. Just do <keycombo + action="simul"><keycap>Alt</keycap><keycap>F2</keycap></keycombo> (hold down <keycap>Alt</keycap> and press <keycap>F2</keycap>), and you will find a login prompt waiting for you on the second <quote>virtual - console</quote>! When you want to go back to the original - session, do <keycombo action="simul"><keycap>Alt</keycap><keycap>F1</keycap></keycombo>.</para> - - <para>The default &os; installation has eight virtual consoles - enabled. <keycombo action="simul"><keycap>Alt</keycap><keycap>F1</keycap></keycombo>, - <keycombo action="simul"><keycap>Alt</keycap><keycap>F2</keycap></keycombo>, - <keycombo action="simul"><keycap>Alt</keycap><keycap>F3</keycap></keycombo>, - and so on will switch between these virtual consoles.</para> + console</quote>! When you want to go back to the + original session, do <keycombo + action="simul"><keycap>Alt</keycap><keycap>F1</keycap></keycombo>.</para> + + <para>The default &os; installation has eight virtual + consoles enabled. <keycombo + action="simul"><keycap>Alt</keycap><keycap>F1</keycap></keycombo>, + <keycombo + action="simul"><keycap>Alt</keycap><keycap>F2</keycap></keycombo>, + <keycombo + action="simul"><keycap>Alt</keycap><keycap>F3</keycap></keycombo>, + and so on will switch between these virtual + consoles.</para> <para>To enable more of them, edit <filename>/etc/ttys</filename> (see &man.ttys.5;) and add @@ -5021,8 +5051,8 @@ ttyvb "/usr/libexec/getty Pc" <para>Use as many or as few as you want. The more virtual terminals you have, the more resources that are used; this - can be important if you have 8 MB RAM or less. You may - also want to change the <literal>secure</literal> to + can be important if you have 8 MB RAM or less. You + may also want to change the <literal>secure</literal> to <literal>insecure</literal>.</para> <note> @@ -5036,11 +5066,12 @@ ttyvb "/usr/libexec/getty Pc" <important> <para>If you want to run an X server you <emphasis>must</emphasis> leave at least one virtual - terminal unused (or turned off) for it to use. That is to - say that if you want to have a login prompt pop up for all - twelve of your Alt-function keys, you are out of luck - — you can only do this for eleven of them if you - also want to run an X server on the same machine.</para> + terminal unused (or turned off) for it to use. That is + to say that if you want to have a login prompt pop up + for all twelve of your Alt-function keys, you are out of + luck — you can only do this for eleven of them if + you also want to run an X server on the same + machine.</para> </important> <para>The easiest way to disable a console is by turning it @@ -5066,14 +5097,15 @@ ttyvb "/usr/libexec/getty Pc" <para>Next, the easiest (and cleanest) way to activate the virtual consoles is to reboot. However, if you really do not want to reboot, you can just shut down the X Window - system and execute (as <systemitem class="username">root</systemitem>):</para> + system and execute (as <systemitem + class="username">root</systemitem>):</para> <screen>&prompt.root; <userinput>kill -HUP 1</userinput></screen> - <para>It is imperative that you completely shut down X Window - if it is running, before running this command. If you do not, - your system will probably appear to hang or lock up after - executing <command>kill</command>.</para> + <para>It is imperative that you completely shut down X + Window if it is running, before running this command. If + you do not, your system will probably appear to hang or + lock up after executing <command>kill</command>.</para> </answer> </qandaentry> @@ -5083,21 +5115,25 @@ ttyvb "/usr/libexec/getty Pc" </question> <answer> - <para>Use <keycombo action="simul"><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>F<replaceable>n</replaceable></keycap></keycombo> - to switch back to a virtual console. <keycombo action="simul"><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>F1</keycap></keycombo> + <para>Use <keycombo + action="simul"><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>F<replaceable>n</replaceable></keycap></keycombo> + to switch back to a virtual console. <keycombo + action="simul"><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>F1</keycap></keycombo> would return you to the first virtual console.</para> <para>Once you are back to a text console, you can then use - <keycombo action="simul"><keycap>Alt</keycap><keycap>F<replaceable>n</replaceable></keycap></keycombo> + <keycombo + action="simul"><keycap>Alt</keycap><keycap>F<replaceable>n</replaceable></keycap></keycombo> as normal to move between them.</para> <para>To return to the X session, you must switch to the virtual console running X. If you invoked X from the command line, (e.g., using <command>startx</command>) then the X session will attach to the next unused virtual - console, not the text console from which it was invoked. If - you have eight active virtual terminals then X will be - running on the ninth, and you would use <keycombo action="simul"><keycap>Alt</keycap><keycap>F9</keycap></keycombo> + console, not the text console from which it was invoked. + If you have eight active virtual terminals then X will be + running on the ninth, and you would use <keycombo + action="simul"><keycap>Alt</keycap><keycap>F9</keycap></keycombo> to return.</para> </answer> </qandaentry> @@ -5110,32 +5146,32 @@ ttyvb "/usr/libexec/getty Pc" <answer> <para>There are two schools of thought on how to start - &man.xdm.1;. One school starts <command>xdm</command> from - <filename>/etc/ttys</filename> (see &man.ttys.5;) using the - supplied example, while the other simply runs + &man.xdm.1;. One school starts <command>xdm</command> + from <filename>/etc/ttys</filename> (see &man.ttys.5;) + using the supplied example, while the other simply runs <command>xdm</command> from <filename>rc.local</filename> (see &man.rc.8;) or from an <filename>X</filename> script in - <filename>/usr/local/etc/rc.d</filename>. Both are equally - valid, and one may work in situations where the other does - not. In both cases the result is the same: X will pop up a - graphical login prompt.</para> - - <para>The &man.ttys.5; method has the advantage of documenting - which vty X will start on and passing the responsibility of - restarting the X server on logout to &man.init.8;. The - &man.rc.8; method makes it easy to <command>kill</command> - <command>xdm</command> if there is a problem starting the X - server.</para> - - <para>If loaded from &man.rc.8;, <command>xdm</command> should - be started without any arguments (i.e., as a daemon). - <command>xdm</command> must start + <filename>/usr/local/etc/rc.d</filename>. Both are + equally valid, and one may work in situations where the + other does not. In both cases the result is the same: X + will pop up a graphical login prompt.</para> + + <para>The &man.ttys.5; method has the advantage of + documenting which vty X will start on and passing the + responsibility of restarting the X server on logout to + &man.init.8;. The &man.rc.8; method makes it easy to + <command>kill</command> <command>xdm</command> if there is + a problem starting the X server.</para> + + <para>If loaded from &man.rc.8;, <command>xdm</command> + should be started without any arguments (i.e., as a + daemon). <command>xdm</command> must start <emphasis>after</emphasis> &man.getty.8; runs, or else <command>getty</command> and <command>xdm</command> will - conflict, locking out the console. The best way around this - is to have the script sleep 10 seconds or so then launch - <command>xdm</command>.</para> + conflict, locking out the console. The best way around + this is to have the script sleep 10 seconds or so then + launch <command>xdm</command>.</para> <para>If you are to start <command>xdm</command> from <filename>/etc/ttys</filename>, there still is a chance of @@ -5175,8 +5211,8 @@ ttyvb "/usr/libexec/getty Pc" machine with a VTY, the &man.fbtab.5; file exists to solve such problems.</para> - <para>In a nutshell, make sure an uncommented line of the form - is in <filename>/etc/fbtab</filename> (see + <para>In a nutshell, make sure an uncommented line of the + form is in <filename>/etc/fbtab</filename> (see &man.fbtab.5;):</para> <programlisting>/dev/ttyv0 0600 /dev/console</programlisting> @@ -5193,8 +5229,8 @@ ttyvb "/usr/libexec/getty Pc" </question> <answer> - <para>Your mouse and the mouse driver may have somewhat become - out of synchronization.</para> + <para>Your mouse and the mouse driver may have somewhat + become out of synchronization.</para> <para> In rare cases the driver may erroneously report synchronization problem and you may see the kernel @@ -5205,15 +5241,16 @@ ttyvb "/usr/libexec/getty Pc" <para>and notice that your mouse does not work properly.</para> - <para>If this happens, disable the synchronization check code - by setting the driver flags for the PS/2 mouse driver to - <literal>0x100</literal>. This can be easiest achieved + <para>If this happens, disable the synchronization check + code by setting the driver flags for the PS/2 mouse driver + to <literal>0x100</literal>. This can be easiest achieved by adding <screen>hint.psm.0.flags="0x100"</screen> to - <filename>/boot/loader.conf</filename> and rebooting.</para> + <filename>/boot/loader.conf</filename> and + rebooting.</para> </answer> </qandaentry> @@ -5240,8 +5277,10 @@ ttyvb "/usr/libexec/getty Pc" <answer> <para>The detailed answer for this question can be found in - the <link xlink:href="&url.books.handbook;/boot-blocks.html#boot-splash">Boot Time Splash Screens</link> *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201405130334.s4D3YqK1028153>