On Sun, Nov 27, 2016 at 1:41 PM, Jody Bruchon <[email protected]> wrote: > On 11/27/2016 12:11 AM, Denys Vlasenko wrote: >> I looked at these "type codes of GPT partitions" and they seem to be >> a figment of imagination of "GPT fdisk" people: they are not stored on >> disk, >> fdisk authors just assigned them to some GUIDs. >> >> How do you find them useful? > > I use gptfdisk tools for disk imaging and information scripts. The made-up > partition types from gptfdisk are an extremely handy mnemonic device because > I can actually remember them and they make for cleaner code that has to > embed these known GUIDs.
> Off the top of my head, I know that 0700 is > "Microsoft basic data", af00 is "Apple HFS+", ef00 is "EFI system", and IIRC > af01 is "Apple Core Storage." If you asked me to tell you the corresponding > GUIDs, I have no clue at all. The usefulness is like programming in assembly > instead of banging in raw hex codes. Makes sense. However, I still don't understand how do you use them, apart from seeing them on output. > On a somewhat related note, I have started working on implementing the '-t' > switch in fdisk; having BB fdisk automatically pick my GPT partition table > makes me unable to use fdisk to modify the protective MBR. Is your work available somewhere? I am happy to accept patches from people who are actually using the tool they are patching - they are "scratching the itch" which exists in real-world usage. >From your description, you are doing that right now. When you send a patch, add a bit of background why do you need this change, and if there were other solutions which at first looked better, but then proved non-workable, mention those too. For example, before I saw your email, I looked at fdisk_gpt.c and decided to simply delete "Code" column on the output. I take it this is not a good idea? Why? _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
