I have to upgrade my Mint install every two years

I know you’re joking around here, but you don’t have to upgrade every two years. You can use an LTS release instead, or, on the opposite of the spectrum, a rolling release.

Release schedule and duration of support should always be factored into the decision of choosing a distro.

Save your sanity and do Settings -> Blocks -> Block instance -> lemmy.ml

I approve this comment.

Millenials - Load"$“,8 LIST LOAD"LEISURESUIT*”,8,1 (wait 10 min.) RUN

Even the oldest millennials were just toddlers when the C64 was relevant, so this is not a typical millennial experience at all. It’s really a GenX thing… so once again we are forgotten.

I would say millennials’ computer experience starts in the late DOS/Win3.11 era at the very earliest, but more typically in the Windows 9x and early XP era. So even IRQ/DMA/config.sys/autoexec.bat fuckery is not that typical.

Now we’ve got to fucking participate in it?

Ah yes, killing all those innocent civilians hidden in incoming Iranian ballistic missiles…

I guess it’s why some Jellyfin streams started transcoding for me.

You’re better off using the Jellyfin Media Player standalone application anyway.

The thing is, you can’t really engineer against anti-social behavior. For every better made apartment you will find that there is an even bigger anti-social idiot who still manages to make life hell for their neighbors.

I’m pretty blessed with my mostly boomer neighbors (🤞) who don’t make a peep after 10PM, but my girlfriend has had some shitty neighbors even though her apartment is pretty well made. Sound insulation between apartments is no match for cigarette and marijuana smoke wafting in from the balcony below any time you want to open the window to air out, or if, heavens forbid, you want to sleep with the window open in the summer, nor does it help much if they are partying and speaking loudly on their balcony until 4AM on weekdays. And then I’m not even getting into how they’re treating shared spaces.

The proximity makes everything so much worse than it would be with a house, at some point only adding distance helps.

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.

Or ctrl+w to close the fucking site and never come back.

The flag is called --no-preserve-root, but the flag wouldn’t do anything here because you’re not deleting root (/), you’re deleting all non-hidden files and directories under root (/*), and rm will just let you do it.

It’s apparently a hobby and to be competitive, you need to be able to spew bullshit at amazing rates. Personally I’ve maxed out at 140 wpm

I’m limited by the rate at which I can think of bullshit.

yet all I needed is a “this side up” symbol …

Since you forgot to add - - preserve-root It won’t go too far

Go on then … try it.

Or don’t because you will erase your system. (Hint: it’s in the asterisk)

as the binary is already loaded into memory

That’s not the reason why it continues. It’s because there’s still a file descriptor open to rm.

That’s not the reason why it continues. It’s because there’s still a file descriptor open to rm.

In Unix/Linux, a removed file only disappears when the last file descriptor to it is gone. As long as the file /usr/bin/rm is still opened by a process (and it is, because it is running) it will not actually be deleted from disk from the perspective of that process.

This also why removing a log file that’s actively being written to doesn’t clear up filesystem space, and why it’s more effective to truncate it instead. ( e.g. Run > /var/log/myhugeactivelogfile.log instead of rm /var/log/myhugeactivelogfile.log), or why Linux can upgrade a package that’s currently running and the running process will just keep chugging along as the old version, until restarted.

Sometimes you can even use this to recover an accidentally deleted file, if it’s still held open in a process. You can go to /proc/$PID/fd, where $PID is the process ID of the process holding the file open, and find all the file descriptors it has in use, and then copy the lost content from there.

kill -9 1

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

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.

Depending upon their genre and your city’s size, they may never come nearby you

The joy of living in a central, densely populated area of Europe … I’ve been able to see almost all niche bands that I’m into live.