Hmm, weird.
cat should have read the symlink and output everything ok.
Please try it with this patch and tell me how it goes:
diff -r1.9 60-copy-host-files
14c14,19
< cat /etc/resolv.conf > ${prefix}/etc/resolv.conf
---
> if [ -f "/etc/resolvconf/run/resolv.conf" ]; then
> cp /etc/resolvconf/run/resolv.conf ${prefix}/etc/resolv.conf
> else
> cp /etc/resolv.conf ${prefix}/etc/resolv.conf
> fi
>
Thanks,
Radu
Ian MacDonald wrote:
> So I noted the following change in 60-copy-host-files to address the
> problem:
>
> cat /etc/resolv.conf > ${prefix}/etc/resolv.conf
>
> This was what I suggested, but results in a zero byte resolv.conf,
> although one that can be modified - rather than a dangling symbolic
> link.
>
> To effectively accomplish the resolvconf workaround, there should be a
> condition for
>
> /etc/resolv.conf -> /etc/resolvconf/run/resolv.conf
>
> that, if true, copies the contents of the etc/resolvconf/rur/resolv.conf
> into the DomU resolv.conf.
>
> cheers,
> Ian.
> On Wed, 2006-03-08 at 20:11 +0200, Radu Spineanu wrote:
>> Ian MacDonald wrote:
>>> I use resolvconf to configure my resolv.conf on my Dom0. When I create
>>> a new image using xen-tools, it creates a resolve.conf symlinked to a
>>> non-existent file, something it would appear to have obtained from the Dom0
>>> environment, where resolvconf symlinks resolv.conf to another file.
>>>
>> Fixed in CVS.
>>
>> Thanks,
>> Radu
>
>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
