I mean no harm.
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.
I didn’t even think what the questionnaire was about, and filled the entire thing. It’s a rare thing to see for a FOSS project to ask what I’m staring at this very moment, how to make it better. But yes, the questionnaire was a bit oddly structured.
You can’t exceed lightspeed. Current tech is already at 99%
Even the newest “64-bit” cpus are really just 48-bit (or 36-bit on low end) or if bleeding edge 56-bit physical adressing processors. This is the maximum amount of virtual memory a process can have access to. You could memory map all your hard disks an still have room to map more physical memory to VMA.
I once said that the current “AI” is just a excel spread sheet with a few billion rows, from what all of the answer gets interpolated from…
But it’s the spaghetti cabling that makes it work and highly robust.
So, now they are slowly (or immediately and forever, I don’t know the time span) injecting propaganda into their clone of wikipedia and they are simultaneously thus admitting they are doing it. (to further brainwash the russian citizens)
So lettme repeat: FUCK PUTIN, and stuff your rubber clones in your ass. (which there are many of)
The in-rush of endorphins when the modded LCD thing actually worked probably knocked you out?
A bit of a side story: I disassemble probably 1–5 panels in a week. (For recycling, it takes about 20-45min per panel.) The flat cables alone are so flimsy, I would say just assembling a display again from known, matched and functional parts would take days. I would triple or quadruple that to assemble a display from random parts. Considering this, that modded panel is quite amazing to me.
In standalone panels, the PSU has a chance of killing you: the main capacitors can hold multiple joules worth of nope, charged to about 400v. So, if the main caps are not allowed to discharge (if they discharge at all that is), there is a possibility of death when disassembling a panel with an integrated PSU. Waiting “5min” is bad; a PSU needs to be unplugged for a day or two at least before the charge drains out.
I would highly recommend Curve25519, etc., just because such keys are faster and less common than RSA public-private keys in today’s world. RSA 2048-bit keys are considered weak today, while the Curve25519 256-bit keys remain stronger. Also, the ChaCha20-Poly1305 cipher has an interesting backstory and doesn’t necessarily need hardware acceleration (which, in theory, could be borked by the HW-vendor) to obtain good performance.
Unfortunately, some SSH front-ends don’t play nice with Curve25519 public-private keys yet… (I’m pointing at the putty SSH client, but that may have improved from the last time I had to use it)
The backdoor has existed for a month at least. Yikes.
Gamma rays have so much energy that they are basically emitted only by nuclear processes, as far as I know.
Maybe not in a flashlight, but the scientific industry would be very pleased with them. Sterilize water and all surfaces in a second? Flash with 200nm light.
This was an yet another glorious episode from veritasium.
I hope we get well past UVC LEDs. (i.e., shorter wavelengths) UV LEDs are already available. Unfortunately, this progress will stop before X-ray light. With +1 KeV energy, you pretty much must blast off the electrons from the atoms to emit X-rays, which an x-ray tube already does. Or by peeling off a piece of scotch tape.
I read the article enough to find that the Nightshade tool is under EULA… :(
Because it definitely is not FOSS, use it with caution, preferably on a system not connected to internet.
Windows: $ insmod < “http://shady-ring0-blob-from-internet.sys.cn” What could possibly go wrong?
The attack is spread via iMessage. A vulnerable device merely needs to receive a bad message with PDF attachment. --> A Remote code execution. No user interaction.
Yikes. Indeed.
The attack entry point is via bad TrueType font + PDF attachment that only needs to processed once. Once a process touches that, the attack vector begins and exploits are chained until they get kernel mode access. After getting kernel mode access all hope is lost, the attacker owns the device.
Only sliver of hope is that fixing the attack entry point blocks the current attack. And that bug is:
This attachment exploits the remote code execution vulnerability CVE-2023-41990 in the undocumented, Apple-only ADJUST TrueType font instruction. This instruction had existed since the early nineties before a patch removed it.
But unless all the CVEs are patched, it is just matter of time a new attack entry point is found.
Shorter version: Operating systems set up hardware locks and protections to confine processes, and once set up, they cannot be undone. (the hardware + OS denies modifications to the security policy)
Getting arbitrary code execution and root access is one thing, but breaking out from the damm kernel configured hardware protections is insane.
They basically managed to flip a “read-only” switch to “modify-as-much-as-you-like”. The infected device at this point is broken beyond repair, as the firmware(s) may have been tampered with. End result is a terrestrial spy brick.
Any new battery technology news needs to be taken with a grain of salt. They are highly likely over-hyped and the actually realized products will have more problems than the current established tech initially.
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