I updated a laptop to F34. The laptop uses the spinfinity plymouth theme. system-upgrade ran while the theme was chugging along, showing brief status messages in a top level corner, i.e. "Updating <package name>". This is my regular upgrade experience; and nothin unusual about that.
I just started the upgrade on another laptop, but after plymouth came up, it bumped down to the system console to run the upgrade. It's running now just fine, on the system console. I don't recall if this laptop always did that, some of my other servers don't use plymouth and run through upgraded on the console.
But these two laptops are both set up to use the spinfinity theme, and it's just my idle curiosity as to why one of them is running the upgrade on the console. They do use different video hardware, but it just looks nicer in plymouth, and why would video hardware matter, for something like that?
On a related note, after the first upgrade I needed to figure out why it installed a bunch of java bloat, for some reason. I didn't find the usual /root/upgrade.log, and some poking around found "dnf system-upgrade log", as its replacement.
I was surprised to see that "dnf system-upgrade log" offered me logs going all the way back to the F30-F31 upgrade in 2019. They certainly don't take up much space, but I'm just wondering if they ever get cleaned up. I don't see a dnf option to do that.
On 02/05/2021 23:09, Sam Varshavchik wrote:
I was surprised to see that "dnf system-upgrade log" offered me logs going all the way back to the F30-F31 upgrade in 2019. They certainly don't take up much space, but I'm just wondering if they ever get cleaned up. I don't see a dnf option to do that.
How far back do your journal entries go? journalctl --list-boots.
I ask since, to my knowledge, I'd not done anything to trim system-upgrade logs but had changed retention times for the journal. I only show a single upgrade log. So, related?
On Sun, May 02, 2021 at 11:09:20AM -0400, Sam Varshavchik wrote:
I just started the upgrade on another laptop, but after plymouth came up, it bumped down to the system console to run the upgrade. It's running now just fine, on the system console. I don't recall if this laptop always did that, some of my other servers don't use plymouth and run through upgraded on the console.
Looks like the graphical boot is switched off with the "rhgb" and "quiet" options for the kernel command line being removed on this machine - I think that's done via /etc/default/grub by editing the line starting with "GRUB_CMDLINE_LINUX". Maybe compare both files on the two machines: they might explain the graphical/non-graphical install ..
see https://docs.fedoraproject.org/en-US/Fedora/25/html/Installation_Guide/sect-...
Good luck, Wolfgang
Ed Greshko writes:
On 02/05/2021 23:09, Sam Varshavchik wrote:
I was surprised to see that "dnf system-upgrade log" offered me logs going all the way back to the F30-F31 upgrade in 2019. They certainly don't take up much space, but I'm just wondering if they ever get cleaned up. I don't see a dnf option to do that.
How far back do your journal entries go? journalctl --list-boots.
I ask since, to my knowledge, I'd not done anything to trim system-upgrade logs but had changed retention times for the journal. I only show a single upgrade log. So, related?
Most likely. After grinding away, --list-boots spewed out 372 entries, dating back to 2019.
I have not changed any systemd journal settings. This is the default configuraiton of this thing.
Wolfgang Pfeiffer writes:
On Sun, May 02, 2021 at 11:09:20AM -0400, Sam Varshavchik wrote:
I just started the upgrade on another laptop, but after plymouth came up, it bumped down to the system console to run the upgrade. It's running now just fine, on the system console. I don't recall if this laptop always did that, some of my other servers don't use plymouth and run through upgraded on the console.
Looks like the graphical boot is switched off with the "rhgb" and "quiet" options for the kernel command line being removed on this machine - I think that's done via /etc/default/grub by editing the line starting with "GRUB_CMDLINE_LINUX". Maybe compare both files on the two machines: they might explain the graphical/non-graphical install ..
There is nothing wrong with the regular boot. It continues to use plymouth.
This was only the reboot that ran the upgrade.
-
Ed Greshko -
Sam Varshavchik -
Wolfgang Pfeiffer