From: Benjamin Slade <beoram@gmail.com>
To: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: backup questions
Date: Mon, 06 Aug 2018 16:05:28 -0600 [thread overview]
Message-ID: <874lg7f8wn.fsf@jnanam.net> (raw)
Two question relating to backup:
1) In terms of backing up GuixSD, which files do I need to worry about?
(setting aside local data and application settings and so)
So far, I'm backing up:
/etc/config.scm
/var/guix/profiles/
~/.config/
2) I don't seem to be able to install `libchip` (for chop-backup). It
seems to have no substitute binaries and the local build fails. I've
fallen back to using Borg backup for now (which seems good, but more
fragile than I'd like, especially in terms of setting up automated bash scripts).
--
Benjamin Slade - https://babbagefiles.xyz
`(pgp_fp: ,(21BA 2AE1 28F6 DF36 110A 0E9C A320 BBE8 2B52 EE19))
'(sent by mu4e on Emacs running under GNU/Linux . https://gnu.org )
`(Choose Linux ,(Choose Freedom) . https://linux.com )
next reply other threads:[~2018-08-06 22:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-06 22:05 Benjamin Slade [this message]
2018-08-06 22:59 ` backup questions Pierre Neidhardt
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=874lg7f8wn.fsf@jnanam.net \
--to=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).