Your message dated Sat, 9 Mar 2002 15:28:29 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#137473: boot-floppies: DNS resolution not working in busybox
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 9 Mar 2002 14:04:53 +0000
>From [EMAIL PROTECTED] Sat Mar 09 08:04:53 2002
Return-path: <[EMAIL PROTECTED]>
Received: from mailout10.sul.t-online.com [194.25.134.21]
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 16jhSv-0006Nu-00; Sat, 09 Mar 2002 08:04:53 -0600
Received: from fwd11.sul.t-online.de
by mailout10.sul.t-online.com with smtp
id 16jh1P-0001wZ-01; Sat, 09 Mar 2002 14:36:27 +0100
Received: from zombie (520064145672-0001@[217.85.214.247]) by fwd11.sul.t-online.com
with esmtp id 16jh1I-0KxqBUC; Sat, 9 Mar 2002 14:36:20 +0100
Received: from inet by zombie with local (Exim 3.35 #1 (Debian))
id 16jcuT-00010F-00; Sat, 09 Mar 2002 10:13:01 +0100
From: [EMAIL PROTECTED] (Eduard Bloch)
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: boot-floppies: DNS resolution not working in busybox
X-Mailer: reportbug 1.44
Date: Sat, 09 Mar 2002 10:13:01 +0100
Message-Id: <E16jcuT-00010F-00@zombie>
Sender: Eduard Bloch <[EMAIL PROTECTED]>
X-Sender: [EMAIL PROTECTED]
Delivered-To: [EMAIL PROTECTED]
Package: boot-floppies
Version: N/A; reported 2002-03-09
Severity: serious
I noted that recent builds have broken DNS resolving functionality.
Nothing works, no ping, no wget. A run in the strace showed that it
tries to open...
open("/lib/libnss_dns.so.2", O_RDONLY) = 4
open("/lib/libresolv.so.2", O_RDONLY) = 4
This works fine localy, but on the rootfs, this files are not present. I
will probably fix this today; gotta go now.
Gruss/Regards,
Eduard.
-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux zombie 2.4.18-bf2.4 #1 Die Mär 5 11:34:27 CET 2002 i686
Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro
---------------------------------------
Received: (at 137473-done) by bugs.debian.org; 9 Mar 2002 16:46:45 +0000
>From [EMAIL PROTECTED] Sat Mar 09 10:46:45 2002
Return-path: <[EMAIL PROTECTED]>
Received: from mailout03.sul.t-online.com [194.25.134.81]
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 16jjzZ-00062M-00; Sat, 09 Mar 2002 10:46:45 -0600
Received: from fwd02.sul.t-online.de
by mailout03.sul.t-online.com with smtp
id 16jhps-0001SK-04; Sat, 09 Mar 2002 15:28:36 +0100
Received: from zombie (520064145672-0001@[217.85.214.247]) by fwd02.sul.t-online.com
with esmtp id 16jhpk-0vyqMiC; Sat, 9 Mar 2002 15:28:28 +0100
Received: from inet by zombie with local (Exim 3.35 #1 (Debian))
id 16jhpm-0005EQ-00; Sat, 09 Mar 2002 15:28:30 +0100
Date: Sat, 9 Mar 2002 15:28:29 +0100
From: [EMAIL PROTECTED] (Eduard Bloch)
To: Eduard Bloch <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
Subject: Re: Bug#137473: boot-floppies: DNS resolution not working in busybox
Message-ID: <[EMAIL PROTECTED]>
References: <E16jcuT-00010F-00@zombie>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <E16jcuT-00010F-00@zombie>
User-Agent: Mutt/1.3.27i
Sender: Eduard Bloch <[EMAIL PROTECTED]>
X-Sender: [EMAIL PROTECTED]
Delivered-To: [EMAIL PROTECTED]
Moin Eduard!
Eduard Bloch schrieb am Saturday, den 09. March 2002:
> Package: boot-floppies
> Version: N/A; reported 2002-03-09
> Severity: serious
>
> I noted that recent builds have broken DNS resolving functionality.
> Nothing works, no ping, no wget. A run in the strace showed that it
> tries to open...
>
> open("/lib/libnss_dns.so.2", O_RDONLY) = 4
> open("/lib/libresolv.so.2", O_RDONLY) = 4
My mistake.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
