From: Joshua Branson <jbranso@dismail.de>
To: Vladilen Kozin <vladilen.kozin@gmail.com>
Cc: help-guix@gnu.org, guix-devel@gnu.org
Subject: Re: Where to find dmesg and /etc contents of specific system generation?
Date: Wed, 14 Apr 2021 14:34:52 -0400 [thread overview]
Message-ID: <87o8eg90kz.fsf@dismail.de> (raw)
In-Reply-To: <CACw=CXND1w3h_0XYVrWi2SFXMmSO3vEXOch5wGmB21830fUr7w@mail.gmail.com> (Vladilen Kozin's message of "Fri, 9 Apr 2021 13:39:41 +0100")
Vladilen Kozin <vladilen.kozin@gmail.com> writes:
> Hi guix.
>
> Is it possible and where could I find contents of /etc for a specific
> system generation. Ditto dmesg of the last boot of specific
> generation? Not necessarily current generation though.
Hmmm. I suppose you could try to make a guix system vm with that
configuration, and try to fire up the vm and see what happens...I'm not
certain how helpful that would be though.
>
> In a nutshell: I have a generation that boots and works fine, but
> sadly I also have a generation that fails to boot. I'd like to debug
> the issue by looking at its dmesg as far as it had gotten and also
> checking its /etc/fstab and such seeing how the problem appears to be
> mount related.
I think guix may support connecting to a serial console, though I've
never tried it.
You're trying to run a server right? How complicated is your config?
--
Joshua Branson (joshuaBPMan in #guix)
Sent from Emacs and Gnus
https://gnucode.me
https://video.hardlimit.com/accounts/joshua_branson/video-channels
https://propernaming.org
"You can have whatever you want, as long as you help
enough other people get what they want." - Zig Ziglar
prev parent reply other threads:[~2021-04-14 18:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-09 12:39 Where to find dmesg and /etc contents of specific system generation? Vladilen Kozin
2021-04-14 18:34 ` Joshua Branson [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
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=87o8eg90kz.fsf@dismail.de \
--to=jbranso@dismail.de \
--cc=guix-devel@gnu.org \
--cc=help-guix@gnu.org \
--cc=vladilen.kozin@gmail.com \
/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).