[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#474709: marked as done (rbootd should not hard-code eth0)



Your message dated Mon, 07 Apr 2008 15:32:03 +0000
with message-id <E1JitKF-0006mW-At@ries.debian.org>
and subject line Bug#474709: fixed in rbootd 2.0-10
has caused the Debian Bug report #474709,
regarding rbootd should not hard-code eth0
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 owner@bugs.debian.org
immediately.)


-- 
474709: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=474709
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: rbootd
Version: 2.0-9
Severity: important

Please don't hard-code eth0 as interface in /etc/init.d/rbootd.

On modern systems it's possible that eth0 is some device found during
the installation (e.g. firewire) and that the first ethernet device
becomes eth1.  However, the rc script has IFACE=eth0 hard-coded.

The documentation of rbootd says that it's looking for the first
network interface that is up and not 'lo'.  This behaviour should be
fine in most cases.  Maybe the rc file shouldn't lock rbootd to
'-i $IFACE' at all?

Also, since this device is bound to be altered by the admin, it may be
useful to move this configuration into /etc/default/rbootd.

Regards,

	Joey

-- 
If you come from outside of Finland, you live in wrong country.
	-- motd of irc.funet.fi

Please always Cc to me when replying to me on the lists.



--- End Message ---
--- Begin Message ---
Source: rbootd
Source-Version: 2.0-10

We believe that the bug you reported is fixed in the latest version of
rbootd, which is due to be installed in the Debian FTP archive:

rbootd_2.0-10.diff.gz
  to pool/main/r/rbootd/rbootd_2.0-10.diff.gz
rbootd_2.0-10.dsc
  to pool/main/r/rbootd/rbootd_2.0-10.dsc
rbootd_2.0-10_i386.deb
  to pool/main/r/rbootd/rbootd_2.0-10_i386.deb



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 474709@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Martin Schulze <joey@infodrom.org> (supplier of updated rbootd 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: Mon, 07 Apr 2008 17:20:32 +0200
Source: rbootd
Binary: rbootd
Architecture: source i386
Version: 2.0-10
Distribution: unstable
Urgency: low
Maintainer: Martin Schulze <joey@debian.org>
Changed-By: Martin Schulze <joey@infodrom.org>
Description: 
 rbootd     - Remote Boot Daemon
Closes: 437883 465907 474709
Changes: 
 rbootd (2.0-10) unstable; urgency=low
 .
   * New-Maintainer upload (closes: Bug#465907)
   * Added support for nostrip build option (closes: Bug#437883)
   * Improved packaging
   * Let rbootd decide the interface to use (closes: Bug#474709)
   * Added support for default file with interface setting
   * Adjusted changelog
   * Code improvements
     . Avoid trigraph
     . Include <time.h> instead of <sys/time.h> for time()
     . Removed obfuscated C line that was supposed to be dropped in 2.0-4
Files: 
 429a05a8dd8d1fbb67e3f7ecba2fda47 542 net extra rbootd_2.0-10.dsc
 cfa43238ce43259a1d03d1cf99180a31 9541 net extra rbootd_2.0-10.diff.gz
 17fba181a574a83dd88e912b94212eb3 19596 net extra rbootd_2.0-10_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFH+jz5W5ql+IAeqTIRAiH0AKCWK4QN/U07l3cWvdu2RLCZa83JQgCfVihx
T3L0nYFv2SeFUHqTP9L06Lc=
=ZT59
-----END PGP SIGNATURE-----



--- End Message ---

Reply to: