[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Problem with scsi emulation



[Martin Batermann]
> Before I emulated scsi, I referred to it as /cdrom and it worked
> fine.  However, when I changed to the scsi emulation I couldn't get
> /usr/sbin/base-config to work.  Every time I try to install a
> package, it wants me to insert my debian cd in /cdrom which it
> couldn't find.  Same thing happened with ripperx.  Whenever I start
> ripperx it complains that it cannot find the cd-drive.

There are two possibilities, and I'm too lazy to check base-config to
see which one applies.  The first is that your applications are looking
for a device file /dev/cdrom, which should be a symbolic link to scd0
or scd1 (depending on which drive you want to use).  Quite a few apps
look for this for their default CD-ROM drive, so even if base-config
doesn't, it's a good idea to arrange it:

  ln -fs scd1 /dev/cdrom

The second possibility is that base-config is looking for something
listed in /etc/fstab that mounts on /cdrom .  In that case your various
symlinks won't help; what you'll need to do is 'mkdir -p /cdrom' and
add an entry to /etc/fstab reflecting it, such as:

  /dev/scd0  /cdrom  auto  ro,user,noauto  0 0

where once again you can use /dev/scd1 if you prefer that to be your
default drive.  It is OK to have multiple entries in /etc/fstab
referring to the same device, so long as they are not set to mount
automatically (the "noauto" above ensures this).

> Because I had symlinks all over the place, I tried to tidy it up a
> bit and ended up deleting /dev/scd1.  Not knowing how to get
> /dev/scd1 back, I renamed /dev/scd16 to /dev/scd1.  Now I cannot
> mount my dvd-writer.

Right - to recreate /dev/scd1, do this:

  cd /dev; MAKEDEV scd

Peter

Attachment: signature.asc
Description: Digital signature


Reply to: