It doesn't make much sense to install initscripts in current distributions. Most
of them either don't use initscripts at all, locally patch the initscripts or
supply their own. This allows us to eventually drop the --with-distro configure
option.
Many current distributions support multiple init systems and it doesn't make
sense for upstream to make the choice for them. Distributors can still make
their scripts copy one of the initscripts from the source tree if they wish so.
* src/dhcp-manager/nm-dhcp-manager.c: Do not start dhcdbd, but rely on
the system init scripts (or some other mechanism) starting it (or a
compatible DBUS service) before NetworkManager runs. This means that
distributions might need to update their init scripts. This fixes
possible races and is quite a bit cleaner.
* initscript/SUSE/networkmanager.in: Update to start dhcdbd before
starting the NetworkManager daemon.
git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@1607 4912f4e0-d625-0410-9fb7-b9a5a253dbdc
* initscript/SUSE/networkmanager-dispatcher.in: new initscript for
NetworkManagerDispatcher.
* configure.in, initscript/SUSE/.cvsignore,
initscript/SUSE/Makefile.am: support new networkmanager-dispatcher
initscript.
git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@1149 4912f4e0-d625-0410-9fb7-b9a5a253dbdc
* initscript/Gentoo/NetworkManager:
* initscript/RedHat/NetworkManager:
* initscript/RedHat/NetworkManagerDispatcher:
* initscript/SUSE/networkmanager:
CVS remove these in place of .in replacements
* configure.in:
* initscript/Gentoo/NetworkManager.in:
* initscript/RedHat/NetworkManager.in:
* initscript/RedHat/NetworkManagerDispatcher.in:
* initscript/SUSE/networkmanager.in:
These scripts now are generated so they work still when
NM is built using a bindir other than /usr/bin
git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@880 4912f4e0-d625-0410-9fb7-b9a5a253dbdc
