Re: Bookworm: missing sbin in root path?

On Sat, Jul 01, 2023 at 10:07:59PM -0400, Carl Fink wrote: > > On 7/1/23 21:38, Greg Wooledge wrote: > > On Sat, Jul 01, 2023 at 08:58:44PM -0400, Carl Fink wrote: > > > When I type "/usr/sbin/adduser", that works, but shouldn't root default to > > > h

Re: Bookworm: missing sbin in root path?

Yes, I did use su. I had no idea that would cause a problem. Thanks for the pointer. I created /etc/default/su, which should resolve this.  -Carl Fink On 7/1/23 21:38, Greg Wooledge wrote: On Sat, Jul 01, 2023 at 08:58:44PM -0400, Carl Fink wrote: When I type "/usr/sbin/adduser",

Re: Bookworm: missing sbin in root path?

On Sat, Jul 01, 2023 at 08:58:44PM -0400, Carl Fink wrote: > When I type "/usr/sbin/adduser", that works, but shouldn't root default to > having sbin in its path? You probably used su. <https://wiki.debian.org/NewInBuster#Changes> describes the change and the known fixes.

Bookworm: missing sbin in root path?

so not present by default?) and discovered that although the package installed /usr/sbin/adduser, somehow root doesn't have /user/sbin in its PATH. When I type "/usr/sbin/adduser", that works, but shouldn't root default to having sbin in its path? -Carl Fink

Re: /sbin vs /bin

to...@tuxteam.de wrote: > On Sat, Jul 30, 2022 at 02:07:58PM -0400, Greg Wooledge wrote: > > On Sat, Jul 30, 2022 at 02:02:21PM -0400, Timothy M Butterworth wrote: > > > Logging in as root has become taboo. Sudo is the prefered mechanism for > > > running administrator functions. I have root set t

Re: /sbin vs /bin

On Sat 30 Jul 2022 at 20:21:00 (+0200), to...@tuxteam.de wrote: > On Sat, Jul 30, 2022 at 02:07:58PM -0400, Greg Wooledge wrote: > > On Sat, Jul 30, 2022 at 02:02:21PM -0400, Timothy M Butterworth wrote: > > > Logging in as root has become taboo. Sudo is the prefered mechanism for > > > running adm

Re: /sbin vs /bin

On Sat, Jul 30, 2022 at 02:07:58PM -0400, Greg Wooledge wrote: > On Sat, Jul 30, 2022 at 02:02:21PM -0400, Timothy M Butterworth wrote: > > Logging in as root has become taboo. Sudo is the prefered mechanism for > > running administrator functions. I have root set to nologin with a null > > passwor

Re: /sbin vs /bin

On Sat, Jul 30, 2022 at 02:02:21PM -0400, Timothy M Butterworth wrote: > Logging in as root has become taboo. Sudo is the prefered mechanism for > running administrator functions. I have root set to nologin with a null > password to force sudo usage. This makes entering single-user mode ("rescue m

Re: /sbin vs /bin

On Fri, Jul 29, 2022 at 7:08 AM Greg Wooledge wrote: > On Thu, Jul 28, 2022 at 11:39:01PM -0500, Igor Korot wrote: > > Open the Terminal > > Become root by running su > > Try to run ldconfig -> "Command not found" > > Try to run /sbin/ldconfig -> execu

Re: /sbin vs /bin

On Thu, Jul 28, 2022 at 11:39:01PM -0500, Igor Korot wrote: > Open the Terminal > Become root by running su > Try to run ldconfig -> "Command not found" > Try to run /sbin/ldconfig -> execution successful https://wiki.debian.org/NewInBuster#Changes Changes

Re: /sbin vs /bin

g/cgi-bin/search_contents.pl?word=ldconfig&searchmode=searchfiles&case=insensitive&version=stable&arch=i386, > > > > > > ld config is located inside /sbin and it is installed through the > > > libc-bin. > > > > > > Trying to run ldconfig g

Re: /sbin vs /bin

dconfig&searchmode=searchfiles&case=insensitive&version=stable&arch=i386, > > > > > > ld config is located inside /sbin and it is installed through the > > > libc-bin. > > > > > > Trying to run ldconfig gives "No such file or direct

Re: /sbin vs /bin

n=stable&arch=i386, > > > > ld config is located inside /sbin and it is installed through the libc-bin. > > > > Trying to run ldconfig gives "No such file or directory" > > Running "apt install libc-bin" says "Its installed and already a late

Re: /sbin vs /bin

p;arch=i386, > > > > ld config is located inside /sbin and it is installed through the libc-bin. > > > > Trying to run ldconfig gives "No such file or directory" > > Running "apt install libc-bin" says "Its installed and already a latest >

Re: /sbin vs /bin

On Thu 28 Jul 2022 at 22:37:39 (-0500), Igor Korot wrote: > According to > https://packages.debian.org/cgi-bin/search_contents.pl?word=ldconfig&searchmode=searchfiles&case=insensitive&version=stable&arch=i386, > > ld config is located inside /sbin and it is in

/sbin vs /bin

Hi, ALL, According to https://packages.debian.org/cgi-bin/search_contents.pl?word=ldconfig&searchmode=searchfiles&case=insensitive&version=stable&arch=i386, ld config is located inside /sbin and it is installed through the libc-bin. Trying to run ldconfig gives "No s

Re: What is z3fold and do I need it? (error: /usr/sbin/mkinitramfs: 12: /etc/initramfs-tools/conf.d/local.conf: z3fold: not found)

z3fold a choice for zsap compressor module, normally if your seeing a problem you need to add z3fold to initramfs modules file and rebuild. see https://baronhk.wordpress.com/2021/10/03/setting-up-zswap-in-debian-11-gnu-linux/

Re: What is z3fold and do I need it? (error: /usr/sbin/mkinitramfs: 12: /etc/initramfs-tools/conf.d/local.conf: z3fold: not found)

On Fri, 04 Mar 2022, Ottavio Caruso wrote: > ~$ sudo find /lib/modules/ -iname "*z3fold*" > /lib/modules/4.19.0-17-amd64/kernel/mm/z3fold.ko > /lib/modules/4.19.0-14-amd64/kernel/mm/z3fold.ko > /lib/modules/4.19.0-8-amd64/kernel/mm/z3fold.ko > > > Then why doesn't it load up? update-initramfs -u

Re: What is z3fold and do I need it? (error: /usr/sbin/mkinitramfs: 12: /etc/initramfs-tools/conf.d/local.conf: z3fold: not found)

Hi, On Thu, 3 Mar 2022 07:25:01 -0500 Greg Wooledge wrote: (...) > > /usr/sbin/mkinitramfs: 12: /etc/initramfs-tools/conf.d/local.conf: > > z3fold: not found > > Well, as your file says, this is supposed to be a kernel module. On my > system, I have this: > > unic

Re: What is z3fold and do I need it? (error: /usr/sbin/mkinitramfs: 12: /etc/initramfs-tools/conf.d/local.conf: z3fold: not found)

ude in your initramfs. > # They will be loaded at boot time in the order below. > # > # Syntax: module_name [args ...] > # > # You must run update-initramfs(8) to effect this change. > # > # Examples: > # > # raid1 > # sd_mod > z3fold > lz4 > > Then: > > #

Re: /usr/sbin/reboot: disabled in systemd-nspawn container SOLVED

On Sb, 04 sep 21, 17:35:49, sp...@caiway.net wrote: > SOLVED > > /usr/share/open-infrastructure/container/shutdown.txt > is from package progress-linux-container: > > Progress Linux is a Debian derivative distribution focused on system > integration. > > This package is a metapackage to be insta

Re: /usr/sbin/reboot: disabled in systemd-nspawn container

Greg Wooledge [2021-09-04 11:35:25] wrote: > On Sat, Sep 04, 2021 at 04:49:24PM +0200, sp...@caiway.net wrote: >> # file /sbin/reboot >> /sbin/reboot: POSIX shell script, ASCII text executable > > That's not normal for a bullseye system using systemd for init. Indeed. &

Re: /usr/sbin/reboot: disabled in systemd-nspawn container

4:49:24PM +0200, sp...@caiway.net wrote: > >> >> # file /sbin/reboot > > Based on what I read of the thread, that package is > progress-linux-container. > > $ apt-cache policy progress-linux-container > progress-linux-container: > Installed: (none) > Can

Re: /usr/sbin/reboot: disabled in systemd-nspawn container

On 2021-09-04 at 13:20, Greg Wooledge wrote: > On Sat, Sep 04, 2021 at 12:54:35PM -0400, Stefan Monnier wrote: > >> Greg Wooledge [2021-09-04 11:35:25] wrote: >> > On Sat, Sep 04, 2021 at 04:49:24PM +0200, sp...@caiway.net wrote: >> >> # file /sbin/reboot >&

Re: /usr/sbin/reboot: disabled in systemd-nspawn container

On Sat, Sep 04, 2021 at 12:54:35PM -0400, Stefan Monnier wrote: > Greg Wooledge [2021-09-04 11:35:25] wrote: > > On Sat, Sep 04, 2021 at 04:49:24PM +0200, sp...@caiway.net wrote: > >> # file /sbin/reboot > >> /sbin/reboot: POSIX shell script, ASCII text executable >

Re: /usr/sbin/reboot: disabled in systemd-nspawn container SOLVED

SOLVED /usr/share/open-infrastructure/container/shutdown.txt is from package progress-linux-container: Progress Linux is a Debian derivative distribution focused on system integration. This package is a metapackage to be installed in a container (systemd-nspawn). # apt remove progress-linux-con

Re: /usr/sbin/reboot: disabled in systemd-nspawn container

my up-to-date > > > bullseye system: > > > > > > # reboot > > > /usr/sbin/reboot: disabled in systemd-nspawn container > > > > Unless I'm mistaken, these messages are not generated by systemd. > > In fact, there's nothing that resemb

Re: /usr/sbin/reboot: disabled in systemd-nspawn container

my up-to-date > > > bullseye system: > > > > > > # reboot > > > /usr/sbin/reboot: disabled in systemd-nspawn container > > > > Unless I'm mistaken, these messages are not generated by systemd. > > In fact, there's nothing that resemb

Re: /usr/sbin/reboot: disabled in systemd-nspawn container

On Sat, 4 Sep 2021 16:42:45 +0300 Reco wrote: > Hi. > /bin/systemd reboot > > And, what about these: > > ls -al /sbin/reboot > file /sbin/reboot > > Reco > the commands poweroff and reboot are textfiles. I have no idea # mcedit /sbin/reboot: #!/b

Re: /usr/sbin/reboot: disabled in systemd-nspawn container

On Sat, 4 Sep 2021 16:42:45 +0300 Reco wrote: > Hi. > > On Sat, Sep 04, 2021 at 02:40:13PM +0200, sp...@caiway.net wrote: > > Suddenly I can no longer reboot or poweroff my up-to-date > > bullseye system: > > > > # reboot > > /usr/sbin/reboo

Re: /usr/sbin/reboot: disabled in systemd-nspawn container

Hi. On Sat, Sep 04, 2021 at 02:40:13PM +0200, sp...@caiway.net wrote: > Suddenly I can no longer reboot or poweroff my up-to-date > bullseye system: > > # reboot > /usr/sbin/reboot: disabled in systemd-nspawn container Unless I'm mistaken, these messages are not gene

/usr/sbin/reboot: disabled in systemd-nspawn container

Hi, Suddenly I can no longer reboot or poweroff my up-to-date bullseye system: # reboot /usr/sbin/reboot: disabled in systemd-nspawn container Linux container share the kernel of the host system they are running on, there is no need to reboot just the container. However, please contact your

Re: Sid: /sbin/ifenslave missing??

Sven Hartge wrote: > Temporary solution: downgrade to 2.9 again, hold the package and monitor > the bug report I linked. Sorry, the correct bug is https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959236 Unfortunately it has only "normal" severity, "grave" would be better here, since it not onl

Re: Sid: /sbin/ifenslave missing??

Grzesiek Sójka wrote: > On 5/17/20 12:34 PM, Sven Hartge wrote: >> Mind doing a "ifup -v bond0" to really see what is called how and where >> it fails in what way? > after "ifup -v bond0" I get a larg number of following messages > (probably 1000?): > + [ -n ] > + return 0 > + setup_master >

Re: Sid: /sbin/ifenslave missing??

On 5/17/20 12:34 PM, Sven Hartge wrote: Mind doing a "ifup -v bond0" to really see what is called how and where it fails in what way? after "ifup -v bond0" I get a larg number of following messages (probably 1000?): + [ -n ] + return 0 + setup_master + add_master + [ -f /sys/class/net/bond0

Re: Sid: /sbin/ifenslave missing??

Grzesiek Sójka wrote: > On 5/17/20 12:13 PM, Sven Hartge wrote: >> How does your /etc/network/interfaces look like? Usally all the work is >> done via if-pre-up.d and if-up.d scripts provided by the ifenslave >> package. > # cat /etc/network/interfaces > source-directory /etc/network/interfaces.

Re: Sid: /sbin/ifenslave missing??

On 5/17/20 12:13 PM, Sven Hartge wrote: How does your /etc/network/interfaces look like? Usally all the work is done via if-pre-up.d and if-up.d scripts provided by the ifenslave package. # cat /etc/network/interfaces source-directory /etc/network/interfaces.d auto bond0 iface bond0 inet stati

Re: Sid: /sbin/ifenslave missing??

On 2020-05-17 11:27 +0200, Grzesiek Sójka wrote: > After upgrading ifenslave from 2.9 to 2.10 i found that there if no > /sbin/ifenslave binary. To restore network connectivity I had to > manually downgrade to 2.9. Is it on purpose? If so, then how to > properly configure link agg

Re: Sid: /sbin/ifenslave missing??

Grzesiek Sójka wrote: > After upgrading ifenslave from 2.9 to 2.10 i found that there if no > /sbin/ifenslave binary. To restore network connectivity I had to > manually downgrade to 2.9. Is it on purpose? If so, then how to > properly configure link aggregation? It seems y

Sid: /sbin/ifenslave missing??

Hi there, After upgrading ifenslave from 2.9 to 2.10 i found that there if no /sbin/ifenslave binary. To restore network connectivity I had to manually downgrade to 2.9. Is it on purpose? If so, then how to properly configure link aggregation? Thank for any help in advance Greg

Re: Re: Issue with OpenVPN inside a LXC container: Failed at step NAMESPACE spawning /usr/sbin/openvpn: Permission denied

Thanks a ton! I'm running this container on my private network behind a NAT, so I'm not too worried about disabling apparmor. I ended up just giving as loose of a configuration I could and it did the trick. lxc.apparmor.profile = unconfined lxc.apparmor.allow_nesting = 1 lxc.apparmor.allow_in

Re: Issue with OpenVPN inside a LXC container: Failed at step NAMESPACE spawning /usr/sbin/openvpn: Permission denied

Hi. On Tue, Jul 16, 2019 at 10:57:06PM -0400, Simon Bernier St-Pierre wrote: > I have a LXC container which is connected to a remote VPN using > OpenVPN. After upgrading to buster, the VPN does not start anymore. > I'm using Debian buster on my host OS These are relevant to the problem.

Issue with OpenVPN inside a LXC container: Failed at step NAMESPACE spawning /usr/sbin/openvpn: Permission denied

0:32:30 dl systemd[70]: openvpn-client@pia.service: Failed to set up mount namespacing: Permission denied Jul 16 20:32:30 dl systemd[70]: openvpn-client@pia.service: Failed at step NAMESPACE spawning /usr/sbin/openvpn: Permission denied Jul 16 20:32:30 dl systemd[1]: openvpn-client@pia.service: Ma

Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?)

On Vi, 31 mai 19, 08:51:20, Greg Wooledge wrote: > On Fri, May 31, 2019 at 11:47:26AM +0200, Pascal Hambourg wrote: > > > https://wiki.debian.org/MergedUsr > > > > The wiki says this page does not exist yet. > > It's actually . Right, thanks (again) Greg for co

Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?)

