Docker isn’t required for automatic ripping machine. Theres a bare metal install.

I was just joking around, I hope you didn’t take it too personally. I’ve been hearing a lot of KDE enthusiasm lately.

And xfce is great, but it has its pitfalls.

I also get excited about projects, I’m no different.

I have a surface pro 6 and I love it.

You should, however, mention that the cameras do not work (yet), which makes this a no-go as a full laptop replacement.

Good stuff!

I just vi the systemd/system/fancyname.service files father than use systemd edit, but I think the result is the same.

There are two configs you can add to the [service] directive:

user=someuser

This should allow you to run the service under the credentials of your choosing.

Remember to systemctl daemon-reload after making changes to unit files.

That is not normal. I have much the same setup, sabnzbd, Plex, jellyfin, sonar, radar. They all run under a particular user and their /opt and /var/lib folders don’t ‘revert’ to their old ownership and permissions.

Either something is watching those folders and setting permissions, or some kind of immutability is in play, but permissions normally don’t revert like that.

Did you read my comment?

If you are referring to fastboot oem unlock, there are almost no phones that don’t have dual or even triple bootloader partitions, so that won’t work by itself.

click the buttons on the web page

I wouldn’t trust a chrome USB TTY permission to touch anything hardware of mine.

Flashing the phone’s bootloader and image is still done with adb and fastboot, but unlocking the bootloader is by now pretty much done with tools only made for windows.

Mostly this is because the exploits use factory flashing tools provided by manufacturers, which are nearly always windows.

Debian and xfce, generally. I’m happy to wait for features when they arrive, and xfce works fine.

However, Debian with gnome on my surface pro 6. Xorg just doesn’t handle rotation and touchscreen things very well.

On the other hand, several apps still behave very poorly under Wayland, so it’s a bit of a catch 22 at the moment.

The issue is that they are pushing their own version of flatpaks, some of which are broken, instead of contributing to flat hub and making that the default.

Well, tbf Brodie had only just covered that Hector had left upstream.

Also, it’s hot on the heels of one of leads of the nouveau driver leaving redhat and the nouveau project altogether. Karol Herbst has pointed out friction with Linux kernel maintainers as well.

There are a number of other devs who are less… Shall we say set in their ways and are perceived as completely opposite to the free and open values they once encouraged 20 years ago. And i don’t think anyone wants to see the Linux community fragment along these lines.

deleted by creator

You’ve mentioned that you dont care about systemd several times, but it’s certainly not clear from your post.

Many companies contribute to the LF. Intel, Qualcomm, Samsung, oracle, redhat, are all platinum members. Are you concerned because poettering works for ms that they’re going to privatize Linux?

What is your issue with run0?

If you don’t care about systemd, then why post?

Sysvinit is done. It is not graceful at handling dependant services, it was hard to test, and customising a service was painful compared to unit files.

For someone who’s been at Linux for 30 years, you clearly haven’t spent any time fighting with init scripts.

Don’t get me wrong, I’m not a fan of Poettering. His approach lacks any empathy for anyone who’s entrenched in a current system and breaks stuff with his deployment approach.

But run0 solves a LOT of problems with sudo, problems that have always existed. Have you ever tried to deploy a sudoers file in an ecosystem of Linux systems relying on LDAP? Sudo definitely needs fixing.