emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#54112: closed (dd seek_bytes etc. is confusing)


From: GNU bug Tracking System
Subject: bug#54112: closed (dd seek_bytes etc. is confusing)
Date: Wed, 23 Feb 2022 02:59:02 +0000

Your message dated Tue, 22 Feb 2022 18:58:19 -0800
with message-id <3d906d36-5152-f92f-831e-009d024fcb92@cs.ucla.edu>
and subject line Re: bug#54112: dd seek_bytes etc. is confusing
has caused the debbugs.gnu.org bug report #54112,
regarding dd seek_bytes etc. is confusing
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
54112: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=54112
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: dd seek_bytes etc. is confusing Date: Tue, 22 Feb 2022 09:03:46 -0800 User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 While looking into Bug#45648 I noticed that the GNU extensions count_bytes, seek_bytes, and skip_bytes are confusing, and the proposed fix to bug#45648 would make them even more confusing. To fix this confusion, we should deprecate these options, and instead say that if you want to use byte counts you should use a number string ending in "B".

Here's another way to put it.  Currently this:

   dd oseek=100KiB

means "seek 102,400 blocks". It should simply mean "seek 102,400 bytes", which is what it says. And if we change oseek's meaning this way, we don't need "oseek_bytes".

Although this is an incompatible change to GNU dd, I don't think it'll affect real-world uses (who would use oseek in such a confusing way now?) and overall it will be a win.



--- End Message ---
--- Begin Message --- Subject: Re: bug#54112: dd seek_bytes etc. is confusing Date: Tue, 22 Feb 2022 18:58:19 -0800 User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0
On 2/22/22 09:29, Pádraig Brady wrote:
That is a more concise and direct way to achieve the same functionality.
+1

I guess we should remove docs for the other options,
but leave support there for backwards compat.

Sounds good, I installed the attached and am closing the bug report.

Attachment: 0001-dd-counts-ending-in-B-now-count-bytes.patch
Description: Text Data


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]