Recently i've done several improvements in the sources of simple-netaid and i would like to share with you a brief tutorial explaining how to build it from source. The procedure has been tested in Void Linux and Slackware, but i had trouble running ifupdown in the later. Bear in mind that ifupdown is debian specific, though it's also used in a few independent distributions like Void and Alpine Linux. I still didn't try to build simple-netaid in Alpine, hence i'll specify the build dependencies only for devuan and void.

In de{bi,vu}an you can install them via apt:

# apt-get install git-core build-essential pkg-config autoconf automake libtool intltool libiw-dev libcdk5-dev \
gettext libjson-c-dev libprocps-dev libsigc++-2.0-dev libncurses-dev libvte-2.91-dev libgtk-3-dev

In Void the packages can be installed using the xbps package manager:

# xbps-install git base-devel pkgconf autoconf automake libtool intltool gettext-devel json-c-devel \
procps-ng-devel libsigc++-devel ncurses-devel vte-3-devel gtk+3-devel

Both libiw-dev (i.e. wireless-tools) and cdk5 are missing in the void repo, and we'll need to build them from source. In summary, we're going to build the projects below:

• libpstat

• libubox

• ubus

• wireless-tools (only in Void)

• libnetaid

• snetaid

• cdk5 (only in Void)

• simple-netaid-cdk

• simple-netaid-vte3 (optional)

- Installing LIBPSTAT

Developed by Jude Nelson, libpstat is a small library for getting information on running processes in an OS-agnostic way. The source is available in his git repository, but i added a few extras to suit the needs of simple-netaid. Build it as follows:

$ git clone https://git.devuan.org/aitor_czr/libpstat.git
$ cd libpstat
$ make OS=LINUX

Now install it as root:

# make install PREFIX=/usr/local

- Installing LIBUBOX

This consists of a set of utilities, mostly wrappers, that are used by many OpenWrt projects. In this case, it's present in Ubus. The original code (developed by Felix Fietkau) uses the cmake build system, but i replaced it with gnu make:

$ git clone https://git.devuan.org/aitor_czr/libubox.git
$ cd libubox
$ make

As root:

# make install PREFIX=/usr/local

- Installing UBUS

Ubus is a system level micro bus architecture basically consistent with DBus. Again, i replaced cmake with the gnu autotools build system (instead of make in this case, because ubus is daemonized and the autotools provide configuration flags suitable for the different scenarios the end user may face depending on the installed init system).

To build the sources you'll have to export the PKG_CONFIG_PATH variable in order to find the libubox library. In Void:

$ export PKG_CONFIG_PATH=${PKG_CONFIG_PATH}:/usr/local/lib/pkgconfig

In devuan:

$ export PKG_CONFIG_PATH=${PKG_CONFIG_PATH}:/usr/local/lib/$(dpkg-architecture -qDEB_HOST_MULTIARCH)/pkgconfig

Download and build the source:

$ git clone https://git.devuan.org/aitor_czr/libubus.git
$ cd libubus
$ autoreconf -i -f

At this point, in devuan with sysvinit run the following command:

$ ./configure --prefix=/usr/local --disable-runit
$ make

In Void with runit:

$ ./configure --prefix=/usr/local --disable-sysvinit
$ make

You can now install ubus:

# make install

You'll face "libtool: warning: remember to run 'libtool --finish /usr/local/lib'" warning because libtool complains that the prefix specified in the during the make phase is different from the one you have when you run make install. But it's a harmless warning and you don't need to do anything.

- Installing WIRELESS-TOOLS (Only in VOID LINUX)

You can download it from the Hewlett Packard repo:

$ git clone https://github.com/HewlettPackard/wireless-tools.git
$ cd wireless-tools/wireless_tools
$ make

As root:

# make install

- Installing LIBNETAID

This library consists of some C bindings for the high level ifupdown network manager. Download and build it as follows:

$ git clone https://git.devuan.org/aitor_czr/libnetaid.git
$ cd libnetaid
$ make

As root:

#make install

- Installing SNETAID

Configuration daemon for simple-netaid. For the same reason than Ubus, it uses the gnu autotools build system:

$ git clone https://git.devuan.org/aitor_czr/snetaid.git
$ cd snetaid
$ autoreconf -i -f

In devuan with sysvinit:

$ ./configure --prefix=/usr/local --disable-runit
$ make

In Void with runit:

$ ./configure --prefix=/usr/local --disable-sysvinit
$ make

You can now install snetaid:

# make install

- Configuring snetaid

Once the installation of snetaid completes, you need to create your user account. First of all create a new group named snetaid and add yourself to the group:

# groupadd netaid
# usermod -aG netaid $USER

Now issue the ldconfig command before starting the installed daemon (in some systems -e.g. Slackware- you may need to add the line /usr/local/lib to your /etc/ld.so.conf):

# ldconfig

After that, you'll be able to start snetaid. In devuan with sysvinit:

# service snetaid start

In Void with runit:

# sv start snetaid

At this point, i recommend you to reboot the system other than restarting the daemons to ensure that both ubus and snetaid start automatically without issues during the boot process. If everything went as spected, the output of ubus -v list should look similar to this:

