Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 27 Feb 2004 08:06:43 -0900
From:      "Mark Weisman" <mark@mystic1.net>
To:        "Jerry McAllister" <jerrymc@clunix.cl.msu.edu>
Cc:        questions@freebsd.org
Subject:   RE: Boot and MBR.
Message-ID:  <88EB08D16800D34EA145D7DD2AA44998E655@minnie.outland>

next in thread | raw e-mail | index | archive | help
I've installed GAG, and that is a really easy setup! It identified all
the partitions, and what was in them, stepped me through the process of
copying the manager to the disk and everything, kudos for the
recommendation! When I select to boot to the WindowsXP partition, it
come to a black screen with red squares in a diagonal line across the
screen, not sure but it doesn't look good. Have to hit reset on the box
to get out, the three finger salute doesn't work. I see the cursor
blinking in the upper left corner, yet no operating system. Any ideas?

Res Ipsa Loquitor,
Mark-Nathaniel Weisman
Site Master
Mystic1.net


-----Original Message-----
From: Jerry McAllister [mailto:jerrymc@clunix.cl.msu.edu]=20
Sent: Friday, February 27, 2004 7:24 AM
To: Mark Weisman
Cc: Jerry McAllister; questions@freebsd.org
Subject: Re: Boot and MBR.


>=20
> Just out of curiosity what is the order in creating a dual boot=20
> system? Which operating system do you put on first? I see that having=20
> WinXP setup in partitions is not a good idea, yet I'm not aware of how

> to load the system in just a slice? I would appreciate any and all=20
> help in trying to get this thing online. I need my workstation back as

> soon as possible. Thanks.

I am not sure which thing you are referring to when you use
the word 'order' but...

Install whatever MS-Win system you want to have first and make sure it
boots OK.

Then, use one or another utility to shrink the MS slice and make room
for another - you can have up to 4 primary slices.   FIPS works fine
if the MS slice (called partition in MS land) is a FAT, but if it is
NTFS you will need some more sophisticated utility like Partition Magic
(which is not free - about $69 in Best Buy type stores) I have heard
there is a newer free one now available that can handle NTFS and MS
extended slices (partitions in MS speak) but I don't remember the
name.   Partition Magic will create a slice (which they call partition
since they are mostly MS oriented) and mark it as a FAT32 - or something
else if you tell it too.

