I wanted to thank everyone for contributing and helping out. In the end, I decided to go
for ddrescue (because I could not find jetcat-mod beyond some old posts of Michael
online). In any case, ddrescue copied everything with a meter in around six hours. It also
reported a few bad bits (in the old drive) and I am now trying to figure out how to
identify the files with those bad bits.
Thank you again for all your help and discussion. I learnt a lot of new and cool way of
doing things! I have said this in the past, but I love this discussion group for how
helpful and free with time and suggestions people are. My father-in-law uses Ubuntu for
historical reasons and they do not come even close in those discussion lists (in fact they
are very far).
On Sat, 8 Sep 2018 17:08:30 -0600 JD <jd1008(a)gmail.com> wrote:
On 09/08/2018 04:48 PM, Cameron Simpson wrote:
> On 09Sep2018 06:45, Michael D. Setzer II <msetzerii(a)gmail.com> wrote:
>> On 8 Sep 2018 at 17:10, Patrick O'Callaghan wrote:
>>> The link in the footer points to g4l, but nothing in your message
>>> mentioning jetcat-mod makes that connection. Only an off-list message
>>> from you explained it, and you then repeated the information on-list.
>> In my original message to the thread I specified that I had been the
>> maintainer of the g4l disk imaging project since 2004, and made some
>> comments. Later there was talk of using dd to do the copy, and I
>> pulled the
>> one line from the 2000+ line script that specifically does the clone
>> The entire project is on sourceforge with the source code. Project is
>> completely free, no paid options, no donations. Just an option that some
>> might find useful.
>> Wasn't trying to force it on anyone, and just sharing what I had seen
>> over the
> As the one on the tar/cp side of this discussion, I'd like to support
> Michael here.
> He did indeed say he was the g4l maintainer. And he was perfectly
> clear when he post his dd pipeline that it came from the g4l package.
> It isn't unreasonable at all that it uses a tool that is part of that
> same package.
> There's any number of "progress reporting cat" type commands out
> there; I've got one of my own called prcat  (just a perl script
> accepting a commandline buffer size, no fancy threading or parallelism).
> IMO there's little value in this bickering over an _example_ command
> line whose function is clear on inspection just because it has an odd
> but obviously equivalent to "cat" command in the middle. Particularly
> since nothing in this discussion is Fedora specific; it all applies to
> pretty much any Linux system and nearly applies to any UNIX system in
> general (such as the Mac I'm typing this on). Can we please go back to
> _technical_ discussion instead of this?
> To satisfy the "no link to the code" people:
>  https://bitbucket.org/cameron_simpson/css/src/tip/bin/prcat
> Cameron Simpson <cs(a)cskk.id.au>
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
Important Notice: This mailbox is ignored: e-mails are set to be deleted on receipt.
Please respond to the mailing list if appropriate. For those needing to send personal or
professional e-mail, please use appropriate addresses.