<buenouanq>when might the next version release be coming up?
<pkill9>what's the difference between /run/booted-system and /run/current-system?
***enick_345 is now known as sturm
<sturm>If I'm looking to run a `curl URL | bash` type installer in a container but getting `curl: (60) server certificate verification failed. CAfile: none CRLfile: none`, what package might I be missing? Container is run like this `guix environment --ad-hoc wget --container --network --share=$HOME/Downloads`
<sturm>sorry, replace "wget" with "curl" in the above container command
<sturm>Ah, adding `--expose=/etc/ssl/certs` does the trick to share the host's certs. I wonder still though if you can install these directly in the container. Adding "nss-certs" as an ad-hoc depedency doesn't seem to do it.
<lo_mlatu>Ask questions again...I now have compiled an extra kernel module, after defining a package for it, how can I configure to load that module(the .ko file) at boot time
<lo_mlatu>the `initrd-modules` field seems can only detect the modules included in the kernel, `initrd` seems can do the job but...is there an easy way? rather than rewrite the whole gexp
<grillon>yesturday guix system reconfigure stopped with gnome-desktop needed but not installed. So I installed it(as root) and restart guix system reconfigure. then because I'm not alone to use the computer I had to restart fully working
<grillon>I think the best for me is starting in a vm. Is there a command to do p to v? I have read it's easy to reproduce a system with guix.
<civodul>lo_mlatu: you can use --skip-checks if needed
<civodul>that is, if you think 'guix system' makes a wrong diagnostic regarding modules, then use 'guix system reconfigure --skip-checks'
<civodul>grillon: could you explain exactly what you typed and what you got?
<civodul>it may be easier to do that on firstname.lastname@example.org though
<lo_mlatu>civodul: Sorry maybe I didn't explain it well...`initrd-modules` seems to accept a list of strings which represents the filename of the modules, during system reconfiguration it will try to find corresponding .ko files in the kernel directory( I guess, didn't fully check the source code)
<lo_mlatu>Now I have a module file which is "out of kernel", how can I make a configure so the build process can find it?
<sneek>pkill9, lfam says: The booted-system is the system that was booted. If you then reconfigure, I'd expect the current-system will have changed (have not read the code)
<thomassgn>mbakke: bavier` Have just into the 4.14.32 kernel and are having the exact same problems with the atheros wifi card. I saw linux libre had a release message the other day with something about wireless cards(think it was ralink, but maybe...), doing a guix pull now and will be building the 4.16 kernel to see if it helps...
<lo_mlatu>Hi it's me again...I have installed `linux-libre-headers`, but I didn't find header files such as `modules.h` or `platform_device.h` which is needed for compiling a module..can any one help me?
<thomassgn>So linux-libre 4.16-rc7 has a few new dependencies, and fails to build here. Just stops building (during compilation (CC and AR going on). Trying 4.16 now
<thomassgn>haha, I just realised also, rc7 is release candidate so linux-libre-4.16 is higher version than 4.16-rc7, isn't it?
<lo_mlatu>Sorry for bothering..I have installed `linux-libre-headers`, but I didn't find header files such as `modules.h` or `platform_device.h` which is needed for compiling a kernel module, so how can I get these files?
<thomassgn>You don't specify mbr or gpt in relation to your bootloader
<thomassgn>some of the schemes (like some efi (maybe all efi)) requires gpt.
<thomassgn>I get "guix build: warning: ambiguous package specification `email@example.com'" from 'guix build -K firstname.lastname@example.org' and then it chooses linux-libre-4.16-rc7... Why?
<thomassgn>And how can I make it choose what I write instead?
<zybell_>efi needs gpt,because it finds the bootpartition by a special gptID. gpt doesnt exclude partitioning with mbr. A disk can be partitioned with both. Mostly its done by entering the whole gptdisk into the mbr as one strange/alien partition, so that BI/OS that don't understand gpt don't touch. But with care one can enter the bootpart into mbr too. Because its formatted as FAT syslinux should work.
<jonsger[m]>is it intended that the qemu image doesn't have "mkfs.fat32"?
<pkill9>does the GuixSD installation image come with an installation guide in a text file?