Sorry for the inconvenience.  Known Navigation header breakage, its being "rebuilt."
There may be other unforeseen breakage primarily in the handbook portion of the wiki.
The Table Of Contents section of each "PC-BSD® Users Handbook" page may be the best workaround.

Difference between revisions of "Talk:Dual Booting"

From PC-BSD Wiki
Jump to: navigation, search
m (boot0cfg)
(Grub 2: new section)
Line 9: Line 9:
 
From commandline:
 
From commandline:
 
  boot0cfg -B ada0
 
  boot0cfg -B ada0
 +
 +
== Grub 2 ==
 +
 +
I noticed the section on Grub 2 is a little out of date. The map command is a legacy command. In Grub 2, it was renamed to drivemap. Also, the device names changed slightly in Grub 2: the partitions of the hard drive are counted from '''1''' instead of 0: so, (hd0,msdos1) is the first partition of the first hard drive.
 +
 +
drivemap isn't actually needed to boot PC-BSD if it's on the second disk, at least for me. My menuentry is something like this:
 +
 +
<code>menuentry "PC-BSD 9.1" {<br />
 +
insmod ufs2<br />
 +
set root=(hd1,msdos1)<br />
 +
chainloader +1<br />
 +
}</code><br />

Revision as of 17:42, 1 January 2013

The option to install a boot loader during PC-BSD installation is no longer present in the GUI, hence the mods to the discussion around recovering from "accidental use" of that previously available option.


Unsure exactly how/where to fit this in:

boot0cfg

From commandline:

boot0cfg -B ada0

Grub 2

I noticed the section on Grub 2 is a little out of date. The map command is a legacy command. In Grub 2, it was renamed to drivemap. Also, the device names changed slightly in Grub 2: the partitions of the hard drive are counted from 1 instead of 0: so, (hd0,msdos1) is the first partition of the first hard drive.

drivemap isn't actually needed to boot PC-BSD if it's on the second disk, at least for me. My menuentry is something like this:

menuentry "PC-BSD 9.1" {
insmod ufs2
set root=(hd1,msdos1)
chainloader +1
}

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox