Cheaper is one aspect. Less physical things to have to keep track of and manage is what I am really after. I want a singular device that is capable of all the things/modes that I want. I’m sure I’ll get downvoted for this, but what I see is a singular device capable of all sorts of things being eventually small enough to be embedded inside a body, essentially like cyborg. Like 100 years from now assuming society doesn’t collapse by then.
Why have one device or why desktop mode?
One device because it would reduce the burden on me of maintaining multiple devices, the security updates, passwords, etc.
Why desktop mode? Because when I try to do what I would call “serious work” (probably a bad name for it, but think something requiring extended periods of deep focus), the interface of smartphones is not conducive for it. Precision of a mouse is required, ability to type 100+ words per minute is required, so that necessitates mouse and keyboard. Then there’s the UX itself. Smartphones have tiny screens so they can’t have many menu items or controls in the apps that are used for “serious work”. That requires larger screen real estate, so necessitates an external monitor.
I don’t want to start rambling so I’ll just leave it at that.
I’ve been wanting a phone that can dock and be used as a full fledged desktop since smartphones first came out. Samsung Dex apparently comes close, but is too limited in terms of the desktop app side.
They should have just called it appleOS 26 since they are bumping all of it to 26 and unifying the look and feel between all of their OSs.
How difficult is it for an adversary to get in the middle of the TPM releasing the keys to LUKS? That’s why I would want attestation of some sort, but that makes it more complicated and thinking about how that would work in practice makes my head spin…
Is clevis using an attestation server or is it all on a single machine? I’m interested in getting this set up but the noted lack of batteries included for this in the common distros makes it a somewhat tall order.
please share the script?
I’m really not sure. I’ve heard of people using Ceph across datacenters. Presumably that’s with a fast-ish connection, and it’s like joining separate clusters, so you’d likely need local ceph cluster at each site then replicate between datacenters. Probably not what you’re looking for.
I’ve heard good things about Garbage S3 and that it’s usable across the internet on slow-ish connections. Combined with JuiceFS is what I was looking at using before I landed on Ceph.
I know Ceph would work for this use case, but it’s not a lighthearted choice, kind of an investment and a steep learning curve (at least it was, and still is, for me).
I went and edited my hosts file and added all of my devices, but I only have a handful. Tailscale on macOS has a lot of bugs, this being one of many.
Step four, you want to pull the fluid column up to unstick the trash, so go slow ‘down’ and somewhat more forceful on the ‘up’.
Try these steps:
$ sudo apt-get purge nvidia* # remove current installed nvidia software including drivers
$ sudo ubuntu-drivers devices # verify it sees your graphics card
$ sudo ubuntu-drivers autoinstall # install drivers automatically
$ sudo reboot
This is everything I ended up doing which eventually fixed it for me:
# Update repo
sudo apt update
# Remove amdgpu drivers
sudo apt purge xserver-xorg-video-amdgpu
sudo apt purge libdrm-amdgpu*
sudo apt purge libdrm-amdgpu1
# Blacklist the amdgpu driver since we are using nvidia only
echo "blacklist amdgpu" | sudo tee -a /etc/modprobe.d/blacklist.conf
# Remove nvidia driver and install from system76 repo
sudo apt purge *nvidia*
sudo apt-add-repository -y ppa:system76-dev/stable
sudo apt install -y system76-driver-nvidia
sudo apt upgrade -y
sudo reboot
It depends on the container I suppose. There are some that are very difficult to rebuild depending on what’s in it and what it does. Some very complex software can be ran in containers.
I’ve been wanting to tinker with NixOS. I’ve stuck in the stone ages automating VM deployments on my Proxmox cluster using ansible. One line and about 30 minutes (cuda install is a beast) to build a reproducible VM running llama.cpp with llama-swap.
Do you gave an nvidia graphics card? The only problem I’ve had since I installed Pop OS is their shity driver installer crapped out somehow and I gad to recover my system by blacklisting amd graphics driver, uninstall nvidia driver and reinstall. It wad not for the feint of heart.
Typically, the container image maintainer will provide environment variables which can override the database connection. This isn’t always the case but usually it’s as simple as updating those and ensuring network access between your containers.
A lot of times it is necessary to build the container oneself, e.g., to fix a bug, satisfy a security requirement, or because the container as-built just isn’t compatible with the environment. So in that case would you contract an expert to rebuild it, host it on a VM, look for a different solution, or something else?
reproducing those installs from scratch + restoring backups would be a single command plus waiting 5 minutes.
Is that with Ansible or your own tooling or something else?
Isn’t the context of that quote around the kernel and kernel space vs user space? I don’t see how that thought really extends to distros that simply implement the kernel as one of their packages.