Joachim Wiberg
193a51af86
The previous fix, setting 'rm: false' to prevent the parallel builds from replacing each other, caused the latest tag to not be updated. Very confusing, not just to end-users, but also for devs. This patch changes the workflow to use a separate release step that runs in sequence, waiting for the build to finish, before it moves the latest tag. The trick to solving this is to use upload/download artifact. It is the recommended way of sharing files between independent jobs in a workflow. Notice the lack of 'name:' in both and 'path:' in the latter, it means "don't care" just upload and then download everything to the artifact/ directory. Making the job of the releaser action quite simple. Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
Infix is an embedded Linux Network Operating System (NOS) based on Buildroot, Finit, and ifupdown-ng.
Login with user 'root', no password by default on plain builds. See the online
helpcommand for an introduction to the system.
Hardware
aarch64
By default, Infix builds with support for the following boards (you may enable additional boards in the config, of course):
- Marvell CN9130 CRB
- Marvell EspressoBIN
- Microchip SparX-5i PCB135 (eMMC)
See the aarch64 specific documentation for more information.
amd64
Primarily intended to be run under QEMU for development & test as well as evaluation, demo and training purposes, e.g. using GNS3.
QEMU
A virtualized instance can easily be launched from a Linux system, with
Qemu installed, by issuing make run.
Some settings, e.g. networking, can be configured via make menuconfig
under External options -> QEMU virtualization.
GNS3
Download the latest build of amd64, unpack in a dedicated directory
and use "Import Appliance" to install the .gns3a file into GNS3.
Infix will show up in the "Router" category, it has 10 interfaces
available by default for use as switch ports or routing.