• 0 Posts
  • 29 Comments
Joined 1 year ago
cake
Cake day: September 8th, 2023

help-circle













  • genie@lemmy.worldtoTechnology@lemmy.worldThis was the first result on Google
    link
    fedilink
    English
    arrow-up
    9
    arrow-down
    1
    ·
    edit-2
    8 months ago

    Now I don’t know enough about electronics to know how wrong this is

    Very, assuming the refrigerator in question typically runs on a typical power grid you’d find in the US or Europe (source: am electrical engineer)

    Mainly because most compressors I’m aware of use alternating current (AC) motors, or at a minimum accept AC power. Batteries alone produce direct current (DC). The simplest way to make this work would involve an inverter (converts DC to AC). Cheap ones probably have at least a 10% conversion loss, so you’re looking at an hour or two at most.

    Edit: should also mention that discharging a typical lead-acid battery until it’s all the way flat (realistically below ~11V) does irreparable damage. Might be cheaper to replace the contents of your fridge :)



  • Haha I’ve had a journey to get here, all because I have a 12th gen Framework.

    Initially I got Debian Sid working but ran into power management issues with the module system. I switched over to arch and loved that for a while but frankly I was too careless and kept breaking my system. The way I use Arch it wasn’t a stable daily driver. Then I switched over to NixOS and loved it, but I bricked 3 of 4 ports with a firmware update (again me being careless). Graciously, Framework helped me fix the issue.

    After all of that I decided to go with a distro that is officially supported by Framework. Between Ubuntu and Fedora I choose Fedora since they don’t have ads for Ubuntu Pro :) I also like SELinux by default and wanted to broaden my horizons


  • I tried Debian + Nix once upon a time too. Honestly flatpaks and containers did everything I needed and more, and every dev team I’ve been on already has familiarity with the container workflow.

    I’m a huge fan of Debian and Nix, don’t get me wrong, but it was shy of perfect for my use case. Glad it works for you though! I’ve been using Fedora + Nix home-manager with flakes for almost two years and I don’t think I’ll ever go back



  • It’s definitely a skill that I haven’t mastered either! That being said I think it’s one of the pillars of being a bonafide “super user” and I’d like to set there one day :)

    Maybe I’ll take inspiration from this post and write something up about what I learn in the future about manpages.

    Cheers and happy tinkering!


  • genie@lemmy.worldtoLinux@lemmy.mlWhat I've Learned This Week
    link
    fedilink
    arrow-up
    3
    ·
    edit-2
    10 months ago

    Thanks for putting this out for public benefit! I haven’t messed around with MacOS much but the things you’ve mentioned are nice to know.

    I believe that’s a shell/bash standard variable, but I need to learn where it came from and how it works

    You may know this already, but I’ve found the man (as in manual) utility to be one of the most useful things in GNU/Linux user space. I don’t have much insight into ‘${file##*/}’ off the cuff, but I can tell you there’s manual entries for file, sh, and bash that may help you track it down.

    # simply type man [some-command]
    man file
    man sh
    man bash
    man man # very useful for getting started!
    

    Manpages are local to your system so they’re extremely fast to pull up and searchable!

    Here’s some online info on man if you’re interested:

    (30 sec read) Unix stack exchange tips & tricks

    (5 min read) It’s FOSS writeup