After this happened, my next step was to get re-involved in Debian Live to help it carry on after the loss of Daniel. Here’s a quick update on some team progress, notes that could help people building Stretch images right now, and what to expect next.
- Iain uploaded live-config, incorporating an important fix, #bc8914bc, that prevented images from booting.
- I want to get live-images ready for an upload, including #8f234605 to fix wrong config/bootloaders that prevented images from building.
Test build notes
- As always, build Stretch images with latest live-build from Sid (i.e. 5.x).
- Build Stretch images, not Sid, as there’s less of a chance of dependency issues spoiling the build, and that’s the default anyway.
- To make build iterations faster, make sure the config is modified to not build source & not include installer (edit auto/config before ‘lb config’) and use an apt caching proxy.
- Don’t forget to inject fixed packages (e.g. live-config) into each config. Use apt pinning as per live-manual, or drop the debs into config/packages.chroot.
Test boot notes
- Use kvm, giving it enough ram (-m 1024 works for me).
- For gnome-desktop and kde-desktop, use -vga qxl, or else the desktop will crash and restart repeatedly.
- When using qxl, edit boot params to add qxl.modeset=1 (workaround for #779515, which will be fixed in kernel >= 4.3).
- My gnome image test was spoiled by #802929. The mouse doesn’t work (pointer moves, but no buttons work). Waiting on a new kernel to fix this. This is a test environment related bug only, i.e. should work fine on hardware. (Test pending.)
- The Stretch standard, lxde-desktop, cinnamon-desktop, xfce-desktop, and gnome-desktop images all built and booted fine (except for the gnome issue noted above).
- The Stretch kde-desktop and mate-desktop images are next on my list to test, along with Jessie images.
- I’ve only tested on the standard and lxde-desktop images that if the installer is included, booting from the Install boot menu option starts the installer (i.e. didn’t do an actual install).
See the TODO in the wiki. We’re knocking these off steadily. It will be faster with more people helping (hint, hint).
I’ve been using this process for debugging the installer while launched from a Debian Live desktop. Having a full live environment at your disposal during install is a boon to debugging because you don’t have to work within the constraints normally imposed upon you by the limited debian-installer environment. Caveat: running debian-installer from the debian-installer-launcher still has one or two unresolved issues, so unless you’re specifically working on live integration issues like I am, compare with a conventional d-i image install to gain the added confidence the install is the same in both environments.
There are no longer active maintainers working on debian-installer-launcher and live-installer, and I think it’s really important for wheezy to release with solid support for live installs, so I’ve been using this setup to try to solve #702335. So far, progress is slow because I’m new to this. If anyone is interested in collaborating in this work, give me a shout. I am SynrG @ irc.oftc.net and can be found on #debian-live and #debian-boot if you would like to drop in.
- Use images/lxde-desktop config from live-images.git and build your own image with live-build >=3.0.1-1. Just add “-b hdd” in auto/config before starting your build, as having a read/writable image is handy for this exercise.
- Boot the live medium. You may prefer to do this in a VM for convenience, having prepared a blank virtual disk image as your target in advance.
- Make any small changes you want to the installer before launching it. A quick hack I’ve used is to “sudo vi /usr/sbin/debian-installer-launcher” and near the end on the line after “prepare” right before “run”, open a new line and add “bash” so an interactive shell will be opened after the installer is extracted but before it is launched. For larger changes (e.g. inclusion of updated udebs, etc.) add them to your live image configuration before building as described in live-manual.
- Open two root terminals and do “debian-installer-launcher -t debug” in one and “tail -f /lib/live/installer/var/log/syslog” in the other. If you’ve added the hack from step 3, don’t forget to “exit” the interactive shell after making changes. Now you can watch debug output as you go through the steps of the installer. If you like, you may append additional boot prompt parameters (e.g. preseeds) to the debian-installer-launcher command.
- During the install, you may modify other parts of the unpacked installer under /lib/live/installer (e.g. to add ‘set -x’ to some scripts) prior to executing steps that would call them.