waych

You mean appreciating? They have doubled in price since release...

People don't usually understand that apt allows you to configure multiple sources across versions simultaneously, so you can e.g. run stable, but also selectively install from backports or unstable.

To do so, add the sources for trixie-backports and unstable, and add the following configuration (e.g. /etc/apt/preferences.d/trixie-sid-pin) so that the system knows which sources your prefer:

   # Default to trixie
   Package: *
   Pin: release n=trixie
   Pin-Priority: 990
   
   # Very low priority for sid
   Package: *
   Pin: release n=unstable
   Pin-Priority: 100
   
   # Give backports medium priority
   Package: *
   Pin: release n=trixie-backports
   Pin-Priority: 500

Now the system can access the latest kernel from unstable (and backports), while keeping everything else on stable:

   # apt policy linux-image-amd64
   linux-image-amd64:
     Installed: 7.0.12-1
     Candidate: 7.0.12-2
     Version table:
        7.0.12-2 500
           500 http://deb.debian.org/debian unstable/main amd64 Packages
    *** 7.0.12-1 100
           100 /var/lib/dpkg/status
        7.0.10-1~bpo13+1 500
           500 http://deb.debian.org/debian trixie-backports/main amd64 Packages
        6.12.90-2 500
           500 http://security.debian.org/debian-security trixie-security/main amd64 Packages
        6.12.86-1 990
           990 http://deb.debian.org/debian trixie/main amd64 Packages

I believe the kernel in backports gets updated only after it is live in unstable for at least a week, which lately still feels like forever.

20 years ago, Google made a big deal about how they would do the right thing when "the the" was searched.

Oh how things have progressed.

Live patching production kernels makes sense when there is an imminent threat/timeline and rebooting is throttled due to underlying throttling mechanisms that are guarding the health of distributed systems running a-top the systems. Here's a real example I am familiar with:

Consider a hyper-converged cluster with many nodes serving distributed block storage, say at N=3 replication. This can tolerate exactly one N=1 node of outage for the reboot. It would seem preferable to drain the nodes in a way that allows for more parallelism in the per-node kernel-reboot process, but draining is expensive and its cheaper to reboot and hope the data comes back to the pool within some period of time after the reboot. This gets worse linearly as the cluster grows.

A non-trivial size cluster facing this can have a reboot rollout easily stretch from hours into days and even weeks. It is further made slower when the roll-out itself is repeatedly paused when any other production issue is detected, or some other in-cluster event is happening and distributed storage health is degraded or unavailable. If a single (additional) node goes out during the reboot roll-out, data goes unavailable and storage must wait and heal. It also simply takes time for the cluster to reconcile when the storage eventually comes back from reboot to make sure it is all still there.

If your systems are large enough, things will go so slow that things fall into the trap where the target release changes mid-deployment: to benefit from everything learned in the last many days or weeks, security, performance, crashes, whatever! There is benefit because the fixes you cared about most got onto a portion of the cluster sooner than later. There is also penalty, as this resets the time it takes to deploy, elongating the perceived end-to-end deployment time. This negatively affects OKRs and similarly displaces the release of anything that was queued for upcoming releases.

So yeah, live patching is great to get priority fixes out in a matter of minutes or hours. I also think it is the best tool to get oneself out of this rollout-reset trap and onto the next release sooner. Faster than rollback or rollover.

In the real world, leaving booby traps out that can harm others including the innocent are a liability and regularly a crime in itself.

I wonder how long these sorts of games will play before the law applies itself.

FWIW git-branchless, an extension to git, addresses many of these points without leaving git.

IIRC Google has a policy whereby all google3 binaries must be rebuilt within a 6-month window. This allows teams to age-out support for old versions of things, including glibc. grte supports having multiple multiple versions of itself installed side-by-side to allow for transition periods ("v5" in the article).

The "runtime" is a google internal distribution of libc + binutils that is used for linking binaries within the monolithic repo, "google3".

