IRC channel logs
2025-09-14.log
back to list of logs
<mghackerlady_>I emailed the maintainer about it a while ago, and they finally got it working! Should this go on the hurd website as an easy way to try it out? <nexussfan>is the disk read only? can't write files on the machine <nexussfan>the system doesn't even load correctly because it can't write to the console (/dev/console) <diegonc>mghackerlady_ wow! archhurd on the web, pretty cool <diegonc>I mean, it's been some years with no activity <nexussfan>should've put debian hurd, or would that have some issues? <damo22>Fatal glibc error: malloc.c:2601 (sysmalloc): assertion failed: (old_top == init <damo22>ial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev <damo22>_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0) <damo22>/hurd/crash: /hurd/pfinet -i /dev/wm0(854) crashed, signal {no:6, code:6, error: <damo22>0}, exception {0, code:0, subcode:4096000} <damo22>something is fishy with fragmented packets on amd64 rumpnet <damo22>when the captured length is not the same as the original packet length, it breaks <damo22>i tried handling the three cases separatly <damo22>if the two lengths are equal, its simple, but if the captured length is smaller, we have a fragment of a packet and should ignore that packet until we read the full thing again <damo22>if the captured length is bigger, we have an unusual packet where the length we captured is more than the original data length, i dont know if that means it should be truncated to the exact length or not <damo22>ok so the problem is, when i get a fragment, it starts over and reads another fragment only <damo22>what is the smallest non-empty ethernet frame? <youpi>damo22: the ethernet header is 14 bytes <sneek>youpi, gnu_srs1 says: he can restart the build queue on mahler.