News for hackers. Stuff that matters.
Re:Why GNU/Linux Viruses are fairly uncommon (2005) by dragontamer on Sunday January 31, 2021 @12:12PM (#25980380)
This specific joke worked better in 00s when GLIBC compatibility issues were far more of a hassle than today.

But the joke still rings true today: not necessarily with GLIBC anymore... but maybe systemd vs initsystem, or XLib vs Wayland, and other such "non-backwards compatible changes" that seem to occur in the Linux world more often.

Re:Why GNU/Linux Viruses are fairly uncommon (2005) by usr1106 on Sunday January 31, 2021 @01:05PM (#25980942)
> and other such "non-backwards compatible changes" that seem to occur in the Linux world more often.

The term DLL hell was termed in the Windows world for a reason.

If you stay with what the package manager offers for a well-maintained distro I don't think the user ever sees incompatibility issues in Linux. The distro maintainers (or if you build something custom) sees those issues, but often enough a build time, not at runtime.

Re:Why GNU/Linux Viruses are fairly uncommon (2005) by ben0x539 on Sunday January 31, 2021 @01:14PM (#25981029)
How far do people get sticking to first-party packages? I inevitably end up, like, wanting to have videogames or newer development tools or something. I guess developers might be outliers, but even my work laptop ships with distro-managed browser versions that the work-managed SSO login form rejects as too old, so pretty much everybody has a non-distro-packaged browser install.
Re:Why GNU/Linux Viruses are fairly uncommon (2005) by m45t3r on Sunday January 31, 2021 @01:22PM (#25981126)
I don't know any distro that doesn't update browser packages in stable releases. Fedora, Ubuntu, Arch (ok, Arch is rolling release but still) and NixOS at least offer the lastest versions of Firefox and Chromium on its repository. Debian too, but I think they package Firefox ESR instead of Firefox release.
Re:Why GNU/Linux Viruses are fairly uncommon (2005) by ben0x539 on Sunday January 31, 2021 @04:24PM (#25982686)
Yeah, it's an ESR, but the SSO thing specifically wants a recent version and not ESR. Not pretending that's a good decision, but I still have to go along.
Re:Why GNU/Linux Viruses are fairly uncommon (2005) by michaelmrose on Sunday January 31, 2021 @05:06PM (#25983022)
There are many solutions to the same problem. ================================================== A rolling release distro suffers from that problem vastly less than a rolling release since you will usually have current versions of most tools if your distro has enough people to maintain it. See gentoo, funtoo, arch, manjaro, void.

Making it easy to produce alternative package repos goes a long way towards having people actually make them. See overlays in gentoo/funtoo and ppas in ubuntu and ubuntu based distros like mint. This is especially important in ubuntu which is not rolling and can be different degrees of out of date especially if you use the long term support versions.

Making it easy to produce a package goes a long way towards it being easy to make one even if its only used by yourself. Arch/Manjaro Funtoo/Gentoo packages are both very easy.

Gentoo/Funtoo use flags make it easy to build an alternative version of a package eliminating the need to build it because the distro maintainer didn't enable the feature you need.

Arch's AUR makes it easy to add a package that can also be produced from source and updated like any other package via aur helper. Can also have alternative builds of the same package.

Of many distros I have used over time I would say that on Arch and Funtoo I didn't have to build anything manually but I did rely on the AUR and overlays + made a package for funtoo which was very very easy.

On mint and ubuntu I ended up with about a million ppas + building some things.

On net I'd say that rolling release + a system where users can trivially create their own packages on something like the AUR is the most versatile while still being accessible. Funtoo was even more flexible but substantially more complicated.

However for various reasons I'm using Void now and have only 2 manually build things. Gargoyle because its not in the repo and I hadn't figured out how to make a package and mpv with a sndio partch.

Re:Why GNU/Linux Viruses are fairly uncommon (2005) by opan on Sunday January 31, 2021 @03:15PM (#25982135)
If you use a rolling release distro, stuff stays pretty up-to-date. For games, there are usually free software titles packaged. Minetest, Xonotic, StepMania, Cataclysm: Dark Days Ahead, Dungeon Crawl Stone Soup, Nethack, Red Eclipse, Super Tux Kart...
Re:Why GNU/Linux Viruses are fairly uncommon (2005) by atomicnumber3 on Sunday January 31, 2021 @01:26PM (#25981160)
IME:

Organizations just standardize on one thing. CentOS (but not anymore I guess v.v) or RHEL or Ubuntu or Debian etc. Pick an LTS and then install it on all the work-provided hardware and just make sure everything works for your org.

For individuals, (and by that I mean me and like a few of my friends who run GNU+Linux) it's something like:

1. Docker 2. Use Arch Linux

Personally, my setup is:

Machine I use as a PC run Arch so everything is just latest vanilla upstream.

My homelab is ostensibly Ubuntu LTS, but I run docker on almost every host, and have a Proxmox host too, so the Ubuntu layer directly on the machine only really gets used for running ping, dig and nmap (and docker of course).

Re:Why GNU/Linux Viruses are fairly uncommon (2005) by usr1106 on Monday February 01, 2021 @02:37AM (#25986467)
I have have worked over 10 years Linux only. I have never needed to install a different browser.

Sometimes I needed Skype telcos with some customers, recently I needed Zoom for some training. Both have .deb packages that worked. Occasionally I needed some developer tools, but they were generally Linux-friendly and did not cause any trouble.

Yes, I am nowadays selective with what employer I would join. If their IT department is Windows-focussed they are not for me. That greatly limits choice, but reduces daily frustration efficiently.

Re:Why GNU/Linux Viruses are fairly uncommon (2005) by alkonaut on Sunday January 31, 2021 @05:23PM (#25983185)
Isn’t it backwards now though? I rarely experience any library issues in Windows simply because there are nearly no shared libraries. For a desktop system that’s what I want. There are zero times on a desktop that I want to upgrade a shared package used by multiple apps, eg for security fixes.

It’s not worth the hassle. Isolated apps wins every time. Now Windows apps even ship their runtimes bundled (.NET core, C++ runtimes). This is a good thing.

Re:Why GNU/Linux Viruses are fairly uncommon (2005) by AnIdiotOnTheNet on Sunday January 31, 2021 @03:48PM (#25982433)
> If you stay with what the package manager offers for a well-maintained distro

Your choice of software will be limited and almost certainly out of date.

Re:Why GNU/Linux Viruses are fairly uncommon (2005) by heavyset_go on Sunday January 31, 2021 @04:10PM (#25982605)
If you care about running bleeding edge software, then you're probably running a rolling release distribution where the software in repositories is only out of date for a few hours or days.
Re:Why GNU/Linux Viruses are fairly uncommon (2005) by AnIdiotOnTheNet on Sunday January 31, 2021 @04:36PM (#25982791)
Assuming what you want is in there and someone is maintaining it, which is a big if you're doing anything even a little bit unusual.

Linux Desktop seems to believe the world must be bifurcated between "stable, predictable system" and "absolute bleeding edge software". What if I want old trusted versions of some things and bleeding edge of other software?

Re:Why GNU/Linux Viruses are fairly uncommon (2005) by whizzwr on Sunday January 31, 2021 @12:44PM (#25980719)
I feel like rather than glibc, "selinux permission denied", would fit better these days.

..but on second thought, hat's actually selinux doing its job if the executable is a real virus.

Re:Why GNU/Linux Viruses are fairly uncommon (2005) by ed25519FUUU on Sunday January 31, 2021 @12:24PM (#25980501)
Is there any explanation for why backwards compatibility breaking changes are so common in the Linux world despite the fact that linux itself does such a good job avoiding it?
Re:Why GNU/Linux Viruses are fairly uncommon (2005) by Macha on Sunday January 31, 2021 @12:48PM (#25980763)
Are they really especially common in the Linux world?

UX: Windows 7 -> Windows 8 -> Windows 10 had some pretty drastic changes, even if a big part of Windows 10 was a climbdown. Have you followed the skeumorphic -> flat -> 3d again or Gingerbread to Holo to Material Design guidelines?

Dev facing: How have your migrations to WKWebView, notarised builds, M1, the Mac App Store, away from kexts, etc. been? Did you get onboard for WinRT and UWP?

You could argue in the Windows case you didn't _have_ to follow these trends, but you also didn't have to on Linux. Pidgin still works much the same as it did a decade ago. Thunderbird is still here and fundamentally the same as when I started using it as a literal child. You can still install MATE and XFCE and have pretty much the same workflow for desktop linux you had 20 years ago on Gnome 1, except with much much better chance of arbitrary hardware/software X working.

In the Apple case, you have to follow their guidelines in a much sooner period.

Re:Why GNU/Linux Viruses are fairly uncommon (2005) by grawprog on Sunday January 31, 2021 @12:51PM (#25980791)
I could be wrong about this, but I think it mostly just comes down to the maintainers of libraries and software packages.

If you've got a less used or less known software package and an upstream library dev makes a breaking change, you've got a choice, stick with the old version or update your code to work with the new version.

As time passes, new projects are started on the new version, the new version gets picked up by distro maintainers, old version is slowly phased out as more devs use the newer version. Eventually, maintaining old version and new version in package repos is too much effort to be worth it, old version gets removed, any software stuck on the old version is now broken on that distro without a bunch of workarounds.

And essentially, this is happening all the time with most libraries and such.

Re:Why GNU/Linux Viruses are fairly uncommon (2005) by formerly_proven on Sunday January 31, 2021 @01:36PM (#25981267)
Might be a GNU ploy, but the more likely explanation is that compatibility requires extra work and effort. Just think about how often libpng broke compatibility. Some libraries are so bad about this (like libpng) that even rolling release distros like Arch have to package multiple versions.

No one is willing to put in the effort on Linux to make deployment of software easier. And from the PoV of the distros there is nothing to fix anyway. Windows has invented and largely fixed the DLL hell. Linux only managed to copy the problem.

It’s great that the kernel is taking it so seriously, but everything else doesn’t care and constantly breaks compat.

Re:Why GNU/Linux Viruses are fairly uncommon (2005) by PaulDavisThe1st on Sunday January 31, 2021 @03:08PM (#25982073)
Linux has not copied the DLL hell problem. If you think that, you don't understand what DLL hell was.

I assume that by deployment of software, you mean "someone other a distro maintainer building and packaging software". That's no harder on Linux than it is on Windows or macOS (*) , it's just that Linux users have the additional option to get software from their distro too.

macOS: you put everything your app needs into ... well, a folder (with some required filenames and organization)

windows: you put everything your app needs into ... a folder (with some required filenames and organization)

linux: you put everything you app needs into ... a folder. Full integration into "the desktop" needs a few additional steps, easily carried out by an install process.

What is missing on Linux is a nice, clean, commonplace way for users to actually carry out the installation process for 3rd party (ISV) software that isn't packaged using the distro packaging system.

(*) other than issues with certain, ahem, toolkits that make it hard or impossible to statically link against them (and note: these are typically cross-platform toolkits, ironically).

Re:Why GNU/Linux Viruses are fairly uncommon (2005) by stelonix on Sunday January 31, 2021 @12:49PM (#25980774)
As code ages, people lose interest in maintaining. When you begin coding an application, you're usually adding features and that's fun, but as time passes and the software reaches its goal, you're left with finding and fixing bugs. That's no fun. Microsoft manages to do so because there's a money incentive for its employees, while free software has no such equivalent. That's why we see things like completely dropping X and writing Wayland from scratch: it's more fun and quicker for developer. Sucks to be us on the receiving end, though.

I believe until this kind of thinking shifts, there's not gonna be mass adoption of GNU/Linux systems. People expect software to work and keep working 10 years down the road. The current state of the FOSS ecosystem is full of bitrot and rewrites, with zero incentive for developers to maintain code. Beats the hell out of me why there isn't a distro that allows you to give money to patrons of the packages you use. It's a real no-brainer.

Re:Why GNU/Linux Viruses are fairly uncommon (2005) by saizaku on Sunday January 31, 2021 @01:11PM (#25980997)
I'd say the most likely reason would be the modularity of the user land. Namely it makes the adoption of such backwards incompatible changes much easier.

Anyone can make some new piece of software to do something in a new way(ex. init systems). And there will be people who want to use it and don't want to use it. Most of the time distors (and forks) will arise that do it the new way and people who want that will pick those distros. This is really common in the init-systems vs systemd debate.

Re:Why GNU/Linux Viruses are fairly uncommon (2005) by dTal on Sunday January 31, 2021 @01:18PM (#25981081)
I don't think it would be a terribly great obstacle to a malware author to statically bundle glibc.
Re:Why GNU/Linux Viruses are fairly uncommon (2005) by CameronNemo on Sunday January 31, 2021 @01:23PM (#25981130)
Or dietlibc, uclibc, musl.