forcemerge 390756 389821 thanks > mdadm is know to be broken when installing in a chroot without having > /proc mounted, maintainer should check for /proc in the maintainer > scripts (and don't do anything if /proc isn't there, hence reassigning > to mdadm).
maintainer does check for /proc and fails gracefully in its absence.
echo -n 'Generating mdadm.conf... ' >&2
if /usr/share/mdadm/mkconf generate $CONFIG 2>/dev/null; then
echo done. >&2
else
echo "failed (/proc probably not mounted)." >&2
rm -f $CONFIG
fi
and in mkconf:
if [ ! -d /proc/$$ ]; then
echo E: /proc not available. Exiting... >&2
exit 2
fi
Anyway, I am moderately certain that the bug is the same as #390756
and has thus been fixed in -7.
> * there are cases where it is not possible to unmount a mounted /proc
> in a chroot if certain (unkillable) processes access it. since only
> rebooting the whole system helps, we do not mount /proc in the
> chroot.
Wouldn't a lazy umount help?
--
.''`. martin f. krafft <[EMAIL PROTECTED]>
: :' : proud Debian developer, author, administrator, and user
`. `'` http://people.debian.org/~madduck - http://debiansystem.info
`- Debian - when you have better things to do than fixing systems
signature.asc
Description: Digital signature (GPG/PGP)
