Kernel 2.6.8-2.6.11-rc1... What The HECK??????????
I have tried compiling kernels on my 9.1 system since 2.6.8 and NONE since then have had CD Burning as a normal user work. 2.6.9-1.6.11-rc1 have started but not fixated and 2.6.8/2.6.8.1 haven't let a normal user even see the CD-RW. I tried 2.6.7 and it actually worked, but is kind of old considering how fast the kernel develops. Am I doing something wrong? I use k3b 0.11.18 and have also tried from a terminal. Should I re-compile cdrecord? Oh, yea, it DOES work as root, but not as a normal user. Thanks! -Steven
* Steven Pasternak
I have tried compiling kernels on my 9.1 system since 2.6.8 and NONE since then have had CD Burning as a normal user work. 2.6.9-1.6.11-rc1 have started but not fixated and 2.6.8/2.6.8.1 haven't let a normal user even see the CD-RW. I tried 2.6.7 and it actually worked, but is kind of old considering how fast the kernel develops. Am I doing something wrong? I use k3b 0.11.18 and have also tried from a terminal. Should I re-compile cdrecord? Oh, yea, it DOES work as root, but not as a normal user.
There is/has been much discussion of this topic on *this* list as recently as today. I suggest you scan the archives via google. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos
I have tried compiling kernels on my 9.1 system since 2.6.8 and NONE since then have had CD Burning as a normal user work. 2.6.9-1.6.11-rc1 have started but not fixated and 2.6.8/2.6.8.1 haven't let a normal user even see the CD-RW. I tried 2.6.7 and it actually worked, but is kind of old considering how fast the kernel develops. Am I doing something wrong? I use k3b 0.11.18 and have also tried from a terminal. Should I re-compile cdrecord? It won't help. There were security changes in the kernel that affected cdrecord (and many other program, i.e ntp, bind, etc.) starting with 2.6.8. After 2.6.9, it appears they got it working again, but with a caveat. It checks which user is running a process (to protect against
Steven Pasternak wrote: processes elevating their privilege) and keeps track of it. Cdrecord used to need suid root to work as a non-root user. Now, making it suid will cause it to fail as a user. After 2.6.9, cdrecord needs to be 0755. Since SuSE backports a lot of innovation of newer kernels in their kernels, this numbering would not necessarily follow with a stock SuSE kernel. I am running a patched vanilla 2.6.10, and after returning my privileges to the default on cdrecord, it works fine as a user for me using k3b version 0.11.18-3, both with my self-compiled kernel and the SuSE one. Googling and k3b's site will give more info if your interested. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871
El Viernes, 14 de Enero de 2005 22:45, Steven Pasternak escribió:
I use k3b 0.11.18 and have also tried from a terminal. Should I re-compile cdrecord? Oh, yea, it DOES work as root, but not as a normal user. Thanks!
Simply, start with the kernel you want to use and then use k3bsetup to fix permissions. To do it manually, for kernel <= 2.6.7: chmod 666 /dev/hdc chmod 666 /dev/hdd chmod +s /usr/bin/cdrecord and if kernel >=2.6.8: chmod 666 /dev/hdc chmod 666 /dev/hdd chmod -s /usr/bin/cdrecord Miquel.
participants (4)
-
Joe Morris (NTM) -
Miquel A. Noguera -
Patrick Shanahan -
Steven Pasternak