Every package now has or generates a rootfs_files.txt containing a list
of files that should be packed into the rootfs, their permissions and
their owner.
This gives us fine grained controll over the owners and permissions of the
rootfs files (by generating a squashfs pseudo file).
In subsequent steps, this allows us to remove the deploy/devdeploy split and
actually simplifiy most of the build scripts.
Signed-off-by: David Oberhollenzer <david.oberhollenzer@tele2.at>
Make sure dhcpcd does not interfere with resolv.conf. For the router
product we have a dnsmasq running that forwards to a local root
resolver (i.e. unbound).
For the ALIX board, we want to run a DHCP client on one port and a
DHCP server on the other two.
Signed-off-by: David Oberhollenzer <david.oberhollenzer@tele2.at>
- Move root.key into /etc/unbound directory
- Remove pid file from config, it is baked into the configure options
- Make sure unbound does not try to chroot anywhere
Signed-off-by: David Oberhollenzer <david.oberhollenzer@tele2.at>
When "libdir" is not the final path where we install the library,
libtool will mess up the relinking process and prepend the global
library directories to the linker search path.
If we fix the libdir path, libtool will insert it into the rpath
in the binary, which is also pretty bonkers.
Maybe, there is a way to do this correctly, but the various GNU
mailing lists, Debian wiki, etc.. could not provide a better
alternative than patching up libtool scripts.
Signed-off-by: David Oberhollenzer <david.oberhollenzer@tele2.at>
- Remove extra back slash
- The good old "install uses build systems strip tool and it doesn't know
what to do with ARM binaries"
Signed-off-by: David Oberhollenzer <david.oberhollenzer@tele2.at>
If we tell bash to used the installed readline library, it defaults
to adding -L/lib for the readline and history library prefixes.
This prepends the local systems search path to the toolchain search
path and makes bash build break on some systems.
Signed-off-by: David Oberhollenzer <david.oberhollenzer@tele2.at>
The simplification of the overide behaviour may be worth the slight
duplication overhead.
Signed-off-by: David Oberhollenzer <david.oberhollenzer@tele2.at>
Crunch project websites and try to find the latest version for each
package without having to do the work manually.
Signed-off-by: David Oberhollenzer <david.oberhollenzer@tele2.at>
First of all, fix the dependency name in the per-interface service file.
Second, we allow the master services daemonize itself and change the target
to wait. This way, we block init until we are sure the dhcpcd master
is running. Otherwise we have a race condition if init gets scheduled
for some reason and immediately starts the dhcpcd interface daemon that
cannot see the master and decides that *it* is the msater now.
Signed-off-by: David Oberhollenzer <david.oberhollenzer@tele2.at>
- board configuration does not configure network interfaces,
only handles renaming
- router product for Raspberry Pi 3 configures DHCP for ethernet port
- router product for Alix board configures DHCP for third ethernet port,
static addresses for the other two
Signed-off-by: David Oberhollenzer <david.oberhollenzer@tele2.at>
- Service file for dhcpcd master service
- Service template file for interfaces
- Service symlink for each configured interface
- Get DHCP address on raspberry pi 3 for ethernet port
Signed-off-by: David Oberhollenzer <david.oberhollenzer@tele2.at>
