why is /dev/cdrom owned by root:disk after installation?

From: H. S. (greatexcalibur_at_yahoo.com)
Date: 03/16/04

  • Next message: Steve Lamb: "Re: Next stable release: 13 CD's"
    To: debian-user@lists.debian.org
    Date: Tue, 16 Mar 2004 14:09:25 -0500
    
    

    (okay, now I know why my previous two attempts at getting this throug
    have failed: wrong email address)

    Hi,

    I have installed Debian a few time (Woody as well as Sarge). Each time I
    notice that after installation, my CDROM device /dev/cdrom is linked to
    /dev/hdc. But /dev/hdc is owned by root:disk.

    After some research on google and mailing lists, I always reach the
    conclusion that to make any user able to use the CDROM properly, the
    ownership of /dev/hdc need to be changed to root:cdrom, and all users
    need to be made members of the 'cdrom' group. Making the users members
    of 'disk' group is vehementlyl discouraged, apparently it is not a good
    practice from security point of view.

    So why is it the CDROM devices are owned by root:disk? If we always have
    to change (at leat I have to, and from newsgroups many other people have
    to too) the ownership to root:cdrom, and make all users members of cdrom
    group (after all, what other purpose is a CDROM for if not for the use
    of the users?), why do the developers not take this into account and
    configure the CDROM device accordingly and *not* make it owned by
    root:disk but by root:cdrom? And make all users members of the "cdrom"
    groups when they are created? Am I missing something here?

    ->HS

    -- 
    To UNSUBSCRIBE, email to debian-user-request@lists.debian.org 
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
    

  • Next message: Steve Lamb: "Re: Next stable release: 13 CD's"

    Relevant Pages

    • Re: IRP Response
      ... Dude just attach to the CDROM device and you'll get get the routines ... a class upper filter driver in the device stack. ...
      (microsoft.public.development.device.drivers)
    • Re: How to create .iso file image of cdrom (atapi)?
      ... > already `contains' the iso. ... equivalent to the image file created with sysutils/mkisofs, ... assumes that your CDROM device is acd0. ...
      (freebsd-questions)
    • Re: How do I access the CDROM?
      ... > I've got a tar file I'd like to extract, and it is on a CDROM (which was ... > I know how to use tar, but I can't seem to locate the cdrom device. ... First you have to mount the device. ...
      (alt.os.linux.suse)
    • Re: How to detect SATA cdrom
      ... Frans pop emailed me and showed me how to fix the problem: ... Now that everything is installed Debian doesn't detect the cdrom, ... To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx ...
      (Debian-User)
    • unmounting cdrom
      ... It often happens after mounting a cdrom and copying some material from it ... to a directory of the hard drive, that my attempts at unmounting are ... greeted with the error message that the cdrom device is busy. ...
      (alt.os.linux)