Osamu Aoki wrote:
> Hi Michael,
> 
> You are quick :-)  Please understand I am all for removing this package.

And this is why I don't want to discuss this issue with you anymore.


>> *) gnu-fdisk is a tool which is an alternative to fdisk, closely
>> imitating it's interface, not hinting on any fundamental differences
>> between it's predecessor or GPT.
> 
> But when we are dealing with different beast such as GPT, we should not
> fake its situation almost as MBR.  This is the thing most bad about
> gnu-fdisk.

Why is this a problem?

> If your issue is with installer, please put it there.  Please note
> important bug is not RC.

I thought I clearly laid out what the issue is. I'll try it again.

There is currently _NO WAY_ to _SANELY_ edit _THE ONLY_ partition table
available on x86 systems for devices larger than 2TB (which are
available Real Soon Now), without _DESTROYING YOUR BOOT CHAIN_. When the
device in question happens to be your boot device.

> Also I think this is not just Debian problem.  If you know other distro
> doing it right, please point it out.  They may be using some patch to
> the libraries used by gnu-fdisk/parted.

I'm not much of a community guy. The only distribution I actively use is
Debian because it gets stuff most of the times right. I hoped that
somebody would eventually notice the reach of the situation and take
care of it.


> I general, new hardwares (be it huge disk space or new design), causes
> issues.  They are not RC but quite annoying.

Please don't argue about the importance of the bug if you fail to
understand the situation.


Have a good night,
Michael



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to