The return of the son of the demo CD
2009-June: This document is now obsolete. We are in the process of consolidating and re-organizing the website documentation. For now please refer to one of these guides. Alternatively, you can view the in-progress website documentation.
As everyone knows (or should), every BeOS install CD was actually a live CD (way before Linux “invented” it…). And of course so would be for Haiku.
While it used to work long ago, nobody actually tried to make one for some time, and some fixes were required to make it happen again. Making an usable CD still requires some work (Bootscript.cd, ramdisk for settings maybe…), but it finally boots again.
One of the problems was a kernel argument that was passed as int32 and checked for as bool, obviously missing the int32 value. The FloppyBootImage jam file I wrote also lacked the scsi_cd driver in the list of boot modules to be put into the gzipped tarball that goes on the floppy image. Since I used a copy-paste from the NetBootImage file I overlooked this.
It’s still a bit early to distribute demo CDs, but just so you know when the time comes, let’s see how to make one.
Creating a bootable CD requires burning 2 tracks on a single CD. The first track is an El-Torito bootable ISO-9660 file-system containing a boot floppy image, and is created with:
jam -q haiku-boot-cd
This generates an image file named ‘haiku-boot-cd.iso’ in your output directory under ‘generated/’. The second track is the raw BFS image ‘haiku.image’ in ‘generated/’ created with:
jam -q haiku-image
Under Unix/Linux, and BeOS you can use cdrecord to create a CD with:
cdrecord dev=x,y,z -v -eject -dao -data generated/haiku-boot-cd.iso generated/haiku.image
Where x,y,z is the device number of your cd burner (get it with
Windows users might have a look at the .cue files around used for BeOS distros, they should work as well for Haiku.
- Haiku monthly activity report - 08/2019
- GSOC 2019 Final Report
- Haiku Activity Report: Performance Edition
- new PVS studio scan
- Coding week 4,5,6
- [GSoc 2019] Weeks #4, #5 and #6 progress report
- Haiku monthly activity report - 06/2019
- Coding week no 2 and 3
- [GSoC 2019] Weeks #1, #2 and #3 progress reports
- Haiku monthly activity report, May 2019