Your message dated Mon, 29 Sep 2008 01:35:01 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#500193: netbase (without ifupdown installed) does not
bring up the loopback device
has caused the Debian Bug report #500193,
regarding netbase (without ifupdown installed) does not bring up the loopback
device
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
500193: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=500193
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: netbase
Version: 4.33
Severity: normal
As stated if ifupdown is not installed, then even the loopback adapter is not
brought up.
In my view, loopback is vital to the Linux environment.
Thus /etc/init.d/networking sould try other means to bring it up:
* trying ifconfig
* trying ip
* other means I'm not aware of?
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (1020, 'stable'), (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.25.14-eros2
Locale: LANG=, LC_CTYPE="en_US.utf8" (charmap=UTF-8) (ignored: LC_ALL set to
en_US.utf8)
Versions of packages netbase depends on:
ii lsb-base 3.1-23.2etch1 Linux Standard Base 3.1 init scrip
Versions of packages netbase recommends:
ii ifupdown 0.6.8 high level tools to configure netw
-- debconf information:
netbase/upgrade-note/etc-network-interfaces-pre-3.17-1:
netbase/upgrade-note/init.d-split-pre-3.16-1:
netbase/upgrade-note/radius-ports-pre-3.05:
netbase/upgrade-note/portmap-restart-pre-3.11-2:
--- End Message ---
--- Begin Message ---
On Sep 26, Ciprian Dorin Craciun <[EMAIL PROTECTED]> wrote:
> Well, the answer is very simple: if I want a lighweight
> installation of Debian (with the minimum number of packets -- mostly
> for virtual servers / appliances), many applications rely on 127.0.0.1
> to work properly, which doesn't happen. Thus I could consider the
> setup to be broken. (Meaning the package can be installed but can not
> be used.)
> (Another solution is to put ifupdown as a dependency not recommendation.)
The correct solution is to move the init script in the ifupdown package,
which will happen post-lenny.
A non-networked system without the ifupdown package is a corner case not
worth special support.
If you remove ifupdown you are on your own to configure everything, I
can't see why the loopback interface should be special-cased.
--
ciao,
Marco
signature.asc
Description: Digital signature
--- End Message ---
