From: Roel Janssen <roel@gnu.org>
To: 29337@debbugs.gnu.org
Subject: bug#29337: Bash reads system-wide bashrc unconditionally.
Date: Fri, 17 Nov 2017 13:16:13 +0100 [thread overview]
Message-ID: <878tf5ksmq.fsf@gnu.org> (raw)
Dear Guix,
This is more of an issue for GuixSD.
Our 'bash' package seems to behave differently from other distributions
(like CentOS 7), and it behaves differently from the way described in its
manual page.
I added the following line to /etc/bashrc:
echo "Hello, world"
Here's the command to reproduce the problem:
$ env - bash --init-file <(echo "echo \"Goodbye, world\"") -i
Hello, world
Goodbye, world
From the manpage:
...
-i If the -i option is present, the shell is interactive.
...
--init-file file
--rcfile file
Execute commands from file instead of the standard personal initialization file ~/.bashrc if the shell is interactive (see INVOCATION below).
...
So, what should happen, is that it ignores the system-wide initialization
file (and the user's initialization file).
On CentOS 7, the following happens (yes, I added the echo-statement to
/etc/bashrc on CentOS as well):
$ env - bash --init-file <(echo "echo \"Goodbye, world\"") -i
Goodbye, world
On GuixSD:
$ env - bash --init-file <(echo "echo \"Goodbye, world\"") -i
Hello, world
Goodbye, world
Where does this difference come from? And could we make its behavior
similar to CentOS 7, and more importantly, to the description in the
manpage?
Kind regards,
Roel Janssen
next reply other threads:[~2017-11-17 12:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-17 12:16 Roel Janssen [this message]
2017-11-17 21:04 ` bug#29337: Bash reads system-wide bashrc unconditionally Ludovic Courtès
2017-11-20 21:48 ` Roel Janssen
2017-11-21 8:50 ` Ludovic Courtès
2017-11-24 15:46 ` Roel Janssen
2017-11-24 20:51 ` Ludovic Courtès
2017-12-11 11:35 ` Roel Janssen
2017-12-11 13:19 ` Ludovic Courtès
2017-12-11 15:31 ` Roel Janssen
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=878tf5ksmq.fsf@gnu.org \
--to=roel@gnu.org \
--cc=29337@debbugs.gnu.org \
/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.