Hello, On Fri, May 31, 2019 at 08:48:36AM -0500, Jason wrote: > On Wed, May 29, 2019 at 11:46:50PM +, Andy Smith wrote: > > How did you install this system? […] > > One other person in this thread said they used (a script which > > ultimately uses) debootstrap. > > This system was installed

Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?)

On Wed, May 29, 2019 at 11:46:50PM +, Andy Smith wrote: > Hi Jason, > > On Wed, May 29, 2019 at 04:18:51PM -0500, Jason wrote: > > On Mon, May 27, 2019 at 08:12:32AM +0300, Andrei POPESCU wrote: > > > While I didn't mention it in this thread, ping had indeed somehow lost > > > its capabilitie

Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?)

On Fri, May 31, 2019 at 11:47:26AM +0200, Pascal Hambourg wrote: > > https://wiki.debian.org/MergedUsr > > The wiki says this page does not exist yet. It's actually .

Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?)

Hi, i wrote: > > Currently the Default User depends on assumptions about local package > > management which are not obviously related to security. > > That's a future pitfall which just needs its unintentional cover removed. Reco wrote: > The way I see it, the "problematic" package got that Impor

Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?)

On Fri, May 31, 2019 at 12:09:19PM +0200, Thomas Schmitt wrote: > > Not every filesystem supported by Debian > > implements extended attributes needed for capabilities. > > Off the top of my head it's NFS and JFFS2. > > It is about the filesystem which holds the /bin directory. I would deem it > e

Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?)

