Sujet : Re: Yet Another New systemd Feature
De : gtaylor (at) *nospam* tnetconsulting.net (Grant Taylor)
Groupes : comp.os.linux.miscDate : 09. May 2024, 03:31:22
Autres entêtes
Organisation : TNet Consulting
Message-ID : <v1h91a$kln$1@tncsrv09.home.tnetconsulting.net>
References : 1 2 3 4 5 6 7 8 9 10
User-Agent : Mozilla Thunderbird
On 5/8/24 13:32, Carlos E.R. wrote:
Mmm? What is the advantage?
It really depends on what command you do use and what the target user's account is configured with.
`sudo -i` starts the target user's login shell directly. So it might be comparable to `sudo bash` if the target user's shell is bash, but will be different if the target user doesn't have bash as their default shell.
I have aliases `si` to `sudo -i` and `s` to `sudo`. So `si` and `s` are shorter to type and I prefer them.
I also don't know about it. Why should I use it?
I went on a bit of an embrace and extend sudo to make it streamlined for the environments that I work in.
I've also configured sudo on my personal systems to be able to authenticate to sudo with my ssh key.
I've also created a wrapper that I have in my ~/bin directory that keys off of $0 as to what command to pass to sudo. So I have ~/bin/ifconfig -> ~/bin/sudo.wrapper so that I can simply type `ifconfig` as my user and it's run with sudo. It's also authenticated by my ssh key so I'm not prompted for a password.
I'm embracing sudo and making it work for -> do things for me in a way that I don't even need to think about it.
I'd have to stop and think about how much, if any, of that could be replaced with something other than sudo. But seeing as how sudo is standard on the Linux, FreeBSD, Solaris, and AIX systems I work with, I'm somewhat reluctant to find an alternative. Though I do try to keep an open mind and learn about other options.
-- Grant. . . .