I don’t even know when was the last time the desktop environment crashed or couldn’t be started.
1 Like
Yeah, to knock on wood, me neither.
1 Like
@fbodymechanic This one of the most interesting posts I have seen.
As the title says, it is for me!
1 Like
Allow me to add what I found [in this post here]
EDIT: Before doing this please see the posts below
(System clean up & Maintenance - #20 by joekamprad): (by @joekamprad )
yay -Sc
rm -rf .cache/*
However, I would consider the following:
2 Likes
Oh… sorry… if @dalto says so, so better not use it. It sounds logical.
(but I gave a reference where I got it and I didn’t see such warning there…)
Anyway it is good we know it now.
Thanks
UPDATE: I edited my post above accordingly.
2 Likes
I count my self lucky. After I did this before I saw your post/warning, I just rebooted and it went fine…
Many thanks for the warning. And I hope people will consider my edit above and I would not be a cause of any trouble to anybody.
Thanks again.
1 Like
Just stick to the OP. That’s more than you need for regular system maintenance. All these “additions” do more harm than good.
The only possible criticism I could have towards the method in the OP is that it contains too much stuff, not too little. So any additions really just make it worse.
My advice: unless you desperately need storage space, don’t bother clearing your caches. You get no benefit from that, except some free space. When you are making a backup of your home directory, do not include the cache, of course. Removing junk on Linux does not make it run faster (uninstalling orphan packagess does make updating faster, of course).
4 Likes
Yes, while they surely have their uses, neither of these I would recommend under the umbrella of “normal maintenance.”
3 Likes
Reading again that reference (bold are mine):
Indeed these commands should not be used for regular maintenance:
Delete Pacman Cache
pacman/yay -Sc/cRemove Orphan packages
sudo pacman -Rns $(pacman -Qtdq)Clean the Cache
rm -rf .cache/*
Yes… I understood it as not day to day maintenance, that is what I understood from “regular”, so I thought it can be done once or when needed!
You can use then whenever you need, iff you are completely aware of what are good and bad of those commands, and how they can affect your system.
A famous person had wisely said that: your system, your rule ! Hence, it is all up to you, but the explanation provided by @fbodymechanic is entirely sufficient for taking care of system.
the famous person I told is @Shjim
2 Likes
I won’t ever run them again, I promise, after the warning from @dalto that @pebcak mentioned.
I will never do it especially I am just 3 months old with Arch based distros!
1 Like
Nope, you can run them, but the trouble with them is that they remove many things from system, by which restoring system after any trouble causes difficulty to fix them, like they can potentially remove journalctl logs and many others, hence use of those commands are not recommended.
You are more knowledgeable than me as I had joined EndeavourOS in February this year, and I had directly arrived here from Windows only !!
1 Like
Well, you are 6 months old! But I think it is a good step. You will never regret it and will never look back.
I am on Linux since 2000 (Suse), and I never looked back.
But though I have been that long on Linux, Arch is absolutely different in many things.
So, I am learning from scratch!
Honestly, I said many times I have been distro hopping for almost a year, tried almost every thing (RPM, DEB, BSD, Gentoo, Slackware…) but I found Arch based are the best and EndeavourOS is the best of the best. Above all, the community here is wonderful.
4 Likes
Only when it comes to package management and the rolling release model of updating.
In every other regard, Arch is just a normal soystemd-based GNU/Linux OS.
As far as I know, there is no AUR in other distros. IT is only repos for packages to be just installed. Nothing compiled/built on your machine.
…
On Gentoo, almost everything is compiled/built on your machine.
Also, building packages from the AUR with makepkg is very similar to building packages for Debian with dpkg-buildpackage. It’s hardly a unique concept, it’s just one that is executed the best.
Many packages in the AUR are distributed as binaries (though the packaging is still done locally, of course, there is no compiling).
2 Likes
FIrst let me say thank you for this idiot’s guide from myself, an idiot. I’m one month into a reinstall and am naturally big on digital housekeeping.
ok -Rns is Endeavour’s way of saying these are un-necessary orphan?s then why do I have to check them first?
sudo pacman -Rns $(pacman -Qdtq)
[sudo] password for drunkenvicar:
checking dependencies...
:: lv2 optionally requires python-lxml: for lv2specgen.py
:: networkmanager-openconnect optionally requires libnma-gtk4: GUI support (GTK 4)
:: networkmanager-openvpn optionally requires libnma-gtk4: GUI support (GTK 4)
:: python-pyqt5 optionally requires qt5-declarative: QtQml, qmlplugin
Package (57) Old Version Net Change
c-ares 1.19.1-1 -0.48 MiB
compiler-rt 16.0.6-2 -36.95 MiB
docbook-xml 4.5-9 -1.96 MiB
docbook-xsl 1.79.2-7 -26.32 MiB
gnome-autoar 0.4.4-1 -0.53 MiB
itstool 1:2.0.7-1 -0.09 MiB
kwindowsystem 5.110.0-1 -1.81 MiB
libgdm 44.1-1 -0.62 MiB
libieee1284 0.2.11-15 -0.12 MiB
libnma-gtk4 1.10.6-2 -0.45 MiB
mallard-ducktype 1.0.2-9 -0.62 MiB
net-snmp 5.9.1-8 -8.56 MiB
ninja 1.11.1-3 -0.35 MiB
python-attrs 22.2.0-3 -0.55 MiB
python-coverage 6.5.0-5 -1.68 MiB
python-iniconfig 2.0.0-4 -0.04 MiB
python-jsonschema-specifications 2023.7.1-1 -0.05 MiB
python-lxml 4.9.2-3 -5.08 MiB
python-pluggy 1.3.0-1 -0.20 MiB
python-pyrsistent 0.19.3-3 -0.64 MiB
python-pytest 7.4.2-1 -4.01 MiB
python-referencing 0.30.2-1 -0.39 MiB
python-rpds-py 0.10.3-1 -0.64 MiB
python-tqdm 4.66.1-2 -0.65 MiB
qt5-declarative 5.15.10+kde+r31-1 -23.57 MiB
qt5-graphicaleffects 5.15.10-1 -0.53 MiB
qt5-quickcontrols2 5.15.10+kde+r6-1 -8.73 MiB
wasi-libc 1:0+328+1dfe5c3-1 -1.32 MiB
yelp-xsl 42.1-1 -1.34 MiB
appstream-glib 0.8.2-3 -3.74 MiB
autoconf2.13 2.13-7 -0.60 MiB
cbindgen 0.26.0-1 -3.82 MiB
clang 16.0.6-1 -209.20 MiB
fishui 0.8-1 -0.79 MiB
gnome-shell 1:44.5-1 -11.54 MiB
gptfdisk 1.0.9-2 -0.66 MiB
imake 1.0.9-2 -1.24 MiB
libmfx 23.2.2-2 -0.28 MiB
libnautilus-extension 44.2.1-1 -0.23 MiB
lld 16.0.6-1 -6.54 MiB
mercurial 6.5.2-1 -35.24 MiB
meson 1.2.1-1 -13.09 MiB
nasm 2.16.01-1 -3.23 MiB
nodejs 20.7.0-1 -58.64 MiB
python-jsonschema 4.19.1-1 -1.36 MiB
python-pytest-cov 4.1.0-1 -0.16 MiB
python-testfixtures 7.2.0-1 -2.05 MiB
re2 1:20230901-2 -0.40 MiB
rust 1:1.72.1-1 -463.38 MiB
sane 1.2.1-5 -18.29 MiB
wasi-compiler-rt 16.0.6-2 -0.10 MiB
wasi-libc++ 16.0.6-1 -7.58 MiB
wasi-libc++abi 16.0.6-1 -0.34 MiB
webkit2gtk 2.42.1-1 -107.36 MiB
xorg-server-xvfb 21.1.8-2 -1.91 MiB
yasm 1.3.0-6 -4.33 MiB
yelp-tools
OK, I’ll bite. What is Yasm, Alex?
pacman -Si yasm
....
Depends On : glibc
........
ok let’s check glibc, which is not on the orpan-remove list…
pacman -Si glibc
.....
linux-api-headers>=4.10 tzdata filesystem
.....
now I’m really confused…shouldn’t I be looking at reverse deps to make these removal decisions?
and if so, then pacman -Si packagex does not show reverse deps.
How do I make a good decision on what I can get rid of in the -Rns list?
thanks!