#7271 NORM Never A: NetworkManager-0.6 broken in olpc3
Zarro Boogs per Child
bugtracker at laptop.org
Fri Jun 13 16:30:07 EDT 2008
#7271: NetworkManager-0.6 broken in olpc3
------------------------------+---------------------------------------------
Reporter: dsd | Owner: dcbw
Type: defect | Status: new
Priority: normal | Milestone: Never Assigned
Component: network manager | Version: olpc-3
Resolution: | Keywords:
Verified: 0 | Blocking:
Blockedby: |
------------------------------+---------------------------------------------
Comment(by dsd):
Next problem: src/dhcp-manager/nm-dhcp-manager.c dhclient_run() passes the
-x option to dhclient
OLPC-2 has dhclient-3.0.5 and OLPC-3 has dhclient-4.0.0
Fedora had a patch in dhclient-3.0.5 which added a -x option:
{{{
+The -x argument enables extended option information to be created in the
+-s dhclient-script environment, which would allow applications running
+in that environment to handle options they do not know about in advance -
+this is a Red Hat extension to support dhcdbd and NetworkManager.
}}}
However dhclient-4.0.0 *upstream* added a -x option with totally different
meaning:
{{{
- Added -x option to dhclient, which triggers dhclient processes
to exit gracefully without releasing leases first
}}}
Fedora seem to have silently dropped their version of the -x patch with
the 4.0.0 release, so running "dhclient -x" is now just a way of telling
other dhclient's to go away.
NetworkManager upstream removed the -x option:
http://svn.gnome.org/viewvc/NetworkManager/trunk/src/dhcp-manager/nm-dhcp-
manager.c?r1=2674&r2=2681
So we now need to do the same, to make dhclient actually run when NM
launches it.
The #if'd out part was then removed with another change:
http://svn.gnome.org/viewvc/NetworkManager/trunk/src/dhcp-manager/nm-dhcp-
manager.c?r1=3215&r2=3401
(perhaps we need to backport that patch?)
--
Ticket URL: <http://dev.laptop.org/ticket/7271#comment:3>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system
More information about the Bugs
mailing list