Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #205561 > unrolled thread
| Started by | Pierre Couderc <pierre@couderc.eu> |
|---|---|
| First post | 2019-02-21 09:10 +0100 |
| Last post | 2019-02-24 20:20 +0100 |
| Articles | 20 on this page of 72 — 25 participants |
Back to article view | Back to linux.debian.user
Why /usr/sbin is not in my root $PATH ? Pierre Couderc <pierre@couderc.eu> - 2019-02-21 09:10 +0100
Re: Why /usr/sbin is not in my root $PATH ? Reco <recoverym4n@enotuniq.net> - 2019-02-21 09:20 +0100
Re: Why /usr/sbin is not in my root $PATH ? Pierre Couderc <pierre@couderc.eu> - 2019-02-21 09:40 +0100
Re: Why /usr/sbin is not in my root $PATH ? Greg Wooledge <wooledg@eeg.ccf.org> - 2019-02-21 14:30 +0100
Re: Why /usr/sbin is not in my root $PATH ? Reco <recoverym4n@enotuniq.net> - 2019-02-21 14:40 +0100
Re: Why /usr/sbin is not in my root $PATH ? Reco <recoverym4n@enotuniq.net> - 2019-02-21 19:20 +0100
Re: Why /usr/sbin is not in my root $PATH ? ghe <ghe@slsware.net> - 2019-02-21 19:40 +0100
Re: Why /usr/sbin is not in my root $PATH ? Greg Wooledge <wooledg@eeg.ccf.org> - 2019-02-21 20:00 +0100
Re: Why /usr/sbin is not in my root $PATH ? ghe <ghe@slsware.net> - 2019-02-21 21:10 +0100
Re: Why /usr/sbin is not in my root $PATH ? Ric Moore <wayward4now@gmail.com> - 2019-02-21 21:40 +0100
Re: Why /usr/sbin is not in my root $PATH ? Brad Rogers <brad@fineby.me.uk> - 2019-02-21 14:40 +0100
Re: Why /usr/sbin is not in my root $PATH ? Greg Wooledge <wooledg@eeg.ccf.org> - 2019-02-21 14:40 +0100
Re: Why /usr/sbin is not in my root $PATH ? Brad Rogers <brad@fineby.me.uk> - 2019-02-21 14:50 +0100
Re: Why /usr/sbin is not in my root $PATH ? Greg Wooledge <wooledg@eeg.ccf.org> - 2019-02-21 17:30 +0100
Re: Why /usr/sbin is not in my root $PATH ? Reco <recoverym4n@enotuniq.net> - 2019-02-21 18:20 +0100
Re: Why /usr/sbin is not in my root $PATH ? Greg Wooledge <wooledg@eeg.ccf.org> - 2019-02-21 18:50 +0100
Re: Why /usr/sbin is not in my root $PATH ? Andrei POPESCU <andreimpopescu@gmail.com> - 2019-05-26 10:50 +0200
Re: Why /usr/sbin is not in my root $PATH ? ghe <ghe@slsware.net> - 2019-02-21 19:20 +0100
Re: Why /usr/sbin is not in my root $PATH ? Reco <recoverym4n@enotuniq.net> - 2019-02-21 19:30 +0100
Re: Why /usr/sbin is not in my root $PATH ? ghe <ghe@slsware.net> - 2019-05-26 15:50 +0200
Re: Why /usr/sbin is not in my root $PATH ? Andy Smith <andy@strugglers.net> - 2019-05-27 04:20 +0200
Re: Why /usr/sbin is not in my root $PATH ? Andrei POPESCU <andreimpopescu@gmail.com> - 2019-05-27 07:20 +0200
Re: Why /usr/sbin is not in my root $PATH ? Andy Smith <andy@strugglers.net> - 2019-05-27 07:30 +0200
Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?) Jason <electron@emypeople.net> - 2019-05-30 00:00 +0200
Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?) Andy Smith <andy@strugglers.net> - 2019-05-30 01:50 +0200
Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?) Cindy Sue Causey <butterflybytes@gmail.com> - 2019-05-30 03:50 +0200
Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?) Andy Smith <andy@strugglers.net> - 2019-05-30 04:50 +0200
Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?) Reco <recoverym4n@enotuniq.net> - 2019-05-30 08:10 +0200
Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?) Andy Smith <andy@strugglers.net> - 2019-05-30 23:30 +0200
Re: Ping as normal user Stefan Monnier <monnier@iro.umontreal.ca> - 2019-05-31 05:00 +0200
Re: Ping as normal user rhkramer@gmail.com - 2019-05-31 13:20 +0200
Re: Ping as normal user Pascal Hambourg <pascal@plouf.fr.eu.org> - 2019-05-31 13:30 +0200
Gmail problems (was Re: Ping as normal user) rhkramer@gmail.com - 2019-05-31 15:10 +0200
Re: Gmail problems (was Re: Ping as normal user) mick crane <mick.crane@gmail.com> - 2019-05-31 15:40 +0200
Re: Gmail problems (was Re: Ping as normal user) Brian <ad44@cityscape.co.uk> - 2019-05-31 21:50 +0200
Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?) Gene Heskett <gheskett@shentel.net> - 2019-05-30 05:30 +0200
Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?) Andrei POPESCU <andreimpopescu@gmail.com> - 2019-05-31 08:40 +0200
Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?) Pascal Hambourg <pascal@plouf.fr.eu.org> - 2019-05-31 11:50 +0200
Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?) Greg Wooledge <wooledg@eeg.ccf.org> - 2019-05-31 15:00 +0200
Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?) Andrei POPESCU <andreimpopescu@gmail.com> - 2019-06-01 07:50 +0200
Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?) Curt <curty@free.fr> - 2019-05-30 11:20 +0200
Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?) Greg Wooledge <wooledg@eeg.ccf.org> - 2019-05-30 14:40 +0200
Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?) Curt <curty@free.fr> - 2019-05-30 15:10 +0200
Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?) Greg Wooledge <wooledg@eeg.ccf.org> - 2019-05-30 15:20 +0200
Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?) Curt <curty@free.fr> - 2019-05-30 15:30 +0200
Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?) Greg Wooledge <wooledg@eeg.ccf.org> - 2019-05-30 16:30 +0200
Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?) Reco <recoverym4n@enotuniq.net> - 2019-05-30 16:40 +0200
Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?) Greg Wooledge <wooledg@eeg.ccf.org> - 2019-05-30 17:10 +0200
Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?) Reco <recoverym4n@enotuniq.net> - 2019-05-30 17:50 +0200
Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?) Andrei POPESCU <andreimpopescu@gmail.com> - 2019-05-31 09:00 +0200
Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?) "Thomas Schmitt" <scdbackup@gmx.net> - 2019-05-31 09:20 +0200
Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?) Reco <recoverym4n@enotuniq.net> - 2019-05-31 10:30 +0200
Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?) "Thomas Schmitt" <scdbackup@gmx.net> - 2019-05-31 12:20 +0200
Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?) Reco <recoverym4n@enotuniq.net> - 2019-05-31 13:10 +0200
Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?) "Thomas Schmitt" <scdbackup@gmx.net> - 2019-05-31 14:30 +0200
Re: Ping as normal user Sven Hartge <sven@svenhartge.de> - 2019-05-30 17:50 +0200
Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?) Reco <recoverym4n@enotuniq.net> - 2019-05-30 16:30 +0200
Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?) "Thomas Schmitt" <scdbackup@gmx.net> - 2019-05-30 17:10 +0200
Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?) Curt <curty@free.fr> - 2019-05-30 18:10 +0200
Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?) "Thomas Schmitt" <scdbackup@gmx.net> - 2019-05-30 18:40 +0200
Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?) Jason <electron@emypeople.net> - 2019-05-31 16:10 +0200
Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?) Andy Smith <andy@strugglers.net> - 2019-05-31 16:40 +0200
Re: Why /usr/sbin is not in my root $PATH ? Andrei POPESCU <andreimpopescu@gmail.com> - 2019-05-26 10:50 +0200
Re: Why /usr/sbin is not in my root $PATH ? Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups@NTLWorld.COM> - 2019-02-21 17:40 +0100
Re: Why /usr/sbin is not in my root $PATH ? Mart van de Wege <mvdwege@gmail.com> - 2019-02-23 15:50 +0100
Re: Why /usr/sbin is not in my root $PATH ? Tixy <tixy@yxit.co.uk> - 2019-02-23 17:40 +0100
Re: Why /usr/sbin is not in my root $PATH ? John Hasler <jhasler@newsguy.com> - 2019-02-23 18:30 +0100
Re: Why /usr/sbin is not in my root $PATH ? Mart van de Wege <mvdwege@gmail.com> - 2019-02-24 09:50 +0100
Re: Why /usr/sbin is not in my root $PATH ? Curt <curty@free.fr> - 2019-02-24 10:00 +0100
[OT] Re: Why /usr/sbin is not in my root $PATH ? David Wright <deblis@lionunicorn.co.uk> - 2019-02-24 16:40 +0100
Re: [OT] Re: Why /usr/sbin is not in my root $PATH ? Martin Smith <tech@smithproductions.co.uk> - 2019-02-24 19:10 +0100
Re: [OT] Re: Why /usr/sbin is not in my root $PATH ? David Wright <deblis@lionunicorn.co.uk> - 2019-02-24 20:20 +0100
Page 1 of 4 [1] 2 3 4 Next page →
| From | Pierre Couderc <pierre@couderc.eu> |
|---|---|
| Date | 2019-02-21 09:10 +0100 |
| Subject | Why /usr/sbin is not in my root $PATH ? |
| Message-ID | <xtRAB-3PJ-1@gated-at.bofh.it> |
Hi Why /usr/sbin is not in my root $PATH ? xxx@server:~$ su root Password: root@server:/home/nous# echo $PATH /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/snap/bin Why /usr/sbin is not in my root $PATH ? Is it a bug somewhere in debian ? Installing snap ? Or is my system corrupted ? Thanks for any explanation PC
[toc] | [next] | [standalone]
| From | Reco <recoverym4n@enotuniq.net> |
|---|---|
| Date | 2019-02-21 09:20 +0100 |
| Message-ID | <xtRKh-3SE-5@gated-at.bofh.it> |
| In reply to | #205561 |
Hi. On Thu, Feb 21, 2019 at 09:07:09AM +0100, Pierre Couderc wrote: > Hi > > Why /usr/sbin is not in my root $PATH ? > > > xxx@server:~$ su root Because you did exactly this. su(1) says: The optional argument - may be used to provide an environment similar to what the user would expect had the user logged in directly. Make a habit of using 'su -', as this behaviour is here to stay. > Is it a bug somewhere in debian ? Installing snap ? It's a change in Debian, see #833256. There are two su utilities, from 'shadow' and from 'util-linux'. Preserving user's environment unless '-' is specified is a feature of util-linux's su. Reco
[toc] | [prev] | [next] | [standalone]
| From | Pierre Couderc <pierre@couderc.eu> |
|---|---|
| Date | 2019-02-21 09:40 +0100 |
| Message-ID | <xtS3E-3Yz-9@gated-at.bofh.it> |
| In reply to | #205562 |
On 2/21/19 9:15 AM, Reco wrote: > Hi. > > On Thu, Feb 21, 2019 at 09:07:09AM +0100, Pierre Couderc wrote: >> Hi >> >> Why /usr/sbin is not in my root $PATH ? >> >> >> xxx@server:~$ su root > Because you did exactly this. su(1) says: > > The optional argument - may be used to provide an environment similar to > what the user would expect had the user logged in directly. > > Make a habit of using 'su -', as this behaviour is here to stay. > > >> Is it a bug somewhere in debian ? Installing snap ? > It's a change in Debian, see #833256. > There are two su utilities, from 'shadow' and from 'util-linux'. > Preserving user's environment unless '-' is specified is a feature of > util-linux's su. > > Reco > Thnk you very much. This is the answer I needed. Sorry for the noise ;)
[toc] | [prev] | [next] | [standalone]
| From | Greg Wooledge <wooledg@eeg.ccf.org> |
|---|---|
| Date | 2019-02-21 14:30 +0100 |
| Message-ID | <xtWAi-6FI-19@gated-at.bofh.it> |
| In reply to | #205563 |
On Thu, Feb 21, 2019 at 09:31:31AM +0100, Pierre Couderc wrote: > On 2/21/19 9:15 AM, Reco wrote: > > On Thu, Feb 21, 2019 at 09:07:09AM +0100, Pierre Couderc wrote: > > > Why /usr/sbin is not in my root $PATH ? Because you upgraded to buster (or unstable), and Debian in its infinite wisdom has changed the behavior of su between stretch and buster. > > Make a habit of using 'su -', as this behaviour is here to stay. Or use one of several other workarounds, for example putting /usr/sbin and /sbin into your regular user account's PATH. > > It's a change in Debian, see #833256. > > There are two su utilities, from 'shadow' and from 'util-linux'. > > Preserving user's environment unless '-' is specified is a feature of > > util-linux's su. > > > Thnk you very much. This is the answer I needed. Sorry for the noise ;) It's not noise. This is going to be the number one support issue for buster, I just know it. This question is going to come up repeatedly. The su change breaks *so* much. Red Hatters have apparently been living with this behavior for years, and they came up with the "su -" workaround. And hey, if that works for them, great. The problem with "su -" is that it strips out *all* of your environment, *and* it changes your working directory to /root. So, some things which work perfectly well in stretch (with "su") will no longer work in buster (with "su -"). Example 1: $ make $ su - # make install # fails because you're no longer in the build dir Example 2: $ export LANG=something LESS=-X ... $ su - # man something # your environment settings have been lost I haven't upgraded to buster yet, so I haven't had to make any changes to my own environment yet, but I suspect I'll be adding /usr/sbin and /sbin to my regular account's PATH. That will break the smallest amount of stuff for my usage patterns, as I will be able to continue using a normal "su" which will retain my environment and my working directory.
[toc] | [prev] | [next] | [standalone]
| From | Reco <recoverym4n@enotuniq.net> |
|---|---|
| Date | 2019-02-21 14:40 +0100 |
| Message-ID | <xtWJX-6J0-1@gated-at.bofh.it> |
| In reply to | #205576 |
Hi. On Thu, Feb 21, 2019 at 08:20:46AM -0500, Greg Wooledge wrote: > On Thu, Feb 21, 2019 at 09:31:31AM +0100, Pierre Couderc wrote: > > On 2/21/19 9:15 AM, Reco wrote: > > > On Thu, Feb 21, 2019 at 09:07:09AM +0100, Pierre Couderc wrote: > > > > Why /usr/sbin is not in my root $PATH ? > > Because you upgraded to buster (or unstable), and Debian in its infinite > wisdom has changed the behavior of su between stretch and buster. A small nit. They've changed the implementation of su. Behaviour change is a consequence. > > > Make a habit of using 'su -', as this behaviour is here to stay. > > Or use one of several other workarounds, for example putting /usr/sbin > and /sbin into your regular user account's PATH. That'll work too. Reco
[toc] | [prev] | [next] | [standalone]
| From | Reco <recoverym4n@enotuniq.net> |
|---|---|
| Date | 2019-02-21 19:20 +0100 |
| Message-ID | <xu16V-118-1@gated-at.bofh.it> |
| In reply to | #205577 |
Hi. On Thu, Feb 21, 2019 at 11:12:12AM -0700, ghe wrote: > Another Busterism, BTW: ping now requires root privileges. It does on > my > computer, anyway. Maybe I made a mistake when I installed -- somebody > sure did. Ping *always* required root, more precisely, CAP_NET_RAW. So they either made ping root-owned suid, or assigned CAP_NET_RAW capability to it (that's stretch btw): $ /sbin/getcap /bin/ping /bin/ping = cap_net_raw+ep So, run /var/lib/dpkg/info/iputils-ping.postinst (or whatever iputils alternative you have installed), and enjoy sanity restored. Reco
[toc] | [prev] | [next] | [standalone]
| From | ghe <ghe@slsware.net> |
|---|---|
| Date | 2019-02-21 19:40 +0100 |
| Message-ID | <xu1qh-170-7@gated-at.bofh.it> |
| In reply to | #205604 |
On 2/21/19 11:18 AM, Reco wrote: > Ping *always* required root, Maybe, but I didn't know that. I've been on Debian since the days of the major Toy Story characters, and I've always just typed 'ping' and it punged. But thanks, somebodyAtDebian, for correcting my decades old expectation. -- Glenn English
[toc] | [prev] | [next] | [standalone]
| From | Greg Wooledge <wooledg@eeg.ccf.org> |
|---|---|
| Date | 2019-02-21 20:00 +0100 |
| Message-ID | <xu1JD-1dl-5@gated-at.bofh.it> |
| In reply to | #205608 |
On Thu, Feb 21, 2019 at 11:36:44AM -0700, ghe wrote: > On 2/21/19 11:18 AM, Reco wrote: > > > Ping *always* required root, > > Maybe, but I didn't know that. I've been on Debian since the days of the > major Toy Story characters, and I've always just typed 'ping' and it punged. > > But thanks, somebodyAtDebian, for correcting my decades old expectation. You might be confused here. The ping program is intended to *work* for all users, but in order to work, it needs a special capability. Traditionally the ping program acquired this capability by being installed with the setuid bit. In more recent releases of Debian, /bin/ping is no longer setuid, and instead uses the Linux capabilities feature for its special power-up. <http://unixetc.co.uk/2016/05/30/linux-capabilities-and-ping/> is the first link I found which explains this. Seems like the right level of exposition for this thread. It's possible that somehow you removed your /bin/ping and restored it from a backup, but you didn't re-run the thing that gives it the special capabilities it needs. Or, who knows, maybe something else happened.
[toc] | [prev] | [next] | [standalone]
| From | ghe <ghe@slsware.net> |
|---|---|
| Date | 2019-02-21 21:10 +0100 |
| Message-ID | <xu2Po-28c-9@gated-at.bofh.it> |
| In reply to | #205610 |
On 2/21/19 11:50 AM, Greg Wooledge wrote: > It's possible that somehow you removed your /bin/ping and restored it from > a backup, but you didn't re-run the thing that gives it the special > capabilities it needs. Don't think so. Just a vanilla netinstall. Like always. I think. > Or, who knows, maybe something else happened. Something did :-) The shell, or something, talks about socket not being accessible. Certainly reasonable/believable. Thanks -- will fix... -- Glenn English
[toc] | [prev] | [next] | [standalone]
| From | Ric Moore <wayward4now@gmail.com> |
|---|---|
| Date | 2019-02-21 21:40 +0100 |
| Message-ID | <xu3iq-2h9-3@gated-at.bofh.it> |
| In reply to | #205608 |
On 2/21/19 1:36 PM, ghe wrote: > On 2/21/19 11:18 AM, Reco wrote: > >> Ping *always* required root, > > Maybe, but I didn't know that. I've been on Debian since the days of the > major Toy Story characters, and I've always just typed 'ping' and it punged. I just typed "ping redhat.com", as user, and it pinged. But I couldn't get it to "pung". :) Ric
[toc] | [prev] | [next] | [standalone]
| From | Brad Rogers <brad@fineby.me.uk> |
|---|---|
| Date | 2019-02-21 14:40 +0100 |
| Message-ID | <xtWJY-6J0-13@gated-at.bofh.it> |
| In reply to | #205576 |
[Multipart message — attachments visible in raw view] — view raw
On Thu, 21 Feb 2019 08:20:46 -0500
Greg Wooledge <wooledg@eeg.ccf.org> wrote:
Hello Greg,
>$ make
>$ su -
># make install # fails because you're no longer in the build dir
Just do;
$ make
$ sudo make install
Works fine.
--
Regards _
/ ) "The blindingly obvious is
/ _)rad never immediately apparent"
Life goes quick and it goes without warning
Bombsite Boy - The Adverts
[toc] | [prev] | [next] | [standalone]
| From | Greg Wooledge <wooledg@eeg.ccf.org> |
|---|---|
| Date | 2019-02-21 14:40 +0100 |
| Message-ID | <xtWJY-6J0-23@gated-at.bofh.it> |
| In reply to | #205578 |
On Thu, Feb 21, 2019 at 01:30:05PM +0000, Brad Rogers wrote: > On Thu, 21 Feb 2019 08:20:46 -0500 > Greg Wooledge <wooledg@eeg.ccf.org> wrote: > > Hello Greg, > > >$ make > >$ su - > ># make install # fails because you're no longer in the build dir > > Just do; > > $ make > $ sudo make install > > Works fine. Yes, that's another workaround: "just never use su at all, ever again". Please remember, though, that sudo is not installed by default in Debian. So, as with every other workaround that we're discussing, some action is required on the part of the user to implement the workaround. At some point I'm going to need to write a wiki page to explain the change, and list some known workarounds, so that users can pick which one they want to implement.
[toc] | [prev] | [next] | [standalone]
| From | Brad Rogers <brad@fineby.me.uk> |
|---|---|
| Date | 2019-02-21 14:50 +0100 |
| Message-ID | <xtWTD-6Mm-9@gated-at.bofh.it> |
| In reply to | #205580 |
[Multipart message — attachments visible in raw view] — view raw
On Thu, 21 Feb 2019 08:37:35 -0500
Greg Wooledge <wooledg@eeg.ccf.org> wrote:
Hello Greg,
>Yes, that's another workaround: "just never use su at all, ever again".
You're putting words in my mouth. I was dealing with one use case, not
saying "..never use..".
>Please remember, though, that sudo is not installed by default in
Good point, I'd forgotten that.
--
Regards _
/ ) "The blindingly obvious is
/ _)rad never immediately apparent"
Looking for something I can call my own
Chairman Of The Bored - Crass
[toc] | [prev] | [next] | [standalone]
| From | Greg Wooledge <wooledg@eeg.ccf.org> |
|---|---|
| Date | 2019-02-21 17:30 +0100 |
| Message-ID | <xtZou-8jd-7@gated-at.bofh.it> |
| In reply to | #205580 |
On Thu, Feb 21, 2019 at 04:14:53PM +0000, Jonathan de Boyne Pollard wrote: > You could point them to StackExchange in the meantime. (-: > > * https://unix.stackexchange.com/a/460769/5132 On that page: > Doing plain 'su' is a really bad idea for many reasons, Name one! Seriously, what kind of inane statement is that? > If you want to restore behaviour more similar to the previous one you can > add 'ALWAYS_SET_PATH yes' in /etc/login.defs. OK, I'll just go to Debian's online man pages and find the buster man page for su (or login.defs) to find out what that is... ... hey, where's the buster man pages? Oh, lovely. There aren't any. So I'd have to extract the man page out of a buster .deb by hand, or actually RUN buster, to find out how to document the changes in buster and how to work around them. *sigh* ... it's going to be one of *those* upgrades, isn't it.
[toc] | [prev] | [next] | [standalone]
| From | Reco <recoverym4n@enotuniq.net> |
|---|---|
| Date | 2019-02-21 18:20 +0100 |
| Message-ID | <xu0aS-nt-3@gated-at.bofh.it> |
| In reply to | #205594 |
On Thu, Feb 21, 2019 at 11:26:29AM -0500, Greg Wooledge wrote: > On Thu, Feb 21, 2019 at 04:14:53PM +0000, Jonathan de Boyne Pollard wrote: > > You could point them to StackExchange in the meantime. (-: > > > > * https://unix.stackexchange.com/a/460769/5132 > > On that page: > > Doing plain 'su' is a really bad idea for many reasons, > > Name one! Seriously, what kind of inane statement is that? I have five reasons for you. They are called AIX, HP-UX, Solaris, RHEL and busybox's su in no particular order. It's not the first time Debian project chose to do exactly the same others did for decades. > > If you want to restore behaviour more similar to the previous one you can > > add 'ALWAYS_SET_PATH yes' in /etc/login.defs. > > OK, I'll just go to Debian's online man pages and find the buster > man page for su (or login.defs) to find out what that is... > > ... hey, where's the buster man pages? Exactly there they belong. In .deb archives. Reco
[toc] | [prev] | [next] | [standalone]
| From | Greg Wooledge <wooledg@eeg.ccf.org> |
|---|---|
| Date | 2019-02-21 18:50 +0100 |
| Message-ID | <xu0DT-Bi-7@gated-at.bofh.it> |
| In reply to | #205600 |
Well, for those who are interested, I've added some information to <https://wiki.debian.org/NewInBuster>. I'm trusting that the ALWAYS_SET_PATH thing from that random web page was actually correct, because verification would take a lot of work. It's a wiki, so someone else can correct it if it's wrong. When I linked to EnvironmentVariables I also found a section at the end of *that* page which describes the current behavior of su, so I updated that page slightly as well. I can't even begin to guess how many places assume the current su behavior or how difficult it will be to find and change them all.
[toc] | [prev] | [next] | [standalone]
| From | Andrei POPESCU <andreimpopescu@gmail.com> |
|---|---|
| Date | 2019-05-26 10:50 +0200 |
| Message-ID | <y1X0R-66T-11@gated-at.bofh.it> |
| In reply to | #205603 |
[Multipart message — attachments visible in raw view] — view raw
On Jo, 21 feb 19, 12:42:47, Greg Wooledge wrote: > Well, for those who are interested, I've added some information to > <https://wiki.debian.org/NewInBuster>. I'm trusting that the > ALWAYS_SET_PATH thing from that random web page was actually correct, > because verification would take a lot of work. It's a wiki, so someone > else can correct it if it's wrong. > > When I linked to EnvironmentVariables I also found a section at the > end of *that* page which describes the current behavior of su, so I > updated that page slightly as well. > > I can't even begin to guess how many places assume the current su > behavior or how difficult it will be to find and change them all. You have studied this issue in great detail. Would you care to submit a bug against release-notes with proposed wording? Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser
[toc] | [prev] | [next] | [standalone]
| From | ghe <ghe@slsware.net> |
|---|---|
| Date | 2019-02-21 19:20 +0100 |
| Message-ID | <xu16V-118-5@gated-at.bofh.it> |
| In reply to | #205600 |
On 2/21/19 10:15 AM, Reco wrote: > It's not the first time Debian project chose to do exactly the same > others did for decades. Can you say Ptolemy? He (and his followers) did exactly the same he did for centuries. Another Busterism, BTW: ping now requires root privileges. It does on my computer, anyway. Maybe I made a mistake when I installed -- somebody sure did. The idea of putting sbin, etc. (and looking at who has execute) in my user path is becoming more and more attractive. Who needs Unix? OS360 and msdos and CP/M did the job for decades... -- Glenn English
[toc] | [prev] | [next] | [standalone]
| From | Reco <recoverym4n@enotuniq.net> |
|---|---|
| Date | 2019-02-21 19:30 +0100 |
| Message-ID | <xu1gC-147-13@gated-at.bofh.it> |
| In reply to | #205605 |
Hi. On Thu, Feb 21, 2019 at 11:12:12AM -0700, ghe wrote: > Another Busterism, BTW: ping now requires root privileges. It does on > my > computer, anyway. Maybe I made a mistake when I installed -- somebody > sure did. Ping *always* required root, more precisely, CAP_NET_RAW. So they either made ping root-owned suid, or assigned CAP_NET_RAW capability to it (that's stretch btw): $ /sbin/getcap /bin/ping /bin/ping = cap_net_raw+ep So, run "/var/lib/dpkg/info/iputils-ping.postinst configure" (or whatever iputils alternative you have installed), and enjoy sanity restored. PS I should watch who I'm replying to. Reco
[toc] | [prev] | [next] | [standalone]
| From | ghe <ghe@slsware.net> |
|---|---|
| Date | 2019-05-26 15:50 +0200 |
| Message-ID | <y21Hc-uV-5@gated-at.bofh.it> |
| In reply to | #205605 |
On 2/21/19 11:12 AM, ghe wrote: > Another Busterism, BTW: ping now requires root privileges. It does on my > computer, anyway. Maybe I made a mistake when I installed -- somebody > sure did. Fix: 'alias ping="sudo ping"' in .bashrc. I'm on Buster too :-) -- Glenn English
[toc] | [prev] | [next] | [standalone]
Page 1 of 4 [1] 2 3 4 Next page →
Back to top | Article view | linux.debian.user
csiph-web