From: Helmut Jarausch <jarausch@skynet.be>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] How to repair a 'secondary Gentoo system'
Date: Mon, 11 Dec 2017 17:23:21 +0100 [thread overview]
Message-ID: <IPO57E5D.DPGFOKUV.QX4KF6NM@BOQMTVBL.P757M3U6.IANNQ7AA> (raw)
Hi,
I have built a 'secondary' GenToo system on a separate partition. (This
system contains far less packages and uses only CFLAGS for the older
hardware of my wife's laptop).
Until now I've always chrooted into that folder; there I've updated
Gentoo regularly.
But now, don't ask me why,
chroot /OtherGentoo /bin/bash
dies of a segment fault.
Is there any means to repair such a Gentoo system short of rebuilding
it (nearly) from scratch?
Can one use Gentoo's prefix feature?
Many thanks for a hint,
Helmut
next reply other threads:[~2017-12-11 16:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-11 16:23 Helmut Jarausch [this message]
2017-12-11 16:58 ` [gentoo-user] How to repair a 'secondary Gentoo system' David Haller
2017-12-11 19:12 ` Helmut Jarausch
2017-12-11 19:45 ` David Haller
2017-12-11 20:56 ` Rich Freeman
2017-12-11 20:06 ` Dale
2017-12-12 1:45 ` [gentoo-user] " Kai Krakow
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=IPO57E5D.DPGFOKUV.QX4KF6NM@BOQMTVBL.P757M3U6.IANNQ7AA \
--to=jarausch@skynet.be \
--cc=gentoo-user@lists.gentoo.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