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 is weird.
Thus I do want to drop the static prefix of ccw, which has no meaning
(unlike e.g. letters in the PCI enumeration).
I've contacted original contributer of the ccw names, no response yet.
Will propose upstream too.
** Changed in: systemd (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1526808
Title:
installed system qeth NIC name is too verbose
Status in systemd package in Ubuntu:
In Progress
Bug description:
installed system qeth NIC name is too verbose
Specifically on s390x it came up as:
enccw0.0.0600
which is possibly too verbose, however it is definitive and trivial to
understand for anyone with z/VM knowledge as this correlates with
device hex address (aka 0x600 nic)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1526808/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
