𝕽𝖚𝖆𝖎𝖉𝖍𝖗𝖎𝖌𝖍

       🅸 🅰🅼 🆃🅷🅴 🅻🅰🆆. 
 𝕽𝖚𝖆𝖎𝖉𝖍𝖗𝖎𝖌𝖍 𝖋𝖊𝖆𝖙𝖍𝖊𝖗𝖘𝖙𝖔𝖓𝖊𝖍𝖆𝖚𝖌𝖍 
  • 7 Posts
  • 856 Comments
Joined 2 years ago
cake
Cake day: August 26th, 2022

help-circle
  • I love this comment.

    My related anecdote is that I studied Aikido for many years, and there’s a lot of woo-woo in it. Energy, and Ki and whatnot. At one point (I was taking physics at the time) I realized that Aikido of all about directing momentum and force, and force as levers on body parts, and that you could probably calculate all of the various ideal angles for maximum conservation of momentum, and angles for balance points… and I realized that all of the woo-woo was a simplification of all of this that allows people to think about all of these things in real time and intuitively, rather than getting locked up in the theory.

    I doubt that was the process and intention of the inventor, and a lot of practitioners believed in Ki or Chi or magic juice… but it’s all just physics boiled down to something people can easily visualize. And, yes, the problems start when people begin believing the magic juice, and start proclaiming that they can influence someone’s chi from a distance, or some shit. That’s a far cry from: if I bend your wrist this way, it’s incredibly painful and you’re going to fall over to stop it, or break your wrist.







  • As Linux is a multi-user system, stuff you install can either run a system process, or a user process. Most other comments are assuming you installed a process that’s running as a user. On Arch, this could either be an autostart process (which is desktop agnostic) or something attached to Gnome or KDE’s startup.

    On Arch,systemd controls system services. There are two key CLI commands for working with systemd (and some GUIs, but you’ll have to find those). The first is systemctl, and the second is journalctl. The second gets you logs. The first controls services.

    systemctl status will give you an overview of all the services on your system.

    sudo systemctl stop <service name> will temporarily stop a service; ... start ... starts it again. ... disable ... will stop it from starting when you reboot – this does not stop the service, it only prevents it from being started again in reboot. As you’ve guessed, ... enable ... re-enables the service. ... status ... gives you a status for the process, and the last few lines of the log for it.

    systemd services can also be run at the user level; the commands are all the same, but you add --user every time to control the user services.

    journalctl -xe gives you a system log since boot. You can also look at logs for previous boots, look at logs only for a single process (-u <servicename>), look at user processes (same --user argument), tail a log to watch new messages roll in (--tail) and a bunch of other stuff.

    Systemd also controls scheduled jobs (that used to be handled by cron) with timers. Really, most Linux distros these days should be known as systemd/Linux.

    I suspect what you’re looking for is sudo systemd disable <service>, but if it’s a user processes, check ~/.config/autostart and your desktop config tool section for auto-start settings.

    It will help if you can say which desktop you’re using (Gnome? KDE? LXDE? Or just a window manager?) and what the package is. If you give the package name, we can explain exactly how to disable it. Otherwise, you have the hodge-podge of answers below.






  • There are a frightening number of systems that don’t allow “-”, which isn’t even an edge case. A lot of people - mostly women - hyphenate their last names on marriage, rather than throw their old name away. My wife did. She legally changed her name when she came of age, and when we met and married years later she said, “I paid for money for my name; I’m not letting it go.” (Note: I wasn’t pressuring her to take my name.) So she hyphenated it, and has come to regret the decision. She says she should have switched, or not, but the hyphen causes problems everywhere. It’s not a legal character in a lot of systems, including some government systems.









  • I started with rootless podman when I set up All My Things, and I have never had an issue with either maintaining or running it. Most Docker instructions are transposable, except that podman doesn’t assume everything lives as dockerhub and you always have to specify the host. I’ve run into a couple of edge cases where arguments are not 1:1 and I’ve had to dig to figure out what the argument is on podman. I don’t know if I’m actually more secure, but I feel more secure, and I really like not having the docker service running as root in the background. All in all, I think my experience with rootless podman has been better than my experience with docker, but at this point, I’ve had far more experience with podman.

    Podman-compose gives me indigestion, but docker-compose didn’t exist or wasn’t yet common back when I used docker; and by the time I was setting up a homelab, I’d already settled on podman. So I just don’t use it most of the time, and wire things up by hand when necessary. Again, I don’t know whether that’s just me, or if podman-compose is more flaky than docker-compose. Podman-compose is certainly much younger and less battle-tested. So is podman but, as I said, I’ve been happy with it.

    I really like running containers as separate users without that daemon - I can’t even remember what about the daemon was causing me grief; I think it may have been the fact that it was always running and consuming resources, even when I wasn’t running a container, which isn’t a consideration for a homelab. However, I’d rather deeply know one tool than kind of know two that do the same thing, and since I run containers in several different situations, using podman everywhere allows me to exploit the intimacy I wouldn’t have if I were using docker in some places and podman in others.