On 02/05/2012 06:16 PM, Stéphane Graber wrote:
To be safe, I'd much prefer having DELL and other interested users of
the feature help get these networking scripts fixed during the rest of
the cycle (as long as they are still considered bugfixes) and have a
session at UDS in Oakland on biosdevname and turning it on by default.
The real advantage to this feature is on servers. I anticipate that most
server users will stick with an LTS release instead.
On 02/05/2012 07:03 PM, Scott Ritchie wrote:
If I'm reading Dell's email right, it seems like they've volunteered
to help fix the archive in this regard
John's team has had experience fixing this in Fedora. Their work was of
sufficient quality to be picked up by RHEL by default.
On 02/06/2012 09:44 AM, Robbie Williamson wrote:
Am I wrong, or did Dell request that we enable this feature by default
for Dell Poweredge servers *only*, by detecting at boot...and that
they had done something similar with Fedora? If we can contain this
change to only affecting Dell servers, then any issues it creates
would also only affect Dell servers...and I'd think Dell would have a
self-interest in helping us resolve those asap. Right?
This is similar to what RHEL6 is doing. They enable biosdevname by
default only a limited subset of Dell machines (
http://rhn.redhat.com/errata/RHEA-2011-0644.html).
If this feature is picked up specifically for Dell machines, there will
obviously be a vested interest to ensure the rest of the stack doesn't
have problem related to hardcoded interface names.
I'm unsure the timeline John's team will be able to commit to finding
and fixing these things. Feature freeze sounds a bit tight to me. I've
offered to help to review and sponsor his team's fixes however as they
find them.
--
Mario Limonciello
supe...@ubuntu.com
--
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
