Date: Sun, 18 Sep 2011 13:18:49 -0700 From: Kevin Oberman <kob6558@gmail.com> To: "Thomas Mueller <mueller6727"@bellsouth.net Cc: freebsd-current@freebsd.org Subject: Re: 9.0 beta2 & the new bsdinstaller Message-ID: <CAN6yY1vA1jj=9GcijAUW3aKzzbGMKSnacA-WMzvcNL5POYzQRg@mail.gmail.com> In-Reply-To: <20110918095526.D866D1065670@hub.freebsd.org> References: <20110918095526.D866D1065670@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Sep 18, 2011 at 2:55 AM, <"Thomas Mueller <mueller6727"@bellsouth.net> wrote: > Some more ideas on the new bsdinstaller cross my mind. > > Since the way the bsdinstaller would make partitions is unpredictable, at= least to the uninitiated, and in all likelihood at variance with how much = space the user wants to allocate, it might be better to offer a roadmap to = help guide the user to allocating space for FreeBSD using gpart or Rod Smit= h's gdisk. > > Also, I can't see the function of the 64 KB boot partition with no file s= ystem, which does not boot for me, though I can boot the main partition usi= ng grub2 from the System Rescue CD (http://sysresccd.org/). The 64KB freebsd-boot partition is to contain the GPT boot code which is used by UEFI BIOS in place of the old MBR used by legacy BIOS. You need to use gpart(8) to write the GPT boot code to that partition, but I don't know if bsdinstall does so. It might just write the PMBR that is used for booting with legacy BIOS. I'll admit that I have not checked. (See the gpart(8) man page for details on writing the pmbr and gptboot.) I assume bsdinstall writes both so that AMD64 machines with EFI and 32-bit systems will both work. This is very different from the old traditional slice/partition system. --=20 R. Kevin Oberman, Network Engineer - Retired E-mail: kob6558@gmail.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1vA1jj=9GcijAUW3aKzzbGMKSnacA-WMzvcNL5POYzQRg>