this post was submitted on 24 Jul 2023
803 points (99.9% liked)

linuxmemes

21210 readers
89 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

  • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] Johanno@lemmynsfw.com 5 points 1 year ago

    Problem is:

    I have no idea what I asked it to do!

    For example I was creating systemd services and stuff because it is actually fun in comparison to init.d back in the days. Now I usually just copy paste tutorials and adjust it until my stuff works.

    But my boot time somehow got longer O didn't noticed it at first, but when I finally digged to the problem it seems that for timed Services you don't want the Service to be installed(or even able to be instlled) and only enable the timer.

    No tutorial told me that.

    To be fair I didn't read the documentation on systemd. But who does?