No choice was given
DefederateLemmyMl @ SpaceCadet @feddit.nl Posts 1Comments 585Joined 2 yr. ago
DefederateLemmyMl @ SpaceCadet @feddit.nl
Posts
1
Comments
585
Joined
2 yr. ago
Your computer is still using the power and it can damage it
Thats not how that works.
Sure it could cause some data loss, or corruption, or other software issues if the computer was in the middle of something like applying updates, but it should not cause hardware damage. All this applies to holding the powerbutton as well by the way.
or (really unlikely, on a shit connector) you get shocked.
Then you have bigger problems. You shouldn't be using a connector that's a shock or fire hazard in the first place.
But seriously about the only bad thing about it is perhaps some wear and tear on the connector that's not designed to be plugged in and pulled out every day. Alternatively you could also "pull the power" by pressing a button on your powerstrip (if you have that), or by flipping the powersupply button at the back of the computer to off. It all does the same thing: it cuts the power to the computer instantly.
Itโs also more convenient to hold the button instead of having to unplug and re-plug.
Yes, but holding the button is not instant and it relies on a software function in the bios which can be buggy. Usually holding the button doesn't even complete poweroff the system but puts it in a special "standby" power state where the motherboard still keeps providing power to some components. There are some issues that can only be resolved by a complete poweroff.
Someone with the skills and knowledge to "manually" produce some of the many one-off parts that went into this prototype.
The scientists and engineers may know what kind of part is needed, but it takes a different skillset to produce it.
DNS-over-HTTPS
You can also do that with running cloudflared or unbound on your pihole.
What is more dangerous about it than holding the power button?
To be fair, it would also be highly distruptive if you let the computer run overnight to finish some long running job and Windows decides it's rebootin' time. The point is: the OS shouldn't decide for you to reboot.
The official image jellyfin/jellyfin tracks unstable
Huh? That doesn't appear to be the case. jellyfin/jellyfin:latest, which is what they tell you to use in the installation instructions. gives me 10.8.13 which appears to be the latest stable release.
There are newer and unstable versions available in dockerhub as well, but latest doesn't give you those. After all latest is just a tag with no special meaning of itself, it doesn't necessarly give you the most recent build.
Glad to hear that disabling PBO helped, but it does indicate that something may not be entirely healthy with your CPU (or with the way the motherboard is driving it, that also can't be excluded)
For me gravity sync was too heavy and cumbersome. It always failed at copying over the gravity sqlite3 db file consistently because of my slow rpi2 and sd card, a known issue apparently.
I wrote my own script to keep the most important things for me in sync: the DHCP leases, DHCP reservations and local DNS records and CNAMES. It's basically just rsync-ing a couple of files. As for the blocklists: I just manually keep them the same on both piholes, but that's not a big deal because it's mostly static information. My major concern was the pihole bringing DHCP and DNS resolution down on my network if it should fail.
Now with keepalived and my sync script that I run hourly, I can just reboot or temporarily shutdown pihole1 and then pihole2 automatically takes over DNS duties until pihole1 is back. DHCP failover still has to be done manually, but it's just a matter of ticking the box to enable the server on pihole2, and all the leases and reservations will be carried over.
The worst part is to change some things it adds like an extra 4 clicks to the old method.
And then at the final click, it takes you to that control panel screen anyway lol
That's what I do. I do have a small VM that is linked to it in a keepalived cluster with a synchronized configuration that can takeover in case the rpi croaks or in case of a reboot, so that my network doesn't completely die when the rpi is temporarily offline. A lot of services depend on proper DNS resolution being available.
You can use log2ram to mitigate that.
Alternatively, you can even boot a root filesystem residing on an NFS share, but in the case of a rpi hosting the network's DNS and DHCP services, you could end up with a chicken and egg problem.
Try a day or two of mprime as some others suggested.
That wouldn't necessarily reveal a faulty CPU or firmware. I used to have a 3600x that would sometimes crash on idle at low clocks but would run cinebench or geekbench all day and all night.
Iโm pretty sure that itโs not hardware related
Random segfaulting is not something that "just happens" because of an OS misconfiguration, then if the same problem happens on Arch as well as on a clean EndeavourOS live image it convinces me that it is in fact hardware related somehow. As you have already replaced the RAM, my guess is CPU or motherboard issue.
Zen2/B450 is a widely used and well supported configuration on Linux that you normally shouldn't have issues with, but Zen2 CPUs are rather notorious for having fragile memory controllers, and sometimes dodgy AGESA firmware releases that can cause issues on some CPUs. I used to have a 3600X myself that started crashing at idle around a particular firmware release of my motherboard, and it was fixed by a subsequent release.
BTW the fact that it doesn't happen on Debian doesn't necessarily mean that Arch is the culprit. It could just be that Debian is not triggering the fault because of different, perhaps more conservative, compiler optimizations.
As a last ditch effort, you could try resetting your entire UEFI (bios) settings to default, preferably by pulling the CMOS battery.
BTW, is it only GUI applications that are segfaulting? Or other programs as well? Do you have an old spare GPU you can test with?
Again, not all that much user facing, but a lot of under the hood stuff. Reading through the notes, the things that stood out to me: vulkan, direct3d and metal rendering instead of just OpenGL, better HiDPI support including fractional scaling, better concurrency/multi-core support, and bringing the supported development tools up to date.
Mostly the migration to QT6 I think.
Personally, I rather like that they're not doing big changes or redesigns on the user facing side. KDE is pretty damn good as it is and I don't need a whole bag of new-and-shiny breaking my workflow.
Heh the comparison also holds if you use 10=Windows 7 and 11=Windows 8
Or 10=Windows 98 and 11=Windows ME
Kont is also not the most used, nicest way of saying it. โBillenโ is a better match.
"Billen" is "buttocks", it's less vulgar than "kont" but it doesn't mean exactly the same thing. I think kont is also more socially acceptable with Flemish Dutch speakers than with Dutch speakers from the Netherlands.
Should also note that the word "aars" exists too. Given that they went with Arsch in German and Ass in English, it's a bit strange that they chose the word "kont" to represent Dutch.
organization that decided that a lot of Dutchified English would be changed to more Dutch terms. So is โMathโ changed into โWiskunde/Rekenenโ.
Why shouldn't we use our own words to refer to things?
Also the word "wiskunde" wasn't made up by the organization you mention. It came from Simon Stevin, a Flemish 16th century mathematician.
I believe there's one in France too.
This reaction wants to redefine adulthood as post 25
It's even more than that, it wants to make adulthood some kind of sliding window where the age of the older partner defines how "adult" and "capable of making decisions" we see the younger partner, and the older a person gets the more people at the lower end of the age range get excluded for them from this fictional adulthood. For example: 60 and 30 would also be seen as inappropriate.
Now it's perfectly normal for younger people not to find much older people attractive or suitable to have a relationship with and vice versa, and they may even find the idea repulsive, but this is still a personal preference. It's probably even the preference of the majority of people, but that does not mean we should take away the agency of adults to choose their partners when they have a different, non-conforming preference. At that point it has nothing to do anymore with protecting vulnerable people from predators, but about imposing your own preferences and dating standards on other people, and you're quite right in calling it out for the neo-puritanical and conservative thinking that it is.
Plenty of reports to the contrary
https://www.reddit.com/r/Windows10/comments/47biyb/windows_10_restarted_while_i_was_in_the_middle_of/