| 1 |
I suggest either taking a full dd|bzip2 style backup of the hardisk to removable media for the simplest reinstall. Compliment with borgbackup or dervish for space efficient backups to capture more recent changes. Reinstall is the reverse .. lay down the dd image update from the backups with rsync. No need to get caught in messy install routines that will take a lot longer with an uncertain outcome. I have a few arm systems and seem to be doing it at least once a month as the sdcards reach their end of life. |
| 2 |
BillK |
| 3 |
|
| 4 |
|
| 5 |
On 20 June 2022 2:26:27 am AWST, Francisco Ares <frares@×××××.com> wrote: |
| 6 |
>Em dom., 19 de jun. de 2022 às 14:33, Michael |
| 7 |
><confabulate@××××××××.com> escreveu: |
| 8 |
>> |
| 9 |
>> On Sunday, 19 June 2022 18:22:34 BST Grant Edwards wrote: |
| 10 |
>> > On 2022-06-19, Francisco Ares <frares@×××××.com> wrote: |
| 11 |
>> > > Just for the sake of preventing a future failure, besides personal |
| 12 |
>> > > files (minimum and obvious) the "world" file and the binary packages, |
| 13 |
>> > > built along with the package installation, what else should I backup |
| 14 |
>> > > so that I would be able to quickly restore the same full working |
| 15 |
>> > > Gentoo in a new hardware without having to work from stage3 up? The |
| 16 |
>> > > portage tree is one of those items, for sure. But what else? |
| 17 |
>> > |
| 18 |
>> > Make a backup copy of everything under /etc. |
| 19 |
>> > |
| 20 |
>> > I used to try to backup individual /etc/... files that I would need, |
| 21 |
>> > but I always forgot something. |
| 22 |
>> > |
| 23 |
>> > -- |
| 24 |
>> > Grant |
| 25 |
>> |
| 26 |
>> Yes, besides /var/lib/portage/world and /etc/ you may also want to back up |
| 27 |
>> your /boot and kernel config, assuming the hardware (MoBo & peripherals) is the |
| 28 |
>> same (same drivers). I wouldn't bother backing up portage, a resync will |
| 29 |
>> download it afresh. You might want to save /distfiles if you're on a slow |
| 30 |
>> Internet link, but it has to be a copy of the current versions, otherwise the |
| 31 |
>> latest version of each package source will have to be downloaded anyway. |
| 32 |
>> |
| 33 |
>> If you're running databases you'll also want to keep a backup of the |
| 34 |
>> respective /var/lib/*sql directory and if you're running a webserver /var/www/ |
| 35 |
>> * - but you would be aware of the need to keep a fresh backup of all this data |
| 36 |
>> anyway. |
| 37 |
> |
| 38 |
>Also good point, one can always do a "make oldconfig" on a new kernel |
| 39 |
>to recover specific tweaks. |
| 40 |
> |
| 41 |
>Regarding backing up the portage tree, the binary packages won't do |
| 42 |
>much if the last sync is, say, one or two months old or even worse if |
| 43 |
>older. To use "emerge -K" one must have the same package version built |
| 44 |
>in the binary package as the one present in portage. That's what I'm |
| 45 |
>facing right now, it seems my binary packages won't be so helpful |
| 46 |
>after all - I'm beginning to think I'll have to go back to stage-3... |
| 47 |
> |
| 48 |
>Thanks! |
| 49 |
>Francisco |
| 50 |
> |
| 51 |
|
| 52 |
-- |
| 53 |
Sent from my Android device with K-9 Mail. Please excuse my brevity. |
Archives