Package: apt
Version: 0.6.43.3
If /var/cache/apt/archives is a mounted ramfs filesystem, apt-get fails
because it thinks there is no disk space.
df on a ramfs filesystem reports 0 blocks, 0 used, 0 free. This freaks
apt-get out, because it doesn't think there is enough disk space. This
isn't the case, though. A ramfs will grow when you put data in it.
apt-get could check that /var/cache/apt/archives isn't mounted as a
filesystem that gives misleading reports such as ramfs, which is a blatant
hack.
Perhaps this is really a problem with ramfs reporting bogus information. It
seems that it would be reasonable to determine how much ram is available for
a ramfs every time you make the system call.
I am using a fresh install of Debian unstable with the 2.6.16-1-486 kernel.
This problem most likely spans far back with apt-get and/or ramfs.
I will report this as a kernel bug, too(kernel.org, not Debian).
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
