Building systems: the automated way¶
Building and testing your own systems based on
haskus-system requires quite
a few steps: configuring and building a Linux kernel, etc.
Hopefully we have built a tool called
haskus-system-build that performs all
these steps automatically (details are explained in the next chapter if you want
to understand what it does internally).
Prerequisite: you need to have Stack and
The tool is distributed in the
To install the latest version, use:
> git clone https://github.com/haskus/haskus-system.git > cd haskus-system > stack install haskus-system-build
It will install the program into
~/.local/bin. Be sure to add this path to
$PATH environment variable.
You can also install it from Hackage using Stack or cabal-install.
To start a new project, enter a new directory and use the
> mkdir my-project > cd my-project > haskus-system-build init
It downloads the default system template into the current directory. It is composed of 4 files:
> find . -type f ./stack.yaml ./src/Main.hs ./my-system.cabal ./system.yaml
src/Main.hsis the system code
my-system.cabalis the package configuration file that has been tweaked to build valid executables (use static linking, etc.)
stack.yamlis Stack configuration file with the required dependencies on Haskus packages
haskus-system-buildconfiguration file. Let’s look into it:
linux: source: tarball version: 4.11.3 options: enable: - CONFIG_DRM_BOCHS - CONFIG_DRM_RADEON - CONFIG_DRM_NOUVEAU make-args: "-j8" ramdisk: init: my-system qemu: # Select a set of options for QEMU: # "default": enable recommended options # "vanilla": only use required settings to make tests work profile: vanilla options: "" kernel-args: ""
As you can see, it contains a Linux kernel configuration, a reference to our system as being the ramdisk “init” program and some QEMU configuration.
Building and Testing¶
You need to have some programs installed before we continue:
- everything required to build Linux: make, gcc, binutils…
- static libraries (e.g., glibc-static and zlib-static packages on Fedora)
- (un)packing tools: lzip, gzip, tar, cpio
Now let’s try our system with QEMU!
> haskus-system-build test
On the first execution, this command downloads and builds everything required to test the system so it can take quite some time. Then QEMU’s window should pop up with our system running in it.
On following executions building is much faster because the tool reuses previously built artefacts if the configuration hasn’t changed.
Distributing and testing on real computers¶
If you want to distribute your system, the easiest way is to install it on an empty storage device (e.g., usb stick).
Warning: data on the device will be lost! Don’t do that if you don’t know what you are doing!
To install your system on the device whose device file is
> haskus-system-build make-device --device /dev/sde
Note that you have to be in the sudoers list.
Another distribution method is to create an ISO image that you can distribute online or burn on CD/DVD.
> haskus-system-build make-iso ... ISO image: .system-work/iso/my-system.iso
Note that you can test the ISO image with QEMU before you ship it:
> haskus-system-build test-iso
This allows you to test the boot-loader configuration.