Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 27 Jun 2011 09:56:51 -0700
From:      perryh@pluto.rain.com
To:        gyrd-se@thanelange.no
Cc:        doug@safeport.com, freebsd-questions@freebsd.org
Subject:   Re: Dual Boot 8.2 and Windows 7
Message-ID:  <4e08b653.f21Zod5W+PPBQkwI%perryh@pluto.rain.com>
In-Reply-To: <20110626202852.6765f935@parvati.thanelange.no>
References:  <alpine.BSF.2.00.1106231919320.83085@oceanpt.safeport.com> <D7EC3198-B917-4ACB-9BC2-ACE6D5569C07@my.gd> <4D7F86D5012E084A@> <alpine.BSF.2.00.1106240933580.83085@oceanpt.safeport.com> <4e05220e.GBAaOafCcTgMjymv%perryh@pluto.rain.com> <20110626202852.6765f935@parvati.thanelange.no>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
Gyrd Thane Lange <gyrd-se@thanelange.no> wrote:

> On Fri, 24 Jun 2011 16:47:26 -0700
> perryh@pluto.rain.com wrote:
>
> > ... The code in i386/boot2 and
> > lib/libstand is written to find the / (or /boot) FS on a
> > BSD partition of an fdisk "primary partition" (aka slice),
> > or in a GPT partition, and would need additions to handle
> > fdisk "extended partitions".
>
> Some years ago I ran into a similar problem. I ran out of primary
> partitions (using MBR-speak) and had to move FreeBSD into an extended
> partition.
>
> Here the simple patch I wrote for the FreeBSD boot loader:
> <http://parvati.thanelange.no/freebsd/boot_loader/boot_loader.diff>;
> <http://parvati.thanelange.no/freebsd/boot_loader/>;

Any thought of submitting that as a PR?

> The next challenge is to find a boot manager that will pick up
> FreeBSD in an extended partition. For myself I use a self patched
> GRUB. (GRUB also nearly worked out of the box, but had a different
> problem.)

It makes sense that GRUB would understand "extended partitions"
since its roots are in Linux which is often installed in extended
partitions.  Ideally FreeBSD should have a native solution, i.e.
a version of boot2 that would understand extended partitions.
Dunno without trying it if the capability could be added to the
existing boot2 without exceeding available space, or if it would
need a new variant.

> You're welcome to have those patches as well if you need them.

It would be good to get them posted somewhere.  GRUB is not in the
FreeBSD tree AFAIK, so send-pr is likely not all that good a method,
but perhaps they could be pushed upstream to the GRUB maintainers?

> Lastly I have the following in my kernel configuration file:
>
> include GENERIC
> ...
> nooptions         GEOM_PART_BSD
> nooptions         GEOM_PART_MBR
> options           GEOM_BSD
> options           GEOM_MBR
>
> That is because I am not fond of the new mangled device names,
> but prefer the old ones.

What differences?  AFAIK a disk sliced with fdisk and partitioned
with bsdlabel will have partition names like ad0s1a regardless of
which GEOM modules are used to process the MBR and partitions.
It's only if one uses the GPT partitioning scheme instead of
fdisk/bsdlabel that the disk will have partition names like ad0a.



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?4e08b653.f21Zod5W+PPBQkwI%perryh>