From ac9edf5ebe47be68e5f91a54541eb2f2a5aef74b Mon Sep 17 00:00:00 2001 From: Quentin Dufour Date: Sat, 25 Nov 2017 17:47:12 +0100 Subject: [PATCH] More precision --- _posts/2017-11-25-upgrade-fedora-online.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/_posts/2017-11-25-upgrade-fedora-online.md b/_posts/2017-11-25-upgrade-fedora-online.md index db72024..f5bd3ea 100644 --- a/_posts/2017-11-25-upgrade-fedora-online.md +++ b/_posts/2017-11-25-upgrade-fedora-online.md @@ -26,8 +26,8 @@ Just after the segfault, my computer rebooted on Fedora 26. *Some information presented here could be not totally accurate. If you have a doubt, please follow the links.* -`dnf-system-upgrade` use a feature of systemd described here: [Implementing Offline System Updates](https://www.freedesktop.org/software/systemd/man/systemd.offline-updates.html). -By creating a symlink named `/system-update`, at the next reboot systemd will boot to a specific target named `system-update.target` +`dnf-system-upgrade` uses a feature of systemd described here: [Implementing Offline System Updates](https://www.freedesktop.org/software/systemd/man/systemd.offline-updates.html). +By creating a symlink named `/system-update`, at the next reboot systemd will boot to a specific target named `system-update.target`. That's what we name "an offline upgrade" contrary to an upgrade run in the `default.target` which I call "an online upgrade". But when will this symlink created ? When you run the following command: @@ -69,7 +69,7 @@ I didn't have any idea to debug this segfault in the offline mode. So I searched a way to run this command on an online system. If the command segfaults, I'll have some tools to investigate it. If the command works, I'll have an upgraded system. -In my case, everything went well. +In my case, once run online, everything went well. Before typing any command, you must know that this tool is not intended to be run this way.