Date: Fri, 23 May 2014 14:25:48 +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: r44915 - head/en_US.ISO8859-1/books/handbook/bsdinstall Message-ID: <201405231425.s4NEPm5v071252@svn.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: dru Date: Fri May 23 14:25:48 2014 New Revision: 44915 URL: http://svnweb.freebsd.org/changeset/doc/44915 Log: White space fix only. Translators can ignore. Sponsored by: iXsystems Modified: head/en_US.ISO8859-1/books/handbook/bsdinstall/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/bsdinstall/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/bsdinstall/chapter.xml Fri May 23 14:06:31 2014 (r44914) +++ head/en_US.ISO8859-1/books/handbook/bsdinstall/chapter.xml Fri May 23 14:25:48 2014 (r44915) @@ -1547,7 +1547,7 @@ Ethernet address 0:3:ba:b:92:d4, Host ID <row> <entry><literal>freebsd-swap</literal></entry> <entry><literal>4G</literal></entry> - <entry/> + <entry></entry> <entry><literal>exswap</literal></entry> </row> @@ -2144,8 +2144,8 @@ Ethernet address 0:3:ba:b:92:d4, Host ID <sect2 xml:id="bsdinstall-timezone"> <title>Setting the Time Zone</title> - <para>The next menu asks if the system clock - uses <acronym>UTC</acronym> or local time. When in doubt, select + <para>The next menu asks if the system clock uses + <acronym>UTC</acronym> or local time. When in doubt, select <guibutton>[ No ]</guibutton> to choose the more commonly-used local time.</para> @@ -2160,16 +2160,16 @@ Ethernet address 0:3:ba:b:92:d4, Host ID </mediaobject> </figure> - <para>The next series of menus are used to determine the - correct local time by selecting the geographic region, country, - and time zone. Setting the time zone allows the system to + <para>The next series of menus are used to determine the correct + local time by selecting the geographic region, country, and + time zone. Setting the time zone allows the system to automatically correct for regional time changes, such as - daylight savings time, and - perform other time zone related functions properly.</para> + daylight savings time, and perform other time zone related + functions properly.</para> - <para>The example shown here is for a machine located in the Eastern - time zone of the United States. The selections will vary - according to the geographical location.</para> + <para>The example shown here is for a machine located in the + Eastern time zone of the United States. The selections will + vary according to the geographical location.</para> <figure xml:id="bsdinstall-timezone-region"> <title>Select a Region</title> @@ -2209,8 +2209,8 @@ Ethernet address 0:3:ba:b:92:d4, Host ID </mediaobject> </figure> - <para>The appropriate time zone is selected using the arrow - keys and pressing <keycap>Enter</keycap>.</para> + <para>The appropriate time zone is selected using the arrow keys + and pressing <keycap>Enter</keycap>.</para> <figure xml:id="bsdinstall-timezone-confirmation"> <title>Confirm Time Zone</title> @@ -2224,17 +2224,17 @@ Ethernet address 0:3:ba:b:92:d4, Host ID </figure> <para>Confirm the abbreviation for the time zone is correct. If - it is, press <keycap>Enter</keycap> to continue with - the post-installation configuration.</para> + it is, press <keycap>Enter</keycap> to continue with the + post-installation configuration.</para> </sect2> <sect2 xml:id="bsdinstall-sysconf"> <title>Enabling Services</title> <para>The next menu is used to configure which system services - will be started whenever the system boots. - All of these services are optional. Only start the services - that are needed for the system to function.</para> + will be started whenever the system boots. All of these + services are optional. Only start the services that are + needed for the system to function.</para> <figure xml:id="bsdinstall-config-serv"> <title>Selecting Additional Services to Enable</title> @@ -2253,9 +2253,9 @@ Ethernet address 0:3:ba:b:92:d4, Host ID <itemizedlist> <listitem> <para><literal>sshd</literal> - The Secure Shell - (<acronym>SSH</acronym>) daemon is used to remotely - access a system over an encrypted connection. Only enable - this service if the system should be available for remote + (<acronym>SSH</acronym>) daemon is used to remotely access + a system over an encrypted connection. Only enable this + service if the system should be available for remote logins.</para> </listitem> @@ -2284,9 +2284,9 @@ Ethernet address 0:3:ba:b:92:d4, Host ID <title>Enabling Crash Dumps</title> <para>The next menu is used to configure whether or not crash - dumps should be enabled. Enabling crash - dumps can be useful in debugging issues with the system, - so users are encouraged to enable crash dumps.</para> + dumps should be enabled. Enabling crash dumps can be useful + in debugging issues with the system, so users are encouraged + to enable crash dumps.</para> <figure xml:id="bsdinstall-config-crashdump"> <title>Enabling Crash Dumps</title> @@ -2305,11 +2305,11 @@ Ethernet address 0:3:ba:b:92:d4, Host ID <para>The next menu prompts to create at least one user account. It is recommended to login to the system using a user account - rather than as <systemitem - class="username">root</systemitem>. When logged in as - <systemitem class="username">root</systemitem>, there are - essentially no limits or protection on what can be done. - Logging in as a normal user is safer and more secure.</para> + rather than as <systemitem class="username">root</systemitem>. + When logged in as <systemitem + class="username">root</systemitem>, there are essentially no + limits or protection on what can be done. Logging in as a + normal user is safer and more secure.</para> <para>Select <guibutton>[ Yes ]</guibutton> to add new users.</para> @@ -2325,8 +2325,8 @@ Ethernet address 0:3:ba:b:92:d4, Host ID </figure> <para>Follow the prompts and input the requested information for - the user account. The example shown in <xref - linkend="bsdinstall-add-user2"/> creates the <systemitem + the user account. The example shown in <xref + linkend="bsdinstall-add-user2"/> creates the <systemitem class="username">asample</systemitem> user account.</para> <figure xml:id="bsdinstall-add-user2"> @@ -2344,16 +2344,17 @@ Ethernet address 0:3:ba:b:92:d4, Host ID <itemizedlist> <listitem> <para><literal>Username</literal> - The name the user will - enter to log in. A common convention is to use the first letter of the - first name combined with the last name, as long as each - username is unique for the system. The username is case - sensitive and should not contain any spaces.</para> + enter to log in. A common convention is to use the first + letter of the first name combined with the last name, as + long as each username is unique for the system. The + username is case sensitive and should not contain any + spaces.</para> </listitem> <listitem> - <para><literal>Full name</literal> - The user's full - name. This can contain spaces and is used as a - description for the user account.</para> + <para><literal>Full name</literal> - The user's full name. + This can contain spaces and is used as a description for + the user account.</para> </listitem> <listitem> @@ -2382,9 +2383,9 @@ Ethernet address 0:3:ba:b:92:d4, Host ID <listitem> <para><literal>Shell</literal> - Type in one of the listed - values to set the interactive shell for - the user. Refer to <xref linkend="shells"/> for more - information about shells.</para> + values to set the interactive shell for the user. Refer + to <xref linkend="shells"/> for more information about + shells.</para> </listitem> <listitem> @@ -2417,9 +2418,9 @@ Ethernet address 0:3:ba:b:92:d4, Host ID </listitem> <listitem> - <para><literal>Enter password</literal> - The - password for this user. Characters typed will not show on - the screen.</para> + <para><literal>Enter password</literal> - The password for + this user. Characters typed will not show on the + screen.</para> </listitem> <listitem> @@ -2429,15 +2430,15 @@ Ethernet address 0:3:ba:b:92:d4, Host ID <listitem> <para><literal>Lock out the account after - creation?</literal> - Typically - <literal>no</literal> so that the user can login.</para> + creation?</literal> - Typically <literal>no</literal> so + that the user can login.</para> </listitem> </itemizedlist> <para>After entering everything, a summary is shown for review. - If a mistake was made, enter <literal>no</literal> and try again. If - everything is correct, enter <literal>yes</literal> to create - the new user.</para> + If a mistake was made, enter <literal>no</literal> and try + again. If everything is correct, enter <literal>yes</literal> + to create the new user.</para> <figure xml:id="bsdinstall-add-user3"> <title>Exit User and Group Management</title> @@ -2548,47 +2549,45 @@ Ethernet address 0:3:ba:b:92:d4, Host ID </figure> <para>If further configuration or special setup is needed, - select <guibutton>[ Live CD ]</guibutton> - to boot the install media into Live <acronym>CD</acronym> + select <guibutton>[ Live CD ]</guibutton> to + boot the install media into Live <acronym>CD</acronym> mode.</para> <para>If the installation is complete, select <guibutton>[ Reboot ]</guibutton> to reboot the computer and start the new &os; system. Do not forget to - remove the &os; install media - or the computer may boot from it again.</para> + remove the &os; install media or the computer may boot from it + again.</para> - <para>As &os; boots, informational messages are - displayed. - After the system finishes booting, a login prompt is - displayed. At the <prompt>login:</prompt> prompt, enter the - username added during the installation. - Avoid logging in as <systemitem - class="username">root</systemitem>. Refer to <xref - linkend="users-superuser"/> for instructions on how to - become the superuser when administrative access is - needed.</para> - - <para>The messages that appeared during boot can be - reviewed by pressing <keycap>Scroll-Lock</keycap> to turn on - the scroll-back buffer. The - <keycap>PgUp</keycap>, <keycap>PgDn</keycap>, and arrow keys - can be used to scroll back through the messages. When finished, press - <keycap>Scroll-Lock</keycap> again to unlock the display and - return to the console. To review these messages once the - system has been up for some time, type - <command>less /var/run/dmesg.boot</command> from a command - prompt. Press <keycap>q</keycap> to return to the command - line after viewing.</para> - - <para>If <application>sshd</application> was enabled in <xref - linkend="bsdinstall-config-serv"/>, the first boot may be - a bit slower as the system will generate the <acronym>RSA</acronym> and - <acronym>DSA</acronym> keys. Subsequent boots will be - faster. The fingerprints of the keys will be displayed, as seen in - this example:</para> + <para>As &os; boots, informational messages are displayed. + After the system finishes booting, a login prompt is + displayed. At the <prompt>login:</prompt> prompt, enter the + username added during the installation. Avoid logging in as + <systemitem class="username">root</systemitem>. Refer to + <xref linkend="users-superuser"/> for instructions on how to + become the superuser when administrative access is + needed.</para> + + <para>The messages that appeared during boot can be reviewed by + pressing <keycap>Scroll-Lock</keycap> to turn on the + scroll-back buffer. The <keycap>PgUp</keycap>, + <keycap>PgDn</keycap>, and arrow keys can be used to scroll + back through the messages. When finished, press + <keycap>Scroll-Lock</keycap> again to unlock the display and + return to the console. To review these messages once the + system has been up for some time, type <command>less + /var/run/dmesg.boot</command> from a command prompt. Press + <keycap>q</keycap> to return to the command line after + viewing.</para> + + <para>If <application>sshd</application> was enabled in <xref + linkend="bsdinstall-config-serv"/>, the first boot may be + a bit slower as the system will generate the + <acronym>RSA</acronym> and <acronym>DSA</acronym> keys. + Subsequent boots will be faster. The fingerprints of the keys + will be displayed, as seen in this example:</para> - <screen>Generating public/private rsa1 key pair. + <screen>Generating public/private rsa1 key pair. Your identification has been saved in /etc/ssh/ssh_host_key. Your public key has been saved in /etc/ssh/ssh_host_key.pub. The key fingerprint is: @@ -2624,24 +2623,24 @@ The key's randomart image is: +-----------------+ Starting sshd.</screen> - <para>Refer to <xref linkend="openssh"/> for more information - about fingerprints and <acronym>SSH</acronym>.</para> + <para>Refer to <xref linkend="openssh"/> for more information + about fingerprints and <acronym>SSH</acronym>.</para> - <para>&os; does not install a graphical environment by default. - Refer to <xref linkend="x11"/> for more - information about installing and configuring a graphical - window manager.</para> + <para>&os; does not install a graphical environment by default. + Refer to <xref linkend="x11"/> for more information about + installing and configuring a graphical window manager.</para> <para>Proper shutdown of a &os; computer helps protect data and - hardware from damage. <emphasis>Do not turn off the power before - the system has been properly shut down!</emphasis> If the user is a - member of the <systemitem + hardware from damage. <emphasis>Do not turn off the power + before the system has been properly shut down!</emphasis> If + the user is a member of the <systemitem class="groupname">wheel</systemitem> group, become the superuser by typing <command>su</command> at the command line and entering the <systemitem class="username">root</systemitem> password. Then, type <command>shutdown -p now</command> and the system will shut - down cleanly, and if the hardware supports it, turn itself off.</para> + down cleanly, and if the hardware supports it, turn itself + off.</para> </sect2> </sect1> @@ -2656,90 +2655,88 @@ Starting sshd.</screen> troubleshooting, such as common problems people have reported.</para> - <para>Check the Hardware Notes (<link - xlink:href="&url.base;/releases/index.html">http://www.freebsd.org/releases/index.html</link>) - document for the version of &os; to make sure the hardware is - supported. If the hardware is supported and lock-ups or other - problems occur, build a custom kernel using the instructions - in <xref linkend="kernelconfig"/> to add support for devices - which are not present in the <filename>GENERIC</filename> - kernel. The default kernel assumes - that most hardware devices are in their factory default - configuration in terms of <acronym>IRQ</acronym>s, - <acronym>I/O</acronym> addresses, and <acronym>DMA</acronym> - channels. If the hardware has been reconfigured, a custom - kernel configuration file can tell &os; where to find - things.</para> - - <note> - <para>Some installation problems can be avoided or alleviated - by updating the firmware on various hardware components, - most notably the motherboard. Motherboard firmware is - usually referred to as the <acronym>BIOS</acronym>. Most - motherboard and computer manufacturers have a website for - upgrades and upgrade information.</para> - - <para>Manufacturers generally advise against upgrading the - motherboard <acronym>BIOS</acronym> unless there is a good - reason for doing so, like a critical update. The upgrade - process <emphasis>can</emphasis> go wrong, leaving the - <acronym>BIOS</acronym> incomplete and the computer - inoperative.</para> - </note> - - <para>If the system hangs while probing hardware during boot, - or it behaves strangely during install, - <acronym>ACPI</acronym> may be the culprit. &os; makes extensive use of the system - <acronym>ACPI</acronym> service on the &arch.i386;, &arch.amd64;, and - ia64 platforms to aid in system configuration if it is - detected during boot. Unfortunately, some bugs still - exist in both the <acronym>ACPI</acronym> driver and - within system motherboards and <acronym>BIOS</acronym> - firmware. <acronym>ACPI</acronym> can be disabled by - setting the <literal>hint.acpi.0.disabled</literal> hint - in the third stage boot loader:</para> - - <screen><userinput>set hint.acpi.0.disabled="1"</userinput></screen> - - <para>This is reset each time the system is booted, so it - is necessary to add - <literal>hint.acpi.0.disabled="1"</literal> to the file - <filename>/boot/loader.conf</filename>. More - information about the boot loader can be found in <xref - linkend="boot-synopsis"/>.</para> + <para>Check the Hardware Notes (<link + xlink:href="&url.base;/releases/index.html">http://www.freebsd.org/releases/index.html</link>) + document for the version of &os; to make sure the hardware is + supported. If the hardware is supported and lock-ups or other + problems occur, build a custom kernel using the instructions in + <xref linkend="kernelconfig"/> to add support for devices which + are not present in the <filename>GENERIC</filename> kernel. The + default kernel assumes that most hardware devices are in their + factory default configuration in terms of + <acronym>IRQ</acronym>s, <acronym>I/O</acronym> addresses, and + <acronym>DMA</acronym> channels. If the hardware has been + reconfigured, a custom kernel configuration file can tell &os; + where to find things.</para> + + <note> + <para>Some installation problems can be avoided or alleviated by + updating the firmware on various hardware components, most + notably the motherboard. Motherboard firmware is usually + referred to as the <acronym>BIOS</acronym>. Most motherboard + and computer manufacturers have a website for upgrades and + upgrade information.</para> + + <para>Manufacturers generally advise against upgrading the + motherboard <acronym>BIOS</acronym> unless there is a good + reason for doing so, like a critical update. The upgrade + process <emphasis>can</emphasis> go wrong, leaving the + <acronym>BIOS</acronym> incomplete and the computer + inoperative.</para> + </note> + + <para>If the system hangs while probing hardware during boot, or + it behaves strangely during install, <acronym>ACPI</acronym> may + be the culprit. &os; makes extensive use of the system + <acronym>ACPI</acronym> service on the &arch.i386;, + &arch.amd64;, and ia64 platforms to aid in system configuration + if it is detected during boot. Unfortunately, some bugs still + exist in both the <acronym>ACPI</acronym> driver and within + system motherboards and <acronym>BIOS</acronym> firmware. + <acronym>ACPI</acronym> can be disabled by setting the + <literal>hint.acpi.0.disabled</literal> hint in the third stage + boot loader:</para> + + <screen><userinput>set hint.acpi.0.disabled="1"</userinput></screen> + + <para>This is reset each time the system is booted, so it is + necessary to add <literal>hint.acpi.0.disabled="1"</literal> to + the file <filename>/boot/loader.conf</filename>. More + information about the boot loader can be found in <xref + linkend="boot-synopsis"/>.</para> </sect1> <sect1 xml:id="using-live-cd"> <title>Using the Live <acronym>CD</acronym></title> - <para>The welcome menu of <application>sysinstall</application>, shown in <xref - linkend="bsdinstall-choose-mode"/>, provides a - <guibutton>[ Live CD ]</guibutton> option. - This is useful for those who are still wondering whether &os; - is the right operating system for them and want to test some of - the features before installing.</para> - - <para>The following points should be noted before using the - <guibutton>[ Live CD ]</guibutton>:</para> - <itemizedlist> - <listitem> - <para>To gain access to the system, authentication is - required. The username is <systemitem - class="username">root</systemitem> and the password is - blank.</para> - </listitem> - - <listitem> - <para>As the system runs directly from the installation - media, performance will be significantly - slower than that of a system installed on a hard - disk.</para> - </listitem> - - <listitem> - <para>This option only provides a command - prompt and not a graphical interface.</para> - </listitem> - </itemizedlist> + <para>The welcome menu of <application>sysinstall</application>, + shown in <xref linkend="bsdinstall-choose-mode"/>, provides a + <guibutton>[ Live CD ]</guibutton> option. This + is useful for those who are still wondering whether &os; is the + right operating system for them and want to test some of the + features before installing.</para> + + <para>The following points should be noted before using the + <guibutton>[ Live CD ]</guibutton>:</para> + + <itemizedlist> + <listitem> + <para>To gain access to the system, authentication is + required. The username is <systemitem + class="username">root</systemitem> and the password is + blank.</para> + </listitem> + + <listitem> + <para>As the system runs directly from the installation media, + performance will be significantly slower than that of a + system installed on a hard disk.</para> + </listitem> + + <listitem> + <para>This option only provides a command prompt and not a + graphical interface.</para> + </listitem> + </itemizedlist> </sect1> </chapter>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201405231425.s4NEPm5v071252>