Bruno Haible <[email protected]> writes:
> Collin Funk wrote:
>> If you reboot you
>> will be prompted to 'fsck' in a recovery shell. But that never works
>
> Huh? For me, that usually works. When I get tired of pressing 'y',
> I press 'a', and the rest is automatic.
>
> Here are my current installation notes:
>
> Download:
> https://cdimage.debian.org/cdimage/ports/latest/hurd-amd64/debian-hurd-amd64-20250807.img.tar.xz
> -> debian-hurd-amd64-20250807.img.tar.xz
>
> README is at
> https://lists.gnu.org/archive/html/bug-hurd/2025-08/msg00008.html
> https://cdimage.debian.org/cdimage/ports/latest/hurd-amd64/YES_REALLY_README.txt
>
> $ VBoxManage convertfromraw os-install-media/debian-hurd-amd64-20250807.img
> virtualbox/Hurd-2025-64/hurd.vmdk --format vmdk
> Tools > Virtual Media Manager > Add.
> Choose this disk as IDE disk.
>
> Fix reboot loop:
> $ VBoxManage modifyvm Hurd-2025-64 --hpet=on
>
> login: root
>
> Setting the time zone:
> Cf. https://bugs.openjdk.org/browse/JDK-8345213
> # dpkg-reconfigure tzdata
>
> # adduser --shell /bin/bash USERNAME
> login: USERNAME
> password: PASSWORD
> # vi /etc/group
> Add USERNAME to the line 'sudo'.
>
> Can't ssh to 10.0.2.2 (neither with NAT nor with Bridged networking).
> # vi /etc/hosts
> Add line with the host's real IPv4 address.
Thanks, it is probably a user error if it works for you. That is good
news to me.
When testing Hurd I would use the following, which was copied from the
README, outside of s/kvm/qemu-system-x86_64 -enable-kvm/ since the 'kvm'
program seems to be a Debian thing:
$ qemu-system-x86_64 -enable-kvm -M q35 -m 2G \
-drive file=$(echo debian-hurd*.img),cache=writeback \
-net user,hostfwd=tcp:127.0.0.1:2222-:22 -net nic,model=e1000
I'll see if VirtualBox works better for me.
Collin