gyptazy.com is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.
This server runs the snac software and there is no automatic sign-up process.
@netbsd Thanks for providing a gentle intro before I jump in and try #NetBSD.
I'm starting to think I will have to wait until my kit is old enough
but note that there are benefits to an OS that favours those with older kit, or who can only afford s/h.
It's good for inclusion and recycling which is good in itself, will educate some and annoy the fuck out of tech fascists. 👍
Good chance it will run on my #HomeLab although expect I'd have to ditch #Proxmox which I like. #Incus?
Hey #NetBSD guys,
How do you set up #WireGuard? wg-quick isn't available for NetBSD from what I can tell. I got wireguard-go to create the tun0 interface, but when I try to feed the config file to it, I get a parsing error:
rld@discovery:~$ doas wg setconf tun0 /etc/wireguard/protonvpn.conf
Line unrecognized: `Address=10.~~~.~~~.~~~/32,2a07:~~~~::2:2/128'
Configuration parsing error
rld@discovery:~$
(~~~=redacted)
Some #NetBSD questions that keep coming up.
We don't use modules for HW drivers in the default install. All baked into the kernel. If you're curious about desktop hardware, for x86 there are lists https://wiki.netbsd.org/laptops/ https://wiki.netbsd.org/gpus/ (and the pci/usb manual pages)
x86 virtual machines. https://www.netbsd.org/docs/guide/en/chap-virt.html#chap-virt-guest
For disk encryption there's different options, such as creating a small root with the installer, then adding encrypted partitions later (see man cgdconfig). Also: cgdroot.
@Cal if this is a usual #NetBSD install image, I would expect to see some wedges found on sd0 (dk devices). After entering the boot device, you'll be prompted for the root device, swap and if lucky the init path. You could try userconf disable nvme* at the boot prompt to stop the NVMe being detected (or boot -c, then disable nvme* at the userconf prompt)
Gonna be trying #NetBSD on my laptop today just to see what the experience is like.
I wipe it fairly regularly anyway so one extra wipe is honestly no big deal to me.
It doesn't want to boot from my USB drive. I got a "WARNING: 1 error while detecting hardware; check system log" message, that seems the most relevant. Not sure how to, or even if I can, do that from USB. Here's a photo, if anyone feels like helping with troubleshooting.
Is there a port of Librewolf for NetBSD? It's available for OpenBSD but i don't find a binary repo (...) for NetBSD.
i'm encouraged by the #NetBSD movement. I think Linux overestimates the number of users that were reluctant. People like me. People who were exposed to commercial Unix (SunOS, Irix, OSF/1) where on the whole, things worked, were documented, people were serious about standards, and maybe even internal kernel interfaces were documented and stable. People who were exposed to BSD and preferred its stability (and the fact that bash wasn't the default shell). But over time Linux had support for all the newest hardware, because that's where the crowds were. So we adopted Linux. Reluctantly.
But as soon as there's a reason to jump, or go back. We do. I don't suppose the reluctant adopters of Linux are a huge part of the Linux users, but there's enough. It's coming home.

I'm really struggling to get @netbsd installed on my ThinkPad T14 laptop. I can't get the install to even start. I've included a photo of what I'm seeing right after I start the install. I know that I'm doing something wrong, but just can't figure out what that might be. So, NetBSD is a bit different than Linux, huh? 😂
Thanks for any help you can give. I didn't seem this issue when installing on the desktop.
@gmc ha ha, the *not* cool kids, you mean. The cool kids were already on NetBSD!
I'm quietly hopeful that the folks who rally around #NetBSD are turning to it because of the project's wariness of LLM-generated code (though frankly I'd like to see a stronger statement, such as the Current Affairs magazine statement: https://www.currentaffairs.org/news/why-were-banning-ai) or because they want to contribute to a community that isn't populated by towering narcissists and their flying monkeys.
Time will tell.
I'm really delighted to see the real buzz around #NetBSD now that Linux has descended into slop and the kernel team have turned their backs on mentoring a new generation of contributors.
Hey #NetBSD users,
can you share with a n00b how you keep your hosts patched and up to date?
I am used to use freebsd-update/pkgbase and have tried syspatch on OpenBSD once, but here I am completely clueless. 🫠
Moving on to the newest laptop, bought this year, this one has the Intel LunarLake chipset. I made more danger labels, because #NetBSD is in the house! The framebuffer works in X11, but not good enough to be a daily driver...yet! I will have to do a lot of reading to see how new chipsets get ported across operating systems. Maybe it is something simple or maybe not. Don't know until I try. That's why the danger labels. Can't be too safe. I took the next week off work so I can nerd into this.
Well, NetBSD doesn’t see my Wi-Fi adapter. I’m spoiled by having the usual Linux tools like modprobe, lspci, and the like… which aren’t installed on this v11.0 build.
Even dmesg isn’t helping me out. I gotta figure out IF my adapter is supported and WHETHER I can find a drive to copy to this system to get networking up.