IRC channel logs

<damo22>(20:59:30) youpi: just to make sure: are you booting with the linux drivers, or rumpdisk drivers?

<damo22>i use --disable-linux-groups

<damo22>i dont know how to trace the lock back to the name of the symbol from the address of the lock

<damo22>apart from checking the objdump when its in code segment

<youpi>damo22: wi dont know how to trace the lock back to the name of the symbol from the address of the lock

<youpi>I don't know either, but the trace code probably knows

<jpoiret>where can I find the Debian/Hurd startup scripts?

<jpoiret>i finally managed to get everything build for a newer Hurd on Guix, but now I'm hanging while starting the default pager

<youpi>jpoiret: https://salsa.debian.org/hurd-team/hurd/-/blob/master/debian/local/runsystem.sysv

<jpoiret>also, how do you usually debug early boot, before the boot scripts are run? Can't seem to get serial to output anything with qemu, and I think the exec server is malfunctioning (can't exec anything without getting hangs)

<youpi>simplest is to use mach_print

<youpi>with the gnumach console=com0 parameter you should be getting them

<jpoiret>i was hoping there was a general "--verbose" I could use, I'm trying to package a newer Hurd into Guix so I'm not using a checkout

<youpi>AFAIK nobody contributed one

<youpi>(so far)

<jpoiret>how would I go about debugging getting ENOTSUP on setxattr? Specifically, I'm doing (setxattr "/servers/exec" "gnu.translator" "/hurd/exec")

<jpoiret>i'm getting the same for pflocal on /servers/socket/1 by the way, which is probably why I can't use system* afterwards, since it uses pipes

<youpi>I'd just put mach_print in the source path that is supposed to perform the setxattr operation

<gnucode>well I have the hurd re-installed again.

<gnucode>hmmm apt doen't seem to be working so well

<gnucode>hmmm. I don't even have "man" installed....

IRC channel logs

2023-03-19.log