<serieux>I'm currently running Arch Linux. I'm wondering if it is possible to install GuixSD on another partition, similar to debootstrap
<marusich>I've heard of people dual-booting. I don't do it myself, though. I believe it's possible; check out the section "(guix) GRUB Configuration" in the manual. It describes how to add custom boot menu entries.
<serieux>marusich: do you know how debootstrap works?
<marusich>I don't. I don't know if you can dual boot in the same way as that; but dual booting is in theory possible.
<serieux>I'll wait for someone to respond who knows what I mean.
<serieux>But thank you. That was one question I had, whether it was possible to dual boot.
<serieux>it seems like it should be possible. it's basically the same way it is installed from the GuixSD image. I would probably need to install guix on my current Arch Linux system in order to do so
<marusich>I read the man page; I am not sure if it's possible to run a GuixSD system in a chroot, but I know it is possible to run a GuixSD system in a VM. Maybe you already knew that; the details are in "(guix) Invoking guix system".
<marusich>It is also possible to run a GuixSD system in a container. See the same section of the manual. Perhaps that is similar enough to running in a chroot?
<marusich>For any of those mechanisms, you would first need to install Guix onto your Arch Linux system.
<marusich>That's all the info I have; hopefully it's helpful. Maybe somebody else can comment further.
<serieux>marusich, what I want to do is this: format another partition on my hard drive for GuixSD. Then I would mount that partition at /mnt. Then I would run 'guix system init /mnt/etc/config.scm /mnt' from my Arch Linux system.
<serieux>The thing is I think I need herd to run 'herd start cow-store /mnt' to initialize the partition for GuixSD
<marusich>I think that's an installation-image-specific thing.
<serieux>and herd is specific to GuixSD. But anyway, I don't necessarily need this; I was just wondering if it is possible.
<marusich>I think you can just run "guix system init", point it at a directory, and you'll get the files initialized there. So if you're not running the GuixSD installation image, you don't need to use the cow-store thing. I think.
<serieux>I have no issue with using the install image
<serieux>but doesn't 'herd start cow-store /mnt' set up things like /gnu/store and the default configuration template?
<marusich>I don't think so; I'm not 100% sure about it, but my understanding is that the cow-store service just makes it so writes to the store will be persisted to disk.
<marusich>So, I believe you could probably run 'guix system init' (taking care to pass --no-grub) from your Arch system to populate the /mnt directory (on which you have mounted a file system you made earlier on the partition you want to use), and it will deposit all the GuixSD system files there.
<marusich>To boot into the system, you would probably need to modify whatever bootloader configuration file your Arch system normally uses; I don't know how Arch sets that stuff up.
<marusich>Even if you can boot into the GuixSD system you've installed on that partition, I don't know how safe it would be to run 'guix system' commands like 'guix system reconfigure' from within the booted system. I think that, if you are not careful, it would be possible to accidentally overwrite your Arch system's bootloader (installed, presumably, on /dev/sda or the like) with a new one managed by GuixSD. That would probably not be a great
<marusich>So, if your goal is really just to run a persistent GuixSD system without replacing your Arch system, then perhaps using VM might be safer and easier.
<serieux>marusich, yes, I think I'll just use a VM
<marusich>It seems simpler. I think you could probably figure out a clever way to do it without using a VM, but I would not feel comfortable doing that on my own system; I'd be worried about accidentally overwriting things.
<marusich>If there is a supported way to do what you're asking without a VM, I don't know what it is; maybe somebody else will chime in later...
<dpg>GuixSD finally finished compiling the system init, I've rebooted and trying to bootstrap via Libreboot, however it doesn't seem to have a kernel...? I used the --no-grub option which might be the trigger.
<sneek>dpg_, ng0 says: I'd like to tell you more, but with our possibly differing timezones/availability your best shot is either our (SecuShare) chat on psyced.org (see www.psyced.org for an how to connect) or #gnunet here
***dpg is now known as DoublePlusGood23
<DoublePlusGood23>What would an encrypted drive appear as in the initrd? as in the --root option.
<efraim>i have a macbook that I want to try installing guixsd on by going debian -> guixsd, but the debian install keeps on failing to properly boot after installation :/
<janneke>efraim: is -> guixsd directly not an option?
<efraim>its a macbookpro 3,1 from 2007(?) with efi and I know i've installed debian on it before, so it should work
<grillon_>hi I have tried to install guixsd for the first time yesturday and I have problems with perl24 and kvm too. for 90-kvm.rules I got not found 404. for perl I have corrupted source. What can I do?
<grillon_>because of that I cannot do guix system init /mnt/etc/config.scm /mnt
<snape>janneke: or alternatively, you could search for all emacs buffers whose major mode is 'exwm-mode'.
<janneke>snape: ah...and now i see line-mode...things start to make sense
<DoublePlusGood23>Checking in again. Would anyone know what an encrypted root, formatted btrfs, appear as during bootup? trying to use libreboot and can't seem to get the --root flag right. It just drops me to a guile shell in the initrd.
<mbakke>grillon_: continue compiling, I guess... the binaries from the install image should be mostly exempt from garbage collection, but newer ones are not
<mbakke>if you've gone for 5hrs on an i7, there can't be much left :(
<grillon_>build is finished but I cannot use the system anyway. I had another problem before. my disk is gpt. I just activate legacy bios but I cannot install grub on sda
<grillon_>I would like to erase all but I'm not sure my backups of patitions are up to date
<grillon_>anything I can do would takes lot of time. a find for recent files(more recent than my dump) on each partitions. then save theses files, erase everythings and restart installation for 5 hours :(
<grillon_>may be I can save guix partitions too...
<Apteryx>I've got an error trying to build our latest grub. After many passed tests, I get: make: *** [/tmp/guix-build-qemu-minimal-2.9.0.drv-0/qemu-2.9.0/tests/Makefile.include:816: check-qtest-i386] Error. Will investigate.
<grillon_>I was lazy and waste lots of time. what I can do is verify my backup. because I was lazy I did it with dd so I have to check if it's complete. then save guix_root and repart my disk as legacy :(
<grillon_>mbakke: have you receive my previous message? because I was disconnected for 2 minutes but weechat did not notice
<mbakke>grillon_: you don't need to change partition layout, but you need a BIOS boot partition that grub can embed itself in
<mbakke>if you have any space left, create a small 1MB partition and mark it as "bios_grub"
<grillon_>mbakke: I did reboot before you tell me what to do. so I have remount everything as before but if I try init it seems to reinstall. and if I do directly grub-install I have a message about gnu-store
<grillon_>mbakke: wait I restart to tell you the exact message
<grillon_>mbakke: failed to find path of cannonical unionfs
<mbakke>grillon_: uh.. what is the exact command that gives that error?
<Apteryx>lfam: When building qemu, at the ./configure phase, I see make messages such as "make: flex: Command not found", "make: bison: Command not found". Should we include flex & bison as native-inputs?