I've been facing the same issue, not a fresh install in my case.
I'm not sure what the problem is, but forcing `bordeaux.guix.gnu.org as the
substitute server to use got me past the issue.`
`> guix pull --substitute-url="https://bordeaux.guix.gnu.org"`
`This link was also helpful and
Hello all,
I am trying to capture my graphics card at initrd, using vfio, to later pass it
through to a virtual machine. Judging by dmesg, the VFIO module does load
early, however, the card is not captured at that point and the amdgpu driver is
later loaded instead.
This is what I have in my
id all that, the documentation helps a lot. Thank you for the patch!
Best,
-Nick
On Fri, Jan 28, 2022, at 5:51 AM, Andrew Tropin wrote:
> On 2021-12-26 12:17, Nick Zalutskiy wrote:
>
>> The following configuration results in a `~/.run` symlink being
>> created. My expectation
Indeed I missed this in the manual. Thank you!
I was trying to figure out how to close this... no luck.
-Nick
On Sun, Dec 26, 2021, at 4:44 PM, Aleksandr Vityazev wrote:
> Hi,
>
> On 2021-12-26, 12:03 -0500, "Nick Zalutskiy" wrote:
>
>> I'd like to use `guix ho
The following configuration results in a `~/.run` symlink being created. My
expectation is that a `~/run` symlink is created instead. (ie. not a dotfile)
> (home-environment
> (services
> (list (service
> home-bash-service-type
> (home-bash-configuration
>
I'd like to use `guix home` to symlink an executable into my home directory.
Following simple configuration stored at `~/.dotfiles/home-configuration.scm`
> (use-modules
> (gnu home)
> (gnu packages)
> (gnu home services)
> (gnu services)
> (guix gexp)
> (gnu home services shells))
