214
What could your distro learn from another distro?
(self.linux)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 09 Apr 2024
214 points (94.6% liked)
Linux
45753 readers
863 users here now
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.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
While you will get somewhat the same from apt, I like the Debian way of providing base config support in packages and have local config loaded by include statements.
As you don’t edit the default config and automatic updates can happen w/o user input and your config will stay safe
That's the way it should be. But it depends on the software.
What really sucks about the Debian way is how it tries to start daemons in the post-install scripts and if that fails (say because the default config tries to use a port already taken) the entire package system shits itself and is unusable until you fix it.
Usually just the one package fails, unless you have other packages that have a dependency on it. I agree that it's annoying though.
Well, it stays in that half installed state and interferes with any other use of the package manager.
I might be a special case as I Mostly use Linux for servers. But I have maybe experienced one such case on the last three years on our 50-odd servers
I've ran into that with one shitty vendor (I won't/can't give any details beyond this) lately. They 'support' deb-based distributions, but specially their postinst-scripts don't have any kind of testing/verification on the environment they're running in and it seems to find new and exiting ways to break every now and then. I'm experienced (or old) enough with Linux/Debian that I can go around the loopholes they've left behind, but in our company there's not too many others who have sufficient knowledge on how deb-packages work.
And they even either are dumb or play one when they claim that their packages work as advertised even after I sent them their postinst-scripts from the package, including explanations on why this and that breaks on a system which doesn't have graphical environment installed (among other things).
But that's absolutely fault on the vendor side, not Debian/Linux itself. But it happens.