[Bug 1526808] Re: installed system qeth NIC name is too verbose

2016-02-02 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 228-4ubuntu2 --- systemd (228-4ubuntu2) xenial; urgency=high * Use shorter bus_id for ccw net-id interface names. LP: #1526808 * Add a snippet to migrate existing network configuration to new names. -- Dimitri John Ledkov Wed, 27 Jan

[Bug 1526808] Re: installed system qeth NIC name is too verbose

2016-02-01 Thread Dimitri John Ledkov
** Changed in: systemd (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1526808 Title: installed system qeth NIC name is too verbose To manage noti

[Bug 1526808] Re: installed system qeth NIC name is too verbose

2016-01-28 Thread Ubuntu Foundations Team Bug Bot
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1526808 Title: installed system qeth NIC name is too verbose To manage notifications about this bug go to: https://bugs.launchpad.

[Bug 1526808] Re: installed system qeth NIC name is too verbose

2016-01-28 Thread Dimitri John Ledkov
** Patch added: "systemd_228-4ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1526808/+attachment/4558415/+files/systemd_228-4ubuntu2.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.laun

[Bug 1526808] Re: installed system qeth NIC name is too verbose

2016-01-28 Thread Dimitri John Ledkov
Imho, enccw600 is confusing. FIrst of all, I have no idea why ccw code path is compiled on all architectures when this bus is only present on S/390. Furthermore that's the only bus one can have ethernet devices (and dasd disk drives) on. Thus all network nics end up with "ccw" in the name, which

[Bug 1526808] Re: installed system qeth NIC name is too verbose

2015-12-17 Thread Martin Pitt
OK. I suppose "en600" might be too sloppy/short, but "enccw600" seems okay? Care to open a ticket on https://github.com/systemd/systemd/issues so that we can find an upstreamable solution? We don't really want to introduce a permanent Ubuntu delta for this, especially as this will touch code. Than

[Bug 1526808] Re: installed system qeth NIC name is too verbose

2015-12-17 Thread Dimitri John Ledkov
So. en -> is ethernet prefix. Given that there are other types of ccw devices that is ok. cww -> is type of driver used, which is not necessary in the name. 0.0.0 -> i believe is redundant 600 -> is good, as that's the unique address that is used to configure thing in z/VM I'm proposing to sim

[Bug 1526808] Re: installed system qeth NIC name is too verbose

2015-12-17 Thread Dimitri John Ledkov
** Changed in: systemd (Ubuntu) Importance: Undecided => High ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1526808 Title: install

[Bug 1526808] Re: installed system qeth NIC name is too verbose

2015-12-16 Thread Martin Pitt
In case you don't know yet: You want to start looking here: sudo udevadm test-builtin path_id /sys/class/net/eth0 which will say something like D_PATH=ccwgroup-0.0.0600 ID_PATH_TAG=ccwgroup-0_0_0600 which will then result in $ udevadm info /sys/class/net/eth0 P: /devices/qeth/0.0.0600/net/et

[Bug 1526808] Re: installed system qeth NIC name is too verbose

2015-12-16 Thread Ubuntu QA Website
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1526808 ** Tags added: iso-testing -- You received this bug notification because you are a member of Ubuntu Bugs, which is s