You are not logged in.
Not sure if anyone else is seeing this because this may have been part of something I did a way back. I'm getting:
( 35/400) upgrading filesystem [######################] 100%
warning: directory permissions differ on tmp/
filesystem: 777 package: 1777
I know a bit about the filesystem package. If I remember correctly it contains files that are Arch specific like the boot scripts... Now if I'm reading this correctly the 777 permissions of "filesystem" is original directory and "package" is the package's permissions for the tmp directory. Here's my /tmp directory permissions after the update:
drwxrwxrwt 11 root root 4.0K Sep 13 11:41 tmp
Can anyone help me clarify this? Is the problem now fixed, or is there something I need to do?
Last edited by Gen2ly (2010-09-13 19:49:14)
Setting Up a Scripting Environment | Proud donor to wikipedia - link
Offline
I haven't seen pacman changing permission on directories yet, but according to the message, your /tmp didn't have the sticky bit set before the upgrade. Though things will work fine with just 777, not having the sticky bit on /tmp will mean that someone could delete and replace files owned by someone else, which is a security risk.
Offline
Thanks JGC. Setting the sticky bit did the trick.
chmod 1777 /tmp
Appreciate the help.
Setting Up a Scripting Environment | Proud donor to wikipedia - link
Offline