Hi, assume we build chrooted, then the 'real' chroot (the one which ends up in the live system) is already copied to chroot/chroot. the 'unreal' chroot (the one which contains the build-tools such as squashfs-tools) needs network access to install the build-tools.
that means, that the 'taining' of chroot/etc/resolv.conf is legimit and will not end up in the live system. assume we build non-chrooted, then the chroot is not touched at all, and the live-system is build with the host tools. that means, that the chroot/etc/resolv.conf is not touched because it is not needed to be touched, and this is what ends up in the live system. Assumed that people always build 'in order' (by calling lh_bootstrap, lh_chroot and lh_binary; and not individual helpers directly), then, there is as far as I can see still no possibility that resolv.conf is tainted in any way. Do you see any? Regards, Daniel -- Address: Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist Email: [EMAIL PROTECTED] Internet: http://people.panthera-systems.net/~daniel-baumann/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
