Alt account of @Badabinski

Just a sweaty nerd interested in software, home automation, emotional issues, and polite discourse about all of the above.

  • 0 Posts
  • 8 Comments
Joined 5 months ago
cake
Cake day: June 9th, 2024

help-circle





  • My pain tolerance for shitty input methods has been permanently warped after experiencing psychic damage from using Teamviewer to connect to a system over a very flaky HughesNet satellite link. I was working for a vendor that supplied a hardware networking box to a stupid retail company that sells food and shit. I just wanted to ssh to our boxen on a specific network so I could troubleshoot something, but the only way I could get to it was via putty installed on an ancient Windows XP desktop on the same network as our box that could only be accessed with Teamviewer. My favorite part of that was that the locale or something was fucked up, so my qwerty keyboard inputs were, like, fucking transformed into azerty somehow?? The Windows desktop was locked down and monitored to a tremendous degree, so I couldn’t change anything. The resolution was terrible, the latency was over a second, and half of my keyboard inputs turned into gibberish on the other side.

    Oh, and I was onsite at that same company’s HQ doing a sales engineering call while I was trying to figure out what was wrong. I spent 5 days sitting in spare offices with shitty chairs, away from my family, living that fucking nightmare before I finally figured out what was wrong. God damn, what a fucking mess that was. For anyone reading this, NEVER WORK FOR GROCERY/DRUG STORE IT. They are worse than fucking banks in some ways. Fuck.

    EDIT: also, I asked ‘why Teamviewer’ and the answer was always shrugs. This was before the big TeamViewer security incidents, so maybe they thought it was more secure? Like, at least they didn’t expose RDP on the internet…


  • Having been in this situation (the only binary I could use was bash, although cd was a bash builtin for me), echo * is your friend. Even better is something like this:

    get_path_type() {
        local item
        item="$1"
        [[ -z "$item" ]] && { echo 'wrong arg count passed to get_path_type'; return 1; }
        if [[ -d "$item" ]]; then
            echo 'dir'
        elif [[ -f "$item" ]]; then
            echo 'file'
        elif [[ -h "$item" ]]; then
            echo 'link'  # not accurate, but symlink is too long
        else
            echo '????'
        fi
    }
    
    print_path_listing() {
        local path path_type
        path="$1"
        [[ -z "$path" ]] && { echo 'wrong arg count passed to print_path_listing'; return 1; }
        path_type="$(get_path_type "$path")"
        printf '%s\t%s\n' "$path_type" "$path"
    }
    
    ls() {
        local path paths item symlink_regex
        paths=("$@")
        if ((${#paths[@]} == 0)); then
            paths=("$(pwd)")
        fi
        shopt -s dotglob
        for path in "${paths[@]}"; do
            if [[ -d "$path" ]]; then
                printf '%s\n' "$path"
                for item in "$path"/*; do
                    print_path_listing "$item"
                done
            elif [[ -e "$path" ]]; then
                print_path_listing "$path"
            printf '\n'
            fi
        done
    }
    

    This is recreated from memory and will likely have several nasty bugs. I also wrote it and quickly tested it entirely on my phone which was a bit painful. It should be pure bash, so it’ll work in this type of situation.

    EDIT: I’m bored and sleep deprived and wanted to do something, hence this nonsense. I’ve taken the joke entirely too seriously.


  • Badabinski@kbin.earthtoMemes@lemmy.mlawHell Naw
    link
    fedilink
    arrow-up
    0
    ·
    2 months ago

    Seriously. The ECU in my partner’s truck decided that it was done with magic smoke and Marie Kondo’d that shit out, leaving her stranded. Her truck is an old 2002 Dodge Dakota that we’ve been nursing along while the used car market cools down (we want to get her something small and fuel efficient, but cars cost too damn much). Back in 2000 or 2001, some bean counter at Dodge decided that the company really had to cheap the fuck out with their ECUs for the 2002 model year. Because of this, any 2002 Dodge truck has either had its ECU replaced or is a ticking fucking time bomb.

    What’s even better is that nobody makes these shit-ass ECUs anymore. The only replacements you can get are remanufactured units, and it’s highly likely that you’ll get at least one dud before you can find anything decent. We’ve been a tiiiiiiny bit less lucky than that, meaning we’re on our 13th ECU. Our mechanic has gone through everything else to make sure there’s not something external that’s exploding the ECUs, and he hasn’t found anything. Over the course of like 9 weeks, we’ve completely deleted the stock of these stupid things in Utah and all of the surrounding states. We’re now ordering one from Florida that’s been remanufactured by a different company which hopefully won’t grenade itself.

    Fuck American car companies, and apologies to anyone who’s currently having a hard time sourcing an ECU for a 2002 Dodge Dakota. We screened all the bad ones out for you. The only good part about all of this for us is that our mechanic isn’t charging us for anything more than one ECU replacement. The damn truck has been in the shop for 9 weeks, and we’re only going to pay like $1000.