Off-and-on trying out an account over at @tal@oleo.cafe due to scraping bots bogging down lemmy.today to the point of near-unusability.

  • 2 Posts
  • 491 Comments
Joined 3 years ago
cake
Cake day: October 4th, 2023

help-circle
  • Magewell Pro Capture card

    I’ve been kind of shifting towards use of USB devices over internal cards.

    All of the USB devices that I have still can be connected to computers. Ditto for DE-9 serial ports, though I might need a USB adapter.

    But I’ve seen ISA->PCI/AGP->PCIe obsolete a lot of old hardware that I’ve had sitting around, and that’s just on the PC. That includes my video capture hardware.








  • Why am I not surprised to hear APC is crap compared to Eaton?

    Keep in mind that this isn’t my personal experience talking here. I also don’t know if the user in question is correct, or if it might be specific to some portion of the respective brands — both make a wide range of UPSes, from inexpensive to pretty pricey. But I did remember reading that, and it did seem potentially germane to OPs problem, so…shrug

    Someone with a multitester or oscilloscope or something and some of those units could probably examine further, see what the actual behavior is for a given model.











  • tal@lemmy.todaytolinuxmemes@lemmy.worldIt's hacker time
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    25 days ago

    history | grep 'keyword'

    If it’s bash, it’s using readline, which is in emacs-like mode by default, and so you can probably use Control-R to do a reverse i-search (incremental search). Enter to invoke the command. Control-C to abort i-search.

    If a search matches multiple candidates, tap Control-R multiple times to cycle back through results.

    EDIT: Also, ! has a built-in search, so if you are sure of the starting string, you can just do that. I generally prefer to use the interactive search to confirm that I’m not invoking something wonky.

    $ touch a
    $ rm a
    $ touch a
    $ !rm
    rm a
    $ 
    

  • tal@lemmy.todaytolinuxmemes@lemmy.worldIt's hacker time
    link
    fedilink
    English
    arrow-up
    7
    arrow-down
    1
    ·
    25 days ago

    You copy paste the command.

    $ sudo apt update
    -bash: sudo: command not found
    $
    

    Your distro doesn’t set up/install sudo by default, so your first task is installing sudo, then understanding /etc/sudoers syntax and understanding why the command to atomically replace /etc/sudoers is visudo and why on a multiuser system there’s value to atomic replacement. In the meantime, you probably learn about su and maybe, if your distro has disabled them, how to enable switching to the kernel virtual consoles on tty1 through tty7 so that in the meantime, you can do things as root while staying logged in. Also, you’re going to learn about environment variables, so as to set EDITOR, and where your shell config files live, what a login shell is, and in what shells ~/.bash_profile, ~/.profile, and ~/.bashrc run. Also, you first try running visudo as a regular user, but your distro places visudo in /usr/sbin instead of /usr/bin, so you can’t figure out why it’s not installed and are going to learn about the FHS and mlocate and updatedb so that you can find /usr/sbin/visudo and dpkg -S so that you can figure out which package it’s in and confirm that it’s actually installed and learn about PATH.