IRC channel logs
2026-06-17.log
back to list of logs
<nexussfan>Now that QEMU is ported to Hurd, should the qemu source package enable hurd arch support? <sam_>don't think that landed upstream yet <damo22>i will bump the qemu people about it <damo22>there are no official meetings, its pretty adhoc in this channel <damo22>i suggest grabbing the disk image and booting a debian hurd preinstalled in qemu to get started <gasc>Sure, I will start with doing that now, I just wanted to make sure about the meetings but I will make sure to be around here on my spare time <damo22>timezones are sometimes an issue, so you need to be willing to wait a while for answers here <gasc>Sure, that's not a problem for me <gasc>Thank you for answering, I will start my research/reading now <damo22>hurd is mostly working at this point, but in general it needs more drivers for hardware <rrq>and I wish for a tap interface :) <damo22>ok ive alerted someone for qemu patches <etno>Any idea why `ports_manage_port_operations_one_thread(..., 1000)` would not be returning from time to time ? <etno>I mean, I expect it to return when there is nothing to do. But a breakpoint right after it is never triggered. <Darelelve>etno: The ports_manage_port_operations_one_thread function states that this is unsafe for most translators and the timeout is pre-set to zero. <etno>Oh, I didn't notice this warning in the header file. Is the multi-threaded variation the preferred one ? Darelelve <Darelelve>etno: I saw this warning in manage-one-thread.c. There's also a similar warning in manage-multithread.c, so it's hard to say which is more correct. <etno>(about the comments, I mean)