I ordered something from someone awhile back and it came with a free flash drive in the shape of a credit card. It had pictures of puppies on it so naturally it's a puppy linux drive now.
This is entirely irrelevant but hopefully someone gets a smile out of it.
is there a way to make it work like a rolling release of sorts? i'd want to use debian, but i don't want to stay with old packages and wait 2 years for an update
You could use debian testing. It's a somewhat "rolling-release" model. You will get more up to date packages with more stability too.
You could also use unstable, but I wouldn't recommend it personally.
Edit: if you really need the most up to date version of some packages, you can pin them to use the unstable repo. This would be a pretty reasonable solution.
This is literally me calling a marine "Jarhead" or "grunt". Sorry, military habits never die. I'm showing them love by calling them that, at least that's what my intentions are.
even those deb files that only run on Ubuntu for some damn reason on my Debiain system.
FUCK i understand now! the software i wanted to install had a .deb but its website said it was for ubuntu 20.04, no wonder it didn't work on a debian container!
it didn't work, but i soon found out by looking at it's entry on the AUR that the package is itself broken, not the distro environment it's supposed to be installed on
Arch User Repository. If you're using Arch, you get the basic stuff from the official repositories. But for most programs there's the AUR. They're often less polished, some of it may be proprietary. There are package managers dedicated for it, that also know to handle the official repositories.
Just switched a couple of my systems from Pop and Fedora (gnome) to Debian 12 w/ KDE Plasma.
All in l I like it. I don’t like where Canonical or RedHat are moving, for the FOSS consumer. Canonical is making huge strides as an enterprise distro but for home use I’ve really moved away from it since Unity.
Originally I went Fedora because my office was a RHEL shop but we’re moving towards Ubuntu.
Thankfully RHEL/Centos/Fedora also get attention thanks to the large corporate influence.
Anything else can just be compiled from scratch, after spending 6 hours trying to figure out what ajfiwn-0-libs-dev is in redhat land, only to find out it was libfiwn-devel all along.
distrobox: Tool for creating one-off containers of a different Linux distro.
container: A virtual OS environment that runs on your computer, but doesn't know that it's running in your computer. It's not the same as a VM or emulator.
flatpak: A tool designed by RedHat for running sandboxed Linux programs in any environment. Flatpak can either refer to the system as a whole (eg: "You need to install flatpak on your machine to use our tools") or an individual program packaged for the flatpak system (eg: "You must download the latest flatpak of Firefox").
AUR: The Arch User Repository. A collection of installation scripts to add software to Arch Linux. These scripts are not owned or maintained by anyone officially affiliated with Arch, so you can find AUR packages for almost anything.
So, the comment becomes: Stick it in a dedicated environment designed to run Debian. Then package it so anyone can run it. Then make it easy for anyone running Arch Linux to install it.
I don't know what the Linux community's consensus on appimages are, but I wouldn't mind if people made more appimages because, for the few distros I've used, appimages just usually work.
AppImages are definitely convient to use. However the two issues I have with them are that there's no easy way to find them (eg flathub) and they're not automatically integrated with the DE. Requiring a tool that manages AppImages to make it easier.
Only n00bs code their programs from scratch. Cool people build their own kernel, OS, compiler, and coding language, and they already have that program built in.
Debtap is suprisingly easy to use after switching to arch (highly recommend), but i actually love .deb files. Obviously it's a slight risk to the user in the similar way
dot EXE's can be for windows , but they really do simplify package management for when you're newer to linux.
BlendOS Will let you install virtually any package format through containerization, but it shows up just as if it was a native app. It's pretty neat to see and I hope more distros adopt this
And again...
Distrobox is your friend. Me, I like an immutable OS (kinoite) but I still want the AUR…
distrobox-create --name arch --image archlinux:latest
distrobox enter arch
install yay as normal
yay -S vscodium
distrobox-export --app vscodium
yay exa
distrobox-export --bin /usr/sbin/exa
exit [back to kinoite]
exa [works]
vscodium [works, has icon in application launcher]
Well it does technically, the issue we're talking about is how it's packaged, one you extract the package the software will work just the same (assuming there aren't any version mismatches between kernel modules). DEBs (Debian based distros) and RPMs (RedHat based distros) are the two biggest package formats, the next common format is a tar ball.
Add to this, this gives birth to more modern packaging format like flatpak, appimage, and snap, that works across all distro with proper permission control.
Now for most graphical apps, you just search on the app store and click install, like a iphone user.
The software itself should run, but the installers themselves use different standards. I'm pretty sure you could set up your own distro to use installers from different one, though it may require some work.
Windows kind of has that too, with all the .MSI, .exe, .msix and all the appxpackages and how almost none of that works out of the box anymore because you'd otherwise be able to install another browser without opening edge once
It's just maintaining arch that was a bit of a headache for me. I loved having access to the AUR and being able to use bleeding edge.. well, everything. But too much of my time ended up going to fixing issues after updates or finding out what package to choose when there were conflicts during updates.
Open it up in midnight commander, and it will unpack it into a virtual directory structure, complete with install/uninstall scripts.
Look at the install script to see what it's thinking, pull out the file structure, copy into your filesystem.
Oh, and hope. Because often you need to get matching glibc and other dynamic libraries that the program was compiled against. Which isn't the end of the world as the dynamic linker will look in the local directory where the program is first for libraries, but it becomes a hassle pretty quickly.
Yeah, I hate those with a passion. Or those who send you to a GitHub page that explains nothing, gives you the tar and expects you to read their mind 😂
What could possibly go wrong with running precompiled binaries that were linked to a set of precompiled libraries with a completely different set of precompiled libraries.
You're not wrong, it's definitely not something a n00b should attempt in most cases. But I've done this before to save myself the need for distrobox. A lot of proprietary software only offers .deb, but is usually either statically linked or comes with its own set of nearly all the libraries it needs. So just extracting and running it often does the trick on non-debian distros like Fedora in my case.
Seriously though, just use distrobox or see if there's an unofficial package for your distro that you trust (AUR/copr/ppa/OBS). It's more straight forward especially if you don't know what you're doing.
me, who definitely knows how to and in fact totally prefers to build everything from source: [nervous laughter] yeah what kinda dingus exclusively uses .debs amirite?
Software has a Linux version and it only comes as a .deb
Depends on a load of packages exclusive to Ubuntu and installing it on stock Debian is bloody impossible
Yeah I remember when Steam came to Linux. Never got it to work. I hope it is better nowadays? (Sadly can't check. My only pure Linux box at the moment is a Raspberry Pi, I don't expect Steam to run on that either)
You can get Steam on just about any distro, for years at this point. And there's always Flatpak for these cases too although for Steam I recommend native packages.
it doesn't matter which one is better, it's about compatibily, and there's no way to install .debs on, like, rpm based distros without getting completely broken uninstallable packages
Distrobox is the way. Running Fedora and I have debian and arch boxes (with their own home dir) installed. Graphical applications work without any fuss and I have yet to run into an issue.