[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: mount.davfs: program is not setuid root

From: Leo Famulari
Subject: Re: mount.davfs: program is not setuid root
Date: Mon, 19 Apr 2021 20:47:08 -0400

On Mon, Apr 19, 2021 at 10:30:13PM +0200, Simon Streit wrote:
> I just tried again, and called mount as:
> --8<---------------cut here---------------start------------->8---
> /run/setuid-programs/mount -t <URL> ~/test/
> --8<---------------cut here---------------end--------------->8---
> where URL is my remote URL share trying to mount it to local test dir,
> where it fails with:
> --8<---------------cut here---------------start------------->8---
> /run/current-system/profile/sbin/mount.davfs: program is not setuid root
> --8<---------------cut here---------------end--------------->8---

So, '/run/setuid-programs/mount' is somehow resolving to

The executables in /run/setuid-programs are not supposed to be links.

They are created while "activating" Guix System by copying the programs
listed in the (setuid-programs) field of config.scm into
/run/setuid-programs and making these copies setuid.

Documentation on that:

And the code:

Can you do `ls -la /run/setuid-programs`, and share the entire output of
that command?

By the way, regarding the default order of $PATH, here is my path from a
VM image created with the "bare bones" template [0] from the Guix source

$ `guix system vm gnu/system/examples/bare-bones.tmpl`
[ ... QEMU launches the VM and I log in ...]
$ echo $PATH

So, you could consider that the default order on Guix System. Annotated:

1) programs specified setuid by the system administrator
2) your user's `guix pull` profile
3) your user's profile of installed packages
4) programs provided via the (packages) field of config.scm (and maybe
from system services?)
5) same as 4, but programs contained in an 'sbin/' directory


reply via email to

[Prev in Thread] Current Thread [Next in Thread]