On 11/19/2010 10:20 AM, Samuel Thibault wrote:
What can I say that I have not already said? I started by the netboot iso for amd64 from last sunday 14/11 image. I chose the default graphical installer. The target disk was already formatted but using a 32 bit install and with a too small /usr and 32 bits binaries. I thus started the partitioning by deleting first one by one the existing partitions using only the partman interface and then recreated them one by one using partman with different size, adding the LABEL and changing the /tmp fs type from ext3 to ext2VALETTE Eric RD-MAPS-REN, le Fri 19 Nov 2010 09:20:59 +0100, a écrit :If you don't want to fix it, I do not care.We DO want to fix it. But we can't fix something that we don't understand. When we try to reproduce this bug we just get proper permissions. So there must be something that we are doing differently. It could even be a completely unrelated detail like language, chosen debian mirror, etc. That's why we need precise details to be able to reproduce the issue, and thus fix it. I cannot insure the /tmp settings were wrong from beginning immediately after the first reboot as I did not install anything beyond the strictly basic installer packages and did not have any graphical packages at that time and may have missed it. I also logged only as root and thus may have missed the tmp permission problem. Then I did after that 1) restore my apt source list 2) a dpkg --set-selection from a the previously saved 32 bit instal get-selection and an apt dselect-upgrade 3) rebooted and verified that KDM was started but did not log in as it was past midnight Again I cannot assure that /tmp setting were wrong at that time. What I'm sure of: 1) at the end /tmp setting were wrong 2) I never executed a *self cooked script* changing tmp settings I you looked at the path for tmp permission setting and the path looks correct this is enough for me. BTW I have a question: do you set the 1777 on the root of the real tmp FS and also on the "umounted" /tmp directory? because tmp mounting first failed with my own generated kernel because I forgot to enable ext2 (only ext3 was enabled), I had to recompile it before being able to actually mount /tmp as an ext2 FS and I do not remember with which kernel I did see the wrong permissions (aka with /tmp mounted as an ext2 fs or the one available via the / filsesystem if the mount is not yet performed or fails). I would not have opened the bug given all i did in addition to the other install if I did not remember have already seen the same bug on another totally different install (with a different installer version). -- eric |