Mailinglist Archive: opensuse (3337 mails)

< Previous Next >
RE: [SLE] hal/haldaemon
  • From: "Greg Wallace" <gregwallace@xxxxxxxxxxx>
  • Date: Sat, 22 Apr 2006 17:50:23 -0500
  • Message-id: <!&!AAAAAAAAAAAYAAAAAAAAABYv/fsiAbFHuuseWu7lbHnCgAAAEAAAAJRKbdwbMZBGl5lUJ50aY9ABAAAAAA==@xxxxxxxxxxx>
On Saturday, April 22, 2006 @ 5:13 PM, Ken Schneider wrote:

>On Sat, 2006-04-22 at 17:58 -0400, Doug McGarrett wrote:
>> At 04:48 PM 4/22/2006 +0200, Leendert Meyer wrote:
>> >Content-Disposition: inline
>> >
>> >On Saturday 22 April 2006 15:24, Istvan Gabor wrote:
>> >> I also cant't stand the name 'cdrecorder' (SUSE's default).
>> >
>> >That's to distinguish it from its read-only counter-part (AKA cdrom).

>Why, do they refer to different pieces of hardware? I see no need to
>have different names for the same piece of hardware just to reference a
>different operation, read or burn.

>Ken Schneider
>UNIX since 1989, linux since 1994, SuSE since 1998

My machine only has one DVD device which reads and writes CDs but only reads
DVDs. There are two different devices set up for it in fstab, /dev/cdrom
and /dev/cdrecorder. The configuration of the two is identical. One points
to /media/cdrom and the other to /media/cdrecorder. They both are of type
subfs, which I think means they're HAL managed. There was no /media/cdrom
on my machine, though I'm pretty sure there was one there before. So, just
for the heck of it, I created it again. I plugged in a CD and it
auto-mounted to /media/cdrecorder. So, I umounted it and mounted it under
/media/cdrom. When I issued the mount, I got the following message back --

mount: block device is write-protected, mounting read-only

I guess HAL is enforcing a read-only capability if you actually use
/dev/cdrom instead of /dev/cdrecorder.

Greg Wallace

< Previous Next >