LilyDevOS

This repository, named LilyDevOS, is the replacement of LilyDev. Even if the final product will still be called LilyDev, this is the place where the images will be created from now on.

Two different options are provided: a full VM image for all operating systems and lightweight containers (currently based on Fedora and Debian) which can be run only on Linux hosts.

Full virtual machine

Runs on: any OS with a Virtual Machine software.

Download the latest release. The image built for being emulated on VM software has a -vm suffix.

You must first decompress the zip archive. Then you can verify the integrity of the data comparing the hash in the SHA256SUMS file with the output of this command (in Linux):

sha256sum lilydevos-vm-VERSION.raw

In Linux you can test it quickly by using something like this (tested on Fedora.. the location of OVMF_CODE.fd might be different in other distros):

qemu-kvm -m 512 -smp 2 -bios /usr/share/edk2/ovmf/OVMF_CODE.fd -drive format=raw,file=lilydevos-vm-VERSION.raw

512M of RAM should be enough, as the image contains also a swap partition of 2G. If you can assign 1024M, even better. In case you see some weird error while compiling lilypond, your guest might be running out of memory (check the RAM available with the command free -m) and you should try assigning more RAM to the virtual machine.

Once you are sure about the suitable settings, you'd better register the virtual machine in libvirt or, in libvirt terms, define a domain. Enter the directory where you saved the .raw file and launch this command:

virt-install --name lilydevos-vm-VERSION --memory 1024 --os-type=linux \
--os-variant=fedora25 --boot loader=/usr/share/edk2/ovmf/OVMF_CODE.fd \
--network=default --disk /FULL/PATH/TO/lilydevos-vm-VERSION.raw \
--noautoconsole --import

(available OS variants are listed by the command osinfo-query os)

Now the virtual machine will be available on all libvirt clients, such as virt-manager or GNOME Boxes. If you still want to launch it from command-line, use these commands:

virsh start lilydevos-vm-VERSION
virt-viewer --connect qemu:///session lilydevos-vm-VERSION

You'll log in as dev user (the password is lilypond).

Desktop preferences suggestions:

• Disable the screensaver: click on the menu icon on the bottom left, then on Preferences»Monitor settings; in the Mode dropdown menu choose Disable Screen Saver.

• Change keybord layout from default US (american) to your national layout in Preferences»Keyboard and Mouse»Keyboard Layout; add your layout and then move it up to the list so it will be the default.

Container

Runs on: Linux only. Requirements: systemd-nspawn, available in systemd-container package.

It's the best choice if you want to run LilyDevOS in a Linux host: lightweight, full access to host system resource (including RAM), easy access from host to guest file system through the file manager (so no need to set up shared folders).

Download the latest release. You need root privileges to extract the content, so you'd better do it on the command line:

sudo tar xf lilydevos-VERSION.tar.xz

Start the container:

sudo systemd-nspawn -bD lilydevos-VERSION

At the login type root and press Enter (no password needed). Then change to the regular user dev, go to the home directory and run the setup.sh script:

su dev
cd
./setup.sh    # this should be run only the first time

You are now ready to start contributing to LilyPond.

When you've done, you can shutdown the machine with these commands:

$ exit
# shutdown -h now

(the first command will let you go back from dev user to root user, who has the privileges to shutdown the system)

Remember that dev user can get root privileges with sudo (even if you should not need it). The password is lilypond.

There's a good chance that your user in the Linux host and the dev user in the container have the same uid (probably 1000, use the command id to find it out). If that's the case, you can easily access and edit the files in the container from your host as you wish, using a file manager or your favorite GUI text editor. In case the id is different, read this tutorial on changing UID and GID.

Running graphical applications from the container

You might need to run one or more graphical applications from the container, for example gitk or lily-git. This should work out of the box, if two requirements are met:

1. The id of the guest user must the same as the id of the host user. Usually it is, as you should have 1000, the id assigned to the first normal user.
2. Another requirement is that the DISPLAY variable must be set to the same value of the DISPLAY value in the host. We assumed that the value is :0. If it's not, run echo $DISPLAY in the host and change accordingly the DISPLAY variable in ~/.bashrc in the guest.

The containers does not include a browser, which is needed to log in to Rietveld while uploading the patch via git-cl. Unfortunately I could not find any text browser which worked with git-cl. As installing a graphical browser would add several dependencies and I want to keep the container as small as possible, the best solution is launching git-cl from the host. Otherwise you may install a browser in the container, e.g.:

sudo dnf install firefox      # Fedora
sudo aptitude install firefox # Debian