𝕽𝖚𝖆𝖎𝖉𝖍𝖗𝖎𝖌𝖍

       🅸 🅰🅼 🆃🅷🅴 🅻🅰🆆. 
 𝕽𝖚𝖆𝖎𝖉𝖍𝖗𝖎𝖌𝖍 𝖋𝖊𝖆𝖙𝖍𝖊𝖗𝖘𝖙𝖔𝖓𝖊𝖍𝖆𝖚𝖌𝖍 
  • 10 Posts
  • 1.58K 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.


  • This is fantastic. Was not expecting the punchline.

    Young me would have missed the personal interaction. Older, less hormonally-motivated me would be fine if the accommodations were nice, reasonably large, and contained a good, Linux-based, powerful computer, a copy of the entire Library of Congress archives, and deep clones of Github and Sourcehut. A decent, fast, current generation AI setup would go a long way to filling any gaps. I think I could probably live for several decades - maybe centuries - left to my own devices. Until the literature and media ran out.

    I’d like to be able to work with AI systems to generate movies from my favorite sci-fi books. Just, throw literature at it, give it some direction, tweak the output, have a ton of dedicated processing power and a lot of free time, and no copyrights to worry about.








  • Honestly, find an existing project in your language of choice with an active maintainer and start fixing tickets.

    You start a new project, odds are you’re stuck maintaining it for years, and it becomes a job, or it dies. IME, it’s far better to find a project you yourself use and like, that you’re capable of contributing to, and doing that. Start popping stuff off the bug list, if you’re a hero, or implement that missing feature in the backlog that you want. Your commitment to the project is a patch. Or, maybe you like working with the project and you become a long term contributor.

    That’s just my recommendation. I’m not saying don’t start something new; just, if you’re looking around for things to do, and aren’t passionately trying to scratch an itch you haven’t found a solution for, you’re most likely just going to create a throw-away project.

    Just my opinion.