Then install FreeBSD.   Presuming you use the CD sysinstall method,
when you get to the partitioning stage it shows you the primary
slices on the disk and what they currently have in them.   Put the
cursor on the new FAT slice that was created when you resized stuff with
PM or FIPS and 'D' delete it.  Then hit 'C' create and it will
make that a FreeBSD slice.   Then hit 'S' make it bootable (which,
non-intuitively will put an 'A' in the Flags column to indicate it
should be bootable.   I have also, sometimes, moved the cursor up and
marked the slice with the MS system in it as bootable (hit 'S' on it)
but sometimes not bothered and it hasn't seemed to make a difference as
long as the MS system booted OK before I got started.

As soon as you get this done and hit 'Q' to save and go on, you will
be presented with a screen that has three choices.  =20
   BootMgr    Install the FreeBSD Boot Manager
   Standard   Install a standard MBR (no boot manager)
   None       Leave the Master Boot Record Untouched

On this screen you want to choose the first one:  BootMgr
Then use the tab to make sure OK is selected and go on to
the next stuff.

After this you will be put in to a screen to divide up the FreeBSD
slice in to partitions.   Do this as needed for your installation

>From here on out you are past the boot stuff.  You will choose what you
want installed - if you have room, just grab it all, and where you want
to install from - FTP or CD, etc

Finish up the install and network configuration.

When you boot, you will be presented with a menu something like:

  F1  DOS
  F2  FreeBSD

or maybe=20

  F1  ??
  F2  FreeBSD

or I have on one machine

  F1  ??
  F2  DOS
  F3  FreeBSD

because it is a Dell machine and has a bootable Dell Slice with their
maintenance stuff on it.

You get a menu listing for every slice that is marked bootable
regardless of what it is.   It labels all MS FAT slices as 'DOS'
regardless of which MS system is on it..=20
You get the ?? if the Boot Manager finds it bootable, but doesn't know=20
sort of system it is - such as for NTFS.   It doesn't have to know what=20
kind of system it is to boot it so the ?? doesn't matter.  It is just a=20
cosmetic annoyance.   IF it is too much for your stomach to take, then=20
you can get a fancier Boot Manager such as GAG or GRUB and install it
and you can configure those with whatever labels you want to use. Those
can be installed later after the system is fully installed=20
and you have some time to play. =20

The basic FreeBSD boot manager is small to fit in the official one=20
sector space that is available.  The fancier boot managers generally use

some additional space that, by convention is never otherwise used, but=20
is not officially available for it.   I kind of with they (whoever does=20
this sort of official definition) would just officially redefine the
standard so the whole unused cylinder was official boot mangler space.

////jerry


>=20
> Res Ipsa Loquitor,
> Mark-Nathaniel Weisman
> Site Master
> Mystic1.net
>=20
>=20
> -----Original Message-----
> From: Mark Weisman
> Sent: Thursday, February 26, 2004 4:59 PM
> To: Jerry McAllister
> Cc: questions@freebsd.org
> Subject: RE: Boot and MBR.
>=20
>=20
> You are right, I have them setup originally under WinXP as partitions,

> then added FreeBSD to the second partition where it calls it a slice.=20
> Divided up the slice into the required folders. I have tested, and it=20
> is not cosmetic, in that when I select that menu item, the computer=20
> goes to the next row and stays indefinitely. I can put WinXP back on=20
> the computer if I have to, however, wouldn't that put the WinXP MBR on

> the box? I've gone in under fdisk and set the slice bootable, however=20
> nothing. I'm not sure how to install it now to just that slice. Any=20
> help would be greatly appreciated.
>=20
> Res Ipsa Loquitor,
> Mark-Nathaniel Weisman
> Site Master
> Mystic1.net
>=20
>=20
> -----Original Message-----
> From: Jerry McAllister [mailto:jerrymc@clunix.cl.msu.edu]
> Sent: Thursday, February 26, 2004 1:27 PM
> To: Mark Weisman
> Cc: questions@freebsd.org
> Subject: Re: Boot and MBR.
>=20
>=20
> >=20
> > I've got my primary drive divided in two partitions, one partition=20
> > had
>=20
> > WindowsXP and the other has FreeBSD 5.1-Release on it. I had=20
> > WindowsXP
>=20
> > installed and working until I put FreeBSD on the second partition=20
> > and had it take control of the MBR. I know that the other partition=20
> > is still bootable if I can get a pointer to it, currently the boot=20
> > menu shows it
> > as:
> >   F!: ??
> >   F2: FreeBSD
> > How can I get that first menu choice to look at the installation on
> the
> > first partition as bootable? Making the machine a dual boot between
> the
> > two system?
>=20
> The fact that it displays ?? is only a cosmetic problem.
> Have you tried selecting F1 to see if it will boot the XP slice?  =20
> Mine does.
>=20
> Also, a side issue, in FreeBSD land, what you have is a disk
> with tw0 'slices' as apposed to partitions.   Probably you have
> your FreeBSD slice divided up in to several 'partitions'.   MS calls
> the primary divisions of a disk partitions, but in BSD UNIX land they=20
> are called slices.
>=20
> > The second question I have, is can I put the command startx into my=20
> > rc.conf file to have it boot directly into the x-server? Any help on

> > these two would be awesome. Thanks.
>=20
> I have not been successfule with that sort of thing.   Anyway, I=20
> don't think just putting it in rc.conf would do the trick because
> that just sets a bunch of variables in there.  Then the stuff is
> actually run from rc (and some other places I think) using those=20
> variable values set in /etc/defaults/rc.conf and /etc/rc.conf..
>=20
> I think you might not want your startx to fire off until after
> you log in anyway.    That would mean putting it in .login (if=20
> you have a csh or tcsh shell)  and that is what didn't work for me,=20
> though I didn't try many variations.
>=20
> But, someone else better weigh in on this.
>=20
> ////jerry
>=20
> >=20
> > Res Ipsa Loquitor,
> > Mark-Nathaniel Weisman
> > Site Master
> > Mystic1.net
> >=20
> > _______________________________________________
> > freebsd-questions@freebsd.org mailing list=20
> > http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> > To unsubscribe, send any mail to
> > "freebsd-questions-unsubscribe@freebsd.org"
> >=20
> >=20
>=20
> _______________________________________________
> freebsd-questions@freebsd.org mailing list=20
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to=20
> "freebsd-questions-unsubscribe@freebsd.org"
>=20
>=20



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