public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: isar-users@googlegroups.com
Cc: Francesco <fdprnd@dave.eu>, Henning Schild <henning.schild@siemens.com>
Subject: [PATCH] doc: Update sudo configuration in the manual.
Date: Fri,  4 May 2018 10:46:19 +0200	[thread overview]
Message-ID: <20180504084619.13253-1-henning.schild@siemens.com> (raw)

Francesco reported build problems with the suggested sudo configuration.
The issue might be that somewhere along the way a user or group other
than root is used, or that there are problems with (NO)SETENV.

Update the manual to include an entry that should prevent such problems,
also add a line to deal with proxies.

Reported-by: Francesco <fdprnd@dave.eu>
Signed-off-by: Henning Schild <henning.schild@siemens.com>
---
 doc/user_manual.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/doc/user_manual.md b/doc/user_manual.md
index 7bdfc1c..70c382e 100644
--- a/doc/user_manual.md
+++ b/doc/user_manual.md
@@ -79,9 +79,11 @@ Isar requires `sudo` rights without password to work with `chroot` and `debootst
 ```
 In the editor, allow the current user to run sudo without a password, e.g.:
 ```
- <user>  ALL=NOPASSWD: ALL
+ <user>  ALL=(ALL:ALL) NOPASSWD:ALL
+ Defaults env_keep += "ftp_proxy http_proxy https_proxy no_proxy"
 ```
 Replace `<user>` with your user name. Use the tab character between the user name and parameters.
+The second line will make sure your proxy settings will not get lost when using `sudo`. Include it if you are in the unfortunate possition to having to deal with that.
 
 ### Check out Isar
 
-- 
2.16.1


             reply	other threads:[~2018-05-04  8:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-04  8:46 Henning Schild [this message]
2018-05-11 15:34 ` Alexander Smirnov

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=20180504084619.13253-1-henning.schild@siemens.com \
    --to=henning.schild@siemens.com \
    --cc=fdprnd@dave.eu \
    --cc=isar-users@googlegroups.com \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox