From: Francisco Ares <frares@gmail.com>
To: gentoo-user <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] Re: Reinstall
Date: Sun, 19 Jun 2022 15:26:27 -0300 [thread overview]
Message-ID: <CAHH9eM5NDLpJK=LUXtvHi06umMpLr2SPp48X9AjYo=sMHXsvOw@mail.gmail.com> (raw)
In-Reply-To: <9002850.rMLUfLXkoz@lenovo.localdomain>
Em dom., 19 de jun. de 2022 às 14:33, Michael
<confabulate@kintzios.com> escreveu:
>
> On Sunday, 19 June 2022 18:22:34 BST Grant Edwards wrote:
> > On 2022-06-19, Francisco Ares <frares@gmail.com> wrote:
> > > Just for the sake of preventing a future failure, besides personal
> > > files (minimum and obvious) the "world" file and the binary packages,
> > > built along with the package installation, what else should I backup
> > > so that I would be able to quickly restore the same full working
> > > Gentoo in a new hardware without having to work from stage3 up? The
> > > portage tree is one of those items, for sure. But what else?
> >
> > Make a backup copy of everything under /etc.
> >
> > I used to try to backup individual /etc/... files that I would need,
> > but I always forgot something.
> >
> > --
> > Grant
>
> Yes, besides /var/lib/portage/world and /etc/ you may also want to back up
> your /boot and kernel config, assuming the hardware (MoBo & peripherals) is the
> same (same drivers). I wouldn't bother backing up portage, a resync will
> download it afresh. You might want to save /distfiles if you're on a slow
> Internet link, but it has to be a copy of the current versions, otherwise the
> latest version of each package source will have to be downloaded anyway.
>
> If you're running databases you'll also want to keep a backup of the
> respective /var/lib/*sql directory and if you're running a webserver /var/www/
> * - but you would be aware of the need to keep a fresh backup of all this data
> anyway.
Also good point, one can always do a "make oldconfig" on a new kernel
to recover specific tweaks.
Regarding backing up the portage tree, the binary packages won't do
much if the last sync is, say, one or two months old or even worse if
older. To use "emerge -K" one must have the same package version built
in the binary package as the one present in portage. That's what I'm
facing right now, it seems my binary packages won't be so helpful
after all - I'm beginning to think I'll have to go back to stage-3...
Thanks!
Francisco
next prev parent reply other threads:[~2022-06-19 18:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 9:57 [gentoo-user] Reinstall Francisco Ares
2022-05-11 11:06 ` Michael
2022-05-11 12:26 ` David Palao
2022-05-11 16:45 ` Laurence Perkins
2022-05-11 18:34 ` Neil Bothwick
2022-05-11 20:34 ` Laurence Perkins
2022-05-11 20:51 ` Wols Lists
2022-06-19 16:23 ` Francisco Ares
2022-06-19 17:22 ` [gentoo-user] Reinstall Grant Edwards
2022-06-19 17:32 ` Michael
2022-06-19 18:26 ` Francisco Ares [this message]
2022-06-20 5:01 ` Bill Kenworthy
2022-06-19 18:08 ` Francisco Ares
2022-06-20 17:28 ` [gentoo-user] Reinstall Laurence Perkins
2022-05-11 14:32 ` Peter Humphrey
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='CAHH9eM5NDLpJK=LUXtvHi06umMpLr2SPp48X9AjYo=sMHXsvOw@mail.gmail.com' \
--to=frares@gmail.com \
--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