Talk:Fix my Gentoo

Note
Before creating a discussion or leaving a comment, please read about using talk pages. To create a new discussion, click here. Comments on an existing discussion should be signed using ~~~~:

A comment [[User:Larry|Larry]] 13:52, 13 May 2024 (UTC)
: A reply [[User:Sally|Sally]] 05:15, 7 December 2024 (UTC)
:: Your reply ~~~~

Changes to /mnt/home/rescue/etc/portage

Talk status

This discussion is still ongoing as of 26 November 2017.

By having a copy to duplicate /mnt/gentoo/etc/portage in /mnt/home/rescue/etc/portage, any changes in the rescue /etc/portage will not be reflected back to /mnt/gentoo/etc/portage.

Is this intentional? So as to stop any self inflicted damage?

What about having a bind mount or hard link between the /etc/portage directories?

or is there some other procedure to better allow this to occur? --Russelld (talk) 07:40, 26 November 2017 (UTC)

bind mount or hardlink will probably modify your original system with the rescue changes (when in chroot you activate the binpkgs features in make.conf file for example)

copy command should be "cp -r /mnt/gentoo/etc/portage /mnt/gentoo/home/rescue/etc"

--Jlandru (talk) 09:22, 25 August 2022 (UTC)

Installing packages into a system too broken to chroot into

I think this page lacks descriptions of how to handle a system that is too broken to chroot into.

Just this weekend, I managed to break linkage to glibc. That was entirely my fault of course, none-the-less, I still needed a way to fix it.

To fix it, I started out pretty much as explained here - Boot from a live USB, mount the broken system to /mnt/gentoo. But then, chrooting into it didn't work, since none of the shells were working since their linking was broken. So instead I used the live sytem's portage with emerge --root=/mnt/gentoo --sysroot=/mnt/gentoo --config-root=/mnt/gentoo to install a working copy of glibc.