I installed endeavour os around 15 days ago but didn’t run eos-update because at that time there was a attack on aur.
Can I now update my eos using eos-update
If you just use eos-update it will not update the aur. To update the aur use eos-update --aur. If you have nothing installed from the aur, it won’t pull anything from there.
If you plan to use the aur, learn to read pkgbuilds and spot red flags.
Ok and it is safe to update after 15 days later or it will break my dual booted system with eos and linux mint
I hope you and some others can find this useful.
One thing worth keeping in mind with the Arch Wiki is that it documents everything historically, including maintenance steps that aren’t meant to be part of a normal routine. Stuff like aggressively removing “unused” symlinks or cleaning out old config files can cause more harm than good — useful to understand, but not something most users should actually do.
For updates, the biggest thing is avoiding partial upgrades. Syncing the pacman database with pacman -Sy just to check for updates is exactly how partial updates happen. Instead, use checkupdates, which safely checks for updates without touching your system state.
The rest of the advice in the thread is solid — especially eos-update and eos-update --aur if you rely on AUR packages. It keeps everything consistent and avoids the “half-updated AUR package breaks something” problem.
On the AUR side, malware is unfortunately a real issue now, so it’s worth glancing at PKGBUILDs before installing. The big red flags are:
-
curl/wget to unknown URLs
-
install scripts that run as root
-
random binaries included in the repo
-
commands modifying system directories outside $pkgdir
If something looks off, it probably is.
And regarding dual‑booting: keeping Windows and Linux on the same EFI partition works, but Windows has a habit of overwriting boot entries during updates. It’s much safer to put them on separate disks and use your firmware’s boot‑device hotkey or reorder entries in the BIOS. Zero drama, zero surprise “Windows ate my bootloader” moments.
Just wanted to add my thoughts to this quickly:
Run checkupdates weekly and look at the output carefully.
If all looks good, run sudo pacman -Syu
If core packages like the kernel have been updated you can restart with systemctl reboot
My main advice is to stick with the official repos and not install from the AUR or other sources.
Been doing it like this for a long time and never once had an issue.
Just being curious how you make the judgement if a update looks good or not.
Are you capable of determin if a e.g. a kernel update will cause a regression on your system up front ?
Or do you do some investigation if that could possibly happen ?
If you are able to answer this questions with : I certainly do I would take my hat of for you.
On another note I always just use reboot
BTW. If I see firmware update. I hold it until kernel update also showup.
Well that is your call, never done that and never had any problem because i did not do that. and also those updates might be (relatively) far apart. Also think that a kernel will be able to support the hardware but to get some “extra features” you would be needing the firmware, but I could be wrong about that.
Got few times kernel panic because of wifi firmware update.
And maybe something else.
Patriculary in regards kernel lags behing firmware packages.