Bug#798329: ifconfig: changed output format breaks scripts

[Thorsten Glaser]

On Tue, 8 Sep 2015, Martín Ferrari wrote:

> Is this breaking a package or just your scripts?

This is breaking at least two scripts of mine, which is where and why
I noticed this immediately after the dist-upgrade today, but there’ll
be others lurking. Probably none of them packaged, though.

> In any case, I think you should be doing this differently. Either using
> iproute2 that has a parseable format (although that has changed too), or

This won’t work, I did quite the WTF today at iproute2 now, as it
appends “@NONE” to the interface names.

I need reliable, consistent, parsable output across all Debian versions
(and some derivates).

> direcly parsing files in /proc/net

Excuse me, but WTF?

The standard Unix interface for things is stdout of other commands,
as in, filters and pipes. ifconfig is *the* standard utility to get
information about interfaces.

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg