So basically Apple wants to kill the filesystem on Mac as well.
So basically Apple wants to kill the filesystem on Mac as well.
Huh, I guess Ubuntu patched Unattended Upgrades to change the config format.
Try "cloudsmith/caddy/stable:any-version";
Do you have a particular reason for not using Aurora Store?
You’re right with the origin. codename
or n
in short form is any-version
. ${distro_codename}
won’t match that, as it contains the codename for your distro release, like bookworm
for Debian 12.
With any-version
the repo owner’s basically saying you can install this regardless of your distro version or they handle it on their end somehow.
Try just using the origin instead, like this.
"origin=cloudsmith/caddy/stable";
Unattended Upgrades only checks and updates programs in repos it knows about. As you found out, you’ll need to add the custom repository to the Origins pattern in 50unattended-upgrades.
You can find a list of all repositories and their data using apt policy
Here are the custom repositories I have on one of my servers:
500 https://repo.zabbix.com/zabbix/7.0/debian bookworm/main all Packages
release v=12,o=Zabbix,a=zabbix,n=bookworm,l=zabbix,c=main,b=all
origin repo.zabbix.com
500 https://repo.zabbix.com/zabbix/7.0/debian bookworm/main amd64 Packages
release v=12,o=Zabbix,a=zabbix,n=bookworm,l=zabbix,c=main,b=amd64
origin repo.zabbix.com
500 https://pkgs.tailscale.com/stable/debian bookworm/main all Packages
release o=Tailscale,n=bookworm,l=Tailscale,c=main,b=all
origin pkgs.tailscale.com
500 https://pkgs.tailscale.com/stable/debian bookworm/main amd64 Packages
release o=Tailscale,n=bookworm,l=Tailscale,c=main,b=amd64
origin pkgs.tailscale.com
500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
release o=. nodistro,a=nodistro,n=nodistro,l=. nodistro,c=main,b=amd64
origin deb.nodesource.com
Look at the line starting with release
and search for a combination that uniquely identifies the Caddy repository.
The output above is using the short form keywords, while the examples in 50unattended-upgrades use the long form. It’s fine to use either.
One special case is the site
keyword. This is the URL coming after origin
in the output above and might be confusing.
Keywords
// a,archive,suite (eg, "stable")
// c,component (eg, "main", "contrib", "non-free")
// l,label (eg, "Debian", "Debian-Security")
// o,origin (eg, "Debian", "Unofficial Multimedia Packages")
// n,codename (eg, "jessie", "jessie-updates")
// site (eg, "http.debian.net")
Based on the apt policy
output above, here’s what I use to enable automatic updates for these repositories.
Using origin
and codename
follows the standard Debian repos and I’d recommend using that if possible.
Node doesn’t provide a reasonable repo file, so I had to set site
based on the URL behind origin
in apt policy
"site=deb.nodesource.com"; //Nodesource repository
"origin=Zabbix,codename=${distro_codename}"; //Zabbix Agent repository
"origin=Tailscale,codename=${distro_codename}"; //Tailscale repository
Yeah, but you need root anyways to mount disks (most of the time), so doing a quick chown
isn’t that much effort.
Edit: chown
> chmod
I use multiple subdirectories under /mnt for my fstab/systemd-mount managed disks. That includes local and network locations.
Without docker you still just copy your files from Windows to Linux, though you have to find the right directories for that. Jellyfin can be installed directly on Debian. Just add their repo and go
You can’t really install packages or modify configs on the host without root. Containers can only do some parts.
Maybe, but now I still need to remember the alias or distribute it to any machine I’m working on.
Not that difficult if you have everything managed with Ansible or similar anyways, but lots of people likely don’t have that setup.
Never used Shopify unfortunately, so I can’t help you with that.
The way I tag media is using MediaElch. It requires manually going through each series and identifying it, but with your proper naming it should give decent suggestions already.
If some metadata is missing for single episodes, try changing the metadata provider, sometimes one or the other just has bad/incomplete data.
As someone who writes bash scripts, fuck no, this is a terrible language and it shouldn’t be used for anything more complex than sticking two programs together.
Also, parallelism goes right out of the window.
Maybe you’d convince me with a real programming language.
I might try run0 for fun, but I don’t think it’ll replace sudo any time soon.
The biggest issue I see is run0 purposely not copying any environment variables except for TERM
.
You’d have to specify which editor to use, the current directory, stuff like PATH
and HOME
every time you run a command.
I think hate is really too strong of a word, dislike at most for me.
My biggest issue with Microsoft is a lack of trust. Apart from that, I just like my Linux setup more and find it easier to use.
Stuff I want to do works how I want to do it and how I’m (now) used to it.
Regardless, I use Windows at work, manage Windows Servers and Azure. It’s just how it is.
Because none of the projects you mentioned are GNU projects.
If you only need file syncing, there are better options than Nextcloud. But Nextcloud is the only real option if you want to create a full suite of replacements for office365 or google thanks to the large plugin ecosystem.
I’ve been brainwashed into finding Elixir interesting due to how it handles parallelism and how good it’s supposed to be for live debugging. (According to ~3 talks I found on youtube)
Edit: Syntax error
You could download stressapptest and run that memory benchmark in the normal system.
I’m not sure how well the current version of Memtest does, but when I was overclocking I was told not to use it as it couldn’t reliably get memory to crash. (Funny problem to have). The two recommended tools are Windows only, so I found stressapptest as the best alternative.
AFAIK they allow custom OIDC providers now.