Linux Notes
The basics:
sudo apt-get update
sudo apt-get upgrade
sudo apt-get autoremove
sudo apt-get clean
I've read arguments back & forth about systemd for years but never learned enough to take a side, or take any kind of action, until I set about troubleshooting a laptop. I just learned the commands
systemd-analyze
systemd-analyze blame, which is much more useful as systemd-analyze blame > blame.txt, where it writes the conclusions out to a text file.
The command > <filename>.txt after a command writes the output of the command to a text file in the home folder. It is handy any time a command puts out too much feedback to read in the console.
systemd-analyze critical-chain draws a tree-like structure that identifies troublemakers in the boot process:
graphical.target @1min 24.661s
└─multi-user.target @1min 24.660s
└─snapd.seeded.service @43.113s +41.544s
└─basic.target @41.198s
└─sockets.target @41.198s
└─snapd.socket @41.178s +20ms
└─sysinit.target @40.891s
└─systemd-resolved.service @38.873s +2.017s
└─systemd-tmpfiles-setup.service @35.961s +2.888s
└─systemd-journal-flush.service @9.336s +26.549s
└─systemd-remount-fs.service @8.947s +318ms
└─systemd-journald.socket @8.805s
└─system.slice @8.713s
└─-.slice @8.713s
To fix what may be a continuing problem:
snap list > snap.txt. This lists all snap packages installed. In the late 20-teens I bought a Dell laptop with Ubuntu installed. It was great for a while but recently its performance has rapidly degraded. I'm trying to determine whether it is from too much Snap cruft, or poorly implemented Snap software, or if updating from Ubuntu 22.04 LTS to 24.04 LTS was a bad move.