A core memory of mine is getting flung off of one of these things because of the centrifugal force, falling on my back, and being unable to breathe for like 20-30 seconds … until I screamed at the top of my lungs, and things slowly returned to normal, while the teacher just went: oh you’re fine, don’t be a baby. I was 6.

kill -9 1

Leave the poor kernel out of it, it has nothing to do with this. It’s Lennart, not Linus.

No can do, you just pressed Z after the UNDOs

Like a time traveller who accidentally steps on a butterfly and erases the whole future that he came from

I don’t think it’s intended as a “solution”, it just lets the clobbering that is caused by the case insensitiveness happen.

So git just goes:

• checkout content of README.md to README.md (OS creates README.md)
• checkout content of README.MD to README.MD (OS overwrites README.md)

If you add a third or fourth file … it would just continue, and file gets checked out first gets the filename and whichever file gets checked out last, gets the content.

It tells you there’s a name clash, and then it clones it anyway and you end up with the contents of README.MD in README.md as an unstaged change.

Platforms like reddit and Tumblr benefit from a friction-free sign up system.

Even on Reddit new accounts are often barred from participating in discussion, or even shadowbanned in some subs, until they’ve grinded enough karma elsewhere (and consequently, that’s why you have karmafarming bots).

Is this a problem here?

Not yet, but it most certainly will be once Lemmy grows big enough.

To screw with Windows users, you should sometimes put a README.md as well as a README.MD in your git repos. It leads to interesting results.

Even more annoying is that it’s very cumbersome to change the case of a file once you’ve created it.

If you accidentally create fIle.txt when you meant File.txt, the rename function does nothing … and it will keep displaying as fIle.txt. You have to rename it to something else entirely, then rename it back to the original name with the intended case.

This isn’t “Windows design”… this is just inherited stone age bullshit from the DOS days when the filesystem was FAT16 and all file names were uppercase 8.3.

NTFS is case sensitive in its underlying design, but was made case insensitive by default, yet case preserving, for reasons of backwards compatibility.

If Microsoft has to design something from scratch, without the need for backwards compatibility, they go for case sensitive themselves. For example: Azure Blob Storage has case sensitive file names.

a bash script to reinstall f—ing everything again

Why would you ever want to do that?

First of all, almost any Arch update induced problem can be solved by downgrading the offending package to the previous version, which handily is available in /var/cache/pacman/pkg/. This is an essential Arch troubleshooting skill.

Even an unbootable system (which has only happened once in my 10 years of using Arch because I didn’t read important news) can be fixed this way, because you can always boot from the installation usb stick and then use arch-chroot to access your installation and fix problems.

Secondly, if the problem was indeed caused by an Arch update, you will just reinstall the problem if you run a reinstall script.

It was much easier to “hide” sit back then unless you were in the know in the industry.

It wasn’t hidden. Everybody knew back in the day what an evil piece of shit he was.

It has just been forgotten about and many current adults weren’t old enough, or even around, in the heyday of his evil empire, so he has been able to whitewash his image. My 50 year old ass remembers though. Fuck Bill Gates.

Ctrl + r to search previous commands

That’s a readline thing by the way, so it doesn’t just work in bash but also works with other cli applications that are compiled with readline support, for example virsh, psql, fdisk, …

LOL, what the fuck is this?

https://snapcraft.io/torrhunt

Note: Limited features after 30 days of evaluation period

It’s also closed source, and the developer has like 30 of the most generic trash apps on the snapstore: https://snapcraft.io/publisher/keshavnrj. My advice would be to stay away from this. Looks shady as hell.

I guess the playstorification of flathub and the snapstore has begun.

No 7 sucked too. It just came off the back of Vista which was a real hot mess, so 7 appeared better.

The thing is, Microsoft has always had an adversarial (or abusive) relationship with its customers, forcing things on them that most of them don’t want. Like active desktop and IE integration in Windows 9x, “activation” and Fisher Price UI in XP, UAC in Vista, forced automatic updates in 7, that awful tile UI in 8.x, telemetry you can’t disable in 10, forced Microsoft accounts in 11 … the list is endless. And then when they back down on one thing, people are like: hurray, Windows is actually good now! … forgetting all the other things they have been forced to swallow in the past.

No. They’re all bad, some are just worse than others. You’ve all just been stockholm syndromed into thinking better of the “less bad” ones.

The new plasma-systemmonitor is garbage. The UI is very clunky, and it’s missing a lot of sensors that were visible with its predecessor ksysguard, for example network sensors are entirely missing for a lot of people, and nobody knows how to fix it. I think it’s beyond fixable to be honest, they should dump it and create something new.

For the time being I use ksysguard6, a port of the old ksysguard that’s been fixed to work with plasma 6.

I too demand justice for Zeke