From: Pierre Neidhardt <ambrevar@gmail.com>
To: Benjamin Slade <beoram@gmail.com>
Cc: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: Re: backup questions
Date: Tue, 07 Aug 2018 00:59:35 +0200 [thread overview]
Message-ID: <87zhxzje3s.fsf@gmail.com> (raw)
In-Reply-To: <874lg7f8wn.fsf@jnanam.net>
[-- Attachment #1: Type: text/plain, Size: 505 bytes --]
1) If you don't want to keep generations you don't have to: then no need to save
/var/guix/profiles or ~/.config/guix.
I personally skip them and only keep the formatted output of `guix package
--list-installed` under version control.
Note that /etc/config.scm can be stored anywhere, it does not have to be in
/etc/.
2) I don't use libchip, so I don't know. How does it fail? Can you provide the
backtrace?
Beside borg, other solutions include restic and duplicity.
--
Pierre Neidhardt
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2018-08-06 22:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-06 22:05 backup questions Benjamin Slade
2018-08-06 22:59 ` Pierre Neidhardt [this message]
2018-08-06 23:15 ` Benjamin Slade
2018-08-06 23:57 ` Björn Höfling
2018-08-19 22:53 ` Björn Höfling
2018-08-21 4:09 ` Benjamin Slade
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=87zhxzje3s.fsf@gmail.com \
--to=ambrevar@gmail.com \
--cc=beoram@gmail.com \
--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).