:No it does not -- it reserves the storage "somewhere at the beginning", 
:but the first sectors are used by the superblock.  Anyways, I think btx 
:is the problem, or something close.
:
:cheers
:   simon

    Yah.  HAMMER is not designed for partitions which overlap the boot
    blocks, which is how normal 32 bit disklabels work (when ad0s1a
    starts at sector 0 instead of sector 16).

    64 bit disklabels are different.  The partitions are out-of-band.

    I really think the best way to deal with it is to have a separate
    /boot partition which has the loader, kernel, and modules and anything
    else the loader needs.

    The bigger issue is making the boot code directly support 64 bit
    disklabels or GPT.

                                        -Matt
                                        Matthew Dillon 
                                        <[EMAIL PROTECTED]>

Reply via email to