fdo-mirrors/NetworkManager
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/NetworkManager/NetworkManager.git synced 2026-01-03 11:40:18 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

2005-06-30 Robert Love <rml@novell.com>

Browse source 
* README: update to reflect nm-applet replacing NetworkManagerInfo.


git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@768 4912f4e0-d625-0410-9fb7-b9a5a253dbdc
This commit is contained in:
Robert Love 2005-06-30 14:35:46 +00:00 • committed by Robert Love
parent ae0754c1e1
commit 911ed8d02a
2 changed files with 14 additions and 18 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
ChangeLog
View file

@ -5,6 +5,7 @@
* gnome/applet/menu-items.c: whitespace, misc. cleanup.
* configure.in: look in "/usr/sbin" for dhcdbd, too. (it shouldn't be
in /sbin unless D-BUS is, folks).
* README: update to reflect nm-applet replacing NetworkManagerInfo.
2005-06-27 Robert Love <rml@novell.com>

31
README
View file

@ -42,28 +42,23 @@ are not.
STRUCTURE:
NetworkManager runs as a root-user system level daemon, since it must manipulate
hardware directly. It communicates over DBUS with at least one other daemon,
the info-daemon. Since Trusted and Preferred Networks are user-specific, there
must be some mechanism of getting this information per-user. NetworkManager
cannot store that information as it is user-specific, and therefore communicates
over DBUS to the info-daemon which provides those lists. NetworkManager also
provides an API over DBUS for any DBUS-aware application to determine the
current state of the network, including available wireless networks the computer
is aware of and specific details about those networks. This API also provides
the means for forcing NetworkManager to associate with a specific wireless
network. Use of DBUS allows separation of NetworkManager, which requires no
user-interface, and the parts of the user interface which might be desktop
environment specific.
hardware directly. It communicates over DBUS with a desktop-level per-user
process, nm-applet. Since Trusted and Preferred Networks are user-specific,
there must be some mechanism of getting this information per-user.
NetworkManager cannot store that information as it is user-specific, and
therefore communicates over DBUS to the user daemon which provides those lists.
NetworkManager also provides an API over DBUS for any DBUS-aware application to
determine the current state of the network, including available wireless
networks the computer is aware of and specific details about those networks.
This API also provides the means for forcing NetworkManager to associate with a
specific wireless network. Use of DBUS allows separation of NetworkManager,
which requires no user-interface, and the parts of the user interface which
might be desktop environment specific.
The info-daemon provides a DBUS service called NetworkManagerInfo, which should
The nm-applet provides a DBUS service called NetworkManagerInfo, which should
provide to NetworkManager the Trusted and Preferred Networks lists upon request.
It also should be able to display a dialog to retrieve a WEP/WPA key or
passphrase from the user when NetworkManager requests it. The GNOME version of
NetworkManagerInfo, for example, stores Trusted and Preferred Networks in GConf,
and proxies that information to NetworkManager upon request.
Other UI bits might include a user-visible application (for example, the
included GNOME Panel applet) providing a list of available wireless networks to
the user and a means to manually select one to associate with.