Well... It must be something else. I was just guessing that you might be running out of space in /tmp since many utilities put tmp files there. Those utilities also (mostly) look at TMPDIR to see where to make tmp files. Sorry bout that.
You might try to look for big increases in space usage while it is running. find has the -xdev option to keep it from following mount points. du also has the -x option that does the same thing. Maybe doing a du before running dpkg-deb and then running du during the build and comparing the output??? jim ---------- From: David Z. Maze[SMTP:[EMAIL PROTECTED] Sent: Sunday, July 19, 1998 1:23 PM To: debian-user@lists.debian.org Cc: The recipient's address is unknown. Subject: Re: dpkg-deb --build and the / partition Lewis, James M <" <[EMAIL PROTECTED]>> writes: LJM> You probably ran out of space in /tmp. Try LJM> export TMPDIR=/var/tmp LJM> (or the equiv in your shell). Doesn't work; I still run out of space in /. LJM> If that doesn't work, you might try making /tmp a link to LJM> somewhere with more space. Is there a good way to do that without breaking things (i.e. the X server) that set up stuff in /tmp? More importantly, why does ls -al /tmp while dpkg-deb is running not show a growing file, if something is trying to put a big file there? -- _____________________________ / \ "Dad was reading a book called | David Maze | _Schroedinger's Kittens_. Asexual | [EMAIL PROTECTED] | reproduction? Only one cat is in the box." | http://donut.mit.edu/dmaze/ | -- Abra Mitchell \_____________________________/ -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
