Bug#174360: marked as done (host name-related setup options are confusingly restrictive)
Your message dated Mon, 22 Mar 2004 02:47:07 -0500
with message-id <E1B5K9L-0007w3-00@newraff.debian.org>
and subject line Bug#174360: fixed in netcfg 0.57
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; 26 Dec 2002 13:32:43 +0000
>From zefram@fysh.org Thu Dec 26 07:32:42 2002
Return-path: <zefram@fysh.org>
Received: from (bowl.fysh.org) [81.5.149.242] (mail)
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 18RY7u-0003ON-00; Thu, 26 Dec 2002 07:32:42 -0600
Received: from zefram by bowl.fysh.org with local (Exim 3.35 #1 (Debian))
id 18RY7s-0004ZG-00; Thu, 26 Dec 2002 13:32:40 +0000
Date: Thu, 26 Dec 2002 13:32:40 +0000
To: submit@bugs.debian.org
Subject: DNS configuration section is inflexible
Message-ID: <20021226133240.GA14175@fysh.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.28i
From: Zefram <zefram@fysh.org>
Delivered-To: submit@bugs.debian.org
X-Spam-Status: No, hits=-4.6 required=5.0
tests=SPAM_PHRASE_00_01,USER_AGENT,USER_AGENT_MUTT
version=2.41
X-Spam-Level:
Package: install
Version: woody
I've installed Debian over the network. Early in the install process,
dbootstrap asks for network and DNS configuration information, which is
used both for the network installation and as the initial configuration
of the installed system.
When asking for a hostname, dbootstrap rejects any hostname containing
dots; it demands an unqualified name. This contradicts the reasonably
popular practice of making the hostname an FQDN, as promoted by Paul Vixie
in BIND documentation. Obviously this doesn't make much difference to
the network install process, but it annoyingly forces the administrator
to modify this part of the configuration once the system is installed
and running.
The next configuration dialogue asks for "the domain name" of the network.
This is a rather confused request. This information is actually used in
two distinct ways: to construct the host's FQDN, and to provide default
qualification for unqualified names in name lookups. These two matters
are logically distinct, and, with the "search" directive replacing
"domain" in modern resolv.conf format, the default qualification need
not even be singular.
Secondly, the mention of "the network" seems to refer back to the IPv4
network-layer configuration that immediately precedes the DNS-related
configuration dialogues. That might be accidental, a case of poor
proofreading, but I don't see what else could be being referred to by the
words "the network". The domain part of the host FQDN, and the default
domain for unqualified names, needn't identify anything really meaningful,
such as a piece of network-layer topology or an administrative grouping.
All it can be said to identify is a group of related *names*, which I
wouldn't refer to as a "network".
(Incidentally, on perusal of the source I see that the domain name
dialogue doesn't check the domain name for validity with anything like
the stringency with which the hostname is checked.)
As a solution, I propose that the DNS configuration should ask the
following questions (with more explanation for those that don't know
the terminology):
1. What is the hostname of this host? You may give an unqualified
or fully-qualified name. [Default name is unqualified.
Check for RFC1123 compliance, allowing but not requiring full
qualification. This is what goes in /etc/hostname.]
2. [If hostname given was unqualified.] What is the domain name
that should be attached to the hostname to make the host's FQDN?
[Default blank, which should be permitted. If non-blank, this
domain name is used to create an FQDN alias in /etc/hosts.]
3. What domains should be searched to look up unqualified hostnames?
[Default is the domain part of the host's FQDN, or "." if that
is blank. Permit multiple domain names. A blank list is treated
as ".". The list goes into /etc/resolv.conf.]
-zefram
---------------------------------------
Received: (at 174360-close) by bugs.debian.org; 22 Mar 2004 07:53:06 +0000
>From katie@ftp-master.debian.org Sun Mar 21 23:53:06 2004
Return-path: <katie@ftp-master.debian.org>
Received: from newraff.debian.org [208.185.25.31] (mail)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1B5KF8-0003uK-00; Sun, 21 Mar 2004 23:53:06 -0800
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
id 1B5K9L-0007w3-00; Mon, 22 Mar 2004 02:47:07 -0500
From: Joshua Kwan <joshk@triplehelix.org>
To: 174360-close@bugs.debian.org
X-Katie: $Revision: 1.45 $
Subject: Bug#174360: fixed in netcfg 0.57
Message-Id: <E1B5K9L-0007w3-00@newraff.debian.org>
Sender: Archive Administrator <katie@ftp-master.debian.org>
Date: Mon, 22 Mar 2004 02:47:07 -0500
Delivered-To: 174360-close@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_12
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-5.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2004_03_12
X-Spam-Level:
Source: netcfg
Source-Version: 0.57
We believe that the bug you reported is fixed in the latest version of
netcfg, which is due to be installed in the Debian FTP archive:
netcfg-dhcp_0.57_i386.udeb
to pool/main/n/netcfg/netcfg-dhcp_0.57_i386.udeb
netcfg-static_0.57_i386.udeb
to pool/main/n/netcfg/netcfg-static_0.57_i386.udeb
netcfg_0.57.dsc
to pool/main/n/netcfg/netcfg_0.57.dsc
netcfg_0.57.tar.gz
to pool/main/n/netcfg/netcfg_0.57.tar.gz
netcfg_0.57_i386.udeb
to pool/main/n/netcfg/netcfg_0.57_i386.udeb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 174360@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Joshua Kwan <joshk@triplehelix.org> (supplier of updated netcfg package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Fri, 19 Mar 2004 18:30:38 -0800
Source: netcfg
Binary: netcfg-static netcfg-dhcp netcfg
Architecture: source i386
Version: 0.57
Distribution: unstable
Urgency: low
Maintainer: Debian Install System Team <debian-boot@lists.debian.org>
Changed-By: Joshua Kwan <joshk@triplehelix.org>
Description:
netcfg - Configure the network (udeb)
netcfg-dhcp - Configure the network via DHCP (udeb)
netcfg-static - Configure a static network (udeb)
Closes: 174360 238653
Changes:
netcfg (0.57) unstable; urgency=low
.
* Bastian Blank
- Use inet_pton and inet_ntop. Why must people always write their own
instead of using well tested standard functions?
- Only recalculate gateway if ipaddress or netmask is changed.
- Never recalculate nameserver.
* Joshua Kwan
- Make the question about adhoc/managed actually do something,
add a template for its question. Note: needs translation.
- Make interfaces honor the decision made in the adhoc/managed question.
- Make sure the WEP question, priority high, always gets asked.
- No gateway, no point-to-point address is OK. (Closes: #238653)
- If netcfg/get_hostname returns a FQDN, seed netcfg/get_domain with it
and do not ask that question a second time. Only ask it if FQDN was
_not_ passed. (Closes: #174360)
- Write out some informative text to INTERFACES_FILE.
* Updated translations:
- Danish (da.po) by Claus Hindsgaul
- French (fr.po) by Philippe Batailler
- Hungarian (hu.po) by VER�K István
- Japanese (ja.po) by Kenshi Muto
- Korean (ko.po) by Changwoo Ryu
- Lithuanian (lt.po) by KÄ?stutis BiliÅ«nas
- Dutch (nl.po) by Bart Cornelis
- Polish (pl.po) by Bartosz Fenski
- Portuguese (Brazil) (pt_BR.po) by André LuÃs Lopes
- Portuguese (pt.po) by Miguel Figueiredo
- Albanian (sq.po) by Elian Myftiu
- Swedish (sv.po) by André Dahlqvist
- Turkish (tr.po) by Osman Yüksel
- Ukrainian (uk.po) by Eugeniy Meshcheryakov
Files:
7a3293912af6b0c3fa044fc897919837 1473 debian-installer optional netcfg_0.57.dsc
079a9f065498c4aa10f7b684e869f139 127531 debian-installer optional netcfg_0.57.tar.gz
3904352e46f16374f639783575905baf 108494 debian-installer optional netcfg_0.57_i386.udeb
14e4749fbf9c64219e60586797c47e2a 82752 debian-installer optional netcfg-dhcp_0.57_i386.udeb
89d18550db07decae12b59ff22e0fe18 93154 debian-installer optional netcfg-static_0.57_i386.udeb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iQIVAwUBQF6VCKOILr94RG8mAQJ0chAA03MGQ43btyiUdXpGPZLuqHS0fpRs/YJy
HZT7HTPuynsHS7F5J47SJTA+DOpxLrnJm/Bg9XOypbdhCPAmV1VokXvadKsTSkM9
edHmAnzzefHFduiNB1K/tsScIymv1PE0nn7QBvsqk+u5tdOXElV2Iy7SsckAbCeK
Z4dAnSdkYqFtY+8rWjqrRpTeeMt9v3sDmzmbFt2vReg20z4BS1vsuDeMrgsU1A2I
Tz/sx1Fr9c8YqXv0ugTFdSdzAb+hCfIDg5SM7NkZ6qdUjv9W/UnBrWHouy/w5QGL
4DYwkYCqEyiT/87Nb08wnULq2ekl22FT4H6O/60825QFHI9HE+5hEWJCk498Pt5d
GfeYWWdz0egrksEIVUqY9ke7EAragLWTMZCjldK3+d2KT2JAzniTDpufw2GB6roP
uqO/oEOMruCb9eOQ8oZVYUMIOO2HG3AlU8PDpRwz7X5+MRrxNeq/UnrYC6zn1qHY
ggt6fAUWWpJRnciBEYJ1upSJTelDAWZAD7lM7ZbF2z2NDwryt2R2amehW+VzcSqA
MtavDSf95/JPT5Kn2VGwKh6H5sf+S5Se2NZSHSdfegtMM5ZqObxGXEPk+eckX+b6
GSrco+3IjpsUgR+tarELIX9ueeT4XaaedE8u1ovygfCMlsYgCdiBlGaO51w6stGZ
1tOor79wPAM=
=BgBD
-----END PGP SIGNATURE-----
Reply to: