On Mon, Nov 21, 2016 at 05:42:15PM -0500, John Ferlan wrote:
[...]
[C] might be more user-friendly, but I'm not sure if we can change the
meaning of the NO_OVERWRITE constant like that. On the bright side,
if blkid can also identify partition tables, we could unify the probing
code with the dis
[...]
>
> [C] might be more user-friendly, but I'm not sure if we can change the
> meaning of the NO_OVERWRITE constant like that. On the bright side,
> if blkid can also identify partition tables, we could unify the probing
> code with the disk backend and stop parsing parted's output (also, catc
On 11/18/2016 07:56 AM, Ján Tomko wrote:
> On Tue, Nov 15, 2016 at 06:48:03PM -0500, John Ferlan wrote:
>> https://bugzilla.redhat.com/show_bug.cgi?id=1363586
>>
>> There's actually a couple of bugs here...
>>
>>only the "input" format type, so any other "types" of format would be
>
> I coul
On Tue, Nov 15, 2016 at 06:48:03PM -0500, John Ferlan wrote:
https://bugzilla.redhat.com/show_bug.cgi?id=1363586
There's actually a couple of bugs here...
only the "input" format type, so any other "types" of format would be
I could a verb.
filtered during the blkid_do_probe resulting
https://bugzilla.redhat.com/show_bug.cgi?id=1363586
There's actually a couple of bugs here...
only the "input" format type, so any other "types" of format would be
filtered during the blkid_do_probe resulting in allowing a new format
type to overwrite a previous format type since when
