IRC channel logs
2026-05-25.log
back to list of logs
<Pellescours>I think ext2fs has a possible deadlock (shown using xfstests). Basically when running the test generic/010, it open a gdbm database write some entries in the file, close it, reopen it as read-only, read content multiple times, then close it and delete it. Often when I run this test, I’m then unable to umount the fs except when I force it. <damo22>rsmarples: the root partition needs to be ext2 because translator entries are stored in the xattrs <damo22>it tells the operating system which program to fire up to serve the device node you are trying to access <damo22>thats how drivers work in userspace <Pellescours>I’m trying to understand why I can’t umount my ext2 partition after the xfstest run. I can see the open ports with portinfo but how can I know what program is linked to a given port? <azert>Pellescours: I think not even ext2fs is aware of that information, by design <azert>you could try to trace this information when running xfstest <Pellescours>youpi: I tried compile gdb git, and the build is broken. Can I send a spontaneous patch or does it need an aggrement for this repo? <jab>off topic, but I am thinking about making a DIY laptop with an eink display. One that doesn't support displaying images. <jab>Apparently this has been done with rasberry Pis. OR there are some older thinkpads that people have used to retrofit an eink display onto. <diegonc>so, I'm looking at a program (openntpd) that chroots into /var/empty/ and then tries to launch HTTPS connections <diegonc>which fails, I guess, because there's no /servers/socket/* in the new root <diegonc>what's the hurdish way to allow sockets in a chroot? <diegonc>tls connect failed: 9.9.9.9 (9.9.9.9): socket: Address family not supported by protocol <youpi>diegonc: you settrans -c /servers /hurd/firmlink /servers <youpi>you can restrict that to /servers/socket <youpi>or even to /servers/socket/2 and 26 <youpi>(or even give it its own tcp/ip stack ;) )