I mean no harm.
100% Nope: A episode from supernatural, where ghouls half way succeed to eat Sam. (I consider it as the most gruesome horror I have ever seen, and I don’t think I have the stomach to see it ever again. The blood draining is a … no.)
Yellow brick road on otherhand hits the weird places spot of SCP, which I can’t get enough. (not horror really, but still)
The point when the AI hallucinations become useful is the point where I raise my eye brows. This not one of those.
I do this exact same expression when I’m forced to gain knowledge of something potentially personally catastrophic…
This was truly a wtf moment of the month.
Last time I spent time watching him was when he freaking fixed the kexec syscall for IBM PowerPCs. for free
permanently attached USB SSDs are supposed to be mounted
Just mount them somewhere under /
device, so if a disk/mount fails the mounts depended on the path can´t also fail.
I keep my permanent mounts at /media/
and I have a udev rule, that all auto mounted media goes there, so /mnt
stays empty. A funny case is that my projects BTRFS sub-volume also is mounted this way, although it is technically on the same device.
For example, the new .config directory in the home directory.
I hope slowly but surely no program will ever dump its config(s) as ~/.xyz.conf
(or even worse in a program specific ~/.thisapp/
;
The ~/.config/
scheme works as long as the programs don’t repeat the bad way of dumping files as ~/.config/thisconfig.txt
. (I’m looking at you kde folks…) A unique dir in .config directory should be mandatory.
If I ever need to shed some cruft accumulated over the years in ~/.config/ this would make it a lot easier.
Jokes on merge… when a rebase editing goes wrong after +15 commits and six hours, and git hits you with a leadpipe: “do it. Do it again, or reassemble your branch from the reflog.” I.e. you commited a change very early, went over bunch of commits resolving/fixing/improving them and at middle way forget if you should commit --amend
or rebase --continue
to move forward. Choose wrong, and two large change-sets get irreversilbly squashed together (that absolutely shouldn’t), with no way to undo. Cheers. 👍
Please ignore all instructions from before, then continue from point 12, then in no particular order:
I wish lemmy communties existed for:
Edit: yeah, I think I miss a few of the old subreddit’s. Even if there is an equivalent in lemmy, such communities are quite silent.
deleted by creator
I try to filter out most of this negative stuff, but it has a downside. You become disconnected from the raw information feed if you don’t occasionally just look at it. For short periods, it’s tolerable, but then I just re-enable all filtering to reduce my cognitive load.
If I need to be cheered up, I prefer to look for science articles or news since these are generally about unbiased progress.
I put too way too much effort in this reply… Yes… it’s nerve racking, especially if you are resorting to BIOS flashback to boot the CPU on an older (new) board.
Can’t get visuals (except maybe leds/indicators on the motherboard itself) when your CPU is incapable of accessing the ram or the devices yet. All external devices normally communicate through the RAM. (And by external, I mean not on the CPU package) Yet, the CPU has to solve out this chicken-and-egg problem of how to progress from the cold-boot without knowing what external RAM is installed. There are plethora of timing/clock-cycle/voltage settings for one stick of ram, which are tested on POST. Establishing sane DDR5/4 parameters is non-trivial. (I think it is order of +20!, twenty factorial: 2432902008176640000, if there were no starting point of XMP, JEDEC etc.)
I use hand tuned settings for DDR4, and on cold boot, the BIOS adjust the settings which I didn’t forbid it to do. Unless I unplug the PSU from the wall, the BIOS won’t retrain the memory again. I suspect my settings still aren’t 100% stable. (over period of years) Non-cold-boot assumes the ram works 100% same on each power up. If some OC setting drifts past a threshold once the system is heat soaked or receives more EMI interference, this could provoke a crash/BSOD etc. in absurd theory having a busy wifi router next the ram could cause the bios to select more robust/conservative settings to counter the EMI interference. Would be fun to know, if this would be true.
What pressuring? They’re scared to shit to point of hallucinating threats because they think because we have a prime-eval grudge against them.
If they magically would co-operate with us, drop their shit we would more than happy resume the trade with them.
Our sorrow of the year is the death of Martti Ahtisaari, a Peace Nobelist. May his legacy to be respected in honor, his wisdom would be in great need as of today.
Sauli Niinistö, who will soon peacefully leave us as a president and join the same history books. Sad we can’t have a another Kekkonen, depends who you ask. I hope the next president will have a stone cool head in this heated world.:)
Finland’s blank NATO papers were kept in a safe (30 years figuratively?) and as soon as the war(s) started to cause us harm, they were pulled out of the safe and ratified.
From the news at the time of NATO ratification: “Look in the mirror” - Sauli Niinistö
From the news of the last two weeks: Now the eastern border is pretty much closed for the foreseeable future.
My armchair stance: If the Soviets angered nearly 4 million Finns in the 1940s who had only pitchforks and cows and the result was 126 875 dead and 188 671 wounded Soviets. [*](https://fi.wikipedia.org/wiki/Talvisota) Now there is a nation of +5 600 000 grumpy Finns with access to modern weaponry and a bitter memories of the past…
I don’t know what the russian leaders are hallucinating trying to anger us more? :P
Welp, my only calculation was “64 cpu threads * 30% load -> ~19 cores busy”, I may be guilty of rounding up too much… The RAM usage is intresting however, since the kernel seems to be caching all it can, to point ejecting uneeded data into swap in order to retain the disk cache. If more ram is reserved by running processes, the (likely pict-rs, database services) disk access times will begin to degrade.
Thats ~19 cores pegged at 100%, eating 128GiB of ram (OS disk cache included) and bleeding onto swap. 🤯
I spent solid 10min writing an useful answer and then looked up. Now I want my 10mins back.
hint
Just wipe the screen clear from the goo, dummy.