On Fri, Jan 1, 2021 at 7:55 PM Sedat Dilek <sedat.dilek@xxxxxxxxx> wrote: > > On Fri, Jan 1, 2021 at 5:14 PM Pavel Machek <pavel@xxxxxx> wrote: > > > > Hi! > > > > > > > > > $ dpkg -L kmod | grep bin | grep depmod > > > > > /sbin/depmod > > > > > > > > > > $ which depmod > > > > > [ empty ] > > > > > > > > > > $ echo $PATH > > > > > /opt/proxychains-ng/bin:/home/dileks/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games > > > > > > Ok, I think this is a broken setup that has a separate /sbin but does > > > not have it in the PATH. > > > > That's how it is supposed to work, AFAICT. It is so on Debian here, > > for example. > > > > /sbin is for management commands, why would I have it in PATH when > > running as normal user? > > > > I am here on Debian/testing AMD64 and waiting for feedback [2]. > > For now I have applied the diff from [1]. > > - Sedat - > > [1] https://marc.info/?l=linux-kbuild&m=160919738006768&w=2 > [2] https://marc.info/?l=linux-kernel&m=160919729606750&w=2 Fixed upstream, see "depmod: handle the case of /sbin/depmod without /sbin in PATH". - Sedat - [1] https://git.kernel.org/linus/cedd1862be7e666be87ec824dabc6a2b05618f36