Hi, i wrote: > > "d/control: Drop Priority of libcap2" > > https://salsa.debian.org/debian/libcap2/commit/5386335db24bfff5cc85bda69dbcda6ab2d7d20d Reco wrote: > Ah, that's what is was. That change made into the stable, I've just checked. Not according to the package tracker: oldstable has 1:2.2

Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?)

alls. It won't be necessary if you switch to merged /usr. AFAIK, the /usr merge does not merge sbin and bin together. https://wiki.debian.org/MergedUsr The wiki says this page does not exist yet.

Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?)

Hi. On Fri, May 31, 2019 at 09:08:55AM +0200, Thomas Schmitt wrote: > Andrei POPESCU wrote: > > The other way would be if the archive priority was changed between > > different installs. > > This has happened in april 2016 (maybe related to bug 780721 ?) > > "d/control: Increase Priori

Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?)

Hi, Andrei POPESCU wrote: > The other way would be if the archive priority was changed between > different installs. This has happened in april 2016 (maybe related to bug 780721 ?) "d/control: Increase Priority of libcap2{,-bin} to important" https://salsa.debian.org/debian/libcap2/commit/a

Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?)

On Jo, 30 mai 19, 18:43:05, Reco wrote: > Hi. > > On Thu, May 30, 2019 at 11:08:22AM -0400, Greg Wooledge wrote: > > I asked on IRC, and got this answer: > > > > The archive (Packages) and individual .debs can disagree on Priority. It's > > mostly a field that has no meaning these days.

Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?)

