2011/9/3 Stephen Allen <marathon.duran...@gmail.com>: > On Sat, Sep 03, 2011 at 11:32:00AM +0000, darkestkhan wrote: >> 2011/9/3 Stephen Allen <marathon.duran...@gmail.com>: > >> > It contains just 2 fields; >> > >> > # User privilege specification >> > root ALL=(ALL:ALL) ALL >> > >> > # Allow members of group sudo to execute any command >> > %sudo ALL=(ALL:ALL) ALL >> > >> >> /etc/sudoers contains informations about who has rights to access root >> level privileges (though I know it can do much more, like giving only >> limited privileges) >> >> at the bottom of /etc/sudoers you should have this line: >> username ALL=(ALL) ALL >> >> where username is the name of user that will have root level >> privileges, so in my case it is like this: >> darkestkhan ALL=(ALL) ALL >> >> >> You will probably have to run in maintenance (or rescue, forgot how it >> was called) mode, after that (or reboot) everything should work > ---end quoted text--- > > Cool. Thanks for the help. > > Strange why that line isn't there aye? >
Well, probably because maintainers can't be sure about which user should have root level privileges, so it has actualized file without asking question whether it should do so (this one is because of synaptic, can't blame it - most (nontechnical) users won't notice those changes, and in most cases system doesn't brake). As I'm updating from command line I got information about changes in /etc/sudoers but I decided to handle this manually as tool for merging changes in config files is not too helpful (but it could be, arch and gentoo are doing much better in this aspect) darkestkhan ------------------------------------------ Feel free to CC me. jid: darkestk...@gmail.com May The Source be with You. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CACRpbMh+e6yxwab=BHNMLB2mUwQ9xTwn=wo_c+zcf7egowm...@mail.gmail.com
