JATth

I tried Luks and BTRFS more than 6 times leading to a script error each and every time.

This was actually my experience also, so I went back to a manual install to just get it done. I think the archinstall script won’t get any configuration of device-mapper/LVM right (including disk encryption with cryptsetup). The disk encrypt setup had even more hoops to go through than just LVM.

I actually don’t get the fuzz/meme about Arch Linux. Yes, the installer drops you into a shell where you need to fix the keyboard layout for starters and the next thing is preparing enough disk resources for the OS which is somehow ungodly hard. My point is that if you can’t then you are not qualified to maintain the installation, or actually RTFM and start to fr think what you do.

René Rebe, I’ll watch him blast about bad code occasionally.

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.

BTW. With clang lto’d kernel 6.9. When non-Arch get the buggy updates, We have already moved on.

But it’s the spaghetti cabling that makes it work and highly robust.

Oh, Sweden, how’s your problem of gangsters with explosives (and thus explosions) going on? We have had some, but those have been mostly directed towards tincan cops. (i.e. traffic cameras, fuck those.)

Finland. You can punch a cop in the face, and the only repercussions is that your are a violent moron with an pricey after math. You can avoid the pricey after math, if you give up before punching the cop in the face. :) (It’s temporary jail time in both cases)

Also, in my country, if a member of police force fires a weapon, this alone means there will be an investigation to determine if the action was really necessary. The police cannot fire weapons without paper work, and are thus reluctant to do so.

If any one would hear that in my country it would be the fiasco of the century. (we have had one) You aren’t even allowed to go near the studying line if you have any criminal record. When the police make an mistake in my country, there will be an investigation. And the investigation is done by a party not in the normie police force, which can and does lead to convictions of the members police force.

Instead, Americans: here is your gun, go shoot and kill anything that moves, you are unimpeachable.

I think (in general) any one should be just allowed to say “oops” in any situation, in any case, however bad it is, to note he/she/(add any extra pronouns) has said/done and gone something that should not have happened or taken place. It’s like software crashing of thinking, which happens and will happen more than we would like to.

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)

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.

So it is btrfs snapshot time again and making it a bootable backup before pacman -Syu?

I have had only single time I remember when the Arch upgrade truly fucked up the system: libreadline.so was broken so bash didn’t work. :D

I always have a second bootable system in case the main system is unable to boot… So I can at least troubleshoot the main system.

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)

• Attacker broke out from the app sandbox. (attacker can run code in the infected process)
• Broke out of the process. (gained root access; attacker can run anything)
• Broke into the kernel space (gained 100% control over the hardware)
• Corrupted some kernel memory via a damm magic MMIO accesses nobody knows (hardware vulnerable)
• Bypassed protections that kernel set up earlier such that it cannot accidentally modify itself.
• Finally broke the kernel via hardware exploit thus the attacker got rootkit level access.

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.