RE: Boot and MBR.

From: Mark Weisman (mark_at_mystic1.net)
Date: 02/27/04

  • Next message: Robert Storey: "Re: Boot and MBR."
    Date: Thu, 26 Feb 2004 17:18:01 -0900
    To: "Jerry McAllister" <jerrymc@clunix.cl.msu.edu>
    
    

    Just out of curiosity what is the order in creating a dual boot system?
    Which operating system do you put on first? I see that having 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 help in
    trying to get this thing online. I need my workstation back as soon as
    possible. Thanks.

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

    -----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.

    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.
    Divided up the slice into the required folders. I have tested, and it is
    not cosmetic, in that when I select that menu item, the computer goes to
    the next row and stays indefinitely. I can put WinXP back on 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
    nothing. I'm not sure how to install it now to just that slice. Any help
    would be greatly appreciated.

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

    -----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.

    >
    > I've got my primary drive divided in two partitions, one partition had

    > WindowsXP and the other has FreeBSD 5.1-Release on it. I had WindowsXP

    > installed and working until I put FreeBSD on the second partition and
    > had it take control of the MBR. I know that the other partition is
    > still bootable if I can get a pointer to it, currently the boot 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?

    The fact that it displays ?? is only a cosmetic problem.
    Have you tried selecting F1 to see if it will boot the XP slice?
    Mine does.

    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
    are called slices.

    > The second question I have, is can I put the command startx into my
    > rc.conf file to have it boot directly into the x-server? Any help on
    > these two would be awesome. Thanks.

    I have not been successfule with that sort of thing. Anyway, I
    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
    variable values set in /etc/defaults/rc.conf and /etc/rc.conf..

    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
    you have a csh or tcsh shell) and that is what didn't work
    for me, though I didn't try many variations.

    But, someone else better weigh in on this.

    ////jerry

    >
    > Res Ipsa Loquitor,
    > Mark-Nathaniel Weisman
    > Site Master
    > Mystic1.net
    >
    > _______________________________________________
    > freebsd-questions@freebsd.org mailing list
    > http://lists.freebsd.org/mailman/listinfo/freebsd-questions
    > To unsubscribe, send any mail to
    > "freebsd-questions-unsubscribe@freebsd.org"
    >
    >

    _______________________________________________
    freebsd-questions@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-questions
    To unsubscribe, send any mail to
    "freebsd-questions-unsubscribe@freebsd.org"
    _______________________________________________
    freebsd-questions@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-questions
    To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"


  • Next message: Robert Storey: "Re: Boot and MBR."

    Relevant Pages

    • Re: Boot-prompt (4.9) - where defined?
      ... that in to partitions. ... 1 FreeBSD slice divided in to: ... To my understanding this is because the boot manager ...
      (freebsd-questions)
    • Re: Re: WinXP and FreeBSD configuration problems
      ... > Why the miniscule 2gb partitions? ... > worrying about the performance of boot and swap on a computer with a 320GB ... > partition I will now call it a slice. ... > FreeBSD slice into partitions, for things like swap, and file-systems. ...
      (freebsd-questions)
    • Re: Dual Boot WinXP + FreeBSD
      ... even though the XP slice that i ... > BOOTMAGIC,FREEBSDs boot loader and also i have used grub (which is ... With grub i was not able to boot fbsd when my ... no matter how I had hard disks and partitions and OSes configured. ...
      (freebsd-questions)
    • Re: It gets worse -- Uninstall of W2k? Not simple for me!
      ... > WinXP, which did not exist in 1999, and can't boot WinXP, so I guess you ... an OS to boot? ... you and I both have FAT partitions. ... I'll go for the install of XP and trust the fix with the few boot ...
      (microsoft.public.win2000.file_system)
    • Re: It gets worse -- Uninstall of W2k? Not simple for me!
      ... > WinXP, which did not exist in 1999, and can't boot WinXP, so I guess you ... an OS to boot? ... you and I both have FAT partitions. ... I'll go for the install of XP and trust the fix with the few boot ...
      (microsoft.public.win2000.general)