Skip Navigation

Posts
0
Comments
553
Joined
2 yr. ago

  • there are issues with the software we’re using that can only be remedied by massive changes or a complete rewrite.

    I think this was the main reason for the Wayland project. So many issues with Xorg that it made more sense to start over, instead of trying to fix it in Xorg.

  • I'm probably the odd one out, but my home server is running Arch Linux. And it's been really smooth. I do weekly maintenance in the form of updates and cleanup and it's been reliable since I set it up a couple of years ago.

  • Sure. But if the project in question only has one or two donation methods and none of those are supported by the company, then the company can't easily donate anything. Companies usually have a strict way of how they can donate and it usually entails Paypal or some other costly solution, while projects like that likely just has a patreon or LibrePay option and perhaps a crypto wallet. Most companies can't work with that.

  • ElementaryOS is a great system, if you need something that behaves and looks a bit like MacOS. It's based on Ubuntu LTS versions, so should be good for a few years at a time.

  • Sounds like you have a general issue with permissions on your filesystem if you can't even write the compose file.

    Have you set up docker stuff before?

  • If you worry about potential other backdoors in newer XZ versions, then you should also look into your kernel, systemd, dbus etc etc. All these things, can potentially contain backdoors that no one knows about yet.

    As for currently known backdoors, the Arch versions are safe.

  • RSS notifications from their respective release pages is how I'm doing it.

  • Maybe it's time to clean out some old snapshots in Snapper.

  • I had a Dell back in the day (like 20'ish years ago) and I had the same experience on the Windows install it came with. Sad to hear that they just switched the issues over to Linux from Windows. :(

  • 127.0.0.1 is actually the most local IP you can connect to, as it will always connect to the device you are on. ;) Can't get any more local than that.

    Sorry, not helping, I know.

  • My server is on my LAN, so I get full Gigabit connection.

  • I can't speak for anyone else, but for me, it's just one file to backup to keep all your custom commands (.bashrc) while it would be many files if you have a script for each.

    I can't see the benefit of having a script for just one command (with arguments) unless those arguments contain variables.

  • I use bash and I usually put /bin/bash in my scrtipts, because that's where I know it works. /bin/sh is only if it works on many/all shells.

    I don't have many such scripts, so I just have one. I don't really share them, as they are made for my usecase. If I do create something that I think will help others, then yes, I share them in git somewhere.

    I do have a scripts folder in my Nextcloud that I sync around with useful scripts.

    Some of your examples can probably just be made into aliases with alias alias_name="command_to_run".

  • I assume you have added the repo because it fixed some issues at some point. Is the repo still needed to fix those or could you remove the repo and just update using normal distro packages?

    DISCLAIMER: I don't use OpenSUSE or any of the variants. I assume that the obs stuff is kind of like how the AUR is for Arch, or PPA's are for Ubuntu. If it's something difference, please disregard my comment.

  • Sure, but they specifically asked for it to unlock on autologin. Meaning no password to be entered. If you lock the screen right away, you still need to put in a password, so that is not what they want.

  • No. You might aswell not use a wallet in that case, since nothing is protecting your passwords.

  • It is very arbitrary. Some/most non-free applications usually drop stuff into /opt, so it does not spread all over the filesystem. It makes sense if the application was not developed with Linux in mind, like Discord, Teamviewer etc.