• 1 Post
  • 30 Comments
Joined 1 year ago
cake
Cake day: July 6th, 2023

help-circle
  • 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.









  • 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:
    






  • 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.



  • 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.