it should probably stay in docker containers
it should probably stay in docker containers
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.
What are you even talking about? systemd is currently under an opensource license, they cant retroactively change that. Any changes would be for it going forward if it is even possible for them to buy the rights to it (which I’m not convinced it is as Lennart Poettering is not the sole contributor and Red Hat / IBM and many others also have a significant stake in it). Sun patented Java on it upon its creation and when oracle bought sun, they bought the rights to those patents. They aren’t comparable situations. Java was never open source, it was source available, but still proprietary.
Its certainly easier to read than most old init scripts and I can see why some distros and openbsd would pick it over systemd for more control. I’m not likely to pick a distro that uses it anytime soon, but i can see why some do.
That is my point, they have tried and failed completely before when their main product was windows licenses. Now, linux is incredibly important to their azure business, they wouldn’t want to potentially cause detriment to that and is far more important to them than windows licenses.
Also why would we have to rip out systemd, even if they tried to claim ownership of it and make it proprietary, it could be forked from before the license change and we would keep on going like nothing happened.
people keep saying this, but what is their extinguish plan? how could they realistically extinguish linux? it’s not a company they can buy, or even a single thing they can ruin.
can you give examples of some? Not trying to bd sarcastic, i do just want to see what alternatives are doing.
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.
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.