From: Richard Fish <bigfish@asmallpond.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] sudo echo cannot write to /etc/ files ?
Date: Thu, 07 Jul 2005 07:31:29 +0200 [thread overview]
Message-ID: <42CCBE31.9060304@asmallpond.org> (raw)
In-Reply-To: <42CCA4BE.5000904@volumehost.com>
Boyd Stephen Smith Jr. wrote:
>
> You want:
> sudo "echo 'media-video/xine-ui ~x86' >> /etc/portage/package.keywords"
>
No, I'm sorry, this is completely false.
Running
sudo "echo 'media-video/xine-ui ~x86' >> /etc/portage/package.keywords"
causes sudo to search the PATH for a *single* executable file named
"sudo echo 'media-video/xine-ui ~x86' >>
/etc/portage/package.keywords". It will find no such file, and report
"command not found".
Besides, the echo command doesn't support the *shell* redirection
operators. It is the *shell* that interprets those. Echo just prints
every argument it receives to stdout, so even if you managed to pass
">>" to echo in it's argv, it would just print those characters to its
stdout.
> This cause the command
> echo 'media-video/xine-ui ~x86' >> /etc/portage/package.keywords
> to be passed to the sudo shell which causes the bash built-in:
sudo has no builtin bash or bash-like shell.
-Richard
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-07-07 5:35 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-06 13:52 [gentoo-user] sudo echo cannot write to /etc/ files ? Holly Bostick
2005-07-06 14:02 ` A. Khattri
2005-07-06 14:25 ` Holly Bostick
2005-07-06 14:20 ` David Morgan
2005-07-06 14:20 ` gentoo
2005-07-06 15:21 ` Holly Bostick
2005-07-06 15:29 ` Christoph Gysin
2005-07-06 15:39 ` gentoo
2005-07-07 3:42 ` Boyd Stephen Smith Jr.
2005-07-07 5:31 ` Richard Fish [this message]
2005-07-06 14:22 ` Edward Catmur
2005-07-06 14:54 ` Holly Bostick
2005-07-06 15:12 ` David Morgan
2005-07-06 15:26 ` Neil Bothwick
2005-07-06 15:28 ` Christoph Gysin
2005-07-06 16:07 ` Holly Bostick
2005-07-06 16:47 ` Christoph Gysin
2005-07-06 18:22 ` Richard Fish
2005-07-06 18:36 ` Holly Bostick
2005-07-06 19:12 ` Richard Fish
2005-07-06 19:42 ` Holly Bostick
2005-07-06 20:28 ` John J. Foster
2005-07-06 20:52 ` Manuel McLure
2005-07-06 19:13 ` Christoph Gysin
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=42CCBE31.9060304@asmallpond.org \
--to=bigfish@asmallpond.org \
--cc=gentoo-user@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox