[gobolinux-devel] Bug in ChrootCompile

[Jonas Karlsson]

Having a go on the WindowMaker recipe I've had some failures and now I  
wanted to clean up all the directories that were left behind. What I got  
was what's below:

]rm -rf Area-WindowMaker-0.92.0*
rm: cannot remove directory  
`Area-WindowMaker-0.92.0-old-20060906-0006/System/Kernel/Devices/shm':  
Device or resource busy
rm: cannot remove directory  
`Area-WindowMaker-0.92.0-old-20060906-0006/System/Kernel/Devices/pts':  
Device or resource busy
rm: cannot remove directory  
`Area-WindowMaker-0.92.0-old-20060906-0006/Programs/Bash/3.1': Device or  
resource busy
rm: cannot remove directory  
`Area-WindowMaker-0.92.0-old-20060906-0006/Programs/Glibc/2.4': Device or  
resource busy
rm: cannot remove directory  
`Area-WindowMaker-0.92.0-old-20060906-0006/Programs/Python/2.4.3': Device  
or resource busy
rm: cannot remove directory  
`Area-WindowMaker-0.92.0-old-20060906-0006/Programs/Compile/20060905':  
Device or resource busy
rm: cannot remove directory  
`Area-WindowMaker-0.92.0-old-20060906-0006/Programs/Scripts/20060905':  
Device or resource busy
rm: cannot remove directory  
`Area-WindowMaker-0.92.0-old-20060906-0006/Programs/Ncurses/5.5': Device  
or resource busy

imagine the chill that went down my spine, when I thought that there were  
things on my system that were deleted. Why? Well because my /dev was  
whiped clean except for 'shm' and 'pts', which were stated busy above. So  
I wondered what else were mounted into chroot environment and was  
forgotten. I haven't found anything yet, but I'm preparing for the worst.  
Anything I should worry about?
Anyhow, I don't know exactly what caused this, but I think I might have  
pressed ^c with a bad timing. Maybe the script should catch such keys and  
clean up the enironment before quiting?

-- 
/Jonas

PS. 'udevstart' got me my /dev back.

Using Opera's revolutionary e-mail client: http://www.opera.com/mail/