From: Carlo Zancanaro <carlo@zancanaro.id.au>
To: Christian Miller <christian.miller@dadoes.de>
Cc: guix-devel@gnu.org
Subject: Re: Experience using the Nix service as a novice user
Date: Wed, 07 Feb 2024 00:22:49 +1100 [thread overview]
Message-ID: <871q9piv6e.fsf@zancanaro.id.au> (raw)
In-Reply-To: <87y1c080bq.fsf@dadoes.de> (Christian Miller's message of "Sun, 04 Feb 2024 21:02:33 +0100")
Hi Christian!
On Sun, Feb 04 2024, Christian Miller wrote:
> I wanted to try out the Nix service and followed the manual. I had
> some trouble while doing so. The following are the steps I took, the
> errors I encountered, and how I resolved them. As well as feedback to
> the experience.
Thank you for this feedback!
I recently installed the Nix service myself, and ran into these rough
edges, but I didn't think to write them down or fix things. Thank you
for the clear and detailed prompt to do so.
I've just sent a patch to guix-patches with some updates to the manual
which attempts to add the pieces that you found were missing. Could you
have a look at that and make sure you're happy with what I've written?
> At this point, I started encountering problems. The command
> "nix-channel --update" returns:
>
> unpacking channels...
> error: opening pseudoterminal master: No such device
> error: program
> '/gnu/store/mh2nc81cvw321q0lx4y38g4n7b86q88y-nix-2.16.1/bin/nix-env'
> failed with exit code 1
>
> This was easy to fix because I had found this solution[1]
>
> sudo herd restart nix-daemon
I didn't mention this in the manual, because this seems more like a bug
that should be fixed. I've also had the same issue, so I'll try to
investigate the next time it happens to see if I can fix it.
> I initially attempted this within a VM ($(guix system vm nix.scm) -m
> 4096 -smp 2) that had 4 GiB of memory and 2 cores. The process was
> terminated. Is it normal for Nix to require such a large amount of
> resources to install a package?
I wouldn't expect it to need that much, unless it was needing to build
things from source. Usually Nix's substitute coverage is pretty good, so
I wouldn't expect you to need to build much from source.
Carlo
next prev parent reply other threads:[~2024-02-06 13:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-04 20:02 Experience using the Nix service as a novice user Christian Miller
2024-02-06 13:22 ` Carlo Zancanaro [this message]
2024-02-26 19:41 ` Christian Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871q9piv6e.fsf@zancanaro.id.au \
--to=carlo@zancanaro.id.au \
--cc=christian.miller@dadoes.de \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).