On Fri, Jun 10, 2011 at 01:45:03PM +0000, Debian Bug Tracking System
<ow...@bugs.debian.org> wrote:
> This was a deliberate change made some time ago to avoid possible
> internal overflows.
It still breaks userspace apps.
> Unix read/write calls have always worked that way.
Thats utter bullshit. Why do you even bother making such a blatantly
incorrect statement when you are completely aware that you simply don't
know? Because you don't know, because it's simply untrue.
Solaris doesn't, HP/UX doesn't. OS/X doesn't (which is officially a
unix). No posix system behaves like that. None have a magic 2147479552
byte barrier, none return fewer bytes than requested except for both
historical and posix-mandated behaviour (or bugs).
So which unix behaves like that? Name just one. There aren't so many 64
bit ones, so surely you cna name just one?
I can understand if debian doesn't want to fix this bug. But corrupting
data when users try to rescue their data with a too large dd blocksize
is clearly too important to let people like you just make blatant wrong
statements and close valid bugreports.
At least leave it open so people who fall over this trap might have a
chance of rescuing their data.
What do you lose by being honest? Are you drepper in disguise, who closes
valid bugreports by making blatantly wrong statements that even he knows are
bullshit?
Because this is what you are doing here.
--
The choice of a Deliantra, the free code+content MORPG
-----==- _GNU_ http://www.deliantra.net
----==-- _ generation
---==---(_)__ __ ____ __ Marc Lehmann
--==---/ / _ \/ // /\ \/ / schm...@schmorp.de
-=====/_/_//_/\_,_/ /_/\_\
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