This decoupling of system libraries from the OS itself is necessary because it otherwise becomes unmanageable to ensure "google3 binaries" remain runnable on both workstations and production servers. Workstations and servers each have their own Linux distributions, and each also needs to change over time.

If the fines were existential threats, who would even want to do business in these countries?

Given that this strategic reserve is to be built from all the various civil and criminal asset forfeitures, and not actually buying any crypto currency, how exactly is this considered a "wealth transfer"?

This is centralizing governance of forfeited assets from across the many agencies that are currently holding wallets with no direction, into a single place: the Treasury. This seems far favorable to letting various (430+) agencies manage these valuable assets on their own where they can easily be lost, stolen, etc.

CSM is required for tools that aren't UEFI enabled. memtest86+ for example can't use a UEFI GOP and requires a BIOS capable VGA. Can't be used with a UEFI-only video card (e.g. recent ryzen igpu).

Also, there is still plenty of hardware out there that only comes with BIOS-capable option roms. These still require CSM if you want them to be be visible at boot.

Wow, 89MB of sphere "data". Why not just use a RNG?

Managed async bulk transfers as-a-service seems relevant to anyone writing lots of data doing multisite including DR. You can easily have this problem and not have yet hit any other scale problems that are addressed by the alluded-to tools people love to hate (k8s, tf, containers etc).

What is being managed here with Effingo is the relatively tiny links between sites, not the bandwidth on the fat local links. Bandwidth needs to be managed and prioritized across all the various copies that are happening across different services apps and teams simultaneously across the company, and across the systems themselves as aggregate for the links. Managing it gives you control on cost but also ensures optimal use within the constraints imposed and consistent and reliable handling of the copy use case.

> [1] e.g. because stock sales/purchases are still inexplicably not instantaneous it's conceivable something terrible could happen in the multiday period between purchasing your shares at a discount, and being able to sell them.

I recall participating in an ESPP where each time it vested (each 6 months) ended up being in a trading black out window, where we had to wait until Earnings Release + 3 days before being able to dump the stock. Lost that 15% gain just about every time.

This is mixing up cmd.exe which is the dos-like (but not dos) scripting interpreter, and conhost.exe which is the actual old terminal emulator/console that the kernel would spin up whenever you ran cmd.exe.

But it is lazy. Sorry if folks feel obligated to defend it.

It may be cynical, sure. But chosing cheap words to address groups of people is poor form for the speaker nevertheless.

If you are addressing others, use better words to describe them. Calling people "folks" all the time is lazy and insulting.

I forget where I first heard this, but whenever someone uses the word "folks", you can often replace that word with the word "idiots" and get the actual underlying meaning of the speaker.

Now not all speakers using it mean it that way, but it's a lazy word to use to group people, and the othering of people it implies seems to equally apply. The condescending tone really shines through.

If you intend on continuing to use this word to address people, know that at least some of us are making this conversion in our heads at all times.

Is it better to leave it to an AI algorithm watching you in the back of the car? One way or another passengers are going to get rated.

True Scotsman spotted!

Is the gemma model as misaligned with wokism like gemini?

Plants die for lack of CO2. It's their food.

No one has an EV that will last 50 years. They are also not made from renewables.

CO2 is plant food, and is a red herring to the energy discussion.

If you consider the consumption of energy required to make an EV versus a die cast combustion engine, you'll see the energy consumption got front loaded.

This is still ignoring the issues listed in TFA?

This seems to ignore the issues raised concerning foreign keys and consumer data protection pruning.

Cyclic logic that says you're wrong for wanting a stable kernel interface, because the kernel keeps changing so the solution is to just get your code merged into mainline. As a tautology, it's true, but it's also a cover for "because we don't want to".

See Windows or android GKI for existence proof that it can be done if so motivated.

I think about this meme every time I get distracted adding more customization to my vimrc. "How do I quit vim?" I ask myself as I dig deeper down the rabbit hole.

> but you won't need to pay for it except in catastrpohic cases.

Is an untested backup really a backup?

Just do a search for gas tax diversion and you'll see you are wrong.

Good thing people like you are on the internet though.