All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Johnson <rmjohnson@adelphia.net>
To: Ray Olszewski <ray@comarre.com>
Cc: linux-newbie@vger.kernel.org
Subject: Re: Polaroid BurnMAX24 CD-RW
Date: Tue, 21 May 2002 23:35:48 -0700	[thread overview]
Message-ID: <3CEB3C44.8060403@adelphia.net> (raw)
In-Reply-To: 5.1.0.14.1.20020521170358.020eb310@celine



Ray Olszewski wrote:

> Mark, let's keep this discussion on the list, please. I've added it 
> back here in a Cc:.

sorry about that, I noticed the other previous ones went straight to you 
also.  I didn't catch it before, but I got this one:).  Usually when I 
reply it automaticly goes back into the group instead of to the sender.

>
> If you run the command "ls -l /dev/cdrom", you will (almost certainly) 
> find that it is not itself a pseudofile entry. Instead, it points to 
> something else, probably /dev/hdc . That's what a symlink is, sort of 
> (read "man ln" for the details).
>
> Once you moved the drive to the IDE-SCSI driver, it was no longer 
> accessible through /dev/hdc, so the /dev/cdrom symlink no longer 
> works. You now have to access it at ... well, I don't really know, but 
> /dev/scd1 is a good bet.
>
> The mount points you are using are set in /etc/fstab . In there is 
> (probably) a line that tells mount to mount /dev/hdc on mount point 
> /mnt/cdrom, and to mount whatever the pseudoSCSI-CD-R/W device is 
> (maybe /dev/scd0) on /mnt/cdrom1 . Or the mount points may use the 
> symlinks /dev/cdrom and /dev/dvd instead.
>
> In any case, once you know where (in /dev) the device pesudofile 
> entries are, you can edit /etc/fstab so the mount points connect to 
> the right devices (or to suitable symlinks).

you're right (except fstab uses /dev/cdrom as hdc and /dev/cdrom1 is 
hdd), and that is why the dvd stopped working.  When I installed the 
cd-rw it linked to cdrom, which is the dvd.  the cd-rw is cdrom1.  now 
that I have dvd as ide-scsi it is now cdrom1.  will it mess up anything 
if I just rename crom1 to cdrom and vice-versa so drive 0 is cdrom amd 
drive 1 is cdrom1. it is confusing having drive 0(cdrom1) as 1.  as for 
it not working after the changes, it was the burner programs wanting to 
have the cd ejected, it resets the cd somehow, mad a bad cd curn as I 
was burning too fast for the prgram and got data underflow.  I slowed 
her down and everything is running pretty smoothly.  I've done about 5 
tests so far with no glitches yet (fingers crossed).

>
> As before, this includes a lot of guessing, based on teh way my Debian 
> systems set themselves up out of the box. YMMV as to the dtails, but 
> this should be enough to get you started in teh right direction.

good guessing.  You were right on 100% both times with a couple minor 
(obvious) changes on my end. The only problems I really had were a few 
program glitches and me being in too big a hurry and missing a command 
or two.

Again, thanks for the help.
-=Mark=-


-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

  reply	other threads:[~2002-05-22  6:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3CE94665.8090104@adelphia.net>
2002-05-21 19:25 ` Polaroid BurnMAX24 CD-RW Ken Moffat
2002-05-21 20:48   ` Richard Adams
     [not found] ` <Pine.LNX.4.21.0205212006510.24300-100000@pppg_penguin.linu x.bogus>
2002-05-21 19:59   ` Ray Olszewski
     [not found]     ` <3CEAD413.3070104@adelphia.net>
2002-05-22  0:13       ` Ray Olszewski
2002-05-22  6:35         ` Mark Johnson [this message]
2002-05-22 16:33     ` Ken Moffat
2002-05-18  5:43 Ray Olszewski
2002-05-19 14:48 ` Ken Moffat
  -- strict thread matches above, loose matches on Subject: below --
2002-05-17  3:25 Ray Olszewski
2002-05-17  3:02 Mark Johnson

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=3CEB3C44.8060403@adelphia.net \
    --to=rmjohnson@adelphia.net \
    --cc=linux-newbie@vger.kernel.org \
    --cc=ray@comarre.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.