$ ubus -v list
'ering.netaid' @0dc00e91
    "interface_down":{"id":"Integer","ifname":"String"}
    "interface_up":{"id":"Integer","ifname":"String"}
    "ifdown":{"id":"Integer","ifname":"String","tty":"Integer"}
    "ifup":{"id":"Integer","ifname":"String","tty":"Integer"}
    "ipaddr_flush":{"id":"Integer","ifname":"String"}
    "wpa_passphrase":{"id":"Integer","essid":"String","passwd":"String","filename":"String"}
    "wpa_supplicant":{"id":"Integer","ifname":"String","filename":"String","tty":"Integer"}
    "uninstall":{"id":"Integer","filename":"String"}
    "scan_active_wifis":{"id":"Integer","ifname":"String"}

- Installing CDK5 (Only in VOID LINUX)

Download the source from debian and build it:

$ git clone https://salsa.debian.org/debian/libcdk5.git
$ cd libcdk5
$ ./configure
$ make

This should go quickly. Once it's built, install it as root:

# make install

- Installing SIMPLE-NETAID-CDK

This is a curses interface for simple-netaid. Build it with make:

$ git clone https://git.devuan.org/aitor_czr/simple-netaid-cdk.git
$ cd simple-netaid-cdk
$ make

And install it as root:

# make install PREFIX=/usr/local

- Installing SIMPLE-NETAID-VTE3

This is an optional Gtk container for the curses interface of simple-netaid. Build it with make in thje same way as the earlier:

$ git clone https://git.devuan.org/aitor_czr/simple-netaid-vte3.git
$ cd simple-netaid-vte3
$ make

And install it as root:

# make install PREFIX=/usr/local

The launcher should appear in the menu right now.

- Final steps

The last step is to install some runtime dependencies and configure ifupdown. In devuan:

# apt-get install ifupdown wpa-supplicant isc-dhcp-client lsb-base

In Void:

# xbps-install ifupdown wpa_supplicant dhcpcd

Void Linux uses NetworkManager by default, but it's highly recommended to disable it when using ifupdown. You can type:

# touch /etc/sv/NetworkManager/down

to prevent the runit from starting NetworkManager on boot.

Finally, add the following lines to the file /etc/network/interfaces, which has been installed together with ifupdown:

auto lo
iface lo inet loopback

iface <wired_device> inet dhcp
iface <wireless_device> inet dhcp

Note: I suggest to by-pass stanzas like auto and allow-hotplug in the configuration of ifupdown, because they may delay the boot process. The master branch of simple netaid will react to the plug-in events of the ethernet cable without the need of any other standalone application like ifplugd or netplug. Therefore, the system will be automatically connected to the network no matter whether or not the cable was plugged in during the boot process, as long as the interface is up when the event occurs.

This is the first I have heard of gnuinos being mentioned in distrowatch.

Remove the folder /var/lib/dkms/snd_hda_codec_cs8409 and reinstall the headers:

$ sudo apt-get --reinstall install linux-headers-5.19.0-0

On the other hand, are you getting random noise with:

$ aplay /dev/urandom -f dat -D hw:1,0

or any other card,device pair?

Files located at /usr/src/snd_hda_codec_cs8409-1.0/ are copied to /var/lib/dkms/snd_hda_codec_cs8409/1.0/source/ where the build process is carried out.
I guess that you forgot to edit dkms.conf in /usr/src/snd...

The following command sends ramdom noise output to hw:0,0 (i.e. :<card>,<device>)

$ aplay /dev/urandom -f dat -D hw:0,0
Playing raw data '/dev/urandom' : Signed 16 bit Little Endian, Rate 48000 Hz, Stereo
^CAborted by signal Interrupción...

No, no... You don't have to run this code. Make will do, because it's part of the Makefile. The recipes concerning to the install target. However, you can leave the Makefile as is, and use modprobe and lsmod without underscores:

# modprobe snd-hda-codec-cs8409
$ lsmod | grep snd-hda-codec-cs8409

But then you have to create an alias by adding the line:

alias snd-hda-codec-cs8409 snd_hda_codec_cs8409

to the modprobes.alias of the running kernel, located in /lib/modules/${kernel_version}/, as I explained previously.

I'm referring to this:

I mean, using hyphens in the module name, it's not listed by lsmod

Yes, they are! I've found some of them. So, I'll write the definitive howto in a few minutes...

This morning I've built it successfully, but now I'm getting the same error than you. The problem is that, testing one of my installers, I formatted the disk where the installation succeded. However, I'm pretty sure that this mess comes from the use of underscores instead of hyphens in the module name. Though I see all the drivers using underscores in /lib/modules, this one is generated as snd-hda-codec-cs8409.ko. You can see this fact in the Makefile, but I'm not sure whether or not hyphens are allowed for kernel module names.

Give me some time, and I'll update my how-to.

Yes.

As a result:

BUILT_MODULE_LOCATION=./    ==>    absolute_dir = /usr/src/snd_hda_codec_cs8409-1.0/ + relative_dir (= ./)

where the Makefile is found, that is:

path_to_the_makefile     ==>       absolute_dir/Makefile = /usr/src/snd_hda_codec_cs8409-1.0/Makefile

All this is right, and the origin of the issue is another one.

Huh? It's the parent directory

Nope. The location is right. This variable is not an absolute path (note that it hasn't a forward slash at the beginning), but a relative path (relative to /usr/src/snd_hda_codec_cs8409-1.0/ where the tarball has been uncompressed). And it's the path to the Makefile, which is located in the parent directory.

In some cases, for example, you can find the Makefile in

/usr/src/<name>-<version>/src/Makefile

Hence, the variable would be BUILT_MODULE_LOCATION=./src

If I'm not mistaken