SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Just installed 13.0 and was kind of surprised that I did not have to set up a burning group to give regular users burning rights. Is this something new with the new version? I always had to do it before in previous versions or the burn would fail due to lack of privileges.
This is also the first time I've used HAL with Slackware, if that makes any difference.
I think if you hit the up arrow during the install when you add a user, it adds you to all the groups you need. In Arch Linux I add myself to the optical group, I think in Slackware it is CDROM??
Yeah, in Slackware cdrom is one of the default groups every one is put in when using adduser: users, audio, video, cdrom, plugdev. Up arrow gives the option to add more groups.
Maybe I was misleading myself into thinking that I ever needed to use the burning group. In KDE 3.5 I just always set it up through the GUI as shadowsnipes mentions. In 4.2 that option seems to have changed as the k3bsetup has been moved from the regular k3b menu to the system settings menu. It appears that k3bsetup has to be run from the command line now if you want to use it with root access to change anything.
I never did add myself to the cdrom or plugdev groups in 12.2, because I didn't use HAL. Maybe that's why I couldn't burn without using the burning group? Or maybe I could and just never tried :^)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.