4 blocked updates

[Muzer]

Donn wrote:
> On Friday, 05 June 2009 20:52:37 Muzer wrote:
>   
>> Because sudo doesn't change the home directory to the /root directory
>> (when kdesudo does), 
>>     
> I think you mean that kdesudo does not change things to root ownership. But 
> then I am not sure why you think this. I could be wrong, but the whole point 
> of *any* sudo is to become (some kind of) root. After that, whatever files are 
> made are made as root. So, kdesudo would have the same effect for that.
>
> Nearest I can tell kdesudo does some fancy footwork with display vars in order 
> to get access to X so that graphical apps can run as root. I am very fuzzy 
> about the details. Make that 100% ignorant :)
>   
Well, running kate with sudo, I get this output:
muzer at muzer-desktop:~$ sudo kate
Error: "/var/tmp/kdecache-muzer" is owned by uid 1000 instead of uid 0.
Error: "/tmp/kde-muzer" is owned by uid 1000 instead of uid 0.
Calling appendChild() on a null node does nothing.
Error: "/tmp/ksocket-muzer" is owned by uid 1000 instead of uid 0.
kate(4492) KToolInvocation::klauncher: klauncher not running... 
launching kdeinit
Error: "/tmp/kde-muzer" is owned by uid 1000 instead of uid 0.
Error: "/tmp/ksocket-muzer" is owned by uid 1000 instead of uid 0.
kdeinit4: Shutting down running client.
kdeinit4: preparing to launch /usr/lib/kde4/libexec/klauncher
Error: "/tmp/ksocket-muzer" is owned by uid 1000 instead of uid 0.
Error: "/tmp/kde-muzer" is owned by uid 1000 instead of uid 0.
kdeinit4: preparing to launch /usr/bin/kded4
Error: "/var/tmp/kdecache-muzer" is owned by uid 1000 instead of uid 0.
Error: "/tmp/kde-muzer" is owned by uid 1000 instead of uid 0.
kdeinit4: preparing to launch /usr/bin/kbuildsycoca4
kbuildsycoca4 running...
Error: "/var/tmp/kdecache-muzer" is owned by uid 1000 instead of uid 0.
kdeinit4: preparing to launch /usr/bin/kbuildsycoca4
kbuildsycoca4 running...
Error: "/var/tmp/kdecache-muzer" is owned by uid 1000 instead of uid 0.
Error: "/var/tmp/kdecache-muzer" is owned by uid 1000 instead of uid 0.
kdeinit4: preparing to launch /usr/lib/kde4/libexec/kconf_update
kdeinit4: preparing to launch


But with kdesudo, I get no errors at all (and I know it still is 
outputting to the terminal since I get messages when it closes). I think 
what it does is it properly changes all of the username variables, the 
home directory, etc, whereas sudo doesn't.

I can't remember any examples unfortunately, but I have had apps that 
deny me access to certain files in my home directory if I ever load it 
with sudo rather than kdesudo.
>   
>>> Which examples of command-line bins would you use kdesudo to run?
>>>       
>> Well, anything that needs a config file in ~. Things like midnight ...
>>     
> I think I see what's going-on here. Some people would rather run Dolphin or 
> Konqueror under kdesudo in order to find and edit some config file (or change 
> some file permission) that is not owned by their normal user account. So, yes 
> kdesudo would be useful to them.
>
> \d
>   


-- 
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCS/CM/IT d>++ s+:- a---- C+++ UL+++>++++ P+>+++ L+++>+++++ E---->--- W+++ N o? K? w--- O+ M-- V- PS PE? Y-- PGP- t+ 5? X- R-- tv+ b++ DI D G++ e- h! !r y 
------END GEEK CODE BLOCK------