Re: Bug#248399: dhcp-found dns servers not placed in resolv.conf after default install
On Thu, May 13, 2004 at 07:11:26PM -0700, Joshua Kwan wrote: (I also note that the binary is GIGANTIC compared to dhcp-client-udeb's! Can anything be done about that?) And it grows horrible if built against a shared uclibc. At least I don't think that mipsel binaries are 3 times as large than i386 binaries. Bastian -- You're dead, Jim. -- McCoy, Amok Time, stardate 3372.7 signature.asc Description: Digital signature
Re: Bug#248399: dhcp-found dns servers not placed in resolv.conf after default install
Update for debian-boot... This bug will be fixed by adding resolvconf support to dhcp-client. A patch has been prepared and fixed the problem for the submitter of #248399. -- Thomas Hood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#248399: dhcp-found dns servers not placed in resolv.conf after default install
On Tue, 11 May 2004 08:43:44 -0700, Matt Zimmerman wrote: In order for dhcp-client to be updated to v3, the various upgrade issues (dhcp-* v2 - dhcp-* v3, dhcp3-* - dhcp-* v3) need to be worked out, and I think it's a bit late in the game for that anyway. We asked about it some time ago and were told to leave it alone for d-i's sake. I note that I have just completed dhcp3-client-udeb support for the Debian installer, and it works. It has not been uploaded yet because it needs further testing (a significant part of netcfg was rewritten at the same time.) (I also note that the binary is GIGANTIC compared to dhcp-client-udeb's! Can anything be done about that?) -- Joshua Kwan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#248399: dhcp-found dns servers not placed in resolv.conf after default install
I just installed dhcpcd 1:1.3.22pl4-10 and dpkg -s reports: Conflicts: dhcpcd-sv, dhcp-client so I don't see how you could have both dhcpcd and dhcp-client (or any other DHCP client that Provides dhcp-client) installed. You're right, dhcpcd is not installed. I have dhcp-client 2.0pl5-16.1 When one installs tasks does tasksel knock out uninstallable items from the list and proceed? If so then that would explain how you ended up with resolvconf but not dhcpcd. Dunno, the huge apt-get command flew by with no prompting (probably a good thing). I haven't really investigated how tasksel calls apt-get. Actually, I thought resolvconf only got installed by the unstable version of tasksel (1.51); I just checked and I have 1.50 (testing) installed here. Now I'm not even sure where resolvconf came from. I am 100% sure I did not install resolvconf directly, and 99% sure I did not install anything that depended on it after the initial install (I checked my bash_history for root, and I think it actually contains every command I've used on this install). It's possible that one of the packages installed by one of the tasks I selected depends on it, however, dpkg --no-act -r resolvconf just says it would remove it, no errors based on dependencies. FYI, I think I chose the following tasks: basic-desktop, broadband, c-dev, desktop, java-dev, kernel-compile, office, print-server, python-dev, science, tex, unix-server, lsb. Re: Matt's comment about how this doesn't affect everyone using dhcp, for instance, him: Sorry, my question wasn't really properly phrased... I guess I just want to know who this would affect... you don't use resolvconf, but it got installed on my system through the installer and base-config/tasksel somehow, and I chose only normal options throughout the process. I had thought it came from tasksel (broadband) and that dhcpcd didn't get installed because it conflicted with dhcp-client or something, but that isn't clear to me anymore. I don't suppose d-i/base-config uses tasksel 1.51 somehow but installs 1.50... If it turns out that resolvconf just got on my system randomly then I guess just making it conflict with dhcp-client would be enough here, but I'm almost positive that this is some kind of default currently. The other email from Stefan seems to show at least someone else with the same problem. Scott -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#248399: dhcp-found dns servers not placed in resolv.conf after default install
Processing commands for [EMAIL PROTECTED]: clone 248399 -1 Bug#248399: dhcp-client installed instead of dhcp3-client Bug 248399 cloned as bug 248578. reassign -1 debootstrap Bug#248578: dhcp-client installed instead of dhcp3-client Bug reassigned from package `debian-installer' to `debootstrap'. retitle -1 Please install dhcp3-client rather than dhcp-client Bug#248578: dhcp-client installed instead of dhcp3-client Changed Bug title. severity -1 wishlist Bug#248578: Please install dhcp3-client rather than dhcp-client Severity set to `wishlist'. reassign 248399 dhcp-client Bug#248399: dhcp-client installed instead of dhcp3-client Bug reassigned from package `debian-installer' to `dhcp-client'. retitle 248399 Needs resolvconf support Bug#248399: dhcp-client installed instead of dhcp3-client Changed Bug title. severity 248399 normal Bug#248399: Needs resolvconf support Severity set to `normal'. severity 211569 normal Bug#211569: want an easy way to disable overwriting of resolv.conf Severity set to `normal'. merge 248399 211569 Bug#211569: want an easy way to disable overwriting of resolv.conf Bug#248399: Needs resolvconf support Merged 211569 248399. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#248399: dhcp-found dns servers not placed in resolv.conf after default install
On Tue, 2004-05-11 at 20:43, Scott Webster wrote: I likely selected the Broadband task in tasksel. I may have dhcpcd installed. I can't check now unfortunately, as the box is at home, and apparently the dynamic IP has changed. If I remember correctly, it is installed, and presumably it would be if it's in the same task as resolvconf. Nevertheless, dhclient is being run, presumably by ifup? I presume. How does ifup choose which dhcp program to run? Or am I offtrack here? It looks for DHCP clients in the following order: dhclient3 dhclient pump udhcpc dhcpcd I just installed dhcpcd 1:1.3.22pl4-10 and dpkg -s reports: Conflicts: dhcpcd-sv, dhcp-client so I don't see how you could have both dhcpcd and dhcp-client (or any other DHCP client that Provides dhcp-client) installed. When one installs tasks does tasksel knock out uninstallable items from the list and proceed? If so then that would explain how you ended up with resolvconf but not dhcpcd. I really should make resolvconf Conflict with dhcp-client (= 3.0.1betaRC4-1) until such time as resolvconf support is added to dhcp-client. This is a bug in the resolvconf package. However, the question remains: Should I add this Conflict or should I work toward getting resolvconf support into dhcp-client? If debootstrap is going to start installing dhcp3-client then I'll do the former. If not then I'll do the latter, provided the maintainers of dhcp-client agree to apply a patch. -- Thomas Hood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#248399: dhcp-found dns servers not placed in resolv.conf after default install
Hi Thomas, On Tue, May 11, 2004 at 03:48:03PM +0200, Thomas Hood wrote: I wondered why dhcp-client is still being installed, rather than dhcp3-client. On Tue, 2004-05-11 at 13:48, Anthony Towns wrote: That's easy: dhcp3-client didn't used to exist. So the question is: Why is debootstrap _still_ installing dhcp-client? Good question. I guess they are using it because that is the official DHCP client package (official in the sense that dhcp3-client started out as the unstable and development version of the ISC DHCP client, IIRC, and when v3 came out as stable we still kept the old v2 client alive in the dhcp-client package for some reasons.) (If dhcp3-client is to replace dhcp-client, why isn't it just being called dhcp-client, with dhcp2-client kept around if it's really needed?) Good question for the dhcp-client maintainers. CC'ing [EMAIL PROTECTED] Migrating the dhcp-* packages to version 3 of the ISC DHCP package was part of our plan. However, a few months ago we asked the debian-installer people on debian-boot and someone said the timing wasn't right for such a migration because of the risk involved. Cheers! Eloy.- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#248399: dhcp-found dns servers not placed in resolv.conf after default install
Processing commands for [EMAIL PROTECTED]: reassign 248399 debian-installer Bug#248399: dhcp-found dns servers not placed in resolv.conf after default install Bug reassigned from package `resolvconf' to `debian-installer'. retitle 248399 dhcp-client installed instead of dhcp3-client Bug#248399: dhcp-found dns servers not placed in resolv.conf after default install Changed Bug title. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#248399: dhcp-found dns servers not placed in resolv.conf after default install
reassign 248399 debian-installer retitle 248399 dhcp-client installed instead of dhcp3-client thanks On Tue, 2004-05-11 at 00:41, Scott Webster wrote: I do not have dhcp3-client installed, only dhcp-client. That's the problem. Resolvconf doesn't support dhcp-client -- only dhcp3-client. Please upgrade to dhcp3-client and let me know whether or not this fixes your problem. I don't know why the installer is installing dhcp-client rather than dhcp3-client. I'll reassign this to debian-installer. Maybe the d-i folks have their reasons for preferring dhcp-client over dhcp3-client but in that case I'd like to know what the reasons are. Adding dhcp-client to resolvconf wouldn't be the easiest job; I haven't bothered doing it because dhcp3-client is the replacement for dhcp-client and I have assumed that new installs will be using dhcp3-client. -- Thomas Hood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#248399: dhcp-found dns servers not placed in resolv.conf after default install
reassign 248399 debootstrap thanks On Tue, May 11, 2004 at 11:43:28AM +0200, Thomas Hood wrote: reassign 248399 debian-installer retitle 248399 dhcp-client installed instead of dhcp3-client thanks On Tue, 2004-05-11 at 00:41, Scott Webster wrote: I do not have dhcp3-client installed, only dhcp-client. That's the problem. Resolvconf doesn't support dhcp-client -- only dhcp3-client. Please upgrade to dhcp3-client and let me know whether or not this fixes your problem. I don't know why the installer is installing dhcp-client rather than dhcp3-client. I'll reassign this to debian-installer. Maybe the d-i folks have their reasons for preferring dhcp-client over dhcp3-client but in that case I'd like to know what the reasons are. Adding dhcp-client to resolvconf wouldn't be the easiest job; I haven't bothered doing it because dhcp3-client is the replacement for dhcp-client and I have assumed that new installs will be using dhcp3-client. dhcp-client is installed by debootstrap, so reassigning there. Cheers, -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#248399: dhcp-found dns servers not placed in resolv.conf after default install
On Tue, May 11, 2004 at 11:46:48AM +0100, Colin Watson wrote: I don't know why the installer is installing dhcp-client rather than dhcp3-client. I'll reassign this to debian-installer. That's easy: dhcp3-client didn't used to exist. (If dhcp3-client is to replace dhcp-client, why isn't it just being called dhcp-client, with dhcp2-client kept around if it's really needed?) Cheers, aj -- Anthony Towns [EMAIL PROTECTED] http://azure.humbug.org.au/~aj/ Don't assume I speak for anyone but myself. GPG signed mail preferred. ``Like the ski resort of girls looking for husbands and husbands looking for girls, the situation is not as symmetrical as it might seem.'' signature.asc Description: Digital signature
Bug#248399: dhcp-found dns servers not placed in resolv.conf after default install
I wondered why dhcp-client is still being installed, rather than dhcp3-client. On Tue, 2004-05-11 at 13:48, Anthony Towns wrote: That's easy: dhcp3-client didn't used to exist. So the question is: Why is debootstrap _still_ installing dhcp-client? (If dhcp3-client is to replace dhcp-client, why isn't it just being called dhcp-client, with dhcp2-client kept around if it's really needed?) Good question for the dhcp-client maintainers. CC'ing [EMAIL PROTECTED] -- Thomas Hood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#248399: dhcp-found dns servers not placed in resolv.conf after default install
On Tue, May 11, 2004 at 09:48:35PM +1000, Anthony Towns wrote: On Tue, May 11, 2004 at 11:46:48AM +0100, Colin Watson wrote: I don't know why the installer is installing dhcp-client rather than dhcp3-client. I'll reassign this to debian-installer. That's easy: dhcp3-client didn't used to exist. (If dhcp3-client is to replace dhcp-client, why isn't it just being called dhcp-client, with dhcp2-client kept around if it's really needed?) Because the debian-installer folks asked the dhcp*-client folks to leave things as they are for sarge. -- - mdz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#248399: dhcp-found dns servers not placed in resolv.conf after default install
On Tue, 2004-05-11 at 17:10, Matt Zimmerman wrote: Because the debian-installer folks asked the dhcp*-client folks to leave things as they are for sarge. So can should debootstrap switch to installing dhcp3-client? -- Thomas Hood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#248399: dhcp-found dns servers not placed in resolv.conf after default install
On Tue, May 11, 2004 at 05:23:06PM +0200, Thomas Hood wrote: On Tue, 2004-05-11 at 17:10, Matt Zimmerman wrote: Because the debian-installer folks asked the dhcp*-client folks to leave things as they are for sarge. So can should debootstrap switch to installing dhcp3-client? I expect not, but ask debian-boot. In order for dhcp-client to be updated to v3, the various upgrade issues (dhcp-* v2 - dhcp-* v3, dhcp3-* - dhcp-* v3) need to be worked out, and I think it's a bit late in the game for that anyway. We asked about it some time ago and were told to leave it alone for d-i's sake. -- - mdz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#248399: dhcp-found dns servers not placed in resolv.conf after default install
Perhaps I'm missing something here, but doesn't this mean that the default install with d-i is now broken by using both dhcp-client and resolvconf? Doesn't this affect everyone using dhcp? Clearly if the default install leads to a non-functioning network it won't be getting rave reviews... I must be confused... Scott Webster On Tue, May 11, 2004 at 08:43:44AM -0700, Matt Zimmerman wrote: On Tue, May 11, 2004 at 05:23:06PM +0200, Thomas Hood wrote: On Tue, 2004-05-11 at 17:10, Matt Zimmerman wrote: Because the debian-installer folks asked the dhcp*-client folks to leave things as they are for sarge. So can should debootstrap switch to installing dhcp3-client? I expect not, but ask debian-boot. In order for dhcp-client to be updated to v3, the various upgrade issues (dhcp-* v2 - dhcp-* v3, dhcp3-* - dhcp-* v3) need to be worked out, and I think it's a bit late in the game for that anyway. We asked about it some time ago and were told to leave it alone for d-i's sake. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#248399: dhcp-found dns servers not placed in resolv.conf after default install
On Tue, 2004-05-11 at 18:34, Scott Webster wrote: Perhaps I'm missing something here, but doesn't this mean that the default install with d-i is now broken by using both dhcp-client and resolvconf? Doesn't this affect everyone using dhcp? Is resolvconf installed by default? If so then it's news to me. (I knew that resolvconf was installed as part of the Broadband and Dialup tasks; however Broadband includes dhcpcd and that does work with resolvconf.) If the installer is installing both dhcp-client and resolvconf then one of the following needs to be done: 1. Install dhcp3-client instead 2. Don't install resolvconf 3. Add resolvconf support to dhcp-client I can supply a patch to implement #3 if it is decided that that is necessary. I haven't worried about getting support into dhcp-client before because I thought that it had been superseded by dhcp3-client. -- Thomas Hood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#248399: dhcp-found dns servers not placed in resolv.conf after default install
On Tue, May 11, 2004 at 08:07:00PM +0200, Thomas Hood wrote: Is resolvconf installed by default? If so then it's news to me. (I knew that resolvconf was installed as part of the Broadband and Dialup tasks; however Broadband includes dhcpcd and that does work with resolvconf.) I likely selected the Broadband task in tasksel. I may have dhcpcd installed. I can't check now unfortunately, as the box is at home, and apparently the dynamic IP has changed. If I remember correctly, it is installed, and presumably it would be if it's in the same task as resolvconf. Nevertheless, dhclient is being run, presumably by ifup? How does ifup choose which dhcp program to run? Or am I offtrack here? Scott -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#248399: dhcp-found dns servers not placed in resolv.conf after default install
On Tue, May 11, 2004 at 09:34:45AM -0700, Scott Webster wrote: Perhaps I'm missing something here, but doesn't this mean that the default install with d-i is now broken by using both dhcp-client and resolvconf? Maybe. Doesn't this affect everyone using dhcp? No? It certainly works fine for me (I don't use resolvconf). -- - mdz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
