• 1 Post
  • 41 Comments
Joined 11 months ago
cake
Cake day: August 6th, 2023

help-circle
    1. I have tried with firewall enabled and disabled (and added the rule for the enabled firewall)
    2. I will check autoblock. That’s one thing I haven’t checked.
    3. I followed the DSM-7 task setup.

    All fantastic suggestions, btw, but my hair-pulling is coming from none of them working (other than autoblock). :)



  • Apologies for the delay. July 4th festivities and rescuing a kitten from a storm drain intervened (upside: we now have a kitten).

    I can ping the NAS from the client on the Tailscale IP (100.x.x.x) and the tailscale hostname. If I SSH to the NAS, I cannot ping the client machine, but everything on the NAS is available from the client other than the NFS share (and I think I remember reading that the Synology tailscale client does not support ping).

    I realize we’re sort of narrowing in on an NFS setting or possibly a firewall setting, and I appreciate your patience in going on this journey with me, but I have configured both according to, most relevantly, the tailscale documentation for connecting to a Synology NAS.



  • It’s the same error regardless of whether I connect by tailscale IP (100.x.x.x) or the tailscale hostname, and it strongly suggests an issue on the Synology, but everything looks correct on the NAS (but I am by NO MEANS an expert):

    mount.nfs: access denied by server while mounting $IP:/volume1/$mount


    1. Declaring the NFS mount in my NixOS configuration; also tried manually mounting via

    sudo mount -o nfs $TAILSCALEHOSTNAME:/$MOUNT /mnt/$MOUNT (with some options like no auto, but I’m doing this from memory)

    1. I’ll try but I have some idea that it won’t respond to ping
    2. I will try in a moment
    3. yes, on the local network (192.168.x.x) — and for the record I allowed access to the NFS share via the tailscale subnet

    The error I am receiving differs depending on whether I’m connecting via CLI or, say, Nautilus but I’ll have to collect the errors when I’m back at the laptop.



  • Please stay to the end because it’s important, and it’s going to be a horrible bait and switch but it’s not INTENDED that way. I can’t think of another way to present the difficult combination of interests that seem to be driving MS software lately.

    I actually quite like Windows 11, and I love Edge when they’re doing their core functions. Windows 11 is reasonably solid and useful for normal use. Edge is faster than Chrome and has the best vertical tabs implementation on the planet. Much of the baseline software that Microsoft is putting out has never been better, and is often really good at doing the basic things software should do. I really do feel like the genuine technology people in Microsoft are trying, and often succeeding, to make good technology products.

    But… the bottom-feeder marketing drones and MBAs got their hands on them and started layering creepier and creepier nonsense over the top. Mandatory logins to glorified data collection engines. Monetization strategies masquerading as features. Overt advertisement. Heavy-handed promotion of Microsoft’s own products. I finally stopped using Edge (on Linux!) when I discovered that just looking at the settings the wrong way would re-enable every intrusive setting imaginable and ditched Windows entirely when I saw the same things creeping into the OS (as well as a general disgust with privately-owned OSes in general). They are destroying trust.

    In the great irony of my life, because normally work PC Windows installs have been hot garbage, I have Win11 on a work laptop and it’s actually really great to use since all of the intrusive stuff is turned off by our security team. I would still prefer linux or macos (in that order), but as a “forced to use it” option, it’s not bad at all. Go back and read that again: it’s a pleasant and easy to use OS if all the intrusive marketing functionality is turned off because it presents a security hazard.

    PS. Not sacrificing anything being predominantly linux-based and am in fact far, far more efficient on linux (and I am not a programmer or in any other technology role).



  • It’s a fair warning, but on my M2 MBA the only things that don’t work are the microphone and some elements of graphics acceleration. I keep macos on a tiny partition for firmware updates and, I guess, to recover in the event of a catastrophic failure, but … it’s been rock solid. Most of the software I use has compatible builds, which might be the most surprising part.




  • The 2016-2017 MBP are unusually bad. Devices on either side of that? You’re fine. But the 2016-2017 devices? No wifi (except in some extremely unusual cases) is the big problem. Even then, it amazes me how much does work, with zero configuration, with a simple graphical install. The problem with this vintage MBP isn’t that it’s hard to get running–it’s that it’s (almost) impossible, but the parts that aren’t impossible are as smooth as they can be.

    Yes, that’s cold comfort. But I’m speaking from the POV of an owner of a 2017 MBP who desperately wanted to keep it going.

    The coda to the story is that my wife used it for a while with her business but it fell victim to an absolutely bizarre heat issue where the heat sink vents hot air directly across the controller cable for the display, leading to inevitable failure. Again: not an issue on either side of this model year. It’s sad because it could’ve served for another 4-5 years, making the initial purchase price substantially more tolerable.




  • I’m on a refurb M2 Air that I picked up from Apple for peanuts. It took me about 15m to get NixOS running on the thing, and it’s going to last me for 10 years, if my old MBP is anything to go by.

    Also, regardless of the hardware politics, I’m not sure I’ve been in awe of a project as much as I have the Asahi team. They’re just doing so much so quickly and with such command of the subject … and they’re so young. It’s a joy to watch them work.