aboutsummaryrefslogtreecommitdiff
path: root/content/docs/gentoo/upgrades.md
diff options
context:
space:
mode:
authorJulien Dessaux2023-04-23 22:33:49 +0200
committerJulien Dessaux2023-04-23 22:34:10 +0200
commitea435049b3a3f5057b3a894040df3cf4f3256d9e (patch)
tree9046430870fa050e6568fcfbe409f8a8d295d0b3 /content/docs/gentoo/upgrades.md
parentDocument the second gotosocial backup job (diff)
downloadwww-ea435049b3a3f5057b3a894040df3cf4f3256d9e.tar.gz
www-ea435049b3a3f5057b3a894040df3cf4f3256d9e.tar.bz2
www-ea435049b3a3f5057b3a894040df3cf4f3256d9e.zip
Refactored syntax highlighting shortcodes into markdown
Diffstat (limited to 'content/docs/gentoo/upgrades.md')
-rw-r--r--content/docs/gentoo/upgrades.md12
1 files changed, 6 insertions, 6 deletions
diff --git a/content/docs/gentoo/upgrades.md b/content/docs/gentoo/upgrades.md
index 83f3c56..4984cd7 100644
--- a/content/docs/gentoo/upgrades.md
+++ b/content/docs/gentoo/upgrades.md
@@ -9,24 +9,24 @@ tags:
## Introduction
Here is my go to set of commands when I upgrade a gentoo box :
-{{< highlight sh >}}
+```sh
emerge-webrsync
eselect news read
-{{< /highlight >}}
+```
The news have to be reviewed carefully and if I cannot act on it immediately I copy paste the relevant bits to my todolist.
## The upgrade process
I run the upgrade process in steps, the first one asking you to validate the upgrade path. You will also be prompted to validate before cleaning :
-{{< highlight sh >}}
+```sh
emerge -qAavutDN world --verbose-conflicts --keep-going --with-bdeps=y && emerge --depclean -a && revdep-rebuild -i -- -q --keep-going; eclean --deep distfiles && eclean --deep packages && date
-{{< /highlight >}}
+```
After all this completes it is time to evaluate configuration changes :
-{{< highlight sh >}}
+```sh
etc-update
-{{< /highlight >}}
+```
If a new kernel has been emerged, have a look at [the specific process for that]({{< ref "kernel_upgrades" >}}).