Wait, what

https://conelrad.blogspot.com/2026/11/atomic-cake-incident-at-80.html

C’est qui qui a fuité aujourd’hui ? C’est le Rassemblement National
https://bonjourlafuite.eu.org/#Rassemblement%20National-2026-11-04

おきた

@m3t00 @msbellows @cpsc_bot

Italian brand. But I don't know where they manufacture... Doesn't everything get made in China now? Lemme look at what carabiners I have around here, lol.

Oh look, they have a carabiner which breaks and the gate won't close recalled right now, too.

"PRODUCT RECALL - NIMBUS LOCK CARABINER

The carabiner’s automatic closing mechanism can break and prevent the gate from closing, posing a risk of serious injury or death due to falling. "

https://www.camp.it/d/us/us/outdoor/content/2988

“The most fascinating ephemeral game is Majestic, an experimental, X-Files-inspired alternate reality game about the chaos of the information age that ran for less than a year before its publisher pulled the plug. Majestic still stands as one of the most ambitious interactive entertainment projects ever undertaken. Intended as a personalized ongoing event for adult audiences that didn’t enjoy gaming’s typical epic-sized power fantasies, the game might have heralded a new direction for the entire medium had it succeeded. Instead, it imploded almost immediately.

“We can’t play Majestic now, so from a slew of articles and anecdotes, I’ve tried to assemble its history and offer a glimpse of what it was, why it failed, and what it could have been.”

https://obscuritory.com/other/majestic/

The article doesn’t really mention it, but I was intrigued to see that several of the media storage boxes in their photos were labeled “MAJESTIC.”

Majestic was an extremely short-lived (launched and canceled within a few months in 2001-2002) early online game from EA that remains among the weirdest gaming experiences I have ever had

https://www.salon.com/2001/08/10/majestic/

@mastodonmigration

Too late.

Send them PACKING. They are traitors

@tuban_muzuru @paninid

I was thinking of global warming, but the "employment" economy also needs to go.

The whole point of automation is that we can have the same (or better) quality of life while working less -- and yet jobs are harder to find, worse than ever, and many people have to have three of them in order to achieve even a minimal standard of existence.

AI is the argument for UBI*.

[/rant]

(*...and breaking up every business into neighborhood-sized co-ops, but that's a different rant.)

https://www.youtube.com/watch?v=9k_L1G0dkFc

#NowPlaying #CurrentBop

Next up in Linux's bootup sequence is to finish initializing all the subsystems related to memory. It needed to start the process early since basically any code will need or want to allocate RAM, but the same time it needed to hold finishing these subsystems until now thanks to some cyclic dependencies.

To do so it 1st finalizes some CPU-specific initialization, which appears to be about retrieving some specs & allocating virtual-memory datastructures.

1/?

Then it retrieves & remembers (via a helper) a CPU-specific zero-page.

For multicore CPUs it validates the `MAX_ZONE_LIST` build flag is greater than 2, carefully allocates (via a suite of helpers & some locks) & validates per-CPU-core "zone lists", sets (via helpers + wrappers adding locking & validation) some "CPU hotplugging" properties with callbacks to update & flush those zone lists, & consults (via another helper) the linker sets some memory profiling globals.

2/?

Then it prepares the "page ext" by allocating & validating (via a helper + wrapper adding iteration & callbacks) it some memory, possibly enables (via another helper) various debugging codepaths, allocates various memory for "kfences", logs (via another helper) current state, possibly allocates & populates (via a suite of helpers) various memory for the "kernel memory sanitizer", & possibly carefully allocates (via a helper) a "stack depot" hashmap.

Much of this relates to debugging.

3/?

Then it uses one of multiple codepaths (via a suite of helpers) to transfer data over to a fancier memory allocator, followed by (via another helper, calling into various memblock routines) to clean up anything left over in the "memblock" allocator. CPU-specific code's invoked to initialize this new allocator, ensuring the memory protections are configured correctly. After which another suite of helpers might carefully allocate & populate a cache while registering a CPU-hotplug callback.

4/?

With that shift complete it invokes (via a helper) memory-initialization callbacks, possibly populates initial memory-leak records, instantiates (via helpers a couple specific kernel-memory cache some of which are CPU-specific, possibly allocates (via a helper) per-CPU-core vmaps, possibly populates (via a helper) the page-ext datastructures & registers a callback while invoking others, & possibly invokes x86-specific code to work around BSP bugs.

5/6!

Bientôt le million

Then this memory-initialization finishes by invoking some x86-specific code to init Page Table Isolation, possibly (via a few of helpers) tidies up some Kernel Memory Sanitizer memory & transfers over to the new memory allocator with a stack-based GC pass, creates another kernel-memory cache for userspace memory, & configures (via a final helper + wrapper) configures permissions on executable memory.

6/6 Fin for today! Tomorrow: maple trees, & maybe more!

おきた

Your Cherokee words for today.
The top word is English followed by how it is written in the Cherokee language followed by how it is spelled in English then how to pronounce it phonetically.

Nah-Skee Nee-Gay-Suh-Nah Dah-Yay-See Gah-Saw-Hee

why is there a cookie recipe in my SCSI card