Surely the alternative to adding an 'auto' line is that the interface
won't automatically be brought up on the first reboot after
installation? Without NetworkManager, I think it's more likely that the
same interface is going to be in use before and after installation.
With NetworkManager, the installer *already* calls
/usr/lib/NetworkManager/ifblacklist_migrate.sh, which is supposed to
disable 'auto' lines in favour of NM. Thus, I think Clint's comment #3
is based on some mistaken assumptions, or else is mistakenly ascribing a
network-manager bug to d-i.
I'm more than happy for this bug to remain open for discussion, but I
don't think simply removing the 'auto' line is the solution, nor do I
think that simply punting and asking the user what to do is a good
approach; and I'm going to mark this Won't Fix for oneiric as we could
easily do more harm than good by changing behaviour at this late stage.
I rather suspect that fixing this in a way that makes everyone happy
will require changes outside the installer; having to predict what
reality will be at some later point in the installer never works well.
** Changed in: netcfg (Ubuntu Oneiric)
Status: Confirmed => Won't Fix
** Changed in: netcfg (Ubuntu Oneiric)
Assignee: Ubuntu Installer Team (ubuntu-installer) => (unassigned)
** Changed in: netcfg (Ubuntu)
Assignee: Ubuntu Installer Team (ubuntu-installer) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/847782
Title:
installer writes a permanent ethernet entry in interfaces file
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netcfg/+bug/847782/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