On Mi, 29 mai 19, 23:29:21, Gene Heskett wrote: > > the default $PATH the installer sets up for $users, apparently does not > include any of the sbin's, only /usr/bin and /bin. I've been fixing that > for several generations of debian installs. Probably shouldn't as there > may be some good re

Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?)

Hello, On Thu, May 30, 2019 at 09:08:38AM +0300, Reco wrote: > Easy. You run debootstrap, set some --include options (which pull > libcap2-bin by dependency), and then you tar the whole resulting > filesystem. > tar never understood file capabilities, so they are lost in the process. Sure, tar is

Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?)

Hi, i pointed to: > > https://www.debian.org/doc/debian-policy/upgrading-checklist.html#version-4- 0-1 > > [...] Packages may now depend on packages with a lower priority. [...] Curt wrote: > So it seems the reason invoked above is no longer valid due to a change in > policy. It can be legally c

Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?)

On 2019-05-30, Thomas Schmitt wrote: > > So the explanation in > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780721#10 > > iputils-ping, as priority "important", cannot declare a dependency on > libcap2-bin, which is priority "optional". > > is wrong and in direct contradiction to The Po

Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?)

Hi. On Thu, May 30, 2019 at 11:08:22AM -0400, Greg Wooledge wrote: > I asked on IRC, and got this answer: > > The archive (Packages) and individual .debs can disagree on Priority. It's > mostly a field that has no meaning these days. > > I'm not 100% sure how to interpret that. Are

Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?)

