slackbuilds_ponce/network/NetworkManager
Robby Workman 3a608519b6 network/NetworkManager: Hackery to set static hostname
Problem reported by Fırat Birlik on the NM mailing list:
http://mail.gnome.org/archives/networkmanager-list/2010-June/msg00105.html

Signed-off-by: Robby Workman <rworkman@slackbuilds.org>
2010-06-22 05:59:12 -05:00
..
doinst.sh network/NetworkManager: Hackery to set static hostname 2010-06-22 05:59:12 -05:00
fi.epitest.hostap.WPASupplicant.service network/NetworkManager: Fixed path to wpa_supp in dbus service file 2010-06-13 20:59:01 -05:00
NetworkManager.info
NetworkManager.SlackBuild network/NetworkManager: Hackery to set static hostname 2010-06-22 05:59:12 -05:00
nm-system-settings.conf.new network/NetworkManager: Hackery to set static hostname 2010-06-22 05:59:12 -05:00
README
slack-desc

NetworkManager attempts to keep an active network connection available at all
times.  The point of NetworkManager is to make networking configuration and
setup as painless and automatic as possible.  NetworkManager is intended to
replace default route, replace other routes, set IP addresses, and in general
configure networking as NM sees fit (with the possibility of manual override as
necessary).  In effect, the goal of NetworkManager is to make networking Just
Work with a minimum of user hassle, but still allow customization and a high
level of manual network control.

You will probably want to install network-manager-applet (for a configuration
UI) for sure, along with ModemManager (if you want support for configuring
broadband modem connections) perhaps one or more of the VPN-related addons.