public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: "L. C. Robinson" <lcr@onewest.net>
To: blinux-list@redhat.com
Subject: Re: Sony cd writer problem (Martin)
Date: Tue, 29 Oct 2002 01:16:08 -0700 (MST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0210290027070.1149-100000@rupin.localnet> (raw)
In-Reply-To: <200210261203.g9QC35G02496@dc.cis.okstate.edu>

A few hints:
On our systems here, we have:
ls -l /dev/cdrom                 
lrwxrwxrwx   1 root     root            8 Feb 28  2001 /dev/cdrom -> /dev/sr0
for our CD-RWs

Also from ... doc/cdrtools-cdrecord-1.10/README.ATAPI:
   5.  In the /etc/lilo.conf file add an append line for ide-scsi, in
   my case:
        append = "hdc=ide-scsi hdd=ide-scsi"

And from ... doc/cdrtools-cdrecord-1.10/README.linux:
   -       Linux driver design oddities ******************************************
        Although cdrecord supports to use dev=/dev/sgc, it is not recommended
        and it is unsupported.

        The /dev/sg* device mapping in Linux is not stable! Using dev=/dev/sgc
        in a shell script may fail after a reboot because the device you want
        to talk to has moved to /dev/sgd. For the proper and OS independent
        dev=<bus>,<tgt>,<lun> syntax read the man page of cdrecord.

Hope that helps, LCR

On Sat, 26 Oct 2002, Martin McCormick wrote:

> "Willem van der Walt<vdwaltw@health.gov.za>" writes:
> >What does some thing like 

> >produce? Does it open the drive or complain about the device?
> 
> 	Actually, neither.  It complains about the eject command.
> 
> 	/dev/scd0 is known by the system and works fine at least
> when I am mounting a CDROM for reading.
> 
> 	Before using the SCSI emulation, this device was
> /dev/cdrom so that behavior is exactly as it should be.
> 
> 	This is the darndest problem I have come across yet.  If
> I type
> 
> mount /dev/scd0 /mnt
> 
> I can read the disk as if it was a SCSI device.  I don't know
> what else to try.
> 
> 	By the way, my utmost thanks to everybody who has had a
> suggestion.  I think I have either done something very odd in the
> setup or kernel building process or we have a bug of some kind.
> This just doesn't add up.

-- 
L. C. Robinson
reply to no_spam+munged_lcr@onewest.net.invalid

People buy MicroShaft for compatibility, but get incompatibility and
instability instead.  This is award winning "innovation".  Find
out how MS holds your data hostage with "The *Lens*"; see
"CyberSnare" at http://www.netaction.org/msoft/cybersnare.html




  reply	other threads:[~ UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Martin McCormick
 ` L. C. Robinson [this message]
  -- strict thread matches above, loose matches on Subject: below --
 Martin McCormick
 Martin McCormick
 ` Willem van der Walt<vdwaltw@health.gov.za>
 Willem van der Walt<vdwaltw@health.gov.za>

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=Pine.LNX.4.44.0210290027070.1149-100000@rupin.localnet \
    --to=lcr@onewest.net \
    --cc=blinux-list@redhat.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).