Hi, Curt wrote: > >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780721 > >> (libcap2-bin is recommended but is not a dependancy of iputils-ping, > >> because "iputils-ping, as priority 'important', cannot declare a > >> dependency on libcap2-bin, which is priority 'optional'"). > Why is my

Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?)

I asked on IRC, and got this answer: The archive (Packages) and individual .debs can disagree on Priority. It's mostly a field that has no meaning these days. I'm not 100% sure how to interpret that. Are different mirrors giving out different Packages files with different Priority settings?

Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?)

Hi. On Thu, May 30, 2019 at 10:26:29AM -0400, Greg Wooledge wrote: > On Thu, May 30, 2019 at 05:19:49PM +0300, Reco wrote: > > "dpkg -s" gets package state from /var/lib/dpkg/status. > > "apt-cache" also uses /var/lib/apt/lists/*. > > > > Basically your result tells that libcap2-bin is "o

Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?)

On Thu, May 30, 2019 at 05:19:49PM +0300, Reco wrote: > "dpkg -s" gets package state from /var/lib/dpkg/status. > "apt-cache" also uses /var/lib/apt/lists/*. > > Basically your result tells that libcap2-bin is "optional" from the > repository POV, but your local package database thinks it's "impor

Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?)

Hi. On Thu, May 30, 2019 at 09:10:55AM -0400, Greg Wooledge wrote: > On Thu, May 30, 2019 at 01:00:19PM -, Curt wrote: > > On 2019-05-30, Greg Wooledge wrote: > > > But libcap2-bin is priority important in both stretch and buster. > > > > Why is my Stretch apt-cache command telling m

Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?)

On 2019-05-30, Greg Wooledge wrote: > On Thu, May 30, 2019 at 01:00:19PM -, Curt wrote: >> On 2019-05-30, Greg Wooledge wrote: >> > But libcap2-bin is priority important in both stretch and buster. >> >> Why is my Stretch apt-cache command telling me it's priority optional? >> Or am I once a

Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?)

On Thu, May 30, 2019 at 01:00:19PM -, Curt wrote: > On 2019-05-30, Greg Wooledge wrote: > > But libcap2-bin is priority important in both stretch and buster. > > Why is my Stretch apt-cache command telling me it's priority optional? > Or am I once again missing some essential thing? Uh... a

Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?)

On 2019-05-30, Greg Wooledge wrote: > On Thu, May 30, 2019 at 09:11:44AM -, Curt wrote: >> There is a bug related to this imbroglio: >> >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780721 >> (libcap2-bin is recommended but is not a dependancy of iputils-ping, >> because "iputils-ping,

Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?)

On Thu, May 30, 2019 at 09:11:44AM -, Curt wrote: > There is a bug related to this imbroglio: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780721 > (libcap2-bin is recommended but is not a dependancy of iputils-ping, > because "iputils-ping, as priority 'important', cannot declare a >

Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?)

On 2019-05-29, Andy Smith wrote: > > How did you install this system? Because /bin/ping is supposed to > come with file capabilities such that the user can allow it to do > what it needs to do (this is part of what 'dpkg-reconfigure > iputils-ping' restores). So it would be interesting to know how

Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?)

Hi. On Thu, May 30, 2019 at 02:44:58AM +, Andy Smith wrote: > So my question is, are installs done by debootstrap somehow losing > the file capabilities? I ask because in this thread, one of the > other people reporting a /bin/ping without the correct capabilities > did their install t

Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?)

On Wednesday 29 May 2019 07:46:50 pm Andy Smith wrote: > Hi Jason, > > On Wed, May 29, 2019 at 04:18:51PM -0500, Jason wrote: > > On Mon, May 27, 2019 at 08:12:32AM +0300, Andrei POPESCU wrote: > > > While I didn't mention it in this thread, ping had indeed somehow > > > lost its capabilities on m

Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?)

Hi Cindy, On Wed, May 29, 2019 at 09:48:44PM -0400, Cindy Sue Causey wrote: > So, yeah, at least for Debootstrap. "iputils-ping" is in there at the > absolute very first start where the Developers have picked the very > first packages that get the party started before the User then picks > everyth

Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?)

On 5/29/19, Andy Smith wrote: > Hi Jason, > > On Wed, May 29, 2019 at 04:18:51PM -0500, Jason wrote: >> On Mon, May 27, 2019 at 08:12:32AM +0300, Andrei POPESCU wrote: >> > While I didn't mention it in this thread, ping had indeed somehow lost >> > its capabilities on my system. 'dpkg-reconfigure

Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?)

Hi Jason, On Wed, May 29, 2019 at 04:18:51PM -0500, Jason wrote: > On Mon, May 27, 2019 at 08:12:32AM +0300, Andrei POPESCU wrote: > > While I didn't mention it in this thread, ping had indeed somehow lost > > its capabilities on my system. 'dpkg-reconfigure iputils-ping' fixed it. > > That work

Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?)

On Mon, May 27, 2019 at 08:12:32AM +0300, Andrei POPESCU wrote: > > While I didn't mention it in this thread, ping had indeed somehow lost > its capabilities on my system. 'dpkg-reconfigure iputils-ping' fixed it. That worked for me (I'm not the OP) with Stretch on an ARM board. Before running

Re: Why /usr/sbin is not in my root $PATH ?

Hello, On Mon, May 27, 2019 at 08:12:32AM +0300, Andrei POPESCU wrote: > On Lu, 27 mai 19, 02:15:49, Andy Smith wrote: > > > > Glenn, and Andrei, do you do anything out of the ordinary to > > install? > > https://salsa.debian.org/amp-guest/pine64/blob/master/pine64_buildimage Seems it does a d

Re: Why /usr/sbin is not in my root $PATH ?

On Lu, 27 mai 19, 02:15:49, Andy Smith wrote: > > Glenn, and Andrei, do you do anything out of the ordinary to > install? https://salsa.debian.org/amp-guest/pine64/blob/master/pine64_buildimage > Myself I have seen this happen when untarring the operating system > as by default tar does not sto

Re: Why /usr/sbin is not in my root $PATH ?

Hello, On Sun, May 26, 2019 at 07:41:41AM -0600, ghe wrote: > 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"' i

Re: Why /usr/sbin is not in my root $PATH ?

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

Re: Why /usr/sbin is not in my root $PATH ?

On Jo, 21 feb 19, 12:42:47, Greg Wooledge wrote: > Well, for those who are interested, I've added some information to > . I'm trusting that the > ALWAYS_SET_PATH thing from that random web page was actually correct, > because verification would take a lot of wo

Re: Why /usr/sbin is not in my root $PATH ?

On Jo, 21 feb 19, 11:26:29, Greg Wooledge wrote: > On Thu, Feb 21, 2019 at 04:14:53PM +, 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 b

Re: [OT] Re: Why /usr/sbin is not in my root $PATH ?

On Sun 24 Feb 2019 at 17:28:18 (+), Martin Smith wrote: > On 24/02/2019 15:39, David Wright wrote: > > On Sun 24 Feb 2019 at 08:57:37 (-), Curt wrote: > > > On 2019-02-24, Mart van de Wege wrote: > > > > Really, not using a clean, known environment as root is plain good > > > > practice, a

Re: [OT] Re: Why /usr/sbin is not in my root $PATH ?

On 24/02/2019 15:39, David Wright wrote: On Sun 24 Feb 2019 at 08:57:37 (-), Curt wrote: On 2019-02-24, Mart van de Wege wrote: Really, not using a clean, known environment as root is plain good practice, and has been for years, if not actually decades. Have you expressed the opposite of

[OT] Re: Why /usr/sbin is not in my root $PATH ?

On Sun 24 Feb 2019 at 08:57:37 (-), Curt wrote: > On 2019-02-24, Mart van de Wege wrote: > > > > Really, not using a clean, known environment as root is plain good > > practice, and has been for years, if not actually decades. > > Have you expressed the opposite of your intention here? Often

Re: Why /usr/sbin is not in my root $PATH ?

On 2019-02-24, Mart van de Wege wrote: > > Really, not using a clean, known environment as root is plain good > practice, and has been for years, if not actually decades. Have you expressed the opposite of your intention here? A clean, known environment sounds like something in one of those Morm

Re: Why /usr/sbin is not in my root $PATH ?

John Hasler writes: >> But it's not Joe Random User, it's Joe Sysadmin > > Worse. Who is most likely to have put weird stuff in his environment? And it's not as if sysadmins never log in as other users. Oh no. Really, not using a clean, known environment as root is plain good practice, and has

Re: Why /usr/sbin is not in my root $PATH ?

> But it's not Joe Random User, it's Joe Sysadmin Worse. Who is most likely to have put weird stuff in his environment? -- John Hasler jhas...@newsguy.com Elmwood, WI USA

Re: Why /usr/sbin is not in my root $PATH ?

On Sat, 2019-02-23 at 15:27 +0100, Mart van de Wege wrote: > Greg Wooledge writes: > > > > > The problem with "su -" is that it strips out *all* of your > > environment, > > That's a feature, not a bug. You *don't* want to import Joe Random > User's environment into root's. But it's not Joe Ra

Re: Why /usr/sbin is not in my root $PATH ?

Greg Wooledge writes: > > The problem with "su -" is that it strips out *all* of your environment, That's a feature, not a bug. You *don't* want to import Joe Random User's environment into root's. Mart -- "We will need a longer wall when the revolution comes." --- AJS, quoting an uncertain s

Re: Why /usr/sbin is not in my root $PATH ?

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

Re: Why /usr/sbin is not in my root $PATH ?

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

Re: Why /usr/sbin is not in my root $PATH ?

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,

Re: Why /usr/sbin is not in my root $PATH ?

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. -- Gle

Re: Why /usr/sbin is not in my root $PATH ?

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 san

Re: Why /usr/sbin is not in my root $PATH ?

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

Re: Why /usr/sbin is not in my root $PATH ?

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

Re: Why /usr/sbin is not in my root $PATH ?

Well, for those who are interested, I've added some information to . 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

Re: Why /usr/sbin is not in my root $PATH ?

On Thu, Feb 21, 2019 at 11:26:29AM -0500, Greg Wooledge wrote: > On Thu, Feb 21, 2019 at 04:14:53PM +, 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'

Re: Why /usr/sbin is not in my root $PATH ?

Greg Wooledge: 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. You could point them to StackExchange in the meantime. (-: * https://unix.stackexchange.com/a/460769/5132

Re: Why /usr/sbin is not in my root $PATH ?

On Thu, Feb 21, 2019 at 04:14:53PM +, 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 i

  1   2   3   4   >