some self-quoting:
fbt: Guys. Guys. Guys guys guys.
fbt: If someone wants to rewrite coreutils in go
fbt: The only name you should ever consider is goreutils
Because of course they are! It aligns perfectly with how the systemd upstream behaves: “We have decided X is how it is supposed to be, now change everything according to our decision. And gain a runtime systemd dependency in the process.”
Fuck these guys, seriously.
...by default. Do I have to even say that's complete insanity? Apparently I do, as people are defending this change going as far as saying that the old behaviour was a bug that tools like tmux and screen were abusing.
It's also, of course, not actually expected behaviour and a bug. What are you saying? It was like that for 30 years, so it very much is expected behaviour? Nope.
Now listen here you little shits. I've been a system administrator for around 10 fucking years now. I can tell you what this change will result in: confusion. Lots and lots of confusion. Hours of trying to figure out what went wrong only to at some point finally linking logging out your last session and your processes dying.
systemd continues its well-established tradition of breaking shit that worked for decades. And people still defend that calling everything the systemd upstream doesn't like “a bug” or “abuse”. You disgust me.
This guy is legally blind, and he's still better than that polygon employee:
So the Alpha (non-DRM) and MP beta versions of the new DooM (or Doom 4) work perfectly on WINE... but the finished version does not. The culprit? Denuvo DRM.
You could have had Linux compatability basically for free, id. But you fucked up and lost Linux customers for no good reason at all. GG guys. 10/10.
So Mozilla are fucking retards and removed any convenient way to add a custom URI handler.
- You can't add one by just following a, say, ssh://host link. Firefox doesn't ask you what to use to open the link anymore, just goes HURR DURR UNKNOWN PROTOCOL.
- You can't add one in Preferences -> Applications. No “add” button anymore.
- You can't force it through about:config like you used to.
Here is how you can do it though. Find a file called mimeTypes.rdf in your firefox profile and add the custom protocol.
First, add the scheme in the 'urn:schemes:root' block:
<RDF:Seq RDF:about="urn:schemes:root">
...
<RDF:li RDF:resource="urn:scheme:telnet"/>
...
</RDF:Seq>
Then, add a new block:
<RDF:Description RDF:about="urn:scheme:telnet"
NC:value="telnet">
<NC:handlerProp RDF:resource="urn:scheme:handler:telnet"/>
</RDF:Description>
Now restart the browser and go to Preferences -> Applications. telnet will be there.
And to you, the person who decided to remove this function: Choke on your own cock.
I've recently noticed that my mail server wasn't checking SPF records and decided to fix that. Turns out postfix can't do that natively, only with an external command. I chose postfix-policyd-spf-perl as my external SPF checker. Randomly.
Howto, at least for Arch
Install postfix-policyd-spf-perl from AUR.
Add to the end of /etc/postfix/master.cf:
policy unix - n n - - spawn
user=postfix-external argv=/usr/lib/postfix/postfix-policyd-spf-perl
The leading tab is important.
Add to smtpd_recipient_restrictions in /etc/postfix/main.cf:
check_policy_service unix:private/policy,
Do that after reject_unauth_destination, not before.
Check the logs, it should be checking SPF records now.
Over the years, I've had countless conversations about Linux distributions and their pros and cons. One recurring topic in these conversations is the idea that Arch Linux being flexible is a myth. Now why do people think it's a myth? The overwhelmingly most common argument is: “You can't remove systemd, therefore it's not as flexible as, say, Debian”. And that has some truth to it, but usually not in the way it's meant to.
See, I think that there is a huge disconnect between two groups of people here, mostly due to a complete lack of understanding of a simple fact: User freedom, the way a lot of people see it, is almost completely opposed to the concept of simplicity in system design.
People who say that Arch is not flexible usually don't actually mean flexibility or simplicity. What they mean is “I can't do pacman -S sysvinit and get a nicely working system”. And that is true, you can't. But I want you to think about something for a minute: why can you do that with Debian? Don't read further till you come up with some sort of answer in your head.
...
Got your answer? Good. Now answer me this: why can't you as easily swap systemd for OpenRC, s6 or Epoch? Does the answer to that align with the answer you gave to the first question? Probably not, and here's why:
The reason you can easily revert to the old init/rc system is the same as the one for not being able to switch to OpenRC, s6 or Epoch as easily: the old system is supported, but the others are not. And that is something so many people insist on bashing Arch for.
Debian — and I'm only using it as an example here — supports two init/rc systems. To put in anything else and make it actually work decently, you would need to support it yourself. And the ammount of work that is required to do so is what we call flexibility. The less tightly coupled components of a system are, the easier it is to make something with it that is not in any way supported officially.
Debian gives you a product with specific select choices of how to build your system. The result is a system trying to accomodate for a wide variety of usecases, which inevitably leads to complexity, as you need to make sure different components work well together and provide at least some functionality out of the box. That is what people call user freedom.
Arch gives you a toolbox and a single loosely coupled supported base for a system. What you do with it is up to you entirely. Including not using the base group at all. That is what we call simplicity, which leads to flexibility, but raises the entry bar a lot. To actually make any use of the freedom Arch provides, you need to know what you are doing. Some people don't want that, and it's completely fine not to. But don't confuse what distros like Debian give you with system flexibility. It's not.
Found a neat little plugin on unixporn. It plugs your firefox notifications into your system's native notifications (libnotify in the case of Linux):
From a certain site:
$ ls /usr/local/etc/php.ini | awk '{print $1}' | xargs grep memory_limit
/usr/local/etc/php.ini: memory_limit = 32M