2

I was just thinking : with Windows Vista, two of my pals has issues editing some files on which they have no right...
And we get really **** of trying to edit these files.

So I was thinking about one thing : of course it's easy to take root rights with a shell, but it would be nice if the end-user could open files in root mode whenever he wants to.

Maybe KIO could do that ? While trying to save a file you don't have rights on, a notification would appear and tell us we don't have the right to modify the file, and asking us if we want to become root to edit this file, or if we want to save it elsewhere, or to do nothing.

No ?

I think there are "open as root" service menus. Would that do what you want?

I don't think this is really related to KIO.

I'm not sure it's a good idea to ask for the root password as soon as you want to edit a file you don't have permission to write to. For new users, it could become something like UAC in Vista (you know, this dialog); an annoying dialog that you just click away without a second thought (but it is even more annoying in "Linux", because you have to type a password each time!). After all, there's a reason you (the user) can't edit the files.

If you know you have to open a file as root, you can do it from service menus such as this one.

If you need to edit some files which your user have no right to, to the point of it getting annoying, what you need to do is fix your permissions.

Alec wrote:If you need to edit some files which your user have no right to, to the point of it getting annoying, what you need to do is fix your permissions.

chown_ -R hans / ?

You need to write your password when you launch your package manager too, right? Maybe this isn't a bad idea, it might be me who's not used to think in that way (since I rarely encounter the same problem).

Hans wrote:

Alec wrote:If you need to edit some files which your user have no right to, to the point of it getting annoying, what you need to do is fix your permissions.

chown_ -R hans / ?

You need to write your password when you launch your package manager too, right? Maybe this isn't a bad idea, it might be me who's not used to think in that way (since I rarely encounter the same problem).

Heh, well, if you're constantly writing stuff all over your system, you might have a different problem

As for the package manager (if you are sure no one will come to your computer and uninstall your glibc!), you can can give yourself the privilege by editing the sudoers file. It would look something similar to this (you edit the file with the command "visudo"):

Code: Select all

%shutdown       laptop=(root) NOPASSWD: /sbin/reboot.sh
%shutdown       laptop=(root) NOPASSWD: /sbin/halt.sh

This allows me to run the script "sudo /sbin/reboot.sh" as root and it does not ask for the password as long as I'm in the group "shutdown."

Ah, I know about sudoers; was just reflecting over the whole "ask for root password when the user doesn't understand why", if it really is as bad as I said in my first post.

Conclusion: I don't really know, so I will stop guessing and let those who know do the talking.