Maybe you could just try a different Transmission docker image or build your own? Sounds like some weird instability in that particular version.
Maybe you could just try a different Transmission docker image or build your own? Sounds like some weird instability in that particular version.
What do you mean by a file being displaced? Like do you want it to be unreadable, or unmodified, or just not deleted?
It’s not really possible to have a level of protection that would require more than sudo
because with root access you bypass anything else.
You could put the files on an encrypted volume that uses a special password when it is mounted. Or you could use the chattr
command to set special ext4 attributes that would make it unmodifiable (but could be removed with sudo). Or just record the file’s hash, and that way you know it hasn’t been modified later.
It seems like that port needs to be accessible from the public Internet. Your local computer probably has at least one more firewall between it and the Internet, running on your router. You need to also forward the port on your router, which is what it says in the second half of the guide.
I’ve been using Wayland for 5 years. There were a few bugs in the beggining, but now it works great. These threads are such a waste of time.
I have over 100 confirms X11 developments
That’s great dude. Why don’t you go maintain it then, apparently nobody else wants to: https://www.phoronix.com/news/RHEL10-Removing-X.Org
Wayland took too long
Look up how long btrfs has been in development, or at audio subsystem churn. These things take time, because it’s mostly volunteers working on them.
Systemic complexity has doubled in the last two years
What does this even mean?
Mir was better
It turns out the Canonical dumping random stuff over the wall is not the same as creating a legitimate open source community around a project.
Unfixable amount of race conditions
As if there’s never been a synchronization bug in X… But also System76 and others are writing Wayland compositors on Rust anyway.
I mean xwayland is the best supported X implementation today, and will only get better. You’re not ditching everything when you maintain backwards compatibility.
I think that it’s a great project, and I hope it succeeds. My sense is that there is more momentum around Nix, so for a lot of uses it just makes more sense.
Guix and Nix both have the same issue imo, which is using a loosely typed language with an odd syntax. I feel like something both strongly typed and with a more common syntax would be easier to edit and faster to evaluate.
wearing a collar
What are they, some kind of kittypet?
Most of his fans have never really read his more academic works (like the one with the grandma sex dream). So, I guess they like his vibe. But his vibe is weepy alcoholic. What’s so great about that?
It creates a flat network between all of your devices anywhere, so if you have a home server that you want to connect to from elsewhere you can do that without port forwards.
What’s your use case? Maybe you would be better off with Tailscale or something like that
Biden dropped out. You don’t have to keep doing this.