OK but Wayland is not responsible for arranging monitors

Where's the article?

It's even worse, they're not getting paid. These shills only get rewarded by getting the phones slightly before general availability (but after actual reviewers)

They're not doing a recall, but that doesn't mean they won't somehow compensate big OEMs for their warranty issues.

Yeah, even the TLDR makes it sound more like Qualcomm is yielding to the pressure from OEMs who want to be able to offer longer updates

But "open source" doesn't even mean that you can reproduce it or use it for free.

You're thinking of source-available licenses. Open source has a clear and widely accepted definition that requires a certain level of freedom. You're free to ignore this definition, but you can't expect the rest of the world to do the same.

To be clear, open source allows for only providing access to paying customers, but those paying customers are then free to use and distribute their copies without any further payment. Then it wouldn't be open source anymore.

If a thief knows your PIN (by watching an earlier unlock), Android is now requiring “biometrics for accessing and changing critical Google account and device settings, like changing your PIN, disabling theft protection or accessing Passkeys, from an untrusted location.”

Sounds great for Pixel 6 series with their reportedly highly reliable fingerprint sensors /s

Honestly, I'm not sure what to think about this - extra protection against unauthorized access is good, but requiring biometric verification with no apparent alternative irks me the wrong way.

Maybe that's just because of my experiences with Nokia 5.3 and its awful rear fingerprint sensor with like 10% success rate. But then again, there will eventually be phones with crappy sensors running Android 15.

The astrophotography mode on Pixels (the only way to get 4 min exposure in the default camera app) works by taking quite a few photos with shorter exposures and then matching them up in post processing.

You even get a short animation at the end where every captured photo gets processed using the rest, so you can see stars moving around during the capture.

Here's Stallman's/FSF's view on requiring ~~loyalties (lol)~~ royalties (read the whole section, it's explicitly stated at the end), and here's similar requirement in OSI's Open source definition.

You are free to use whatever license you wish, but don't call it FOSS/Open source if you don't agree with their definitions.

The idea is to use TPM to store the keys - if you boot into a modified OS, TPM won't give you the same key so automatic unlock will fail. And protection against somebody just booting the original system and copying data off it is provided by the system login screen.

Voilà, automatic drive decryption with fingerprint unlock to log into the OS. That's what Windows does anyway.

Or is there any functional difference between the two methods?

Can't test right now, but I have a strong suspicion you will have trouble getting IP broadcast to work. Normally broadcast address is calculated by setting all bits after the network prefix to 1, but your computer believes to be in a /32 "network". It won't broadcast over routes that are not part of its network.

And even if you calculate the broadcast address successfully (maybe the software you use has /24 hardcoded for whatever reason), no computer configured with a /32 address will receive it - 192.168.0.255 is not within the 192.168.0.1/32 network, so it will probably get forwarded according to your routes if you have forwarding enabled (except it shouldn't in this case with one network interface, because you never send packets back the way they came from)

No, kernel immediately stops execution of all normal processes once it gets into a kernel panic, and there's no way for processes to hook into this functionality. It is intended to be the emergency stop state when the kernel realizes it doesn't know what's going on and it would be dangerous to continue executing. So it does the bare minimum to report the issue and then stops even its own execution.

There's also a softer variant of the kernel panic called kernel oops that should let the user choose to continue if they think the risk of data corruption doesn't outweigh losing all data currently in memory. But just like the kernel panic, it is handled completely inside the kernel and userspace is frozen until the user chooses to continue.

This is intended for situations where systemd runs into an unrecoverable issue while booting (for example you have misconfigured fstab and a required disk is missing). Without this, you just get thrown into the terminal with some error messages that might not make much sense to you if you don't have a decent understanding of Linux. Now, you get a more newbie friendly message and a QR code that should bring you somewhere you can learn more about possible causes and troubleshooting steps.