<rant>
The clock in the OS works by having the time updated based on the counter in the RTC.
Sun with #Solaris Zones made every object inside the kernel have a zone context and then very carefully abstracted and hardened any exchange across zone boundaries so that there isn't even a handle on global resources inside a zone.
So it followed that each zone could have its own clock object spawned and all existing software would seamlessly work inside a zone.
1/2
Aaron Toponce ⚛️:debian: /
npub14d…s5uyy
2023-08-23 22:09:36
Author Public Key
npub14dfr55yyvfw0leduur7e4af7fnkeegww6e2n64laxkkdyn4sufrqhs5uyyPublished at
2023-08-23 22:09:36Event JSON
{
"id": "5b4751350d94b652cd73799dd7d9d936fafc84bf72bff3233ef64ed8bc310931",
"pubkey": "ab523a5084625cffe5bce0fd9af53e4ced9ca1ced6553d57fd35acd24eb0e246",
"created_at": 1692828576,
"kind": 1,
"tags": [
[
"t",
"solaris"
],
[
"proxy",
"https://fosstodon.org/users/atoponce/statuses/110941213592842123",
"activitypub"
]
],
"content": "\u003crant\u003e\nThe clock in the OS works by having the time updated based on the counter in the RTC.\n\nSun with #Solaris Zones made every object inside the kernel have a zone context and then very carefully abstracted and hardened any exchange across zone boundaries so that there isn't even a handle on global resources inside a zone.\n\nSo it followed that each zone could have its own clock object spawned and all existing software would seamlessly work inside a zone.\n\n1/2",
"sig": "207a774789fe3381f6e4f4a85628c8bd2663cc7152bdf589b466236af190ced62a8d9ab0516851f5c935098d29d8a62a5968b5bed1e217e361fa6e13e2318d9e"
}