Gregory K. Ruiz-Ade wrote:
On Nov 20, 2007, at 11:12 AM, DJA wrote:
You would not explicitly use it unless you use WPA or WPA2 on your
access point. If you use NetworkManager, then you use it without
knowing it. Eventually, all Wifi connections invoked via either the
KDE or Gnome GUI's (and probably others) will also use it to do much
of the heavy lifting.
This, sadly, is not immediately useful to those who run neither GNOME
nor KDE, or exist only in console-land. In such cases, knowledge of
what's going on behind the scenes is quite useful.
Gregory
--Gregory K. Ruiz-Ade <[EMAIL PROTECTED]>
Not so. Neither KnetworkManager nor Wpa_supplicant need be run from a
GUI. In fact, until very recently (the time frame prior to FC6) those
programs needed to be run from the CLI or a script since there was no
reliable GUI tool with which to use them. They are both CLI tools. The
GUI front ends merely interact with them in a prettified manner.
There are some major changes occurring under the skin in Linux in
general which will affect how many services are handled, networking
being one in particular. Much of it centers around the rising importance
of DBUS and HAL system-wide management. In fact, many of Fedora's tools
in the system-config-* category, and their text-based counterparts
(*-tui) are going to be replaced sooner than later.
It seems, from what I've read, many of the distros are moving in this
direction. So while the existing tools, CLI and GUI are still useful,
and anyone wanting to clue-fully manage their system should know how and
when to use them, it is still a good idea to become familiar with the
newer mechanisms being developed, especially when they may soon replace
some their better-known legacy equivalents.
--
Best Regards,
~DJA.
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
