Probably a better idea would be to leave it archived. Whoever wants to take over can fork it and prove themselves by showing their work.
The xz debacle has shown that there are risk involved in an established developer endorsing an unknown one.
Just a note, the US military completed the phase-out of floppy disks in 2019.
Bold of you to assume Ubuntu was a recent version.
Don’t worry, Ubuntu was probably Lucid. 🤭
Medical environments are notorious for inept tech skills and slow technology adoption.
If you did a full memtest and it came out good then OK.
I’m just saying don’t discount hardware issues. Bad RAM blocks are notoriously hard to diagnose by use alone because there’s not just one symptom you can point at, and they can manifest themselves wildly differently on different apps and different OS depending how large the blocks are and how they are spread.
Luckily there’s a very simple and straightforward test you can make to put it out of your mind.
Why not just open the movie with Jellyfin in a tab and share that tab like you do now?
If OP gets Jellyfin working they can just share the tab or window that the Jellyfin web interface is running in. Jellyfin will take care of the playback. No need for the other people to use Jellyfin too.
A crash 1-2 times a week sounds very strange no matter what Linux distro you’re using. I would suggest testing your RAM right away, it could be a hardware problem.
Is it that none exist or that none can be made?
I mean they can be made but it’s going to require reinventing a lot of wheels. You need access to other windows to make this (and lots of other stuff) work, period. Wayland has simply moved the burden of exposing that information to other layers. By the time this is accomplished 100% the information is going to be exposed just as much as on X11, just in a different way.
Because that’s like. the main feature about Wayland.
Is it? It has always seemed like a solution looking for a problem to me. When’s the last time you heard about anybody having a problem with this under X11?
In theory it can be used to do bad things. In practice it’s like wearing a helmet 24/7. It sounds like a good idea and it could help in case you’re in a car crash or a flower pot falls on your head… but the inconvenience makes you not seriously consider it.
My main problem with it is that they simply tossed the dead cat over the wall. You can’t simply say “removed you deal with it” and call it a day, then expect all the rest of the stack to spend a decade solving the problem you created, while you get to look shiny for solving an “issue” that nobody cared about.
My other problem is that it should have been a toggle. Let people who really need to tighten security turn this feature on and let everybody else get on with their lives. Every other isolation feature on Linux (firewalls, AppArmor, containers etc.) is fully configurable. How would it be if your firewall was non-optional and set to DENY ALL all the time? It would be crazy unusable. Yet Wayland made that “the main feature”? Ridiculous.
No screen readers for one thing since they can’t access other windows. You’ll find that most accessibility features require access to other windows in some manner.
Use Borg Backup. It has built-in deduplication — it works with chunks not files and will recognize identical chunks and avoid storing them multiple times. It will deduplicate your files and will find duplicated chunks even in files you didn’t know had duplicates. You can continue to keep your files duplicated or clean them out, it doesn’t matter, the borg backups will be optimized either way.
I think they count every download of every package, every version, every time. It’s not the number of unique users or even packages.
If you install 3 apps you might need to download 3 versions of graphics driver, 3 versions of desktop environment libraries and so on, It won’t count as one user installing 3 apps, it will show up as 10 -20 downloads. And that’s just the initial install, every time you update them it counts another 10-20.
With cgroups, it’s a standard kernel feature. You can limit RAM, CPU, network access, lots of things. It’s used in Docker, LXC, Kubernetes and lots of container solutions.
There’s some hardcore conflation going on that assumes that people with technical skills will tend to be good at everything, or that they’ll gravitate towards the uber-geeky stuff.
In my experience it’s a very wide spectrum. Lots of programmers are strictly focused on the language they use and don’t care to know anything about the OS, or networking, even computers. They are definitely not jacks of all trades.
There are people who can do programming as well as system administration and build a PC and build some book shelves and so on. But that’s a very specific type of person who’s a tinkerer and happens to be into programming, it’s not because they’re a programmer.
I’ve tried Firefox limited to 1 GB for a laugh. It’s usable. It won’t do many tabs at the same time but it’s usable.
You can actually go lower than that but you’ll start to run into limitations with YouTube videos etc.
There are also other browsers out there that are more light-weight but perhaps not as feature-full as Firefox. Giving up extensions alone reduces a lot of complexity. If you fire up the package installer on any Linux distro and search for “browser” you’ll find a ton. There aren’t many engines but there are a lot of browsers.
I’ve had my fill of proprietary media boxes. I have a box full of them somewhere. Eventually they fall behind in codecs and protocols and processing power and updates and they become useless.
I guess I’ll bite the bullet and install Kodi in a container…
See if flatpak has some sort of export format that would let you install everything the same on the other machine. Some package managers have that.
It’s not. Series X and series S use native Bluetooth and work with xpadneo. Older controllers use their own proprietary receiver that needs to be plugged into the machine and work with regular xpad.