Re:How the Linux desktop shoots itself in the foot.
by 3pt14159 on Thursday October 15, 2009 @08:37AM
(#883235)
The thing that bothers me in Ubuntu is this: Sometimes I want to do something with a desktop app on a file in /var/ or /bin/ the desktop app tells me "permission denied" or what have you. How the hell do I type "SUDO" and my password? Even if there is a way (which I doubt) if it isn't obvious to me, then it certainly will not be obvious to other potential users.
[ Parent
| on HN ]
Re:How the Linux desktop shoots itself in the foot.
by pbhjpbhj on Thursday October 15, 2009 @09:04AM
(#883283)
If this annoys you and you can't work out how to fix that annoyance or work around it then messing around in /var or /bin is going to ruin your installation. Having a barrier to entry is often a good idea IMO.
One could solve it by having a "reveal content" button that allows you to enter the dir by entering the su password ... but I think that makes it a little too easy.
For me Alt+F2 and "kdesudo dolphin" doesn't seem too tricky (especially with autocomplete) to get a root fm.
Re:How the Linux desktop shoots itself in the foot.
by brunov on Thursday October 15, 2009 @08:57AM
(#883266)
Regular users shouldn't have to edit files in /var/ or /bin or anything other than /home/sixpackjoe.
If you are savvy enough to know what you are doing editing system files, then you should know about doing so from the command line using sudo, or use gksudo as pointed before.
Re:How the Linux desktop shoots itself in the foot.
by RyanMcGreal on Thursday October 15, 2009 @09:08AM
(#883291)
I've found that it works if you launch the application from the command shell using sudo, e.g.:
`sudo gedit /boot/grub/menu.lst`
But as others have noted, the average user shouldn't have to edit system files.