I think the right thing to do is to hardwire the default to eth0 but
make it configurable in /etc/autopkgtest/xenlvm_adt_config (not
/etc/default/autopkgtest).
I'm afraid I don't have a patch planned to do that right now.
Thanks,
Ian.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists
severity 508660 normal
thanks
Mark Purcell writes ("Bug#508660: adtxenlvm: initscript assumes eth0"):
> This RC bug has been filed against one of your packages for a few weeks
> without comment from you.
I agree that the bug is a problem but I disagree with the severity.
I will
On Sunday 14 December 2008 06:14:24 Arndt Heuvel wrote:
> Package: adtxenlvm
> Version: 1.2.0
> Severity: serious
> Justification: Policy 10.4
Ian,
This RC bug has been filed against one of your packages for a few weeks
without comment from you.
There is also a patch suggestion from Gunnar.
Ar
The remaining references to eth0 appear to be used only in the domU,
where we control the interface names.
There is a simpler way to get the first "real" interface name which is:
ls /sys/class/net | awk '$1 != "lo" { print $1; exit }'
I'm not entirely convinced that this is the right thing to do
tag 508660 + patch
thanks
Hi,
The attached patch will allow you to specify the network interface via
the NETIFACE variable in /etc/default/autopkgtest. If this variable is
not set, the interface will be guessed as the first interface in
/proc/net/dev - More correct altrnatives can be, of course,
Package: adtxenlvm
Version: 1.2.0
Severity: serious
Justification: Policy 10.4
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Richte autopkgtest-xenlvm ein (1.2.0) ...
* adtxenlvm: installing firewall rules
/etc/
6 matches
Mail list logo
