From: Daniel Robbins <drobbins@gentoo.org>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] rc5 - /tmp has no sticky bit
Date: Fri Jul 6 22:15:03 2001 [thread overview]
Message-ID: <20010706221412.A11694@cvs.gentoo.org> (raw)
In-Reply-To: <20010706215655.C10437@cvs.gentoo.org>; from drobbins@gentoo.org on Fri, Jul 06, 2001 at 09:56:55PM -0600
On Fri, Jul 06, 2001 at 09:56:55PM -0600, Daniel Robbins wrote:
> On Fri, Jul 06, 2001 at 09:45:45PM +0000, Collins Richey wrote:
>
> > 2) old habits die hard - you forgot to set the sticky bit for /tmp, but chmod
> > 1777 /tmp did the trick.
>
> We have had the sticky bit set on /tmp (in the baselayout ebuild) for a very
> long time. If your /tmp directory was created by the baselayout ebuild, then
> your sticky bit should have been set too. Could you please try to track down
> the cause of this problem, as it isn't a simple case of us forgetting to set
> the sticky bit.
OK; I think I've figured out the cause of the problem. What happens is that Portage
will create the /tmp/portage directory if it doesn't exist, and uses 0755 perms for
both. Since you built your system from scratch, Portage created /tmp/portage before
baselayout could be built and merged, and thus the 1777 perms were not applied. The
fix is for me to specifically check if ${ROOT}/tmp exists, and if not, create it with
the sticky bit explicitly set.
Thanks for the info you provided, as it helped me to track down the problem. Now to
fix this in Portage...
--
Daniel Robbins <drobbins@gentoo.org>
President/CEO http://www.gentoo.org
Gentoo Technologies, Inc.
next prev parent reply other threads:[~2001-07-07 4:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-06 21:37 [gentoo-dev] rc5 - /tmp has no sticky bit Collins Richey
2001-07-06 21:57 ` Daniel Robbins
2001-07-06 22:15 ` Daniel Robbins [this message]
2001-07-07 6:37 ` Collins Richey
2001-07-07 6:33 ` Collins Richey
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=20010706221412.A11694@cvs.gentoo.org \
--to=drobbins@gentoo.org \
--cc=gentoo-dev@cvs.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