<_tibbe>Hi, what is needed in the operating-system declaration to let fuse use extensions like fuse-exfat?
<lsl88>Hi again! I have two questions. 1) is there a way of scrolling up a tty? not a console. Sometimes I do | less but it is not good at all. 2) I know you don't like vBox, I was installing GuixSD over qemu. I faced strange issues, like having /dev/sda already partitioned, with Microsoft stuff. This did not happen at all with my retroPC and over vBox. I haven't used qemu in the past. And I am using the same .iso. I have searched over the inter
<g_bor>lsl88: and what is guixsd.img? How is it created? Is that your /dev/sda?
<lsl88>g_bor: and I create the qemu-img create -f qcow2 guixsd.img 50G first. I deleted the partitions, created them with cfdisk
<lsl88>g_bor: sorry, I was writing that part. And the .iso is the one I used in the past: guixsd-install-0.15.0.x86_64-linux.iso
<lsl88>g_bor: also, I will better paste some weird things I get
<civodul>_tibbe: i believe you just need to install "fuse-exfat"
<lsl88>g_bor: I am delaying my paste because I believe I messed sth up with guix pull after guix package -i qemu complained about not guix pulling. I was checking my last guix generation and its date is not match when I guix pulled.
<_tibbe>civodul: I tried that but it did not work. I will try again and verify that it does not work
<_tibbe>no that definitly does not work for me: Neither with mount, gio mount or Thunars mount
<civodul>_tibbe: what i do is "sudo mount.exfat ...", and that works
<civodul>however i don't know what it would take to make it work with GVFS & co.
<civodul>perhaps we should somehow make exfat known to udisks or whatever is taking care of that?
<_tibbe>civodul: You're right. That works. That is kind of difficult: Fuse itself is in no way configurable. There is no kind of service or firmware from which we can detect which extensions are installed and supported
<lsl88>inux.tar.xz and get "No such directory ‘guix'". So I just added gnu in between (wget ftp://alpha.gnu.org/gnu/guix/guixsd-install-0.15.0.x86_64-linux.iso.xz) and it is found but the last message is: ==> RETR guixsd-vm-image-0.15.0.x86_64-linux.tar.xz ... No such file ‘guixsd-vm-image-0.15.0.x86_64-linux.tar.xz’. Any ideas?
<lsl88>g_bor: I see, but if I want to install it with guix system, maybe I am not understanding it well, but how can I download the prebuilt image from here? ftp://alpha.gnu.org/guix/guixsd-vm-image-0.15.0.system.tar.xz’ (the one that I could not download)?
<lsl88>g_bor: or should I use guix system vm and the .scm file is one of the that is described? I don't understand very well the difference between vm and vm-image and which one I should use. I believe it worked on vBox because I set it, as you said, like a live cd/DVD
<cbaines>lsl88, I think one of the key differences between vm and vm-image, is that the vm command will share the host store with the vm, while the vm-image command will copy store items in to the image it's creating. Does that make sense?
<g_bor>lsl88: the image you could not download is a fully baked one, you just give that one to qemu as the only disk, and you are good to go.
<g_bor>you can create one from a working guix using guix system vm-image
<g_bor>a guix system vm is not self-contained, it shares the store with the host, and the store is read only from the guest.
<davidl>if I set the mount point in the bare-bones.scm file to /mnt instead of /, Im getting a wrong type argument error, which is probably not what I should get.
<lfam>What is returned by `guix system vm` is a short shell script, which launches a QEMU instance using files found in the host machine's /gnu/store. These machines are immutable — the file system is read-only
<lfam>I recommend reading the script to understand what's going on
<lfam>Whereas vm-image returns a QEMU image file that must be copied out of /gnu/store in order to use.
<lfam>That's more like a full system, as g_bor said
<lfam>Does anyone have any idea about the problems with libboost_system since the core-updates merge?
<lfam>lsl88: The file used to create the VM image that we offer for download is at 'gnu/system/examples/vm-image.tmpl'. However, I don't recommend using that unless you are going to use it on a hosted VPS service
<lfam>Just use something that fits your needs more directly
<lsl88>cbaines: yes, that compressed iso file worked, and I used it both for bare metal installation and the instalation in vBox. The problem was using it with qemu. And the ne that did not work was the other one
<lsl88>f things, that I did not see over bare metal or vBox, and so on. And I don't know how to copy and paste it from quemu to show it in paste debian
<davidl>lsl88: I just figured out how to do that yesterday: you can add -virtfs local,path=/home/<user>/vm_share_dir,mount_tag=host0,security_model=none,id=host0 to the qemu command line options. Then from vmguest, mount it with mount -t 9p -o trans=virtio,version=9p2000.L host0 /mnt. You then have shared directory that you can write files to from VM at /mnt.
<g_bor>lsl88: can you help me trying to reproduce what you have?
<davidl>lsl88: from there on you can open the /mnt/mytext.txt from host and copy paste to paste.debian
<g_bor>I guess it goes like this: qemu-img create hda.img, wget the guix iso installer.
<lfam>Does anyone have a build log for the pre-core-updates Boost 1.66.0?
<rekado>civodul: sorry about the bind mount. I thought I had added it to the config already.
<apteryx>hello! I'm finishing to package Openboardview, and struggling with a small detail; I want to use the cmake-build-system, but include also the two extra phases provided by the glib-or-gtk-build-system. I've found an example in the cups package, but I can't seem to get it working with my package: https://paste.debian.net/1054385/. Any ideas welcome!
<lfam>apteryx: Can you add a paste of the error messages you get?