<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.10.1">
</HEAD>
<BODY>
I'm using pbuilder in a slightly different way than most. I nfs boot my target boxes from the pbuilder tree. I have a little script that makes them bootable.<BR>
This works amazingly well, and is a very convenient development toolset. One problem I've noted however is that pbuilder sometimes refuses to unmount after a build if a target box is booted from the tree. It seems to get confused about the mount state of /proc.<BR>
<BR>
eg:<BR>
root@xxx:/# exit<BR>
exit<BR>
umount: /xxx/root/proc: device is busy<BR>
umount: /xxx/root/proc: device is busy<BR>
<BR>
Could not unmount proc, there might be some program<BR>
still using files in /proc (klogd?).<BR>
<BR>
avoid this message.<BR>
<BR>
I haven't dug into the code yet, I thought I'd throw this out there first.<BR>
What about using "umount -lf " to exit trees?<BR>
<BR>
Another nit I've seen is that on build failures, or if a someone hits a bunch of ctrl-C's in a row, it can leave the bind mounts in place. This causes "very bad things" if you decide to "sudo rm -rf" the tree with the bind mounts still attached.<BR>
Are there any trap handlers in pbuilder? If so, we should add some to catch the over-eager user pounding on ctrl-C to quit.<BR>
<BR>
-Bruce
</BODY>
</HTML>