From: "Michael Kintzios" <michaelkintzios@lycos.co.uk>
To: <gentoo-user@lists.gentoo.org>
Subject: RE: [gentoo-user] I (user) can write to / ... but why?
Date: Tue, 16 Aug 2005 11:21:02 +0100 [thread overview]
Message-ID: <F49BE7328A1DA246AFC5C2CDDB86D9170D47C4@BCV0X134EXC0005> (raw)
In-Reply-To: <200508160917.40396.ext-dirk.heinrichs@nokia.com>
> -----Original Message-----
> From: Dirk Heinrichs [mailto:ext-dirk.heinrichs@nokia.com]
> Sent: 16 August 2005 08:18
> To: gentoo-user@lists.gentoo.org
> Subject: Re: [gentoo-user] I (user) can write to / ... but why?
>
>
> Am Dienstag, 16. August 2005 09:00 schrieb ext Ralph Slooten:
>
> > Yeah, there are other files scattered throughout the
> filesystem owned by
> > me. Some are due to being compiled as me, and installed as root
>
> If they were installed as root, they would be owned by root.
> The reason must
> be another. But since / is owned by you, it would have been
> possible to
> also "make install" as that user.
Could it have something to do with axllent being in the portage group
and the latter being left with its default access rights? (running as
root)
--
Regards,
Mick
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-08-16 10:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-15 18:27 [gentoo-user] I (user) can write to / ... but why? Ralph Slooten
2005-08-15 19:12 ` Daniel da Veiga
2005-08-15 20:21 ` Christoph Gysin
2005-08-15 20:45 ` Neil Bothwick
2005-08-16 1:07 ` Nick Rout
2005-08-16 5:21 ` Ralph Slooten
2005-08-16 5:17 ` Ralph Slooten
2005-08-16 5:41 ` Dirk Heinrichs
2005-08-16 7:00 ` Ralph Slooten
2005-08-16 7:17 ` Dirk Heinrichs
2005-08-16 10:21 ` Michael Kintzios [this message]
2005-08-16 9:26 ` Nick Rout
2005-08-16 9:47 ` Frank Schafer
2005-08-16 13:33 ` Ralph Slooten
2005-08-16 7:14 ` Christoph Gysin
2005-08-16 7:42 ` Neil Bothwick
2005-08-16 16:09 ` [gentoo-user] I (user) can write to / ... but why? (solved) Ralph Slooten
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=F49BE7328A1DA246AFC5C2CDDB86D9170D47C4@BCV0X134EXC0005 \
--to=michaelkintzios@lycos.co.uk \
--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