Hello, i was wondering if eos-update will just update everything as i’m trying to maintain my system and keep everything up-to-date
My apologies if this sounds dumb as this is my first time using EndeavourOS or anything arch-based (and arch in general), i did just run eos-update just now but y’know i wanna make sure running eos-update was one of the correct ways to update everything on it.
Hoping to hear back!
Yes, eos-update will update your system. More infos here: Eos-update news
Welcome to the community @Sentry64 
To ensure it updates AUR applications too, run it with:
eos-update --yay
If using that, then yes it’s a thorough update.
ohh alright, thanks for the reply!!
oh that’s useful, thank you for the tip!! i’ll be sure to use that to check!!
thanks for the welcome aswell!! so far my experience with endeavouros is pretty nice! i’d say it’s a good introduction to arch aswell too!
From eos-update source code:
# eos-update
Package updater for EndeavourOS and Arch.
Basically does about the same as
sudo pacman -Syu
with some additional features:
- updates Arch and EndeavourOS keyrings first (if needed)
- manages pacman db lock
- checks available disk space
- runs `sync` after update
and optionally
- updates AUR packages with the given AUR helper (`yay` or `paru`)
- checks update compatibility between Nvidia driver and kernel (only on EndeavourOS)
- clear package databases, see option `--clear-databases`
- reset keyrings, see option `--keyrings-reset`
- check for unsupported mirrors in files (option `--check-mirrors`)
- /etc/pacman-d/mirrorlist
- /etc/pacman.d/endeavouros-mirrorlist
## Synopsis
eos-update [options]
## Options
--help, -h This help.
--check-mirrors Check files /etc/pacman.d/endeavouros-mirrorlist and /etc/pacman.d/mirrorlist
for unsupported mirrors.
This may be useful when one or more mirrors start failing unexpectedly.
Note: only x86_64 hardware is supported.
--check-mirrors-eos Check file /etc/pacman.d/endeavouros-mirrorlist for unsupported mirrors.
--check-mirrors-arch Check file /etc/pacman.d/mirrorlist for unsupported mirrors.
--nvidia Check also nvidia driver vs. kernel updates. Useful only with the Nvidia GPU.
--clear-databases Clears package database files.
Use this only if package database issues constantly make system update fail.
--keyrings-reset Resets Arch and EndeavourOS keyrings.
Use this only if keyring issues constantly make system update fail.
--no-keyring Do not try to update keyrings first.
--no-sync Do not run 'sync' after update.
--show-only-fixed Show only packages that have already been fixed (runs: arch-audit -u) and exit.
--show-upstream-news Show the news page of the upstream site and exit.
--helper AUR helper name. Supported: yay, paru, pacman.
Default: pacman
Other AUR helpers supporting option -Sua like yay should work as well.
--paru Same as --helper=paru.
--yay Same as --helper=yay.
--aur Uses the AUR helper configured in /etc/eos-script-lib-yad.conf.
--pacman Same as --helper=pacman. Default. (Note: pacman does not support AUR directly).
--min-free-bytes Minimum amount of free space (in bytes) that the root partition should have
before updating. Otherwise a warning message will be displayed.
Default: 1000000000
# basic update for native packages
eos-update
# update also packages from the AUR
eos-update --aur
# check and report the validity of the configured Arch and EndeavourOS mirrors
eos-update --check-mirrors
``
One more question though, should i run the update everyday? or weekly cause i remember hearing somewhere that some people should update stuff at least weekly but i was wondering if updating daily would be better and/or if it wouldn’t hurt anything, hope this isn’t a dumb question to ask
I update daily because if I have to roll back, there’s less to roll back.
Update whenever you like. There is no best practice. Once a week is fine. Every day is fine. Multiple times a day is fine.
If there is some really bad bug or security vulnerability the arch team usually puts out news on their website and people will talk about it here.
Welcome to the forum 
You could install
eos-update-notifier
And configure it to set it to get notified about updates, on whatever frequency you like (hourly, daily, weekly).
But if you want to avoid large updates, update at least once a week would be adviceable I think.
I would install Tograde cause it will update all the odd ones eos-update does not including anything you have installed from the AUR, so you can run eos-update then topgrade after eos-update done. Example below of what was updated.
System updated! 🐧
── 02:54:31 - Configuration update ─────────────────────────────────────────────
── 02:54:31 - snap ─────────────────────────────────────────────────────────────
All snaps up to date.
WARNING: There is 1 new warning. See 'snap warnings'.
── 02:54:31 - Firmware upgrades ────────────────────────────────────────────────
Updating lvfs
Downloading… [***************************************]
Successfully downloaded new metadata: Updates have been published for 0 of 3 local devices
Devices with no available firmware updates:
• CT1000P3SSD8
• CT1000T500SSD8
• SSD 990 EVO 2TB
No updatable devices
── 02:54:34 - Flatpak User Packages ────────────────────────────────────────────
Looking for updates…
Nothing to do.
── 02:54:34 - Flatpak System Packages ──────────────────────────────────────────
Looking for updates…
ID Branch Op Remote Download
1. [✓] org.freedesktop.Platform.GL.default 24.08 u flathub 3.2 MB / 156.8 MB
2. [✓] org.freedesktop.Platform.GL.default 24.08extra u flathub 2.0 MB / 156.8 MB
3. [✓] org.freedesktop.Platform.GL.nvidia-570-124-04 1.4 u flathub 375.6 MB / 376.7 MB
Updates complete.
── 02:55:08 - TLDR ─────────────────────────────────────────────────────────────
Successfully updated cache.
── 02:55:11 - Visual Studio Code extensions ────────────────────────────────────
No extension to update
── 02:55:11 - Node Package Manager ─────────────────────────────────────────────
── 02:55:11 - Yarn Package Manager ─────────────────────────────────────────────
── 02:55:11 - micro ────────────────────────────────────────────────────────────
Checking for plugin updates
Nothing to install / update
── 02:55:11 - Lensfun's database update ────────────────────────────────────────
Info: root privileges needed for updating the system database.
Info: updating user DB in '/home/cccp/.local/share/lensfun/updates'
Reading http://lensfun.sourceforge.net/db/versions.json …
Reading http://wilson.bronger.org/lensfun-db/versions.json …
Info: No newer database was found for last installed Lensfun.
── 02:55:17 - Summary ──────────────────────────────────────────────────────────
System update: OK
config-update: OK
snap: OK
Firmware upgrades: OK
Flatpak: OK
TLDR: OK
Visual Studio Code extensions: OK
micro: OK
Lensfun's database update: OK
Note that eos-update-notifier is not really needed because updates are coming many times a day.
But eos-update-notifier might be useful before a new user finds the ways to do the basic maintenance.
To say something about update frequency: you can choose when to update but I’d recommend updating at least once a month. Also weekly or daily is OK.
And eos-update does native and AUR packages. Flatpaks or snaps are not handled.
My answer to this is yes.
I run updates even several times a day. I want to install the new packages as soon as they are available in the repos for whatever bug and security fixes they bring.
For some critical stuff like kernels, web browsers, mail clients, I want them to get updates as soon as possible for bug and security fixes. I sometimes even update them from testing repos like I just did with Firefox.
It is also easy enough to do, so why not. I don’t see the point of using a bleeding edge distro when you don’t update your system for weeks or months and run outdated software .