On Tue, Aug 30, 2016 at 3:19 PM, Felix Miata <mrmazda(a)earthlink.net> wrote:
Kamil Paral composed on 2016-08-30 06:24 (UTC-0400):
>> Following the instructions on
>>
https://fedoraproject.org/wiki/DNF_system_upgrade
>> eventually I reached
>> dnf system-upgrade download --refresh --releasever=25
>> which apparently completed without error, ending by directing to run
>> dnf system-upgrade reboot.
>> So, I did, and it booted normally. Nothing is running that isn't supposed to
>> be running in a normal boot.
>> dnf system-upgrade log
>> reports no logs found. The only dnf string in journalctl -b is starting the
>> makecache timer. This is not the first time I've tried those wiki page
>> instructions exactly like this with same result. What's supposed to be
>> happening that isn't?
> It's supposed to boot into an offline updates mode, and do the upgrade.
> Please file a bug and attach logs ("journalctl -b -1" after you boot into
> standard desktop instead of offline updates mode). Thanks.
What I was looking for is the process that triggers "offline updates mode".
If it involves the bootloader, I know whatever it may be simply doesn't
exist. This is a multiboot installation, so no Fedora bootloader is involved
in its boot process. If not bootloader related, I'll go ahead and file a bug,
or even if it is, but you indicate you want one anyway.
What triggers it is the creation of /system-update symlink and a
reboot. Then systemd picks that up and for that boot considers
system-update.target the default target.
--
Chris Murphy