From: gentoo@depardo.ch
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] sudo echo cannot write to /etc/ files ?
Date: Wed, 6 Jul 2005 16:20:47 +0200 [thread overview]
Message-ID: <200507061620.47943.gentoo@depardo.ch> (raw)
In-Reply-To: <42CBE237.7050508@planet.nl>
Le Mercredi, 6 Juillet 2005 15.52, Holly Bostick a ecrit :
> Hey, ho--
>
> Here's (one of) today's non-critical problems that's getting on my
> nerves, so hopefully somebody can help.
>
> I've finally got around to setting up sudo. It works fine, except for
> one thing.
>
> I don't just give myself blanket permissions to sudo to all commands; I
> made a Cmd_Alias group which includes a lot of utility apps. And, like
> many of you, I included emerge in this group.
>
> But a lot of the time, when I do an emerge -av, I find that there's a
> USE flag I want or don't want for the package, or I want an unstable
> version, or whatever, which means I have to echo to one of the files in
> /etc/portage.
>
> Echo is in the sudo-ed group, and echo isn't the problem-- the problem
> is that permission is refused to write to the file itself (which is an
> error *from* echo, so it would seem that echo itself is OK as far as
> sudo goes). Which means that I have to su anyway, to echo to the file,
> which really isn't the point of the exercise.
>
> As I see it, this error can mean only one of two things:
>
> sudo does not give me a login shell (so my UID is 'really' still my UID
> and not root's, and I don't have permission to write to the file); or
>
> there is another, "invisible" cli utility responsible for actually
> writing to the file, which is not sudo-ed.
>
> Or could it be something else?
>
> In any case, does anybody know how I could fix this? It's really
> screwing up my useability, which was just starting to shape up nicely :-) .
>
> Thanks,
> Holly
I think the problem come from the fact that echo is sudo-ed but the shell
redirection isn't.
Compare this:
su -c "echo foo > /etc/portage/whatever"
and
su -c "echo foo" > /etc/portage/whatever
The first one will succeed, but not the second.
To solve your problem, I would just do:
chgrp -R portage /etc/portage
chmod -R g+w /etc/portage
--
mat
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-07-06 14:30 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 [this message]
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
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=200507061620.47943.gentoo@depardo.ch \
--to=gentoo@depardo.ch \
--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