[SOLVED] Using connman with Slackware 14.1

jgrim · 04-22-2014, 05:03 PM

I am trying to use Connman instead of Network Manager in Slackware 14.1. I've downloaded, compiled and installed connman 1.23 from source, but now I am uncertain how to make it start with init. Is it enough to add "su /usr/sbin/connmand" to rc.local, or should I edit the appropriate rc.<runlevel> scripts to start/stop the thing?

The documentation for Connman is a bit light and everything I've read so far has to do with starting it with systemd, not init.

Anyone running this way that can provide some insight?

Didier Spaier · 04-22-2014, 05:11 PM

willysr has provided all that's needed to make and install a connman Slackware package here.

Oh, and if you intend to use Slackware, making Slackware packages instead of manually compiling and installing the software eases maintenance by large.

jgrim · 04-22-2014, 06:57 PM

Thanks Didier, I'll give that package a try this evening.

One of the reasons that I enjoy using Slackware is that package management is minimal. I like learning and knowing what is going on under the hood. I will probably take willysr's package apart to see what it does and then do those things myself.

I'll be interested to see if he had to add "-lncurses" to make it compile.

genss · 04-23-2014, 03:15 AM

Quote:

Originally Posted by jgrim

..or should I edit the appropriate rc.<runlevel> scripts to start/stop the thing?

yes

i added to Willy's script, to the "stop" function

Code:

connmand_stop() {
  killall connmand 2> /dev/null
  killall wpa_supplicant 2> /dev/null
  killall connman-vpnd 2> /dev/null
}

Didier Spaier · 04-23-2014, 04:03 AM

Quote:

Originally Posted by jgrim

[...] or should I edit the appropriate rc.<runlevel> scripts to start/stop the thing?

No. the /etc/rc.d/rc.<numbered_runlevel> structure is not used by Slackware per se as stated in /etc/rc.d/init.d/README.fuctions :

Code:

If you're reading this in /etc/init.d/, Slackware's real init directory is
/etc/rc.d/.  Maybe you already knew this, but it never hurts to say.  :-)

This script was taken from Fedora (and is presumably licensed under the GPL).
While I don't see Slackware init scripts making much use of it (but use it
if you wish), some third party init scripts (such as for commercial software
designed to run on Red Hat based systems) expect this script and use it in
their own init scripts, so it's a good idea to make it available here.

These functions are provided solely for commercial (or other) software that
expects to find "Red Hat-isms".  I wouldn't use them to write new init
scripts (personally), but if you've had experience with them in the past
and like them, by all means feel free.

It's planned to continue support for them.

genss · 04-23-2014, 04:16 AM

i should read better
thx Didier

willysr · 04-23-2014, 05:09 AM

I think i already mention it on the README

Quote:

You must give execute permission on /etc/rc.d/rc.connmand and run
/etc/rc.d/rc.connmand start before you can use this application

To make this process repeated on every boot sequence, add this line
in your /etc/rc.d/rc.local:

if [ -x /etc/rc.d/rc.connmand ]; then
/etc/rc.d/rc.connmand start
fi

jgrim · 04-23-2014, 10:19 AM

Fixed!

Thanks Didier for the guidance and willysr for the excellent SlackkBuild package!

Is it just me or do most people who use connman also use Enlightenment and eConnman? That's the only reason I wanted it.

bamunds · 04-23-2014, 10:50 AM

When I run enlightenment window manager on my Slack 14.1 x86_64 I use the slacke17 package (available from sourceforge.com), which has the connman removed. Then I add the systray module and already available in Slackware nm-applet to show in the systray. That way I don't have to struggle with building connman, which is reported as unstable by the slacke17 maintainer. Additionally, by using network manager and nm-applet there is consistency across the window managers that I alternate between. I find my Slackware is more stable and consistent if I only use slackpkg or sbopkg as my application packages and not try to build packages as a newbie.