I mean, it is shit posting

I think we finally figure out how to not poop for three days

Holy propaganda batman!

The list of articles on that website is…extremely focused on one subject only.

Locks are only held during system calls. Process termination is handled on the system call boundary.

You’re projecting windows kernel insanity where it doesn’t belong.

What the duck Microsoft bullshit is this?

There is no concept of locked files in extfs, much less inside the kernel. Resource locks and unkillable processes is some windows bullshit that no sane operating system would touch with a ten foot pole.

Nope. Bitkeeper used it in the master-slave pairing and the term was carried forward. Gitlab did a whole writeup about it.

Well? Do you have any grapes?

Well? Do you have any grapes?

$previous_job allowed us to pick. One of my coworkers had to replace his laptop, and I convinced him to try out Linux this time. I handed him the bootstrap script and he was back to working by the afternoon.

Our CEO got wind of this and said as a matter of policy everyone is switching to Linux unless they have a good reason (needing excel for financial reports is a good reason). The two new hires who had been setting up their dev environment for over a week at that point were the trigger for this.

Used by search engines for listing which pages should be indexed.

Google’s documentation

This is a shit shitpost post shitpost.

TCP Selective Ack is very much a thing, but it does take extra memory so lots of TCP stacks exclude it or disable it by default.

TCP was never designed with wifi in mind. TCP retransmission was only ever meant to handle drops due to congestion, not lossy links.

Tmux is a wonderful complement to mosh. Together you get persistence even when your local client loses power (speaking from experience)

I worked with mosh for years to connect to servers on other continents. It was impossible to work otherwise. It only has two small warts: forwarding, and jump hosts.

The second is fixable/ish with an overlay network, but that isn’t always an option if you don’t control the network. I tried to solve this with socat but wasn’t able to configure it correctly - something about the socket reuse flag was very unhappy.

Also that in order to exploit this it requires an active man in the middle. Which requires any of the following:

• Reverse proxy hijack/NAT hijack - from a compromised machine near the server
• BGP hijack - stealing traffic to the real IP
• DNS hijack - stealing traffic to send to a different IP
• Malicious/compromised network transit
• Local network gateway control
• WAP poisoning - wifi roaming is designed really well so this is actually easier than it sounds.

Almost all of those have decent mitigations like 801.x and BGP monitoring. The best mitigation is that you can just change your client config to disable those ciphersuites though.

You clearly haven’t watched your forklift safety video. Warning: blood starts a few minutes in.

Memes at home are made with 100% creatitity

I was not expecting the drama around it. Is the issue truly a different orthography or is more like a different font/ligature issue?

EDIT: forgot the article I found on it: https://restofworld.org/2021/tulu-unicode-script/

Since when is immutability controversial? Linus called out the Google patches as badly designed with massive code quality issues for good reason. Theo described OpenBSDs approach to it and it is truly a simply concept with good security ramifications.

Weetabix would like a word