From: Cygwin on behalf of Brian Inglis
Sent: 23 June 2020 8:33 PM
To: cygwin@cygwin.com
Subject: Re: [cygwin] DD bug fails to wipe last 48 sectors of a disk
I don't have the facilities to test, and there appear to be *NO* Windows
documentation details on error
From: Hashim Aziz
Sent: 19 June 2020 7:19 PM
To: cygwin
Subject: DD bug fails to wipe last 48 sectors of a disk
I first came across this bug last year, and wrote up my findings in a detailed
answer to the StackExchange network:
https://superuser.com/questi
I have no idea what bottom posting is, mailing lists are new to me and I find
them a very archaic and noisy way to communicate development changes. I really
wish the Cygwin dev team would enter the 21st century and move to a modern
development process involving a repository like Github, I'm conv
g fails to wipe last 48 sectors of a disk
Do you get the same behavior when you run dd with iflag=fullblock? Without
that flag, it's possible dd's input to read a smaller block than requested
(which would correspond with a smaller write to the output).
On Tue, Jun 23, 2020 at 9:28 AM Hash
liot Moss
Sent: 20 June 2020 9:26 PM
To: The Cygwin Mailing List
Subject: Re: [cygwin] DD bug fails to wipe last 48 sectors of a disk
On 6/20/2020 1:31 PM, Hashim Aziz via Cygwin wrote:
> To reproduce simply run the following command on a drive (obviously, this
> will irreversibly wipe all
of a disk
> -Original Message-
> From: Hashim Aziz via Cygwin
> Sent: Friday, June 19, 2020 2:19 PM
>
> I first came across this bug last year, and wrote up my findings in a
> detailed answer to the
> StackExchange network:
>
> https://superuser.com/questions/1505715/why-d
I first came across this bug last year, and wrote up my findings in a detailed
answer to the StackExchange network:
https://superuser.com/questions/1505715/why-does-dd-give-me-an-error-at-the-end-of-zero-writing-a-disk
I didn’t then have the time to report it to this mailing list, but have just
7 matches
Mail list logo
