From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Testing a used hard drive to make SURE it is good.
Date: Mon, 22 Jun 2020 23:18:24 -0500 [thread overview]
Message-ID: <914a9d55-03f8-7791-be53-db13335706ff@gmail.com> (raw)
In-Reply-To: <20200622225927.blqrjpexx5l5bhch@grusum.endjinn.de>
[-- Attachment #1: Type: text/plain, Size: 1299 bytes --]
David Haller wrote:
> Hello,
>
> On Mon, 22 Jun 2020, Dale wrote:
>> David Haller wrote:
>>> On Thu, 18 Jun 2020, Dale wrote:
>>>> David Haller wrote:
> [..]
>>>>> ./ones | dd of=/dev/null bs=8M count=1000 iflag=fullblock
>>> [..]
>>>> I got it to compile, at least it created a file named ones anyway. What
>>>> I'm unclear about, where is the if= for dd in the command? All the
>>>> commands I've seen before has a if= and a of=. The if for input and of
>>>> for output or target.
>>> ==== man 1 dd ====
>>> if=FILE
>>> read from FILE instead of stdin
>>> [..]
>>> of=FILE
>>> write to FILE instead of stdout
>>> ====
>>>
>>> note the stuff after 'instead' ;)
>> So it is piped in with the | thingy? Got it.
> Exactly. Hm. Maybe 'dev_one' might be a better name for the program...
> Or something ;)
>
> [..]
>> Thanks much.
> You're welcome.
>
> -dnh
>
That name makes sense. Later on, I might look at that file and say,
what is that for? Hit delete and down the rabbit hole it goes. I think
I'll go do that and also edit my notes as well. Before I forget it. ;-)
Now I have a way to write ones to a drive or file. Yeppie!
Dale
:-) :-)
P. S. I hope the new glasses, when they come in, helps my memory. Never
hurts to hope right?
[-- Attachment #2: Type: text/html, Size: 2505 bytes --]
next prev parent reply other threads:[~2020-06-23 4:18 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 16:07 [gentoo-user] Testing a used hard drive to make SURE it is good Dale
2020-06-15 19:20 ` Spackman, Chris
2020-06-15 19:54 ` Mark Knecht
2020-06-15 20:00 ` Rich Freeman
2020-06-15 20:04 ` Mark Knecht
2020-06-16 7:34 ` Dale
2020-06-16 8:22 ` Wols Lists
2020-06-16 9:04 ` Dale
2020-06-16 11:02 ` Wols Lists
2020-06-16 11:26 ` Dale
2020-06-16 11:36 ` Michael
2020-06-16 12:25 ` Rich Freeman
2020-06-16 23:38 ` antlists
2020-06-17 9:47 ` Rich Freeman
2020-06-23 16:14 ` Sid Spry
2020-06-23 17:20 ` Rich Freeman
2020-06-23 18:44 ` Sid Spry
2020-06-16 13:14 ` Dale
2020-06-16 23:24 ` antlists
2020-06-17 4:47 ` Dale
2020-06-17 12:32 ` Wols Lists
2020-06-17 12:04 ` Rich Freeman
2020-06-16 8:29 ` Neil Bothwick
2020-06-16 8:52 ` Dale
2020-06-15 19:54 ` [gentoo-user] " Grant Edwards
2020-06-15 20:04 ` Grant Edwards
2020-06-15 23:03 ` [gentoo-user] " madscientistatlarge
2020-06-15 23:18 ` David Haller
2020-06-16 7:17 ` Dale
2020-06-16 7:32 ` William Kenworthy
2020-06-16 7:37 ` Dale
2020-06-17 15:27 ` David Haller
2020-06-18 8:07 ` Dr Rainer Woitok
2020-06-23 16:08 ` Sid Spry
2020-06-23 16:38 ` [gentoo-user] " Grant Edwards
2020-06-23 16:41 ` Sid Spry
2020-06-23 17:26 ` Dale
2020-06-23 18:32 ` Sid Spry
2020-06-23 19:37 ` Dale
2020-06-23 20:03 ` Rich Freeman
2020-06-24 4:26 ` Wols Lists
2020-06-18 9:14 ` [gentoo-user] " Dale
2020-06-22 1:52 ` Pengcheng Xu
2020-06-22 2:15 ` Dale
2020-06-22 19:10 ` David Haller
2020-06-22 20:29 ` Dale
2020-06-22 22:59 ` David Haller
2020-06-23 4:18 ` Dale [this message]
2020-06-17 6:02 ` Dale
2020-06-20 9:50 ` Dale
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=914a9d55-03f8-7791-be53-db13335706ff@gmail.com \
--to=rdalek1967@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox