I instald the 2007.1 and I like it a lot... but this new K3b witch comes with the distro doasn't have the k3b setup2 program witch updated the permissions on cdrecord and other burning command... and I got a warnning about not using these as root.... how can I update manually or set it up to use them as root?

I have the same problem. My k3b's "Setup k3b" menu item is missing, so I can't configure the permissions.

You could chown k3b I suppose. What I've usually done is to change the permissions of the programs needed (generally CDRecord (now Wodim I think), cdrdao, mkisofs, growisofs, dvd+rwtools) to user rather than root. Open a Terminal & log in as root using the su command, Return, followed by root password, then type chown user:user /usr/bin/[package]

This has generally had the desired effect of improving performance & allowing certain actions such as burning iso dvd's that were otherwise failing, although I don't know how advisable it actually is from a security point of view - I've never had any problems though.

THX for the quick reply....
If I understand it right this is the correct form of the command:
chown rootilatus /usr/bin/cdrecord

No, you log in as root first - open a terminal, type su, press return, type your root password (the password you use to open the Mandriva Control Centre or install software)& then press return again. The prompt'll then say something like[root @ localhost]#. Next type chown user:user /usr/bin/whatever it is you want to change, where user is your the name that you log in with normally.

This command is also very useful if you ever need to edit any configuration files that are in the root directory.

Hope that's a bit clearer. Don't worry about getting it wrong- the command line still confuses the life out of me & I've been using Linux for a good few years. In fact to my shame, chown is about the only command I really ever use!

You don't need to change permissions. When the "warning" appears just click the box that you don't want to see it again, and close it. K3B will work just fine for your user.

THX for the clearings.... I just didn't understand the chown command now it's OK...

Yeah I know but If you run it as a normal user it may haw problems.... and it's a lot faster when burning DVD's whit root permissions...

This is true...

What I really wish could be done myself, is allow any user to run k3b, but have it run with root permission, while at the same time, no need for the user to know the root password, AND no way to get the root password (especially in an easy way, like reading a shell script file, text file, exc.)

S'alright. Chown stands for change owner by the way

Create a burner group (any name that makes sense to you will work). Edit your new burner group to make the user(s) you want to have access to burn disks member(s). The easiest way to do this is with Userdrake (System > Configuration > Other > User Administration in the menu system). Finally change the group ownership of the associated software to burner: Allow group members to execute the file:Any file named in the K3b warning is a good candidate (or the base file to which it links e.g.: /usr/bin/cdrecord links to /etc/alternatives/cdrecord which links to /usr/bin/wodim), so /usr/bin/wodim is a good candidate. /usr/bin/cdrdao, and /usr/bin/growisofs may be other good candidates. The advantage here is that you can choose which users in a multi-user environment can have access to burning a disk to CD or DVD.

HTH,

Until here everything seemed ok:
[root@localhost pilatus]# chgrp iras /usr/bin/cdrecord
[root@localhost pilatus]# chgrp iras /usr/bin/wodim
[root@localhost pilatus]# chgrp iras /usr/bin/cdrdao
[root@localhost pilatus]# chgrp iras /usr/bin/dvd+rw-format
[root@localhost pilatus]# chgrp iras /usr/bin/growisofs
but the next step is not working:
[root@localhost pilatus]# usermod g +x /usr/bin/cdrecord
usermod: user /usr/bin/cdrecord does not exist
then I tryed the command this way to:
[root@localhost pilatus]# usermod g pilatus +x /usr/bin/cdrecord
usermod: user /usr/bin/cdrecord does not exist
[root@localhost pilatus]# usermod g pilatus +x /usr/bin/wodin
usermod: user /usr/bin/wodin does not exist
[root@localhost pilatus]# usermod g iras +x /usr/bin/wodin
usermod: user /usr/bin/wodin does not exist
[root@localhost pilatus]#
but neither way works... what did I wrong or what did I miss.....
edit: iras=the burning group that I created, pilatus=the user witch I use

I believe it is wodim not wodin

My point here is that the cdrecord warning, although relevant, is kind of a bit wrong since wodim has become the default. But the chown suggestions are correct

(and so new default is geniso or whatever it is called instead of mkisofs)

Still not working:
[root@localhost pilatus]# usermod g iras pilatus +x /usr/bin/wodim
usermod: user /usr/bin/wodim does not exist
[root@localhost pilatus]# usermod g +x /usr/bin/wodim pilatus
usermod: no flags given
[root@localhost pilatus]# usermod g iras +x /usr/bin/wodim pilatus
usermod: no flags given

and it's wreally frustrating cauze now the max dvd writing speed is 1-2x and it takes more than a half an hour to burn a dvd.....

install the locate package
then
locate wodim
to find where wodim hides
(or use konqueror and find function)

or type as root
which wodim