IRC channel logs

<ZhaoM>wierd my /var/log/dmesg stopped at '...task loaded: pci-arbiter --host-priv-port=1 --device-master-port=2 --next-task'

<ZhaoM>but I want to see the message after it...

<ZhaoM>did anyone also come across this issue?

<crupest>Now I see why uv_pipe_chmod in libuv works on FreeBSD and macOS, where getsockname also returns empty string. Libuv uses kqueue as event loops on them. In the kqueue implementation, it calls 2 special fcntl interfaces (F_GETPATH of macOS, F_KINFO of FreeBSD) to get and fill paths of files before calling actual system interface (chmod, here). On Hurd, libuv uses unix poll as event loops, which does not have this logic.

<crupest>I think I made some mistake. macOS works because its doc is wrong and it does return the file name of the socket.

<ZhaoM>Do we have a size limit for info in /var/log/dmesg?

<ZhaoM>youpi: is this still the case? Any investigation is needed? https://darnassus.sceen.net/~hurd-web/open_issues/m4_vs_stack/

<youpi>I don't know

<azert>hakanrw_: in regards to gnumach on riscv64, did you manage to boot it already?

<azert>I think you can pretty much follow what Sergey did for arm64 and the devtree protocol

<youpi>please synchronize about the devtree support, yes ;)

IRC channel logs

2025-04-07.log