On Tue, Mar 30, 2004 at 11:12:02AM -0500, Christopher Martin wrote: > 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.
This is default behavior when DHCP has been used. I'm not sure if it's _sound_ behavior, but it's not been a problem for me in all my installs. > 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. This is easy, but I would like to know what the Right Thing is to do. Maybe debian-boot can enlighten me... -- Joshua Kwan
signature.asc
Description: Digital signature
