"the passing of the years has done nothing to improve my temper"
if the default plan9.ini config on eg the usb drive doesn't work then you are going to have to get your hands dirty
9front kernel meets multiboot specifications, so a grub config is straightforward: # on bios/mbr menuentry "9front" --class os { set root=(hd0,msdos1) multiboot /9pc64 } in theory it should load plan9.ini from the same partition. i wanted to manually specify for peace of min. grub is a confounding piece of software so you can't use initrd command with multiboot software, so use module: menuentry "9front" --class os { set root=(hd0,msdos1) multiboot /9pc64 module /plan9.ini }
henesy recommends something diff, maybe this was written before multiboot implementation but copying it here for posterity just in case: # for uefi, gpt menuentry "9front" --class os { insmod part_gpt insmod search_fs_uuid insmod chain search --no-floppy --set=root --fs-uuid 1DA5-9F85 chainloader ($root)/boot/9frontx64.efi }
if things go wrong try enabling acpi or disabling vesa. eg: *acpi=1 if things go wrong with the above without error messages, congratulations: you have a learning opportunity.
if you get to the bootargs line, congrats. you have some options options tcp/tls/il try to mount a filesystem over the network. - it sets this up with ip/ipconfig - wifi is rumoured to work but requires configuration in plan9.ini - you can boot from an iso like: - local!/shr/sdUxxxxx/9front.iso - you have to figure out what those xs are supposed to be you can escape to a shell with !rc
license ∆ Tue Mar 23 18:17:17 EDT 2021