From: James <james@piku.org.uk>
To: linux-admin@vger.kernel.org
Subject: Re: Producing ISO from CDROM
Date: Sun, 19 May 2002 22:37:33 +0100 [thread overview]
Message-ID: <20020519213733.GN10446@piku.org.uk> (raw)
In-Reply-To: <20020519205953.42758.qmail@web12506.mail.yahoo.com>
On Sun, May 19, 2002 at 01:59:53PM -0700, fred pasteck wrote:
|
| # dd if=/dev/hdc of=cdrom.iso
| dd: reading `/dev/hdc': Input/output error
| 1000480+0 records in
| 1000480+0 records out
This happens with me, but the resulting ISO always works... I just
ignored it.
| Should I be using 512k blocks and the specific number
| of blocks with the count= argument? My reason for
No, if anything you should be using blocks that are 2048 bytes since
that's what CDs use. Look that number up though, I might have got it
wrong.
--
I will not sell land in Florida
6AD6 865A BF6E 76BB 1FC2 | www.piku.org.uk/public-key.asc
E4C4 DEEA 7D08 D511 E149 | www.piku.org.uk wnzrf@cvxh.bet.hx (rot13'd)
next prev parent reply other threads:[~2002-05-19 21:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-19 20:59 Producing ISO from CDROM fred pasteck
2002-05-19 21:37 ` James [this message]
2002-05-20 1:38 ` Michael French
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=20020519213733.GN10446@piku.org.uk \
--to=james@piku.org.uk \
--cc=linux-admin@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).