Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 23 Apr 2002 02:54:15 -0400 (EDT)
From:      Peter Leftwich <Hostmaster@Video2Video.Com>
To:        Mike Meyer <mwm-dated-1019623222.d610de@mired.org>
Cc:        Patrick O'Reilly <bsd@perimeter.co.za>, mpd <mpd6334@cs.rit.edu>, FreeBSD LIST <FreeBSD-Questions@FreeBSD.Org>
Subject:   Re: MBR, mfsroot.flp, handbook, and list fail me.. FRUSTRATION waning
Message-ID:  <20020423024557.V16227-100000@earl-grey.cloud9.net>
In-Reply-To: <15551.40886.583787.975543@guru.mired.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 18 Apr 2002, Mike Meyer wrote:
> > You answered one part of a two-part question.  Can I be logged in regularly as root, or must I boot up to a floppy or CDROM to repair the MBR to my liking?
> This has already been answered once on this thread, and the question you gave me had two choices: logged in regularly as root, and booted from a floppy. You have to be root. It doesn't matter how you get there.

Hello again, Mike and list.  Sorry for my confusion (some is still leaking
forth); It seems we had various answers in various stages being trounced
about (use fdisk, use boot0cfg, use -B -b, use just -b... and so on)

> > I don't know what I'm doing, and the instructions for boot0cfg and fdisk are NOT COMPLETE (the handbook is very lacking in this department too). When I recently got the boot0cfg command to run, it told me "Device busy."
> If they aren't complete, please tell us what's missing so we can fix them. Better yet, provide the patches yourself once you've figured out the answers.

Actually, the manpage for boot0cfg is pretty good, but it doesn't go over
having an MBR (menu) vs. just a standard boot procedure (one OS, but other
partitions are mountable later).

It seems that I do NOT want the -B flag after all, because it seems to
install boot0 (image?) which would be the F1, F2, etc menu I despise, and
further, there is hope as I just noticed a flag for -s (slice) so I can not
only tell boot0cfg which disk but also which slice to boot into, yeay!

But a lasting lament: The manpage doesn't explain if the /boot/* files are
used by boot0cfg to overwrite some kind of image, nor does it go into
detail about how to tell differences between boot0, boot1, boot2 etc.

As far as assembling this into one working command line, I am yet lost. :(

> > To reiterate what I am trying to do -- My computer has just one HD, but (among others) the two partitions listed below:
> > /dev/ad0s2a on / (ufs, local)
> > /dev/ad0s1 on /msdos (msdos, local)
> > IS there a command to use the standard MBR manager (no F1, F2, etc.. menu) *and* boot directly, automatically to /dev/ad0s2a but keep /dev/ad0s1 (/msdos) mountable?  THANKS. *sigh* *grumble*
> fdisk.
> 	<mike
> Mike Meyer <mwm@mired.org>			http://www.mired.org/home/mwm/

So are you saying boot0cfg is *only* going to give the user/sysadmin an MBR
with a menu?  fdisk makes me fearful :)

> Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information.

{What's Perforce?  Do you do PERL consulting/web development/programming?}

--
Peter Leftwich
President & Founder
Video2Video Services
Box 13692, La Jolla, CA, 92039 USA
+1-413-403-9555


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020423024557.V16227-100000>