search for: efi_alloc_and_read

...nswering these questions... thanks... -sharlene ~~~~~~~~~~~~~~~~~~~ 1. Reserving the minor numbers that would have been used for the "h" slice for the "wd"     nodes instead creates a "hole". Is this the long term design and therefore not likely to change? 2. The efi_alloc_and_read(3EXT) function provides a pointer to a dk_gpt_t structure that     contains an array of efi_nparts dk_part structures. (efi_partition.h) Will efi_nparts be 15 or 16? 3. Will dk_part[7] correspond to sd@0,0:h or to sd@0,0:wd or is it somehow reserved? 4. Does the fact that efi_nparts is a member...