I just did a fresh install of Mandrake 10.0 on my laptop (AMD XP 1400+). I have two mount points:

/dev/hda3 --> /
/dev/hda7 --> /home

It originally came with /tmp in / , which has attributes drwxrwxrwt.
Now, for some reason, I really want to move /tmp to /home/tmp (i.e. move /tmp to the second partition, but as a part of the second filesystem). So I made tmp subdir in the /home, and it already has attributes drwxrwxrwt before this relocation.

So here's my config in fstab:

Do you know what happens? Every now and then, the /tmp permission was reset to drwxr-xr-x !! Then many programs would scream because they can't write to /tmp. Is this automatic of Mandrake (which, as I could tell, contains quite a bit of magic here and there), or what? Is it because this kind of trick is not allowed? (I.e. am I not supposed to remount /home/tmp as /tmp)? Should I just make a softlink from /tmp to /home/tmp?

NOTES:
* Linux Kernel: 2.6.3-7mdk.

If you check the logs, there might be something in there about it changing the permissions on "world-writable" files. Depending on the security level you chose, there are a variety of daily checks that occur (looking for world-readable/-writeable files, SUID programs, changes to the RPM database, etc...). Personally, I would just use a symbolic link.

--mascdman

Yup. I think that's because of `msec' (Mandrake security) feature. Sometimes it's nice to have this, but often it's a nuisance too, to have my settings overriden "magically" by its actions.

There was no information about the attribute change in the log file (syslog, dmesg, /var/log/security etc..). The action was logged in /var/log/messages.

To turn off this "feature", I had to go to Mandrake Control Center, choose "Security", "Permissions", then set up a custom rule in which /home/tmp's permission is explicitly set to 1777. Anyway, just a bit annoying feature of the otherwise-useful msec. :-)