From: nicolagi@sdf.org
To: 9front@9front.org
Subject: [9front] How to rollback?
Date: Sun, 13 Dec 2020 15:14:23 +0000 [thread overview]
Message-ID: <A3F4207C8748F2AC1722AE4B5EBEC976@sdf.org> (raw)
Hi all,
it's clear to me from the FQA how to compile the system from sourceces
and upgrade the system. I've done it a few times in VMs in the past.
Now that I have a stable system that I use every day, I'm more
concerned I might break it. People here seem to be trying kernel
patches all the time... so it must be possible to safely rollback in
case of problems. How does one do that? Suppose I upgrade the system
and it hangs on reboot; how does one rollback?
I'll take this opportunity to add another question. I have a Unicomp
Model M keyboard and sometimes I get spurious key repeats, see
resulting “sourceces” typo above. It doesn't happen with other
keyboards (but I'd rather use this one). Any hint as to how I might
debug this, or provide useful information?
Thank you,
Nicola
next reply other threads:[~2020-12-13 15:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-13 15:14 nicolagi [this message]
2020-12-13 15:30 ` Sigrid Solveig Haflínudóttir
2020-12-13 15:54 ` nicolagi
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=A3F4207C8748F2AC1722AE4B5EBEC976@sdf.org \
--to=nicolagi@sdf.org \
--cc=9front@9front.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 NNTP newsgroup(s).