leahneukirchen/ignite

OBSOLETE: use Void Linux

ignite's Issues

Current state of development

Hi,

Have been messing with runit for a while and was thinking of bringing it too ArchBang as an alternative init system. Wondering what current state of development ignite is in and how much works. Basically need base + X and openbox window manager. Do you use systemds own udev or something else?

Mr Green

dnsmasq

#! /bin/sh
exec /usr/bin/dnsmasq -k --user=dnsmasq

shutdown -c doesn't remove /etc/nologin

Timed shutdown creates /etc/nologin. This file should probably be removed when shutdown is cancelled.

Allow service@blah?

Starting multiple instances of a daemon with different configs by running eg systemctl enable netcfg@wifi-uni is one of the nice things about systemd.

This is tricky to get working in ignite because of the requirement that it works on read only roots.

Possible implementation:

/etc/runit/2:

...

     case ${daemon:0:1} in
       !) ;;
       *)
         [[ $daemon =~ ([^@]+@)([^@]+) ]]
         if [ ${BASH_REMATCH[1]} ]; then
           cp -r /etc/sv/${BASH_REMATCH[1]} $d/$daemon
           ln -s /run/runit/supervise.$daemon $d/$daemon/supervise
           echo -n "${BASH_REMATCH[2]}" > $d/$daemon/config
         else
           ln -s /etc/sv/$daemon $d
         fi;;
     esac

...

Example daemon:
/etc/sv/tincd@/run:

#! /bin/sh
PROFILE=`cat config`
exec /usr/bin/tincd -D -n $PROFILE

This is inconsistent with the rest of ignite - no supervise in /etc/sv/..., creating actual files in /run instead of symlinks

prevent systemd predictable network names, use script name in eth0

Plain archlinux + packer + ignite-git installation has no left-over /etc/udev/rules.d/70-persistent-net.rules and >udev-201 starts renaming the links to enp2s8.

/etc/sv/eth0 has to be edited and renamed to make this work.

TODO: revert that behaviour to old style. I look into [1].

[1] http://us.generation-nt.com/answer/gentoo-dev-call-testers-udev-predictable-network-interface-names-help-210046042.html

Clash with halt,reboot,shutdownn ....

Currently ignites halt,reboot,shutdown,poweroff clash with installed versions. This means package will fail to install under you remove them. Wondering if systemd-sysvcompat needs to be removed? (or added as 'conflicts' in PKGBUILD)

provide rc.conf template / install README file

non-migrated systems lack rc.conf, and retrieving the README file from packer-tmp/website sucks.

Please install README to /usr/share/doc/... and backup+install /etc/rc.conf

static ip configuration

One can use dhcpcd to request and get a static ip.
A eth0-static service would be nice to do that.

I have a branch where I tested such a service and works fine.

This would mean that some variables would need to be configured on /etc/rc.conf.
I guess we'd need INTERFACE (or unconditionally eth0) ADDRESS NETMASK GATEWAY BROADCAST and NAMESERVER (?) for such a simple configuration.

---

If not dhcpcd, ip could be used to achieve a static ip configuration, like:

ip link set dev "$INTERFACE" up &&
ip addr add "${ADDRESS}/${NETMASK}" broadcast "$BROADCAST" dev "$INTERFACE" &&
ip route add default via "$GATEWAY"

ofcourse ip would exit once it's done its job, so it's not very suitable here,
but it can be used in /etc/rc.local (for anyone wanting this if this is rejected).

---

So, that's the idea. I am not sure it's worth it.
Configuring in /etc/rc.local should work fine too.