From: David Haller <gentoo@dhaller.de>
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 21:10:24 +0200 [thread overview]
Message-ID: <20200622191024.5djoxb4aroowwb6t@grusum.endjinn.de> (raw)
In-Reply-To: <91bbab90-88b1-47ac-3c80-a8a842b5b48f@gmail.com>
Hello,
On Thu, 18 Jun 2020, Dale wrote:
>David Haller wrote:
[..]
>> Compile with:
>> gcc $CFLAGS -o ones ones.c
>> or
>> gcc $(portageq envvar CFLAGS) -o ones ones.c
>>
>> and use/test e.g. like
>>
>> ./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' ;)
>I'm assuming that if I want to target sdb, I'd
>replace null with /dev/sdb.
Yes.
>As I've posted before, even my scripting skills are minimal. Surprised
>I got it to compile even.
Well, you could copy & paste and on gentoo, there is bound to be a
'gcc' ;)
>something. I placed all this in the /root directory. I'm assuming I
>can copy paste the commands above while in /root to make it work?
Yes. Or put 'ones' in /root/bin/ or even /usr/local/bin. Depending on
if you expect to use the program later on. But if it's just for this
once it's fine in /root/ alongside the sourcecode.
HTH,
-dnh
--
BUGS
It is not yet possible to change operating system by writ
ing to /proc/sys/kernel/ostype. -- Linux sysctl(2) manpage
next prev parent reply other threads:[~2020-06-22 19:10 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 [this message]
2020-06-22 20:29 ` Dale
2020-06-22 22:59 ` David Haller
2020-06-23 4:18 ` Dale
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=20200622191024.5djoxb4aroowwb6t@grusum.endjinn.de \
--to=gentoo@dhaller.de \
--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