Ian- By default, the local console user is granted ownership of various devices to allow an easier desktop experience. At least on Red Hat, which devices to grant is defined in /etc/security/console.conf . It's been ages since I looked at this file, because now I no longer have a dual terminal server/desktop configuration, but I imagine if you look there will be some comments that will help you out.
-Todd [EMAIL PROTECTED] wrote: > Thx to Todd and Petre for the responses. > > Todd, I checked the /dev. The device is owned by root.disk with 660 > permission. I added the user to the "disk" group and it worked. > However, I noticed that if someone was using the server directly, the > device ownership changed to the login user (with the same "disk" > group) and the permission changed to 600, therefore defeating the > group-based permission. Is there a way to keep the group permission > even though someone is using the server directly? I guess I need your > help in setting up the udev rules. > > Petre, yes sudo worked too, but I'd rather avoid giving sudo to k3b > since it will allow the user to peek into other user's files. Thx for > the info about the webCDwriter. It could provide an alternative solution. > > -ian > > > Todd Shoemaker wrote: >> Ian- >> >> In general the cdrom device (usually /dev/cdroms/cdrom0, which is >> usually a symlink to /dev/ide/... ) will be assigned an owner of >> root, but most distros assign these device to relevant groups, such >> as "cdrom". Take a look at which group FC5 assigns to your cdrom >> device (use 'ls -l /dev/cdroms/', and then use ls -l on the file that >> cdrom0 points to). If it is a group like "cdrom" or "users", and the >> group has read/write permissions on the device, then you can add that >> user to the group and K3B should work. Let me know if you need help >> with any of the commands I mentioned. If FC5 didn't assign the >> device to a group, then we can help you add a rule to the udev rules >> to grant permissions to a group. >> >> -Todd >> >> [EMAIL PROTECTED] wrote: >>> I need help in configuring my Fedora Core 5 LTSP server to allow a >>> regular user to burn a CD from his/her LTSP client. >>> The drive is installed in the server. However, a regular user from a >>> remote client cannot see this drive when he/she tries to burn a CD >>> using K3B. >>> If the user login to the server directly, then the user can access >>> the drive. >>> Right now, the only way to do it from a remote client is to run K3B >>> as a superuser. >>> >>> Has anybody experience this? >>> >>> Regards, >>> -ian >>> >>> >>> ------------------------------------------------------------------------- >>> >>> Take Surveys. Earn Cash. Influence the Future of IT >>> Join SourceForge.net's Techsay panel and you'll get the chance to >>> share your >>> opinions on IT & business topics through brief surveys -- and earn cash >>> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV >>> >>> _____________________________________________________________________ >>> Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: >>> https://lists.sourceforge.net/lists/listinfo/ltsp-discuss >>> For additional LTSP help, try #ltsp channel on irc.freenode.net >>> >>> >> > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
