You shouldn’t be comparing with DIMMs, those are a dead end at this point. CAMMs are replacing DIMMs and what future systems will use.

Intel likely designed Lunar lake before the LPCAMM2 standard was finalized and why it went on package. Now that LPCAMMs are a thing, it makes more sense to use those as they provide the same speed benefits while still allowing user replaceable RAM.

You were never actually able to buy a game, it has always been a “license” to play it. Even for physical cartridges and disks. The difference being, legally speaking, if you actually owned it, you could make and sell copies of it or take the assets from the game and make a new game with them and then sell that. Owning a license means you can play it, but cant make copies or reuse the assets.

Even with physical media, that license could in theory be taken away if the rights holder chose too. Realistically it would be impossible to enforce since there is no way of tracking down all the physical copies, so no one has ever tried to do it. But legally it works exactly the same as on steam. The only change is that a new california law is going to require steam, and other stores, to be transparent about it, but nothing is actually different.

Even on GOG, where they give you a DRM free binary, if the rights holder doesnt want it available anymore, they have to take it away. You wouldn’t be able to download it and if you had saved a copy of the DRM free binary, playing it would legally be the same as piracy at that point.

Despite all of this, game preservation is alive and well and isn’t going anywhere.

AWS has multiple teirs of storage options in s3, some replicate and some dont. by default those that do replicate do so in multiple availability zones, but not across regions. unless you turn on cross-region replication (CRR) which is an additional charge.

So, for example without CRR if your bucket is in us-east-1 and 1 availability zone goes down you can still access the data, but if all of us-east-1 is down, you cannot.

All that stuff you talked about in the tabletop lore is literally talked about in the game. It’s not hitting you in the face in the main quest line, but if you play the side quests you find tons of fucked up shit that the corps are doing.

As if managers even know what RISC-V is

Its the server world that is demanding it. For most consumers 4.0 is more than enough, but servers are already maxing out 5.0 and will probably immediately max out 6.0 when devices actually become available.

the NSA (which lacks a mandate to act on US soil, and CF is a US company)

They absolutely do have a mandate to operate on US soil, that is actually the main mandate and there is a separate military agency (CNMF) that operates on foreign soil. They are both headed by the same guy though so they might as well just be one agency.

the thing about Recaptcha is that it didn’t always gate keep a google provided service, so that logic doesn’t really work. i agree though that we all benefit from less bots.

yahoogle

There is one extra step. I have an 6700xt, and with the docker containers, you just have to pass the environment variable HSA_OVERRIDE_GFX_VERSION=10.3.0 to allow that card to work. For cards other than 6000 series, you would need to look up the version to pass for your generation.

Here’s an example compose file that I use for ollama that runs ai models on my 6700xt.

version: '3'
services:
  ollama:
    image: ollama/ollama:rocm
    container_name: ollama
    devices:
      - /dev/kfd:/dev/kfd
      - /dev/dri:/dev/dri
    group_add:
      - video
    ports:
      - "11434:11434"
    environment:
      - HSA_OVERRIDE_GFX_VERSION=10.3.0
    volumes:
      - ollama_data:/root/.ollama

volumes:
  ollama_data:

have you tried the rocm docker containers that amd makes for your needs? it pretty much makes installing rocm on the base OS unneeded for me. https://hub.docker.com/u/rocm https://github.com/ROCm/ROCm-docker

it doesn’t, what this is suggesting is the vpn was routing traffic through it so they could analyze snapchat traffic. not the contents of it but essentially meta analysis of the traffic. how often it was sending data, how much data, where it was going etc.

just a small correction, /etc does get snapshotted when upgrades happen and will roll back along with everything else. you are correct though that home does not get snapshotted and is fully mutable.

I don’t have an answer to your nvidia question, but before you go and spend $2000 on an nvidia card, you should give the rocm docker containers a shot worh your existing card. https://hub.docker.com/u/rocm https://github.com/ROCm/ROCm-docker

it’s made my use of rocm 1000x easier than actually installing it on my system and was sufficient for my uses of running inference on my 6700xt.

Immutable isnt really the best word for these distros. Its why fedora is changing the name to atomic, as in changes made to the system are done atomically like git. This also means changes can be rolled back just as easily as they were made.

The trick was to install VSCodium from the Toolbox

Another option you can try that I use is the dev containers extension which allows you to move your workspace to different containers from within vscode. I will say however, i have tried many times to get it working in vscodium and have been unsuccessful and it only seems to work in vscode proper.

With fedora atomic, lets say i wanted to try out kde desktop for a while. i would first pin my current build so i can roll back to it if i dont end liking kde with

$ sudo ostree admin pin 0

Then i would rebase to the kde branch with

$ rpm-ostree rebase fedora:fedora/39/x86_64/kinoite

Then just reboot. That’s literally it and i would have a kde system with all my layered packages and i could roll back to my old system at anytime.

all changes in etc are snapshotted with each update so you could just roll back to your previous version and it would fix it.

I assume you meant you messed up permissions in your home directory, and yes that is pretty much the only place you can permanently mess something up with silverblue.

honestly i feel exactly the opposite, I don’t think it’s really necessary for servers as tools like ansible are already well established in that space. Plus most servers are VMs these days which can be snapshotted easily. Also, lot of these “immutable distros” require a reboot to apply changes which is non ideal in a server, but a non issue for desktop as you can shut it down when you go to sleep.

I run fedora atomic on my desktop and laptop because i never have to worry about my system getting into a broken state, I can always roll back or even spot the problem and fix it before i reboot to apply the change. I know a lot of people say you can accomplish the same thing with btrfs snapshots, but that requires extra thought and effort on my part, where fedora atomic it happens automatically with every update.

what issues have you had with libvirt and windows? Once you get the windows drivers installed, it works pretty much the same as other solutions. only thing thats still a pain in the ass still is shared folders.