IRC channel logs
2023-05-19.log
back to list of logs
<gnucode>haunt installs for me, but I am having some trouble installing guile-commonmark <gnucode>it looks like commonmark is installed, but haunt doesn't see it during the configure phase <janneke>i can't seem to boot debian-hurd-20220824.img with rumpdisk, ie, with using "noide" <jpoiret>you could install the latest and greatest in a vm then use that <gnucode`>jpoiret: how would you "install the latest and greatest in a vm"? <jpoiret>well, use an iso installer then update all packages <gnucode`>I'm using stable/hurd-i386/debian-hurd... <gnucode`>I would be interested in trying that latest and greatest, but I've been told it can be difficult to update reliably. <gnucode`>i guess I can try to install from the latest iso image...just see if the installer works. <jpoiret>i did that just last week in a vm, didn't try much but it was pretty easy to do <gnucode`>ok. I will give a try on bare metal then. <janneke>jpoiret: i could just apt-get upgdate, apt-get upgrade in the debian-hurd-20220824.img, right? <biblio>janneke: apt-get update might fail due to certificate initially. you may add apt options to check cert initially or install certificate manually. <biblio>janneke: i suggest to do apt-get dist-upgrade via ssh connection to hurd image from main machine. <biblio>janneke: otherwise everything worked when I updated last time. <jpoiret>yes, I had to install the keyring manually by downloading the dpkg first and installing it <janneke>apt-key adv --keyserver hkp://p80.pool.sks-keyservers.net:80 --recv-keys <janneke>E: gnupg, gnupg2 and gnupg1 do not seem to be installed, but one of them is required for this operation <janneke>and none of those can be installed... <janneke>E: Package 'debian-keyring' has no installation candidate <biblio>janneke: better with certificate but for doing experiments you may # apt-get update --allow-insecure-repositories <biblio>janneke: I faced issue in vga output during upgrade. So, next time I did upgrade via ssh. <janneke>jpoiret, biblio: thanks, dist-upgrade is running! <janneke>ACTION 's debian skills surely have gone rusty <janneke>yay, i believe noide => rumpdisk is working after a dist-upgrade <janneke>Checking root file system...fsck.ext2: No such device or address while trying to open /dev/hd0s2 <janneke>typed:part:2:device:wd0 on / type ext2fs (ro,relatime,no-inherit-dir-group) <janneke>so, i also need to fix a startup/runsystem script when using wd0+noide, makes sense <janneke>Checking root file system.../dev/wd0s2: clean, 42057/259072 files, 416312/1035776 blocks <janneke>Debian GNU/Hurd 12 debian console -- with noide/rumpdisk \o/ <janneke>this setup uses the acpi server which is broken and has been disabled in the latest rumpkernel build... <janneke>(and so we don't have it on guix, so we'll see...) <janneke>meanwhile, i've built a patched gnumach to support the "noide" option :-) <janneke>still, pretty happy with this, gaining some understanding and working setups <jpoiret>so will we need to build less stuff in gnumach? I also don't know if we should disable the in-kernel drivers completely, if we can get netdde working <janneke>jpoiret: dunno, i guess it's safe to keep them for now, and use "noide" , e.g. to disable the gnumach disk driver; it gives the user more options <janneke>--multiboot-command-line=root=part:2:device:wd0 <janneke>Hurd server bootstrap: ext2fs[part:2:device:wd0] exec startup proc auth. <janneke>--multiboot-command-line=root=part:1:device:wd0 <janneke>ext2fs: part:1:device:wd0: Invalid argument <janneke>hmm...could missing /dev/wd* device nodes cause this error? <jpoiret>can gnumach run in userspace on linux? we have i686-linux listed under the supported systems for gnumach