qgil at desdeamericaconamor.org
Fri Jan 20 19:50:40 GMT 2006
Why a new user would use gksudo to install packages having a great basic
tool to do so under Applications, and Synaptic under System >
Administration - plus a direct connection between both?
I'm still wondering for what reason would we send a new or regular user
to gksudo or sudo on the command line.
Maybe hardware compatibility problems are a possible source of
recommendations that require sudo-ing on the command line, if only to
edit config files.
What other actions do you think would send a new user to sudo?
Discussing the sudo issue without real examples is... quite abstract.
Hardware compatibility is (still) the typical problem new users face,
but applying a solution requires sometimes advanced expertise. Or
following the steps on a FAQ or forum thread like a monkey.
Ubuntu and driver developers are doing a great work in hardware
compatibility. Making MadWifi work on Debian 18 months ago implied a lot
of sudo-ing and command line. Now in Ubuntu needs no configuration at
all. Users are also understanding that they can save a lot trouble just
picking the right devices. Hopefully in few years users won't need to
sudo (nor worry) to have hardware recognised and configured.
What else? :)
En/na Dmitriy Kropivnitskiy ha escrit:
> John Nilsson wrote:
>> One thing to experiment with is to include a more detailed description
>> of what is to be done in the gksudo dialog like this:
Quim Gil - http://desdeamericaconamor.org
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 189 bytes
Desc: OpenPGP digital signature
Url : https://lists.ubuntu.com/archives/ubuntu-devel/attachments/20060120/b77a6e61/signature-0001.pgp
More information about the ubuntu-devel