IRC channel logs
2023-09-18.log
back to list of logs
<GNUmoon`>man that's annoying. I have some changes that I want to send upstream...but I can't get magit to work on the Hurd at the moment. <GNUmoon`>I am trying to use emacs tramp (from my linux box) to ssh into my Hurd machine, so that I can use magit on Linux... <GNUmoon`>though I can ssh into my hurd box from my Linux machine just fine. <GNUmoon`>I suppose I will try upgrading doom emacs <AlmuHS>I include scripts to deploy a Debian GNU/Hurd machine, creating and installing if necessary, download gnumach sources and compiling it with rump and optional support for smp <jab>AlmuHS thanks for the tip, but I actually have not messed much with any coding yet. I am mostly working on documentation at the moment, and probably not good documentation... <gnucode>So AlmuHS_ mentioned yesterday that he has the Hurd running on a Thinkpad T410, and that damo22 has the Hurd running in a x220. Does anyone know if those machines can use the internet? Or are they using "apt offline". <AlmuHS>gnucode: these machines get internet connection via Ethernet <AlmuHS>if you attach Ethernet cable, the connection is set automatically without any problems <AlmuHS>in t410, you need a Debian GNU/Hurd version more modern than 2021 <AlmuHS>I'm remembering that sometimes ping command doesn't work. But apt connect without problems, once added the properly lines to sources.list <AlmuHS>the properly repositories, i refer <danmorg>i am curious about the hurd and device drivers. I know the kernel for the hurd is a microkernel - GNU Mach. i am curious if a rump kernel is being used. i read a paper that hurd and netbsd can use a rump kernel for device drivers in userland. <gnucode>danmorg: yes. The Hurd is currently using rumpdisk, which is a rump kernel powering our disk drives. We now support most SATA SSDS thanks to the rump kernel. <gnucode>Work is ongoing to use rumpusb for sub support. And rumpnet, for what I believe will be using the NetBSD TCP/IP stack. <nikolar>how is the netbsd network card support <danmorg>i decided to download and try an iso of the debian hurd i386 20230608 netinst... fingers crossed... <azert>gnucode, nikolar, i thought that rumpnet was for network card drivers, since netbsd should have quite a few <azert>while for tcp/ip we already have two different stacks <nikolar>How good is netbsd's networking hardware support <nikolar>Like can it be expected to run on newer hardware <gnucode>azert: that is entirely possible. I had assumed that we had wanted to update out TCP/IP stack. I could be wrong. <gnucode>I have been known to be wrong before. :) <gnucode>nikolar: it's hardware support is probably much better than the hurd's currently. :) <nikolar>Yeah I know that, it should be a win either way <gnucode>nikolar: no idea. I use OpenBSD occasionally. So it is probably ok. <gnucode>It would be nice to see a phoronix networking benchmark between Linux, *BSDs, and the Hurd. I feel like we would not win that competition... <nikolar>you can't really compare hurd to the rest, the amount of work invested into hurd is way less then any of those <azert>Yeah there would be no comparison <azert>Optimist side: There are probably very low hanging fruits for anyone that wanted to dig into optimizing the network <azert>danmorg: real hardware or qemu? <gnucode>azert should we optimize lwip or pfinet?