On Mon, 29 Jun 2009, Andreas Unterkircher wrote:
> Package: base-files
> Version: 5lenny3
> Severity: normal
>
>
> I'm trying to track down a nasty problem which I encounter from
> to time on some of my Lenny machines. Sometimes, when I applied
> updates via apt or cron-apt, I noticed afterwards, that the
> permissions on /dev/null suddenly set to 644 instead of 666.
>
> So far I was now able to reproduce this behaviour when I invoke
> dpkg-reconfigure on the base-files package.
>
> u...@srv-mfm-vm01:~$ ls -l /dev/null
> crw-rw-rw- 1 root root 1, 3 2009-06-09 10:40 /dev/null
> u...@srv-mfm-vm01:~$ sudo dpkg-reconfigure base-files
> u...@srv-mfm-vm01:~$ ls -l /dev/null
> crw-r--r-- 1 root root 1, 3 2009-06-09 10:40 /dev/null
>
> So does this come from the base-files package itself?
Let's try to debug it even more: Does it also happen if you do this by
hand, as opposed to using dpkg-reconfigure?
/var/lib/dpkg/info/base-files.postinst configure 5lenny3
The postinst references /dev/null twice, at the very beginning, like this:
install_local_dir() {
if [ ! -d $1 ]; then
mkdir -p $1
fi
chown root:staff $1 2> /dev/null || true
chmod 2775 $1 2> /dev/null || true
}
Assuming that /dev/null exists and has the right permissions, I don't see
how those lines could be blamed for the bug you experience.
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
