• 2 Posts
  • 124 Comments
Joined 3 years ago
cake
Cake day: June 15th, 2023

help-circle


  • My ex-brother-in-law killed a family of four while DUI. The cops really screwed up the investigation so he was able to get the charges down to a minor moving violation. He never saw the inside of a jail.

    When I was in high school a friend of a friend that I knew and had hung out with at a couple of times was a serial killer/rapist. He was one of the last people executed by that state.

    Edit: My grandfather killed some Nazis in WW2. Several former coworkers killed people in the line of duty as soldiers. And, I worked as a records clerk at a nursing home, so I knew several doctors and nurses that had taken people off life support.



  • My version is definitely wordier, but I like it.

    add-alias() {
      if [[ -z "$1"  ||  -z "$2" ]]; then
        echo "Useage: add-alias <alias_name> \"<command_to_alias>\""
        return 1
      fi
      echo "alias $1='$2'" >> ~/.bash_aliases
      source ~/.bash_aliases
      echo "Alias '$1' for command '$2' added and sourced."
      
    }
    

    And, of course, the first thing I test it with is $ add-alias alias-add add-alias.








  • The dev entry point changing like that means that it disconnected and then reconnected, which shouldn’t have anything to do with the specific file system on the drive. That really makes it sound like the drive isn’t getting quite enough power, which causes a brown out, which Linux detects as the drive getting unplugged and coming back, which is why it gets a new dev entry.

    A look through the usb logs by using something like usbrip would confirm that.