© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
OK, I found it.
During debootstrap run, a process "udevd --daemon" is started. It persists when debootstrap gets to the end. If you kill it, the process reading from debootstrap's stdout is able to terminate.
My guess is that stdout is being passed to that daemon, and it's holding it open.
No idea of the fix though. Why is udevd being started in the first place? If it's being started as a daemon, why is it not closing its stdout? And if there is a reason for running it, shouldn't it be stopped before debootstrap finishes?