Package: udev
Version: 0.056-3
Followup-For: Bug #395889
> I guess you already know it, but I think it should be in the bug log:
> http://marc.theaimsgroup.com/?l=linux-kernel&m=116066318011633&w=2
> contains another way to detect a chroot.
Actually I find that way a little cumbersome. Plus, it will emit an error
message for kernels < 2.6.18. Here is a more straightforward test:
--- /var/lib/dpkg/info/udev.postinst 2005-05-29 19:36:20.000000000 +0200
+++ udev.postinst 2006-11-09 19:25:28.118104583 +0100
@@ -68,7 +68,7 @@
return 0
fi
- if [ ! -r /proc/1/root ]; then
+ if ! [ -r /proc/1/root -a /proc/1/root/ -ef /proc/self/root/ ]; then
echo "A chroot environment has been detected, udev not started."
return 0
fi
(-ef compares inode and device identifiers.)
Regards,
Christoph
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
