From: Indi on
On 2010-02-13, spooky130u(a)NOSPAM.gmail.com <spooky130u(a)NOSPAM.gmail.com> wrote:
>
> I just checked, and it seems to only work as a boot manager for dual-boot
> between windows vista and [whatever], and they specifically state that
> the boot manager in vista is different, and so on.
>
> How would I boot directly from the distribution's DVD (e.g., from the
> Fixit shell prompt)? I've forgotten (and I'm not sure I even CAN do
> this)....
>
> Later,
> --jim
>

EasyBCD works with 7 too, but maybe you have XP?
If so the FreeBSD boot manager works quite well for dual booting.
Check out
http://forums.freebsd.org/showthread.php?t=3737

I don't know how to use the install DVD to boot an existing install,
but I think you can use it to chroot in. It's been awhile since I did
it, but I do remember it's not at all hard if you have the livefs
install CD. In fact, ISTR that once you select the livefs option from
sysinstall one of the options is "rescue", and you can select your
root partition and all that. I'm not at home right now, or I'd pop in
the CD and look it up but I'm pretty sure you'll be able to fugure it
out easily, but you may need the livefs CD rather than the DVD installer.

--
indi

Google Groupers and X-posters are filtered. If you're not a troll
or a spammer then you might want to stop posting like one.
From: spooky130u on
In article <ZgIdn.87177$BV.5220(a)newsfe07.iad>,
<spooky130u(a)NOSPAM.gmail.com> wrote:
>
>In article <4b7716b2$1(a)news.broadpark.no>,
>Torfinn Ingolfsen <tingo(a)start.no> wrote:

>>Yes, this is possible. I wrote a quick tip about it here:
>>http://geekinfo.net/article.php?story=20070107031455259
>
>Thanks - I'll try it out, but probably not until morning.

Well, I did try it just now.... Everything worked great, until the boot.
Then I ended up right back at the mountroot> prompt...same error. I did
notice one thing, though: the boot messages did NOT show the error about
waiting for the usb bus ... and it DID load the kernel from the usb
drive...still didn't find root. It said to remove any errors in
/etc/fstab ... but I checked, and didn't find any (nor would I expect to
immediately after a fresh install).

Something very, very odd is going on here....

Thanks,
--jim

--
73 DE N5IAL (/4) MiSTie #49997 < Running FreeBSD 7.0 >
spooky130u(a)NOSPAM.gmail.com ICBM/Hurr.: 30.39735N 86.60439W

"Now what *you* need is a proper pint of porter poured in a proper
pewter porter pot.." --Peter Dalgaard in alt.sysadmin.recovery

From: Giorgos Keramidas on
On Sat, 13 Feb 2010 12:51:33 +0530, Balwinder S Dheeman <bsd.SANSPAM(a)cto.homelinux.net> wrote:
> On 02/13/2010 12:16 PM, Giorgos Keramidas wrote:
>> It should be ok to install on the /dev/da0 device. I have done this a
>> few times, so here are a few things you probably want to watch out for:
>>
>> * Some times, depending on the order the devices are detected at boot
>> time, the kernel may throw you at the "mountroot>" prompt when you
>> boot from a USB disk. It helps if you use UFS labels to identify
>> the root filesystem on the USB disk.
>> [...]
>
> Thanks, for quite an informative post :)

You are welcome.

> I also had been facing problems in booting 8.0-CURRENT from USB and, or
> SD/MMC cards; I'm not sure, but I think there is some problem with 8.0
> only, because I can easily install and boot 7.0 and 7.2-CURRENT from the
> same media and, or drive, port or card of course on the same machine.

AFAIK the USB timing issues are only present in 8.X.

A new USB stack is the default in 8.X, and there are a few "interesting"
interactions between device discovery and the root mounting code.

> Until now I had been following http://bit.ly/aeKEpM for installing
> FreeBSD on a stick or card; though needs minor adaption for latest
> releases, but worked well up to 7.2-CURRENT.

Ceri Davies' guide is better than my usual "copy everything over" trick
for new, clean installations.

Both install methods have their merits and their faults, though. For
example, my tar-based approach might copy stuff to the USB stick that
shouldn't be there. But it's *very* fast if all you want is to save a
usable copy of a system, e.g. for recovery purposes. Much faster than
going through the steps of re-configuring everything on a clean install.

> I attempted to do the same with
> http://yds.coolrat.org/zfsboot/usbinstall still no joy, particularly in
> the 8.0-CURRENT case again.
>
> The FreeBSD 8.0 fails to find and boot from a geom labeled media on USB,
> that's the /dev/ufs/FreeBSDonUSB here; it drops me at mountroot prompt
> only if I boot it into a single user mode.

This sounds like a bug. You should probably describe the setup at the
freebsd-current mailing list and see if someone more knowledgeable about
the zfs internals has done something similar.

From: Giorgos Keramidas on
On Sat, 13 Feb 2010 13:05:05 GMT, spooky130(a)NOSPAM.gmail.com wrote:
> Oh, just in case I missed it: is there an absolutely safe way that I
> can install the FreeBSD boot manager on the internal (drive c:/ - M$
> XP) drive to dual-boot without having to go into BIOS each time?

No, I'm afraid not :-(

Windows and even some BIOS revisions in relatively 'modern' laptops has
been known to have issues with the MBR boot0 code of FreeBSD. I usually
avoid multi-boot installs for this reason and try to use /boot/mbr as my
boot0 stage code instead of the menu-based boot0 code.

From: Giorgos Keramidas on
On Sat, 13 Feb 2010 15:29:03 GMT, spooky130u(a)NOSPAM.gmail.com wrote:
>> If you don't trust the (installation of) FreeBSD boot manager, you
>> can always set up the Windows boot manager to boot FreeBSD:
>
> It's more that I don't trust myself. I'm still not clear on exactly
> HOW to install the FreeBSD boot manager. I THOUGHT I did that during
> the install---but it ended up on the USB drive, not the internal
> drive, which the system boots to.

You can install boot code to the MBR of any disk with boot0cfg, e.g.:

boot0cfg -v B /dev/ad0

Install the default /boot/boot0 code to the MBR of ad0.

boot0cfg -v -B -b /boot/mbr /dev/ad0

Install the /boot/mbr boot code to the MBR of ad0.

Note: The /boot/mbr code is a simple, quite 'plain' version of an MBR
loader, that simply boots the first active partition of a disk. No
menus, far less compatibility problems with crafty BIOS firmware code,
but also no means of switching to another disk or to PXE boot.