IRC channel logs
2026-06-18.log
back to list of logs
<gasc>Okay, I has playing with Hurd yesterday and I broke the system, looks like something I can debug <gasc>I did send a message earlier, but I lost my internet connect, if someone pinged me please, send it again... <damo22>youpi: #include <sys/types.h> and <string.h> are breaking the qemu test suite when cross compiling <damo22>In file included from ../tests/test-hello.c:19: <damo22>../tests/include/testlib.h:30:10: fatal error: string.h: No such file or directory <damo22> 30 | #include <string.h> // we shouldn't include this from gcc, but it seems to be ok <Alicia>do the tests not include running the resulting executable, which won't work when cross compiling anyway? <rrq>maybe needs CFLAGS=-Iinclude (I used that) <damo22>the tests are run inside qemu which should wokr <damo22>my problem now is that my riscv64 system does not have the grub pc modules or the tool to create the grub rescue image for x86 <damo22>otherwise, i could be using a riscv64 machine for CI <guest_temp_9998>I was pondering about the hurd/mach and I did some reading about the current development, (yes I'm not on my main computer so I made a guest account), could someone point to me one thing that should be adressed and is not currently being made? The TODO file says that sometimes is not up-to-date <azert>guest_temp_9998: we need people writing drivers <guest_temp_9998>Any specific driver in mind? I have some machines (intel from the 1º to 8º gen) and no amd machine, I guess something related to usb and or hdmi I could write (if they haven't been done yet) <azert>usb would be really useful. Complex but not as much as hdmi <azert>first thing would be to build the equivalent of the pci-arbiter but for usb <azert>the current status is a hack. We have rumpusbdisk that is a driver that includes just the storage drivers. And it cannot share the bus <azert>we would like to have a multi-server usb stack <guest_temp_9998>azert: sure, I will be taking a look this night. my correct nickname is gasc. Sending patches here is fine or there's a better place? <azert>the right place for patches is the bug-hurd mailing list <nexussfan>Seems like #rumpkernel doesn't exist anymore <jab>woo hoo! I'm reading through Kent Overstreets' AMA in phoronix. He said that he's probably going to licence the rust rewrite of bcachefs to GPLv3! <jab>Here's hoping that we can eventually use it on the Hurd! <nexussfan>jab: No need for us to officially adopt it, he could just write a translator for it ;) <nexussfan>I would also like more filesystems in Hurd, preferrably btrfs <jab>nexussfan: or we could. :) <jab>He also said that bcachefs will be 50% rust by the end of this year. (that's his goal). <jab>Then he said that once the conversion from C to rust is complete, then he'll start considering how to make bcachefs more portable to other OSes. <jab>It's not commonly known, but 90% of bcachefs run in userspace. Apparently Kent does some weird magic C stuff, that just uses ptheads most of the time. <jab>damo22: you want to use a riscv64 for your CI? How would that work? The Hurd isn't ported to riscV... I'm guessing that you mean you would run Linux on RISCV, and then launch qemu to run the Hurd. <jab>nexussfan: apparently fast enough. When I spoke to Kent about porting bcachefs to the Hurd, he very much so encouraged users to use rust to build a filesystem. <jab>apparently Rust can do cool things with its type system to make sure that you use the API correctly. <Gooberpatrol66>sneek: later tell gasc: it would be useful to boot hurd on all your machines and record what works and doesn't