Hi,

Quoting Samuel Thibault (2026-06-02 01:37:03)
> Johannes Schauer Marin Rodrigues, le lun. 01 juin 2026 10:26:13 +0200, a 
> ecrit:
> > I have not yet figured out how to auto-login the root user in GNU/Hurd. The
> > agetty line which works on Linux errors out with "getty[585]: Bad syntax" 
> > and
> > according to Samuel Thibault it may just be that this feature isn't 
> > implemented
> > yet in hurd.
> 
> Do you know the syntax that is used for that? It can as well just be
> implemented.

this is what debvm does for sysvinit:

https://salsa.debian.org/helmutg/debvm/-/blob/main/share/debvm/customize-autologin.sh?ref_type=heads#L64

C0:2345:respawn:/sbin/getty -8 --noclear --keep-baud -a root console 
115200,38400,9600 $TERM

The magic switch to getty is -a or --autologin which automatically logs in the
given user (in this case, root). When I try that on Hurd I get:

getty[621]: Bad syntax

> > I also do not yet know how to set up networking inside the QEMU guest. The
> > /etc/network/interfaces which works on Linux does not seem to give me any
> > network inside the Hurd QEMU guest.
> 
> It should be working.
> 
> Which kind of configuration are you using?

This is the /etc/network/interfaces that debvm creates:

https://salsa.debian.org/helmutg/debvm/-/blob/main/share/debvm/customize-ifupdown.sh?ref_type=heads#L15

auto /enp*=eth
iface eth inet dhcp

> The inet dhcp method should
> be just working. The static configuration probably needs to make sure
> that /servers/socket/2 is translated as
> 
> /hurd/pfinet -i /dev/eth0 -6 /servers/socket/26
> 
> and /servers/socket/26 as
> 
> /hurd/pfinet -i /dev/eth0 -4 /servers/socket/2
> 
> as I guess ifupdown hasn't yet bet taught to do it.

These translators exist because mmdebstrap created them:

https://gitlab.mister-muffin.de/josch/mmdebstrap/src/branch/main/mmdebstrap#L1107

What else could I investigate to debug whit is going on? For example in Linux
I can just run "ip link" to check which devices are even there. What do I do
on GNU/Hurd?

Thanks!

cheers, josch

Attachment: signature.asc
Description: signature

Reply via email to