mlel...@serpens.de (Michael van Elst) wrote: > bea...@sdf.org (beaker) writes: > > >I think Elst's comment is right, that there isn't actually a primary > >NetBSD bootloader present on the referenced partition so one needs > >to be installed, though I'm unsure how to do this with non-UEFI gpt > >partitioning; do I use gpt(8) or installboot(8) and where to install > >it? If I install it to gpt6 (bios) partition is wipes out GRUB (know > >this from experience...), but if I install it on gpt3 (FFS) is it > >going to mess up the existing file system? > > You install it with installboot to the FFS partition. Chainloading > means that the first partition block is loaded and executed. > > The FFS layout leaves space for an 8kb bootloader (including a hole > for a BSD disklabel, but which isn't used here). Installboot knows > how to handle this.
Ah okay, that's reassuring. I'll do a full backup and try this then. By the way, shouldn't I be using gpt biosboot [-A] [-c bootcode] [-b startsec] [-i index] [-L label] for a gpt partitioned disk or is this relatively recent addition just an alternative of convenience? I'm finding the description in the manpage rather confusing; does it simply "configure" a partition already containing a primary bootloader, ie. swap out existing bootloader with an alternative, or will it actually install the bootloader if none already present? -B
