[Touch-packages] [Bug 1347859] Re: Introduction of Predictable Network Interface Names (aka biosdevname) breaks working systems

2016-05-24 Thread Peter Funk
I consider those unpredictable "predictable interface names" as a very very stupid idea! I don't want my interface eth0 be renamed into something else! Please read this post here: https://lists.dyne.org/lurker/message/20160111.171633.d8fa4287.pl.html Now as the roll out of Ubuntu 16.04 starts

[Touch-packages] [Bug 1347859] Re: Introduction of Predictable Network Interface Names (aka biosdevname) breaks working systems

2016-05-24 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-meta (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.

[Touch-packages] [Bug 1347859] Re: Introduction of Predictable Network Interface Names (aka biosdevname) breaks working systems

2015-07-05 Thread Anthony
I also put GRUB_CMDLINE_LINUX_DEFAULT=net.ifnames=1 in /etc/default/grub and removed 75-persistent-net-generator.rules -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.

[Touch-packages] [Bug 1347859] Re: Introduction of Predictable Network Interface Names (aka biosdevname) breaks working systems

2015-07-05 Thread Anthony
Is there any update on this? I have two USB mobile broadband interfaces and even if I upgraded to Ubuntu Vivid the network names are still not predictable. I had a quick look on the mailing list discussion and It's worth to note that some USB devices have duplicate mac addresses so it

[Touch-packages] [Bug 1347859] Re: Introduction of Predictable Network Interface Names (aka biosdevname) breaks working systems

2015-06-03 Thread Robie Basak
The biosdevname mechanism is being proposed to be changed. Please see https://lists.ubuntu.com/archives/ubuntu-devel/2015-June/038777.html. Feedback appreciated. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in

Re: [Touch-packages] [Bug 1347859] Re: Introduction of Predictable Network Interface Names (aka biosdevname) breaks working systems

2015-04-13 Thread Forest
On Mon, 13 Apr 2015 13:32:15 -, Robie Basak wrote: A release upgrade should not cause biosdevname to get installed. So can you (or someone) please confirm that this is definitely the behaviour in some case, It has now been most of a year since I filed the bug report, so as you might imagine,

[Touch-packages] [Bug 1347859] Re: Introduction of Predictable Network Interface Names (aka biosdevname) breaks working systems

2015-04-13 Thread Robie Basak
Full history in bug 891258 and https://lists.ubuntu.com/archives/ubuntu- devel/2012-January/034687.html, https://lists.ubuntu.com/archives /ubuntu-devel/2012-February/thread.html. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed

[Touch-packages] [Bug 1347859] Re: Introduction of Predictable Network Interface Names (aka biosdevname) breaks working systems

2015-04-13 Thread Robie Basak
Thank you for taking the time to file this and helping to make Ubuntu better. I appreciate your detailed write-up and understand your frustration at the changes made. Before going into policy questions, I'd like to clear up a couple of factual concerns I have after reading your report. I think

[Touch-packages] [Bug 1347859] Re: Introduction of Predictable Network Interface Names (aka biosdevname) breaks working systems

2014-07-28 Thread Daniel Jared Dominguez
** Changed in: biosdevname (Ubuntu) Status: New = Opinion ** Changed in: systemd (Ubuntu) Status: New = Opinion ** Changed in: udev (Ubuntu) Status: New = Opinion -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is

[Touch-packages] [Bug 1347859] Re: Introduction of Predictable Network Interface Names (aka biosdevname) breaks working systems

2014-07-23 Thread Forest
** Description changed: Relatively recent linux distribution upgrades have been causing computers' ethernet devices to be unexpectedly renamed. While I understand that consistent device naming solves problems on some systems (mostly multi-NIC servers and a few specialty embedded devices),