<raghavgururajan>civodul: rekado pkill-9[m] pkill9_ or some one else: I really need to understand this. Can you tell me how to make "grub.cfg" available under "/boot/grub" directory of root partition, by still passing "no-bootloader" in "guix system init"??? In other words, can " guix system init" do "grub-mkconfig" without doing "grub-install"??? Please and thank you.
<rekado>raghavgururajan: I cannot help you if you’re using --no-bootloader.
<raghavgururajan>rekado: I understand. But I am trying to understand how the "bootloader" section of "config. scm" works.
<raghavgururajan>The line "(bootloader grub-bootloader)". Is it executing/triggering both " grub-install" and "grub-mkconfig" function or just the former??
<nckx>raghavgururajan: Dunno what ‘grub-mkconfig’ is, but it's never used at all in Guix.
<rekado>Guix ends up running “grub-install” when it’s asked to install a bootloader.
<raghavgururajan>rekado: Thank you! After you told me not to use "no-bootloader", I reinstalled Guix System with bootloader, but at the end of " guix system init" process, it showed a line "installing for i386-pc". But I used x84-64 installation image. Why it installed got i386??
<lfam>raghavgururajan: That message is from GRUB and it's okay. GRUB calls the traditional PC BIOS bootloader "i386-pc". You did successfully install for x86-64
<lfam>raghavgururajan: We are currently discussing whether and how to make this message from GRUB less confusing, because many people have been asking the same question. It's clear to us that this misleading message is a problem
<nckx>raghavgururajan: Yes? I don't see how that contradicts what I said.
<raghavgururajan>lfam: Phew! Thanks a lot. My final and actual confusion is, did it embed bootloader in the MBR gap or did it install the bootloader inside root file system under /boot directory ?????
<lfam>raghavgururajan: I don't know off the top of my head, sorry. I'm not familiar with bootloaders, even in Guix. Maybe you could take a look?
<olivuser>Hej everyone. Is it possible to include configratuon files of programs such as emacs or i3 in the os declaration file and thus in the disk-image so that it installs the configuration files along with the system itself?
<lfam>olivuser: Hi! Some Guix system services are configured in the OS declaration file (I'll call it 'config.scm'). For those cases, yes, the configuration files are handled in the way you desire. But not every program or service is managed this way in Guix... yet ;)
<olivuser>Alright. So I transmit them manually after system installation?
<nckx>raghavgururajan: MBR gap or not depends on the ‘target’ field. If it's a whole device (/dev/sdx): yes.
<lfam>Hm, okay. You can look at the file /etc/guix/acl to see if there are any keys in it. I don't remember off the top of my head what comes pre-authorized
<lfam>Probably yes for the analogous server behind the CDN (berlin.guixsd.org)
<hyonpotenuse>hello! I have a problem with my guix profile. The "current" symlink is broken and I can't use guix pull (it just hangs). does anyone knows how to fix this?
<hyonpotenuse>also guix pull -l just bugs, it gives an error saying profile doesn't exist
<nckx>raghavgururajan: Possible. The only mention I found in the Guix manual (is that the ‘guide’ you're referring to?) is ‘For legacy systems, the ‘target’ field names a device, like ‘/dev/sda’’ which isn't quite as strong.
<nckx>Using /dev/sdxN *can* be problematic, since some file systems don't reserve space for a boot loader, but it's not wrong.
<lfam>hyonpotenuse: What does the current symlink point to?
<lfam>hyonpotenuse: Also, how did you install Guix?
*Elon_Satoshi does an experiment: `guix pull --no-substitutes && guix --version && bash -c "guix --version"`
<lfam>hyonpotenuse: Okay, and how did you install Guix? From our binary download? From source? A distro package?
<lfam>Did you just install it or has it been installed for a while?
<raghavgururajan>nckx: Perfect! Thank you very much. It's clear now. Is there a way to protect grub images in MBR gap from tampering? Is it possible to cryptographically sign the images??
<jackhill>raghavgururajan (and other fine guix folk): I also have a use case for building a grub.cfg and instailling under boot, but not installing the grub binary on disk.
<nckx>raghavgururajan: A good question to which I don't know the answer. ;-) Sounds a bit like ‘secure’/‘restricted’ boot on UEFI, but who would verify the MBR signature, and against what? In any case, Guix certainly doesn't support anything like that right now.
<jackhill>This is for running a guix system on a VPS provider, that wants to use an external grub binary (not unlike the librebook grub).
<jackhill>maybe an option can be added to the bootloader config for skilling the actual install. I'll try to take a look later, but I'm still new here and learning.
<raghavgururajan>Also one of the reason why libreboot comes with inbuilt grub payload is to not have unencrypted boot partition or binaries on disk. That libreboot's grub can unlock LUKS and boot the system.
<nckx>Should be pretty easy to hack up. You'll probably have a longer ML discussion about the interface ;-)
<jackhill>raghavgururajan: sure. Are you on the guix-devel mailing list? If not, /msg me your address, and I'll cc you.
<apteryx>I often get errors such as: guix substitute: error: host name lookup error: Name or service not known
<apteryx>for example: guix build: error: some substitutes for the outputs of derivation `/gnu/store/8lgwanaijv3bsy6pv8r3a8xx70kzchf7-pyGenomeTracks-2.0.tar.gz.drv' failed (usually happens due to networking issues); try `--fallback' to build derivation from source
<apteryx>maybe the guix-daemon on hydra is doing freegames again
<nckx>apteryx: That would not affect domain name resolution. Sounds like an issue with your [ISP's] resolver.
<mbakke>Elon_Satoshi: Qemu 2.10 is a "hidden" package because it does not receive security fixes, i.e. it's not meant to be used other than for package tests.
<mbakke>Elon_Satoshi: You can use `guix build -e '(@ (gnu packages virtualization) qemu-minimal-2.10)'` as a workaround :)
<lfam>If there is some problem building this package can you file a bug report, Elon_Satoshi? In general it's working on my machine and also on the build farm so it's not easy to help debug it for you without further info
<mikadozero>When logged in as root, chsh -s /path/to/installed/shell gives me a Pam authenticatio failure. How would I do this in config.scm?
<mikadozero>lfam: Thanks I modified the snippet you shared and put it in my config.scm and it worked. The documentation makes me feel that I need to learn more about guile to feel more confident using Guix SD.
<lfam>mikadozero: I can sympathize, I came to Guix without much Scheme / Lisp knowledge
<mikadozero>lfam: I think I am really going to like Guix SD and am thinking of trasition to it for all my systems. So it will be worth learning Guile more deeply.
***maddo_ is now known as maddo
***slyfox_ is now known as slyfox
<Levy[m]>There are a few books on racket which could serve as a good introduction
<Levy[m]>then it's just adjusting to guile which shouldn't be too much of a difference
***jetomit_ is now known as jetomit
<ennoausberlin>Hello. Can someone confirm, that the iso image for guix16 creates a hfsplus partition on an usb stick? Is this intended behaviour?