arnaudlevy/quentin.dufour.io
1
0
Fork 0
forked from quentin/quentin.dufour.io
Code Pull requests 1 Activity

More precision

Browse source
This commit is contained in:
Quentin Dufour 2017-11-25 17:47:12 +01:00
parent 298c2aaf66
commit ac9edf5ebe
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
_posts/2017-11-25-upgrade-fedora-online.md
View file

@ -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.