From: Efraim Flashner <efraim@flashner.co.il>
To: "Etienne B. Roesch" <etienne.roesch@gmail.com>
Cc: Felix Lechner <felix.lechner@lease-up.com>,
help-guix@gnu.org, guix-science@gnu.org
Subject: Re: guix on nfs based systems
Date: Sun, 26 Nov 2023 09:36:54 +0200 [thread overview]
Message-ID: <ZWL1lkfw4MNY5g1g@3900XT> (raw)
In-Reply-To: <CAPX-MzDeKzVBnF0Ri5qJgVKw8Hh=gM6081v2y3mrpQEe7bhfSQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1188 bytes --]
On Fri, Nov 24, 2023 at 06:08:30PM +0000, Etienne B. Roesch wrote:
> Hahaha! Yes, that's what I was getting at!
>
> I suppose one could run gc periodically, in a monthly cron. No?
>
> Etienne
>
> On Thu, Nov 23, 2023 at 1:03 PM Felix Lechner <felix.lechner@lease-up.com>
> wrote:
>
> > Hi Efraim,
> >
> > On Thu, Nov 23 2023, Efraim Flashner wrote:
> >
> > > One thing we do on the small cluster at UTenn is /gnu and /var/guix (in
> > > addition to the home directories) are exported across NFS
> >
> > That's fascinating! Do you ever run 'guix gc', or do you just buy new
> > disks when space runs low?
> >
> > Kind regards (and perhaps, happy Thanksgiving)
> > Felix
We generally run it as necessary, but luckily not too often. With
everyone trained to use profiles we rarely have problems with necessary
packages disappearing. I've generally been the biggest offender with
building and rebuilding packages while packaging new software.
--
Efraim Flashner <efraim@flashner.co.il> רנשלפ םירפא
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-11-26 7:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 17:32 guix on nfs based systems Etienne B. Roesch
2023-11-23 6:32 ` Efraim Flashner
2023-11-23 9:41 ` Etienne B. Roesch
2023-11-26 7:33 ` Efraim Flashner
2023-12-14 14:41 ` Ricardo Wurmus
2023-11-23 13:03 ` Felix Lechner via
2023-11-23 13:03 ` Felix Lechner via Guix-Science
2023-11-24 18:08 ` Etienne B. Roesch
2023-11-26 7:36 ` Efraim Flashner [this message]
2023-12-13 10:17 ` Etienne B. Roesch
2023-12-14 14:46 ` Ricardo Wurmus
2023-12-14 15:28 ` Etienne B. Roesch
2023-12-14 15:33 ` Pierre-Antoine Bouttier
2023-12-14 15:33 ` Pierre-Antoine Bouttier
2023-12-14 15:57 ` Etienne B. Roesch
2023-12-14 19:35 ` [ext] " Ricardo Wurmus
2024-02-15 16:14 ` Simon Tournier
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=ZWL1lkfw4MNY5g1g@3900XT \
--to=efraim@flashner.co.il \
--cc=etienne.roesch@gmail.com \
--cc=felix.lechner@lease-up.com \
--cc=guix-science@gnu.org \
--cc=help-guix@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.
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).