all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Marco van Hulten <marco@hulten.org>
Cc: help-guix@gnu.org
Subject: Re: state of the system
Date: Sun, 26 Nov 2017 23:00:26 +0100	[thread overview]
Message-ID: <87k1ycvgxx.fsf@gnu.org> (raw)
In-Reply-To: <20171125102532.063f8367@graviton.instanton> (Marco van Hulten's message of "Sat, 25 Nov 2017 10:25:32 +0100")

Hi Marco,

Marco van Hulten <marco@hulten.org> skribis:

> Concerning my kodi crash happening on my system but not on other's [1],
> maybe by system got broken and I should reinstall.
>
> I understand that the state of a GuixSD installation is defined by one's
> `config.scm`.  Thus I can very easily reproduce an exact copy of the
> functional system.

Indeed.  This property makes it essentially useless to reinstall, since
the system is stateless (or “mostly” stateless.)

> However, there are also packages installed per user.  What would
> define, excluding data files in the home directories, the complete
> state of a system, including both the core OS and packages (as
> available per user), if there such a thing in GuixSD?

If you use declarative profiles with ‘guix package -m’, then all you
need is to keep both the system config.scm and the user profile
manifests.

Otherwise there’s no fully automated way to capture the whole system
state.  It would be a useful addition!

Besides, if your concern is to allow others to reproduce the Kodi crash
you experienced, my suggestions would be to try and see if you can
reproduce it in a VM created with ‘guix system vm’.  If you can do that,
then others will be able to reproduce it as well and to investigate.

HTH!

Ludo’.

      reply	other threads:[~2017-11-26 22:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-17 20:59 kodi crash, and gdb not found Marco van Hulten
2017-11-19 16:36 ` Marius Bakke
2017-11-19 17:08   ` Marco van Hulten
2017-11-20  0:23     ` Marius Bakke
2017-11-21  4:30       ` Marco van Hulten
2017-11-21 13:21         ` Ludovic Courtès
2017-11-21 19:09           ` Marco van Hulten
2017-11-21 22:59             ` Marius Bakke
2017-11-22  8:52               ` Marco van Hulten
2017-11-25  9:25                 ` state of the system Marco van Hulten
2017-11-26 22:00                   ` Ludovic Courtès [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87k1ycvgxx.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=help-guix@gnu.org \
    --cc=marco@hulten.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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.