linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Valdis.Kletnieks@vt.edu
Cc: linux-kernel@vger.kernel.org
Subject: Re: ide-scsi is deprecated for cd burning! Use ide-cd and give dev=/dev/hdX as device
Date: Tue, 22 Feb 2005 15:27:36 -0500	[thread overview]
Message-ID: <421B95B8.4070006@tmr.com> (raw)
In-Reply-To: <200502190023.j1J0NBDi023090@turing-police.cc.vt.edu>

Valdis.Kletnieks@vt.edu wrote:
> On Fri, 18 Feb 2005 15:23:44 EST, Bill Davidsen said:
> 
> 
>>I'll try to build a truth table for this, I'm now working with some 
>>non-iso data sets, so I'm a bit more interested. I would expect read() 
>>to only try to read one sector, so I'll just do a quick and dirty to get 
>>the size from the command line, seek and read.
>>
>>I haven't had a problem using dd to date, as long as I know how long the 
>>data set was, but I'll try to have results tonight.
> 
> 
> The problem is that often you don't know exactly how long the data set is
> (think "backup burned to CD/RW") - there's a *lot* of code that does stuff
> like
> 
> 	while (actual=read(fd,buffer,65536) > 0) {
> 		...
> 	}
> 
> with the realistic expectation that the last read might return less than 64k,
> in which case 'actual' will tell us how much was read.  Instead, we just get
> an error on the read.
> 
> Note that 'dd' does this - that's why you get messages like '12343+1 blocks read'.
> We *really* want to get to a point where 'dd' will work *without* having to
> tell it a 'bs=' and 'count=' to get the size right....

I think I already had a pretty good grasp on that, in my previous post 
on this I noted: "The last time I looked at this, the issue was that the 
user software did a large read and the ide-cd didn't properly return a 
small data block with no error, but rather returned an error with no 
data. If you get the size of the ISO image, you can read that with any 
program which doesn't try to read MORE than that."

It sounds as if (a) the problem with ide-cd is going to get fixed, and 
(b) ide-scsi may not remain depreciated. A win-win if I ever saw one.

-- 
    -bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
  last possible moment - but no longer"  -me

  reply	other threads:[~2005-02-22 20:22 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-15  0:20 ide-scsi is deprecated for cd burning! Use ide-cd and give dev=/dev/hdX as device Sergio Monteiro Basto
2005-02-15  2:22 ` Sergio Monteiro Basto
2005-02-15  2:25   ` Randy.Dunlap
2005-02-15  3:58     ` Sergio Monteiro Basto
2005-02-15  3:56       ` Randy.Dunlap
2005-02-15 17:02     ` Alan Cox
2005-02-15 17:24       ` Randy.Dunlap
2005-02-15 17:48       ` David Gómez
2005-02-15 22:05         ` Alan Cox
2005-02-15 19:48       ` Kiniger, Karl (GE Healthcare)
2005-02-15 20:03         ` kernel
2005-02-15 23:16           ` Kiniger
2005-02-16  0:35             ` kernel
2005-02-17 23:00           ` Bill Davidsen
2005-02-15 20:15         ` Lennart Sorensen
2005-02-15 23:19           ` Kiniger
2005-02-15 21:25         ` Valdis.Kletnieks
2005-02-16  9:42           ` Kiniger, Karl (GE Healthcare)
2005-02-16 17:36             ` Valdis.Kletnieks
2005-02-17  0:44               ` Alan Cox
2005-02-17 22:58               ` Bill Davidsen
2005-02-18 10:31                 ` Kiniger, Karl (GE Healthcare)
2005-02-18 20:23                   ` Bill Davidsen
2005-02-18 20:50                     ` ide-scsi is deprecated for cd burning! Use ide-cd and give dev=/dev/hdXas device David Lang
2005-02-22 20:34                       ` Bill Davidsen
2005-02-19  0:23                     ` ide-scsi is deprecated for cd burning! Use ide-cd and give dev=/dev/hdX as device Valdis.Kletnieks
2005-02-22 20:27                       ` Bill Davidsen [this message]
2005-02-28 17:11                       ` Kiniger, Karl (GE Healthcare)
2005-02-21 15:00                   ` Alan Cox
2005-02-21 15:25                     ` Bartlomiej Zolnierkiewicz
2005-02-21 17:38                       ` Alan Cox
2005-02-21 17:46                       ` Matthias Andree
2005-02-22 21:10                       ` Bill Davidsen
2005-02-28 10:12                     ` Kiniger
2005-02-15 20:36       ` Sergio Monteiro Basto
2005-02-17  2:27         ` Sergio Monteiro Basto
2005-02-17 23:03           ` Bill Davidsen
2005-02-19 17:55         ` Sergio Monteiro Basto

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=421B95B8.4070006@tmr.com \
    --to=davidsen@tmr.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=linux-kernel@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).