type code space is
so small that collisions should be expected, but util-linux's fdisk in MBR
mode also provides a 0xda code for "non-FS data", so users in that case may
be less tempted to default to the underlying volume type.
---> Drake Wilson
--
To UNSUB
I
can also try to formulate a patch if desired. Thanks for whatever you can
provide.
---> Drake Wilson
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/546c1dc4.2040...@dasyatidae.net
ter question would probably be why that flag->method propagation is done in
manual partitioning mode in the first place; I assume that's used for something,
but I don't know what, having not delved into this code before.
---> Drake Wilson
--
To UNSUBSCRIBE, email
.
---> Drake Wilson
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/545ff86a.3080...@dasyatidae.net
ow.
Unrelatedly, I was actually planning on unplugging all the non-target
disks first as a precautionary measure, but then I forgot to and
didn't think anything further of it until the cold chill of cryptsetup
failing when I tried to read anything from them.
Now I am sad and have filesystems
5 matches
Mail list logo
