Daniel Baumann <[EMAIL PROTECTED]> writes:
> Hi,
>
> before the rootfs image is created, resolv.conf gets truncated (on
> behalf of lh_chroot_resolv remove). This happens independently of
> whetever the chroot is restored from cache or not. Could you provide
> more information in which case you actually end up with a non-truncated
> resolv.conf?
>
>>From a short look at the respective helpers (lh_binary, lh_chroot,
> lh_chroot_resolv), I can't imagine a case where this can happen.
Looking at lh_binary, I now think resolv.conf is always taken from the
host system:
38
39 if [ "${LH_CHROOT_BUILD}" = "enabled" ]
40 then
41 # Configuring chroot
42 lh_chroot_devpts install ${*}
43 lh_chroot_proc install ${*}
44 lh_chroot_sysfs install ${*}
45 lh_chroot_hosts install ${*}
46 lh_chroot_resolv install ${*}
47 lh_chroot_hostname install ${*}
48 lh_chroot_sources install ${*}
49 fi
50
51 # Building root filesystem
52 lh_binary_rootfs ${*}
maybe line 46 should be removed or moved after line 52 ?!
Greetings
Jens
_______________________________________________
debian-live-devel mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/debian-live-devel
