• Ilovethebomb@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    22
    ·
    7 months ago

    I’ve got a Windows 10 machine that can’t be upgraded that I plan to install some flavor of Linux on, probably Mint.

    When I get around to it.

    • Tahl_eN@lemmy.world
      link
      fedilink
      English
      arrow-up
      12
      ·
      7 months ago

      That’s my project for this weekend or next. Gotta figure out how to make it play nice with my Wacom and NAS.

      • grue@lemmy.world
        link
        fedilink
        English
        arrow-up
        6
        ·
        7 months ago

        Are you expecting it to be more complicated than “plug tablet into USB” and “connect computer to network and direct your file browser to the NAS’ IP?”

        • Tahl_eN@lemmy.world
          link
          fedilink
          English
          arrow-up
          4
          ·
          7 months ago

          I’m running Pop!OS on a different old laptop, so I know the basic functionality works out of the box, but that I’m going to have to resort to the terminal to get the express keys mapped on the Wacom. And the NAS connection has been a second-class citizen; it’s been difficult to just browse to it in a lot of apps. I suspect I need to properly mount a the NAS as a drive for it to play nice. Neither are things I’ve bothered with on the Pop system since I’ve just been using it as a web portal, but I want the new device to be more functional.

          • hraegsvelmir@ani.social
            link
            fedilink
            English
            arrow-up
            4
            ·
            7 months ago

            It wasn’t that difficult for me to set up my NAS to automount in my fstab file. I’m pretty sure I just followed this guide and went into my router to make sure the NAS was assigned a static IP address on my LAN. Until I set the IP, it would almost always get the same IP address from my router, but on the rare occasion where it didn’t it would cause some of my self-hosted media services to fail to start at boot when mounting it failed, and it would bork the whole thing. Still, that was more user error than anything else.