Bug#241075: resolv.conf should be created even if empty

[Christopher Martin <christopher.martin@utoronto.ca>]

Package: netcfg
Version: 0.54

(not sure about the exact version of netcfg I installed with, but the 
issue occurred with both beta2 and beta3)

With both beta2 and beta3 I managed to obtain a system with 
no /etc/resolv.conf. I don't mean that it was empty, but that it didn't 
exist.

When I then used pppoeconf to configure an Internet connection, it failed 
to work since it will only enter DNS server IPs into an already existing 
resolv.conf, but will not create that file if it does not exist. I 
contacted the pppoeconf maintainer, but was rather brusquely informed 
that this wasn't a pppoeconf problem, since a resolv.conf should exist, 
even if empty, on any system not "broken". If this is indeed the case, 
please modify netcfg to create that file no matter the outcome of the 
installer's network configuration routines. If not, let me know, and so 
armed I'll have another chat with the pppoeconf maintainer.

Thanks,
Christopher Martin