Eric Dondelinger <Eric.Dondelinger(a)linux.lu> wrote: Hi,
On Wed, May 10, 2006 at 09:05:34AM -0700, Gilles Maria-Sube wrote:
   Recently I installed Ogle video player on Suse10.0,
and once done,
 Ogle failed to start, printing several messages, I remember on
 previous installations that it is due to the file /etc/fstab which
 is incomplete; initial content is:
  /dev/hda4   /                    ext3       acl,user_xattr        1 1
  /dev/hda2   /boot                ext3       acl,user_xattr        1 2
  /dev/hda3   swap                 swap       defaults              0 0
  proc        /proc                proc       defaults              0 0
  sysfs       /sys                 sysfs      noauto                0 0
  usbfs       /proc/bus/usb        usbfs      noauto                0 0
  devpts      /dev/pts             devpts     mode=0620,gid=5       0 0
  /dev/cdrecorder   /media/cdrecorder    subfs
noauto,fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0
  /dev/hda1   /windows/C           ntfs       ro,users,gid=users,umask=0002,nls=utf8 0 0
  (assuming /dev/hda1 is used for windows partition);but it lacks
 something for the cdrom which should be mounted on /mnt/cdrom;
 I suppose this is why dvd cannot be read. 
Do you have separate DVD-ROM and a recorder? If not, /dev/cdrecorder
and your DVD reader are the same device. A solution might be as simple
as putting a symlink /dev/cdrom pointing to /dev/cdrecorder then.
You might of course add a separate entry. I don't have a recent SuSE
around, but on Debian this would look like this:
/dev/cdrom /mnt/cdrom iso9660   ro,user,noauto 0 0
or /dev/hdc (or similar) instead of /dev/cdrom
On older RedHat things are very similar.
 No, DVD-ROM and cdrom are the same; however I have two file descriptor /dev/cdrecorder
and /dev/cdrom, so why not two entries, but your answer seems logical; this happens on my
laptop ACER TM660; by comparison on my laptop Ferrari4000 i'm working with a
Mandriva2006 and I have one entry too:
 /dev/hdc /mnt/cdrom auto
umask=0022,user,iocharset=iso8859-15,codepage=850,noauto,ro,exec,users 0 0
   Unfortunately I modified this file, adding wrong
parameters and since
 this time I cannot open any session on KDE or GNOME: when entering
 user name and passwd on KDE I have the messages: 'could not start
 kstartupconfig' and after I have 'could not start kdeinit'. 
?? sounds *very* strange.
 Well I'm not sure the source of this problem comes from modification in fstab,
obviously I have modified something in the system who generate this behaviour but what???
Greetings & hth, Eric