-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/23/2014 11:45 PM, Drake Wilson wrote: > So---entirely aside from the _other_ subthread about types _inside_ > LUKS---do you still intend to provide this as a reason for not > adding GPT/MBR LUKS types to fdisk, even in light of the > destructive interaction I mentioned in my first post? I'm worried > that my having said anything else while replying to Dale may have > been a mistake and given the impression that "no types inside LUKS" > answers my original concern, which it doesn't. > > As I mentioned, GPT and MBR have significant interop > characteristics with other tools, so I'm not convinced by the > "Linux only uses blkid" there. If that's what you're truly going > with after having seen the practical results, I won't argue > further, but I'd like to know. I have to say that adding more type codes for no reason is something I'm against. Like you said in your first post, the loss was caused by a bug in debian-installer coupled with the lvm type code. If you simply use the normal "Linux" type code, then everything works out fine so I don't see any reason to add more complexity and confusion by introducing yet another type code. Had the useless lvm type code never been introduced in a similar manner, you wouldn't have had the problem you did. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (MingW32) iQEcBAEBAgAGBQJUc0GtAAoJEI5FoCIzSKrwEtkH/iCiZ1Hm4EaBs7btRWD5C0FW fC363eGKNCK4KsYMPpVv+MjdLy1kwonmmI9OFl+uROdnCaZ2/GzgmynlUtviYl3H MtXlWEvmJGCT43Qgm97H3OC/3ihJ2epxAP4J5L7gK7fofTq7iqxpk47J1bm2MjUI XgNMxx31OfQzOtHKZSolJ8wCIC76Zre8tvMjDuGx8AF8JvBnkHpTykWG0B4K3niD 6B5pm/FnSV7t+YoZjkdrJMJsxoZFKU78A1cHeSRuKbXqJVrQXhJbxlcCg21DUGtD YniJM+W/Cy5KQAh2EfuwMQxkSOXnPTZvSTGdjTserDW5fmdUN2Z7PFlGFOlRZmA= =Xcjj -----END PGP SIGNATURE----- -- To unsubscribe from this list: send the line "unsubscribe util-linux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
