CROSSHURD-IMAGE(8)
πΎ crosshurd-image(8) β bestie edition
okay so real talk: crosshurd-image is a script (manual page CROSSHURD-IMAGE(8), in case you were wondering where you are) that β¨createsβ¨ a bootable disk image file with a crosshurd setup. That's it, that's the whole vibe. Read on, babe. π«Ά
πΈ NAME πΈ
crosshurd-image β make a bootable disk image file with a crosshurd setup π
β¨ SYNOPSIS β¨
crosshurd-image [option_*]
π¦ DESCRIPTION π¦
The script crosshurd-image creates a bootable disk image file with a crosshurd setup. Iconic behavior, no notes. You can legit use it as the primary disk for a virtual machine, like, say, with qemu-system-x86_64. Main character disk energy fr fr. π
π OPTIONS π
--disk=filenameβ bestie, use filename for the disk image file instead of the defaultbase.img. Name your child whatever you want π--size=numberβ make the disk image file be number of GiB instead of the default40. Bigger disk = bigger slay.--name=hostnameβ set up the filesystem with hostname instead of the defaulthurd-test. This name gets written into both/etc/hostsand/etc/hostnamein the created filesystem. It's giving real identity. πͺͺ--ip=address/bitsβ use address (ipv4) and bits (the network part bits size) instead of the default192.168.240.2/24. Networking era π--gw=addressβ use this ipv4 address as the gateway instead of the default192.168.240.1. The gateway, the moment, the icon.--cpu=typeβ pick the cpu type forcrosshurd, likei386instead of the defaultx86_64. Choose your fighter βοΈ--extlinuxβ useextlinuxboot equipment instead of the defaultgrub. Different bootloader, same destiny.--mb=fileβ choose which multiboot definition file to use instead of the default/usr/share/crosshurd-image/servers.boot. Custom menu, custom meal π
π NOTES π
crosshurd-image runs through a straight-forward sequence of steps, and here's the whole choreography:
- create a blank disk image file, partitioned in a DOS table with a single partition, and formatted for GNU Hurd (
ext2fs -o hurd) - use
crosshurdfor stage-1 setup of the GNU Hurd Debian filesystem - add a bootloader (
syslinuxorgrub) to the disk image file with stage 1 boot loader, and multiboot configuration for GNU Hurd core modules - finalize setup with hostname and networking setup
The disk image file is then ready to be used as the primary disk for a virtual machine with legacy bios boot. Periodt. π₯
β οΈ heads up bestie: the disk image file is created as a "holes" file, where only data blocks actually in use have been allocated in the filesystem. So the actual size initially is smaller than what, say, ls -l reports. Not a bug, just mysterious. π
π§ MULTIBOOT DEFINITION FORMAT π§
The multiboot definition file is a grub multiboot snippet. The first line constitutes the parameters for the multiboot tag, and the lines following constitute subsequent module declarations separated by blank lines. This snippet will be included verbatim (except for comments and blank lines) for the grub boot option, whereas it will be translated into the syslinux parameter format for its mboot module for the extlinux boot option.
The latter is essentially the same format, except:
- the
modulekeyword for grub is replaced withmboot's module separator tag"---" - arguments are stripped of their surrounding single-quotes
- the line breaks are replaced by spacing, since the
mbootarguments need to be on a single line
Same energy, different syntax. Translating is an art form bestie. π
π AUTHOR π
Ralph Ronnquist <rrq@rrq.au>
πΈ that's the whole page, love you, bye πΈ β this cutie was brought to you by the crosshurd-image(8) source, version dated 2026-03-15. go build that disk image, bestie, you're gonna ate πβ¨ππ¦
π¦ where this page comes from
- ubuntu stonking: crosshurd-image 1.7.66
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms