all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Matthew Brooks <matthewfbrooks@mailbox.org>
To: Julien Lepiller <julien@lepiller.eu>
Cc: help-guix@gnu.org
Subject: Re: How to use "setuid-program"?
Date: Fri, 17 Sep 2021 11:28:36 -0500	[thread overview]
Message-ID: <20210917112742.3bc15e7f@mailbox.org> (raw)
In-Reply-To: <D327429F-3908-4949-8CD9-7B068DA8DFE7@lepiller.eu>

Thanks! I didn't realize there were two versions of the manual, and had been checking the stable one. The /devel one did have the new method, and it worked fine.

On Fri, 03 Sep 2021 16:16:27 -0400
Julien Lepiller <julien@lepiller.eu> wrote:

> Instead of the cold reply, here's an explanation. The /manual corresponds to the stable manual (1.3), and /manual/devel to the current manual.
> 
> You will find the links on the website if you hover the help menu.
> 
> You can also use "info guix" locally to get the mamual matching the current guix you have.
> 
> Le 3 septembre 2021 14:49:48 GMT-04:00, Tobias Geerinckx-Rice <me@tobias.gr> a écrit :
> >Hi Matthew,
> >
> >Matthew Brooks 写道:  
> >> The actual manual, however, still lists the old way as the way 
> >> to do it.  
> >
> >No: 
> ><https://guix.gnu.org/manual/devel/en/guix.html#Setuid-Programs>. 
> >Which one are you consulting?
> >
> >Kind regards,
> >
> >T G-R  



  reply	other threads:[~2021-09-17 16:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-03 18:24 How to use "setuid-program"? Matthew Brooks
2021-09-03 18:49 ` Tobias Geerinckx-Rice
2021-09-03 20:16   ` Julien Lepiller
2021-09-17 16:28     ` Matthew Brooks [this message]
2021-09-17 16:47       ` Tobias Geerinckx-Rice
2021-09-17 18:26         ` Pascal Lorenz
2021-09-19 11:37         ` Efraim Flashner
2021-09-19 15:45           ` Leo Famulari

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210917112742.3bc15e7f@mailbox.org \
    --to=matthewfbrooks@mailbox.org \
    --cc=help-guix@gnu.org \
    --cc=julien@lepiller.eu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.