From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
I use flatpak, pacman, and yay for my software management. I unify the basic needs by using these aliases:
SEARCH
fsearch = flatpak search <input>
psearch = pacman -Ss <input>
ysearch = yay -Ss <input>
REMOVE
fremove
premove
yremove
LIST
flist
plist
ylist
GARBAGE COLLECTION
fcg
pcg
ycg
And so on.
Additionally I also gave ucg as well as an all-in-one garbage collector command.
Quick FYI - Exa is no longer fully maintained; there is a fork called Eza which is maintained. They couldn't take over the original Exa repo as the original creator is unreachable. Eza is in many distros; I've installed it on OpenSuSe Tumbleweed with ease from the factory-oss.
Switched!
You forgot alias the_purge="sudo rm -rf /"
For French language removal?
Non! Aie pitié, je vous en supplie!
Hmmm blank comments after removing French language
Nice aliases! But I'm a fan of topgrade for updating
Why when a simple alias will do?
Laziness, mostly
I think I have a simple function in my .zshrc file that updates flatpaks and runs dnf or zypper depending on what the system uses. This file is synced between machines as part of my dotfiles sync so I don't have to install anything separate. The interface of most package managers is stable, so I didn't have to touch the function.
This way I don't have to deal with a package that's on a different version in different software repositories (depending on distribution) or manually install and update it.
But that's just me, I tend to keep it as simple as possible for maximum portability. I also avoid having too many abstraction layers.
Omg yes pls
I use lsd how is nexa?
vim
Opinion disregarded.
As an aside: I really wish flatpaks would put symlinks or something in ~/.local/bin so you could just run them without the flatpak run boilerplate.
They sorta do.
Flatpak user install puts shims in ~/.local/share/flatpak/exports/bin/. You just need to add it to your path.
I'm pretty sure flatpak system installs are at /var/lib/flatpak/exports/bin/ so you'd just add that to path.
Oh, neat. Surprised that isn't added to the default paths though.
It also still does the annoying name.like.this for binary names rather than just using normal names though.
They’re too long. Geez, learn to implement shorthand or acronyms. What are you a monster?
/roast
Added the exa aliases. Nice to see pacman points exa to eza as the former is unmaintained.
I did notice that recently and am planning to move
For the Flatpak apt upgrade how about "flapt".
I'd like to one day have the confidence to do upgrade -y
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.
True, it's just an example to always look at the output. I've definitely used that in Fedora to reinstall packages when something stopped working after an upgrade.
(Maybe this doesn't happen by itself in Debian but I wouldn't trust Ubuntu for example)
If you haven’t special requirements then just use Debian stable, and never be worried about an update again.
Or if you like beating your head against a brick wall constantly NixOS is really hard to brick. Any update that fails can just be reverted with a reboot.
Of course the downside is poor documentation, and nothing at all works like you expect it to work. It's like hey, you want to learn Linux again from scratch? And by the way no two things work the same.
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.
Ah yes, just like that time when Mandrake kernels burned the cd drives..
I believe in you
Balls of steel or ironclad backups.
Or, simply, masochism.
You forgot apathy. That's what works for me.