alias alias-edit="vim ~/.local/config/alias_config && source ~/.local/config/alias_config && echo 'Alias updated. \n'"
alias ls="exa"
alias find="fdfind"
alias battery-full="system76-power charge-thresholds --profile full_charge"
alias battery-balanced="system76-power charge-thresholds --profile balanced"
alias battery-maxhealth="system76-power charge-thresholds --profile max_lifespan"
alias update-flatapt="sudo apt update && sudo apt upgrade -y && flatpak update --assumeyes"
alias tree="exa --tree"
alias devi-do="sudo incus exec dev0 -- su -l devi"
alias code="flatpak run com.visualstudio.code"
~
I’d like to one day have the confidence to do
upgrade -yIf you haven’t special requirements then just use Debian stable, and never be worried about an update again.
Headline: MAJOR EXPLOIT FOUND IN NEW LINUX KERNEL VERSION!
Debian: business as usual…
TBH I don’t even remember the last time some actually important bug came out on the kernel, long gone are the days of ptrace-kmod.c and hatorihanzo.c
A while back, somewhere around Linux 5.17, some Intel chips in laptops caused the Linux kernal to rapidly set backlight brightness to 100% then zero. This flashing would likely cause it to break. That’s the last one I remember only a year or so ago.
This only effected arch an it’s varients to my knowledge though, as they were the first to recieve the update, and it was fixed very quickly. To my knowledge nobodies systems were broken from this.
Balls of steel or ironclad backups.
Or, simply, masochism.
I always do that. Is that bad on pop os/fedora? I wouldn’t know any different. Selectively choose what to update?
Apparently apt has a stroke sometimes. I don’t think I’ve had an update fuck up this bad but it’s better to read the output so you know what changed in case something stops working.
That’s by no means a routine upgrade though, the guy just “upgraded to” backports which you’re not even supposed to do. Not comparable to the soothingly boring apt upgrade of Debian stable.
I believe in you