public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: linux-kernel@vger.kernel.org
To: kronos@kronoz.cjb.net
Cc: Pat LaVarre <p.lavarre@ieee.org>,
	linux_udf@hpesjro.fc.hp.com, linux-kernel@vger.kernel.org
Subject: Re: Unable to read UDF fs on a DVD
Date: Mon, 26 Apr 2004 11:52:25 -0400	[thread overview]
Message-ID: <408D3039.6090604@tmr.com> (raw)
In-Reply-To: <20040424194727.GA3353@dreamland.darkstar.lan>

Kronos wrote:
> Il Fri, Apr 23, 2004 at 02:21:15PM -0600, Pat LaVarre ha scritto: 
> 
>>P.S. Five postscripts:
>>
>>1)
>>
>>
>>>even with ide-scsi, though.
>>
>>Whoa.  You weren't engaging in the taboo act of running ide-scsi in 2.6
>>back when ls failed, were you?
> 
> 
> No, I wasn't. I'm aware that ide-scsi is not needed with 2.6. I had to
> recompile the kernel with ide-scsi to make Philips fsck happy.

I believe that it would be more correct to say that ide-scsi is not 
required to burn CDs and DVDs, providing you use cdrecord which has been 
modified to work with ide-cd. Since that's the major use it equates to 
"not needed" if that's all you do.

As you seem to note, some DVD burners don't work without ide-scsi unless 
you have some tricks and/or patches, but do work with ide-scsi. Yes, 
even in 2.6.

I totally agree you should try to run without it, but I'd compile it as 
a module in case you need some additional data points.


-- 
    -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:[~2004-04-26 15:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-23 16:28 Unable to read UDF fs on a DVD Kronos
2004-04-23 17:56 ` Pat LaVarre
2004-04-23 19:50   ` Kronos
2004-04-23 20:21     ` Pat LaVarre
2004-04-24 19:47       ` Kronos
2004-04-26 15:52         ` Bill Davidsen [this message]
2004-04-26 21:48         ` Pat LaVarre
     [not found] <OF7EE48D71.4DD148E6-ONC1256E82.003678FE-C1256E82.0038D7EE@phili ps.com>
     [not found] ` <OF7EE48D71.4DD148E6-ONC1256E82.003678FE-C1256E82.0038D7EE@phil i ps.com>
2004-04-26 21:24   ` Pat LaVarre
     [not found] <OFA36FDF30.41353846-ONC1256E83.0039A57A-C1256E83.003B5183@phili ps.com>
     [not found] ` <OFA36FDF30.41353846-ONC1256E83.0039A57A-C1256E83.003B5183@phil i ps.com>
2004-04-27 16:11   ` Pat LaVarre
2004-04-27 19:48     ` Pat LaVarre

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=408D3039.6090604@tmr.com \
    --to=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux_udf@hpesjro.fc.hp.com \
    --cc=p.lavarre@ieee.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