In-reply-to » When you try to change a file that’s currently running, it used to say text file busy. Example:

I guess the question now becomes;

Why does it cause the running process to crash?

⤋ Read More
In-reply-to » When you try to change a file that’s currently running, it used to say text file busy. Example:

Just tried it: It did indeed crash my Wayland session and, since Wayland compositors are sensitive and critical, it froze all input devices. Only way to recover was to SSH into that machine and reboot it. 🤦

⤋ Read More
In-reply-to » When you try to change a file that’s currently running, it used to say text file busy. Example:

Not sure I’m happy with this.

Take this, for example:

https://codeberg.org/dwl/dwl/src/branch/main/Makefile#L64

The install target of a Wayland compositor uses cp to copy the compiled binary to your bin directory. So, as of Linux 6.11, when you recompile this compositor and reinstall it, it will crash your entire Wayland session. 🧟💀🧟

One way to avoid this crash is to use install instead of cp. install calls unlink() before copying the data, thus avoiding this situation entirely. Not all Makefiles do that, though.

⤋ Read More
In-reply-to » When you try to change a file that’s currently running, it used to say text file busy. Example:

It’s intentional:

Matching the behavior of most Unix systems, the Linux kernel has traditionally prevented writes to an executable file that is in use by a process somewhere in the system; that is the source of the “text file busy” message that some readers may have seen. This restriction is intended to prevent unpleasant surprises in running programs. Kernel developers have been phasing out this restriction for a few years, mostly because it does not really protect anything. As of 6.11, the kernel will no longer prevent writes to busy executable files; see this changelog for a lot more details.

Hm.

⤋ Read More
In-reply-to » When you try to change a file that’s currently running, it used to say text file busy. Example:

This changed between linux-6.10.10.arch1-1 and linux-6.11.arch1-1 … Don’t have the time now to do a proper bisect. 🫤

⤋ Read More

When you try to change a file that’s currently running, it used to say text file busy. Example:

First terminal:

$ cc -Wall -Wextra -o test test.c
$ cp test run
$ ./run

Second terminal:

$ cp test run
cp: cannot create regular file 'run': Text file busy

But on my machines today, it crashes the running program. 🤨 As soon as I run the cp, I get a coredump:

$ ./run
... time passes, I do "cp test run" in a second terminal ...
Bus error (core dumped)

How odd. Another mystery to solve …

⤋ Read More

You can pry OpenBSD’s httpd + acme-client from my cold dead hands. Set it up years ago and it never failed (unlike all the fancy stuff we tried at work).

⤋ Read More

@asquare@asquare.srht.site We’ve collectively as a community (welcome to the community too! 🥳) had a many-week, multi-thread debate over this. It all boils down to Content Addressing vs. Location Addressing and the benefits, pros/cons of each approach. Ultimately though threads in Twtxt take advantage of a convention we formalized as the Twt Subject. This is combined with a Location-based Addressing, the Twt Hash extension. In the end we are likely to stay with this approach, but fix the parameters we use and truction.

⤋ Read More
In-reply-to » This is so funny – and very true. 😃 The ancient German art of complaining: https://youtu.be/FcFmVfAg8V0?t=720

@movq@www.uninformativ.de Kaffee und Kuchen erst um vier Uhr? Da sind die beiden aber ‘ne ganze Stunde zu spät dran! Und wie hebt sie denn das Messer, eieiei?!

Lol, Schnitzelklopfen mit einem in Tüte eingepackten Schlosserhammer, das kam mir so auch noch nie unter. :-D

“Like a true German, I’m going to open this beer with my eye socket.” Hahahahahahaaaaa! :-D

⤋ Read More

The V: pattern itself is quite good because you can do quite a lot of powerful things with selected text.

For example: ggV}:s/^/ -/ will insert a - at the beginning of every line turning your bunch of lines into a Markdown list of items 😅

⤋ Read More
In-reply-to » (#olheqvq) @aelaraji … this made me realize that I don’t really know anymore which commands I use. It’s all muscle memory by now. 🤔

@movq@www.uninformativ.de Same here 🤣 My fingers know everything, my brain does not 😅 Same with passwords too, at least the important ones, master password, passwords for my machine(s) and work laptop. Don’t ever try to interrogate me for them, only my fingers know 🤣

⤋ Read More
In-reply-to » Haha, I love it! https://gist.github.com/hackermondev/68ec8ed145fcee49d2f5e2b9d2cf2e52

@lyse@lyse.isobeef.org the addressing of the “Bug Bounty program associated with this case” is such a total BS! I can’t help but believing the kid over Zendesk. The “-99” downvotes are telling. I could’t give mine, because I am not signing up on Zendesk for it. Ain’t nobody got time for that!

⤋ Read More
In-reply-to » Fuck, I lost my pocket knive somewhere.

I thought I lost one of my knives at the flea market this year, but luckily, I just found it in my washbag. Woohoo, yippee! :-) So, I only miss the other that must have fallen out of my pocket when I cycled to the scouts last month.

⤋ Read More

@aelaraji@aelaraji.com Yeah, remebering them is a challenge. It often helped me in the past to just try using one or two new commands over and over again. But that obviously doesn’t work that well when the specialized command does not come up in daily routines all that often.

⤋ Read More
In-reply-to » Haha, I love it! https://gist.github.com/hackermondev/68ec8ed145fcee49d2f5e2b9d2cf2e52

@prologic@twtxt.net @bender@twtxt.net A 15-year-old reported a security vulnerability in some shitware and they acted like absolute dickheads. Unfortunately, that’s how it often goes. The internet is full of similar reports where people a treated like that by companies, sometimes even way worse than that.

Read it, prologic, it’s totally worth it. That’s a great writeup by some very cool dude.

The PR article by the company just speaks for itself and reinforces their dick move. No more questions. https://support.zendesk.com/hc/en-us/articles/8187090244506-Email-user-verification-bug-bounty-report-retrospective

⤋ Read More
In-reply-to » There’s this rumor that you can create a WhatsApp account with a burner phone, then link the phone to a browser on your desktop PC (web.whatsapp.com) and never have to use the phone again. This just doesn’t work. Every ~2 weeks, the session in the browser will time out and you have to re-link again. 🙄

@bender@twtxt.net 🤣

⤋ Read More
In-reply-to » There’s this rumor that you can create a WhatsApp account with a burner phone, then link the phone to a browser on your desktop PC (web.whatsapp.com) and never have to use the phone again. This just doesn’t work. Every ~2 weeks, the session in the browser will time out and you have to re-link again. 🙄

@movq@www.uninformativ.de so, you keep lots of monologues. That’s the best “conversation” to keep! LOL.

⤋ Read More
In-reply-to » There’s this rumor that you can create a WhatsApp account with a burner phone, then link the phone to a browser on your desktop PC (web.whatsapp.com) and never have to use the phone again. This just doesn’t work. Every ~2 weeks, the session in the browser will time out and you have to re-link again. 🙄

(Another weird/funny thing is that I tend to “overload” other people on WhatsApp. I use it on the desktop with a proper keyboard, while they all use cell phones. The end result is me being able to type much more text and much faster, so they all fall behind and can’t really reply properly, because it’s such a huge pain to type on a phone …)

⤋ Read More