

Think that’s called NATing
Think that’s called NATing
The “don’t break userspace” is a kernel rule. It’s ok to break userspace within (like on library upgrades). The equivalent for Linux would be breaking kernel space, which they do… very often. It’s the reason DKMS exists and why Nvidia can be such a hassle
Wow way to make assumptions huh
It’s a fountain pen
Imagine installing Arch without having to bindmount dev, proc and sys smh my head
Stronger compartmentalization
Yeah. I think some people who haven’t experienced the substance think it’s a feel-good-pill where you just ignore the world and experience your own. Well, it can be pills, though that’s not common, and it being forced on your must be horrible.
So yeah, what you write is correct. But at least it was unsuccessful in what the CIA sought out to achieve.
Oh sorry. This was only to elaborate on
As an LSD user, fuck MK Ultra.
I think anyone who took LSD knows that set and setting were probably not optimal at MKUltra.
Yeah, this one is on Kent… again.
He posted on Patreon that there’ll be a DKMS module. In my opinion, this should have been the option from the very beginning and upstreaming at a later point in time. It would have avoided a lot of drama. And now bcachefs is kind of tainted. The only way I ever see it back in mainline is there is an independent downstream of Kent’s kernel that has no connection to him whatsoever.
Shame because I had very good experience with the filesystem. Definitely better than when btrfs was new. But Linus is unfortunately right; Kent is unable to follow agreed collaboration rules.
Unfortunate situation that could have been avoided entirely. Though I don’t want to be too harsh on Kent. He spent a lot of time and work on bcachefs and it’s his most important project. As such, he’s more passionate about all of this. But the same can be said for Linus and the kernel on the other side.
PipeWire my beloved 😍
LFS is a distro in the sense that a cookbook is a buffet
I think it can be assumed that of a machine has sudo, it also has touch.
Plex has better security, federates and shares with other plex servers and generally is less hands-on for transcoding.
Regarding security, it’d be interesting to see how secure it actually is. Yeah, the individual endpoints might be protected better, but is Plex the company maybe a single point of failure?
Allows you to scroll through / view a text file in the terminal.
All the good stuff available and you choose a POSIX shell? To each their own I guess.
Granted, I still prefer it to PowerShell, but only in how it feels, not conceptually.
I don’t agree with your assessment really as I don’t see the core experience declining.
But also, it’s a free project and people are putting in their time wherever they want; I don’t think the project would reject a submission for something based on “we’re doing too much” if it’s within the scope of a desktop environment.
Admirable dedication to the cause
Godspeed, keep the hacking spirit alive
This isn’t what I get when reading bug reports he interacts in. Yeah, sometimes he asks if something can’t be done another way – but he seems also very open to new ideas. I rather think that this opinion of him is very selective, there are cases where he comes off as smug, but I never got the impression this is the majority of cases.
PipeWire for audio couldn’t exist nowadays without PulseAudio though, in fact it was originally created as “PulseAudio for Video”; Pulse exposed a lot of bugs in the lower levels of the Linux audio stack. And I do agree that PipeWire is better than PulseAudio. But it’s important to see it in the context of the time it was created in, and Linux audio back then was certainly different. OSS was actually something a significant amount of people used…