Hello, Sergey Bugaev, le mer. 14 juin 2023 15:12:22 +0300, a ecrit: > Unfortunately the released installation ISO is very broken :( , which > spoils the whole thing. > > Once you install it and try to boot for the first time, you are greeted > with a wall of errors about /dev//tty1
?? I'm not getting such a result at all of course. How did you run the installation *exactly*? As a reminder, the really recommended way to avoid issues is to just run the pre-installed image inside qemu (and README files are actually meant to be read). > I've seen people on a certain online forum report this, > and draw a rather negative conclusion about the state of the Hurd. As usual, we see a lot of people grumble about things, much less people actually report things, and even less people actually have a look at fixing things... And most people just forgetting that it's just the same with *any* OS that doesn't have a huge testing team. Any departure from what is actually tested will get issues, very obviously. One just can't test the whole world of virtualfoo etc. > # ls /dev/tty1 > ls: cannot access '/dev/tty1': No such file or directory > > # ls /dev > ls: reading directory '/dev': Input/output error This looks like filesystem corruption. Did you try to fsck it? > I can't debug this properly myself because of the issue with GDB and > debuginfo I was talking about earlier: GDB (I've tried GDB 13.1 from > Fedora and 10.1 from Debian bullseye) just doesn't "see" the (DWARF?) > debuginfo in the .debug files extracted from the dbgsym debs. Are you running a Linux gdb for a Hurd binary? I don't know if that's supposed to work. Samuel