svn commit: r40800 - head/en_US.ISO8859-1/books/faq
Eitan Adler
eadler at FreeBSD.org
Tue Jan 29 13:41:09 UTC 2013
Author: eadler
Date: Tue Jan 29 13:41:08 2013
New Revision: 40800
URL: http://svnweb.freebsd.org/changeset/doc/40800
Log:
Modernize a number of questions as they relate to bsdinstall.
Also prefer ada over ad
Submitted by: nwhitehorn
Approved by: bcr (mentor)
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 Tue Jan 29 11:35:38 2013 (r40799)
+++ head/en_US.ISO8859-1/books/faq/book.xml Tue Jan 29 13:41:08 2013 (r40800)
@@ -1312,63 +1312,26 @@
</qandaentry>
<qandaentry>
- <question id="win95-damaged-boot-manager">
- <para>&windows; killed my boot manager! How do I get it
- back?</para>
+ <question id="bootmanager-restore">
+ <para>Another operating system destroyed my Boot Manager. How
+ do I get it back?</para>
</question>
<answer>
- <para>You can reinstall the boot manager &os; comes with in
- one of three ways:</para>
+ <para>This depends on what boot manager you have installed.
+ The &os; boot selection menu (likely what you are using
+ if you end up in this situation) can be reinstalled using
+ &man.boot0cfg.8;. For example, to restore the boot menu
+ onto the disk <replaceable>ada0</replaceable>:</para>
- <itemizedlist>
- <listitem>
- <para>Running DOS, go into the <filename
- class="directory">tools</filename> directory of your
- &os; distribution and look for
- <filename>bootinst.exe</filename>. You run it like
- so:</para>
-
- <screen><prompt>...\TOOLS></prompt> <userinput>bootinst.exe boot.bin</userinput></screen>
-
- <para>and the boot manager will be reinstalled.</para>
- </listitem>
+ <screen>&prompt.root; <userinput>boot0cfg -B ada0</userinput></screen>
- <listitem>
- <para>Boot the &os; boot floppy again and go to the
- <guimenuitem>Custom</guimenuitem> menu item for custom
- installation. Choose
- <guimenuitem>Partition</guimenuitem>. Select the drive
- which used to contain your boot manager (likely the
- first one) and when you come to the partition editor for
- it, as the very first thing (e.g., do not make any
- changes) press <keycap>W</keycap>. This will ask for
- confirmation, select &gui.yes;, and when you get the
- Boot Manager selection prompt, be sure to select the
- <application>&os; Boot Manager</application>. This will
- re-write the boot manager to disk. Now quit out of the
- installation menu and reboot off the hard disk as
- normal.</para>
- </listitem>
+ <para>The non-interactive MBR bootloader can be installed using
+ &man.gpart.8;:</para>
- <listitem>
- <para>Boot the &os; boot floppy (or CD-ROM) and choose the
- <guimenuitem>Fixit</guimenuitem> menu item. Select
- either the Fixit floppy or CD-ROM #2 (the
- <quote>live</quote> file system option) as appropriate
- and enter the fixit shell. Then execute the following
- command:</para>
-
- <screen><prompt>Fixit#</prompt> <userinput>fdisk -B -b /boot/boot0 <replaceable>bootdevice</replaceable></userinput></screen>
-
- <para>substituting <replaceable>bootdevice</replaceable>
- for your real boot device such as
- <devicename>ad0</devicename> (first IDE disk),
- <devicename>ad4</devicename> (first IDE disk on
- auxiliary controller), <devicename>da0</devicename>
- (first SCSI disk), etc.</para>
- </listitem>
- </itemizedlist>
+ <screen>&prompt.root; <userinput>gpart bootcode -b /boot/mbr ada0</userinput></screen>
+
+ <para>For more complex situations, including GPT disks, see &man.gpart.8;.</para>
</answer>
</qandaentry>
@@ -3310,10 +3273,9 @@ kern.sched.name: ULE</screen>
paragraph to find out how to move the data after doing
this.</para>
- <para>Should you decide not to do a fresh install, you need to
- partition and label the new disk with either
- &man.sysinstall.8;, or &man.fdisk.8; and &man.disklabel.8;.
- You should also install booteasy on both disks with
+ <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>
@@ -3355,12 +3317,12 @@ kern.sched.name: ULE</screen>
</procedure>
<para>For example, if you are going to move root to
- <devicename>/dev/<replaceable>ad1s1a</replaceable></devicename>,
+ <devicename>/dev/<replaceable>ada1s1a</replaceable></devicename>,
with <filename class="directory"><replaceable>/mnt</replaceable></filename> as
the temporary mount point, it is:</para>
- <screen>&prompt.root; <userinput>newfs /dev/<replaceable>ad1s1a</replaceable></userinput>
-&prompt.root; <userinput>mount /dev/<replaceable>ad1s1a</replaceable> <replaceable>/mnt</replaceable></userinput>
+ <screen>&prompt.root; <userinput>newfs /dev/<replaceable>ada1s1a</replaceable></userinput>
+&prompt.root; <userinput>mount /dev/<replaceable>ada1s1a</replaceable> <replaceable>/mnt</replaceable></userinput>
&prompt.root; <userinput>cd <replaceable>/mnt</replaceable></userinput>
&prompt.root; <userinput>dump 0af - / | restore rf -</userinput></screen>
@@ -3371,8 +3333,8 @@ kern.sched.name: ULE</screen>
as described above, then move the child partition into the
empty directory that the first move created:</para>
- <screen>&prompt.root; <userinput>newfs /dev/<replaceable>ad1s1a</replaceable></userinput>
-&prompt.root; <userinput>mount /dev/<replaceable>ad1s1a</replaceable> <replaceable>/mnt</replaceable></userinput>
+ <screen>&prompt.root; <userinput>newfs /dev/<replaceable>ada1s1a</replaceable></userinput>
+&prompt.root; <userinput>mount /dev/<replaceable>ada1s1a</replaceable> <replaceable>/mnt</replaceable></userinput>
&prompt.root; <userinput>cd <replaceable>/mnt</replaceable></userinput>
&prompt.root; <userinput>dump 0af - / | restore rf -</userinput>
&prompt.root; <userinput>cd var</userinput>
@@ -3384,11 +3346,11 @@ kern.sched.name: ULE</screen>
partition on the appropriate directory in the temporary
mount point, then move the old single partition:</para>
- <screen>&prompt.root; <userinput>newfs /dev/<replaceable>ad1s1a</replaceable></userinput>
-&prompt.root; <userinput>newfs /dev/<replaceable>ad1s1d</replaceable></userinput>
-&prompt.root; <userinput>mount /dev/<replaceable>ad1s1a</replaceable> <replaceable>/mnt</replaceable></userinput>
+ <screen>&prompt.root; <userinput>newfs /dev/<replaceable>ada1s1a</replaceable></userinput>
+&prompt.root; <userinput>newfs /dev/<replaceable>ada1s1d</replaceable></userinput>
+&prompt.root; <userinput>mount /dev/<replaceable>ada1s1a</replaceable> <replaceable>/mnt</replaceable></userinput>
&prompt.root; <userinput>mkdir <replaceable>/mnt</replaceable>/var</userinput>
-&prompt.root; <userinput>mount /dev/<replaceable>ad1s1d</replaceable> <replaceable>/mnt</replaceable>/var</userinput>
+&prompt.root; <userinput>mount /dev/<replaceable>ada1s1d</replaceable> <replaceable>/mnt</replaceable>/var</userinput>
&prompt.root; <userinput>cd <replaceable>/mnt</replaceable></userinput>
&prompt.root; <userinput>dump 0af - / | restore rf -</userinput></screen>
@@ -4594,9 +4556,13 @@ options SYSVMSG # enable for
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>Fixit</guimenuitem> shell from
- &man.sysinstall.8; and issue the commands mentioned
- above.</para>
+ 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>
</note>
<note>
More information about the svn-doc-all
mailing list