installer writes a permanent ethernet entry in interfaces file
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
netcfg (Ubuntu) |
Confirmed
|
High
|
Unassigned | ||
Oneiric |
Won't Fix
|
High
|
Unassigned | ||
upstart (Ubuntu) |
Fix Released
|
High
|
Clint Byrum | ||
Oneiric |
Fix Released
|
High
|
Clint Byrum |
Bug Description
If Ubiquity (the installer) is ran while connected to the internet via ethernet, writes an "auto ethX" line in /etc/network/
So far, it seems like the best solution would be for the installer to give the user the option to choose what to do with the interfaces file after finishing installation. This will also be an issue with upgrades to Oneiric, so the upgrade tool should probably offer the user to "fix" the interfaces file. In all cases, the user should be offered a sane default behavior.
Please see bug #839595 for more information
description: | updated |
description: | updated |
description: | updated |
description: | updated |
Changed in debian-installer (Ubuntu): | |
importance: | Medium → High |
Changed in debian-installer (Ubuntu Oneiric): | |
status: | New → Confirmed |
assignee: | nobody → Canonical Foundations Team (canonical-foundations) |
affects: | debian-installer (Ubuntu Oneiric) → netcfg (Ubuntu Oneiric) |
Changed in netcfg (Ubuntu Oneiric): | |
assignee: | Canonical Foundations Team (canonical-foundations) → Ubuntu Installer Team (ubuntu-installer) |
Changed in upstart (Ubuntu Oneiric): | |
milestone: | none → ubuntu-11.10-beta-2 |
From my perspective, it makes sense for Ubiquity to write the 'auto eth0' (or more generically 'auto ethX') for a non-wireless device that it did the install over.
The difficulty is in determining if the user was just doing an install over that interface or would generally expect it to be permenant. If the user is expecting to keep that system plugged in, then adding an 'auto' entry is the right behavior, and *not* adding that entry may well mean the user cannot reach their machine after install.