[gentoo-dev] rc5 - /tmp has no sticky bit

[gentoo-dev] rc5 - /tmp has no sticky bit

[Collins Richey]

I just finished bringing up rc5 from the 586 iso image and installing Netscape sylpheed and XFCE.  The only errors in the entire process were

1) the already reported broken pipe message
2) old habits die hard - you forgot to set the sticky bit for /tmp, but chmod 1777 /tmp did the trick.

When I first tried sylpheed under normal user, I got /bash ...  bind:  permission error.  In case anyone else has the problem, the answer is above.

-- 
Collins Richey
Denver Area
Gentoo_rc5 XFCE

Re: [gentoo-dev] rc5 - /tmp has no sticky bit

[Daniel Robbins]

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.

Best Regards,

-- 
Daniel Robbins					<drobbins@gentoo.org>
President/CEO					http://www.gentoo.org 
Gentoo Technologies, Inc.			

Re: [gentoo-dev] rc5 - /tmp has no sticky bit

[Daniel Robbins]

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.			

Re: [gentoo-dev] rc5 - /tmp has no sticky bit

[Collins Richey]

On Fri, 6 Jul 2001 22:14:12 -0600 Daniel Robbins <drobbins@gentoo.org> wrote:

> 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...
> 

Sorry, I had already replied with my install procedure.  Glad you found the problem, since it will bite others, too.

-- 
Collins Richey
Denver Area
Gentoo_rc5 XFCE

Re: [gentoo-dev] rc5 - /tmp has no sticky bit

[Collins Richey]

On Fri, 6 Jul 2001 21:56:55 -0600 Daniel Robbins <drobbins@gentoo.org> 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.
> 

I did the following things.  Unfortunately I didn't check the permissions after each; only when Sylpheed failed to run as normal user:

1) Standard install from ISO except grub.  I use Lilo for everything.
2) emerged XFree
3) compiled my own kernel from a saved .config
4) Booted my reference Gentoo partition(R4), mounted necessary partitions (including R5), updated lilo.conf, and issued lilo.  Slso copied over my XF86Config-4 file. Unmounted all partitions except R4.
5) booted from R5 (lilo menu)
6) passwd to set root passwd
7) created /home/collins and adduser collins (group wheel)
8) Added collins to the wheel list in /etc/group and passwd collins to set the new password.
9) emerged sylpheed (losts of gnome stuff got brought in)
10) emerged XFCE
11) login as collins; then startxfce
12) sylpheed failed to start from run
13) issued sylpheed & from term; then I noticed the "bind: permission denied" message.
14) emerged netscape (su mode from term)
15) tried netscape, and it worked.
16) began researching bad permissions I encountered on R4; discoverd the problem with /tmp
17) chmod 1777 /tmp, and sylpheed worked.

-- 
Collins Richey
Denver Area
Gentoo_rc5 XFCE