On Sat, Jan 07, 2006 at 08:42:55PM -0500, Bryan Donlan wrote: > chroot was created using cdebootstrap directly to sid. After a bit of
Okay, I did the same now. > investigation, this seems to be reproducable by emptying or deleting > /etc/fstab, purging quota, and reinstalling. I'm not sure how to That's strange. If /etc/fstab does not exist I get: ... Setting up quota (3.13-4) ... awk: cannot open /etc/fstab (No such file or directory) dpkg: error processing quota (--configure): subprocess post-installation script returned error exit status 2 Errors were encountered while processing: quota If I just touch /etc/fstab to create an empty file I get: ... Unpacking quota (from .../archives/quota_3.13-4_i386.deb) ... Setting up quota (3.13-4) ... Or in other words, everything is fine. > The chroot's root filesystem is xfs, on a LVM volume, and the kernel > is linux-image-2.6.12-1-k7 2.6.12-10, if that matters. Maybe. To be honest it looks like there is something else going on, not just a bug in quota. Is there a way you could tar together your chroot and put it on a server I I could download it to see if it works here? Michael -- Michael Meskes Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED] Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
