jozep

joined 1 year ago
[–] jozep@lemmy.world -1 points 10 months ago (1 children)

Ah I thought you were one of those anti vegan people. I'm too stupid for Lemmy, I always imagine the worse. Gonna delete this app. Sorry.

[–] jozep@lemmy.world 3 points 10 months ago (5 children)

In which situation does a person gets to chose another random person eating habits?

[–] jozep@lemmy.world 0 points 10 months ago (1 children)

On a tangent, I've seen many pitbulls breathing heavily. Is this normal for these dogs? Are other dogs races like this?

[–] jozep@lemmy.world 1 points 10 months ago

Custom configs is for people who might not want to tinker as much so maybe it's not for you if you prefer Arch.

To answer the question you asked previously, yes I had issues with custom configs from Debian. One I remember is mupdf being launched by a bash script and thus not understanding why did I have two PIDs (one for bash, one for the mupdf binary) when starting.

For context this was important because I needed to know the PID of mupdf to send a SIGHUP to update the view.

[–] jozep@lemmy.world 4 points 10 months ago (2 children)

Arch also does its own packaging on its repos.

However you are right that Arch tries to stay as close as possible to the source. This is fondamentally different than the debian (and thus all debian-derived distros) way of packaging where they aim for a fully integrated OS at the expense of applying their own patches to many packages.

The patches can sometimes bring issues since they can bring unexpected behaviour if you come from Arch and sometimes will help the end user tremendously since they won't have to configure every piece of software to work on their computer.

This is really two way of looking at the issue: Arch is make your own OS and Debian has a more hands off approach.

[–] jozep@lemmy.world 29 points 11 months ago (3 children)

That's because it is not :) especially since many WiFi card vendors do not give documentation so writing a driver for it is basically impossible.