schmonz.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.
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.
Wuah, #NetBSD! Ich mach pkgin upgrade in einem Terminal aufm XFCE Desktop. Soweit so gut, es rödelt los und irgendwann findet es, auch XFCE selber updaten zu müssen.
Und PÄNG! ist der Desktop samt dem Terminal und dem laufenden Upgrade-Prozess weg!
Was für eine Chrümschelisoftware!
Okay bejbas so you need to create a non-root user **and** give it a non-null password
Thanks for the grear ux installation screen (/s)
boostedIf one is concerned about organizations that endorse LLM use, and organizations that want to avoid it, then #Debian's recent community decision where it rejected the latter and agreed with the former is something to take into account.
https://lists.debian.org/debian-vote/2026/08/msg00360.html
It's why people are looking at #NetBSD and are frustrated at #FreeBSD. The NetBSD people made a clear statement about not using #LLMs, and FreeBSD does not have a clear statement and in the meantime a few of its developers appear to be merrily using LLMs.
This is one of those questions where the answer is 'of course'. (-:
(Package management did not originate with Linux. AT&T System 5 Release 4 Unix had a package manager.)
The BSDs all have binary package managers, supporting inter-package dependencies.
#OpenBSD has Jordan Hubbard's pkg that was actually written for FreeBSD. #FreeBSD and derivatives (#DragonFlyBSD, #GhostBSD, #MidnightBSD, et al.) now have pkgng, a later rewrite that replaced it in 2012. #NetBSD has pkgin.
They *also* all have the ability to build from source, with doing so automatically integrating with their binary packaging system.
It's called 'the ports system' everywhere but on NetBSD, where it is called 'pkgsrc' (because a 'port' on NetBSD means something else).
Agora is composed of several sub-projects:
- libagora-core, equivalent to Core Foundation
- libagora-drawing, equivalent to Core Graphics
- libagora-text, equivalent to Core Text
- libagora-app, equivalent to Application Kit
- WindowServer, a Wayland-based window server specifically for Agora
- Agora Workspace, a to-be-designed file manager
- Agora Dock, a to-be-designed Dock
More will be added as Agora grows.
Hello, Mastodon!
Agora Desktop is a project to produce a Mac-like desktop environment and UI toolkit, based on the Cocoa API, for Linux and the BSDs.
Up front disclosure: This project makes use of agentic coding in the hands of a 30+ year programming veteran, so if that's a dealbreaker, feel free to ignore it entirely, flames go to /dev/null. Positive interactions only!
Oh thank lod I can change the install colors on my #netbsd installer. My eyes no longer burn.
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.
@nina_kali_nina@tech.lgbt mmmm, alpineBSD you say... That's an interesting concept (I use alpine)
But otherwise...yeah, #NetBSD install weekend around the world!
Oh I am actually reading documentation on how to write #netbsd drivers. Thats actually exciting!
First time I've actually installed #NetBSD on "real" hardware, until now I've only run it in VMs and on a Raspberry Pi 1.
So far configuring it differs a bit from FreeBSD, but commands like ifconfig, route, sockstat, top, and so on are almost identical, which makes it rather intuitive.
The host is online, the first few packages are installed, a service set up and running. Next I will take a look at the npf firewall, can't wait to see how it compares to OpenBSD/FreeBSD pf and learn it's own special features. :)
When it comes to BSD, I've only ever really used OpenBSD on servers, and the occasional time I'd fire up NetBSD on the Dreamcast.
If I were to dive into trying desktop BSD, which way would you go or have you gone? I haven't kept up, and honestly, from a desktop perspective, have zero idea of where to start, and it's high time I started expanding my knowledge to user-facing parts.
(Target machine, if viable, is a Dell XPS 13 9370 Developer Edition; the ones that shipped with Ubuntu by default.)
Thoughts, suggestions, guides, opinions welcome.
| OpenBSD: | 0 |
| NetBSD: | 0 |
| Some other BSD: | 0 |
So if I’m going to commit to #NetBSD then I need my laptop WiFi to work. And then I need my graphics card to be supported.
I could sit and start hacking I guess. But I mean… am I barking up a tree that’s already being climbed?
If I never buy another PC then I’m stuck with my Thinkpad and an old NUC.
For people asking about NetBSD & Steam & Proton & GamesFromThisCentury.
#netbsd
https://github.com/NetBSD/src/blob/trunk/games/wargames/wargames.sh
I guess I'll start my little #NetBSD adventure on the i486 netbook (shoutout to the #UPerU programme http://www.xtec.cat/centres/e3006678/1x1/1x1.html ) and see what's up before fucking with what was supposed to be my livelihood and all
No dear #linux users none of the #bsd s is a drop in replacement for your favorite #distribution . Not every hardware under the sun is 100% supported.
Look at the hardware compatibility lists of the given projects before you set yourself up for frustrations.
#FreeBSD has the broadest mainstream hardware support.
Especially for #NetBSD read this first
https://www.unitedbsd.com/d/1158-netbsd-hardware-compatibility-thread
Day 32
New blog post!
Syncthing is a continuous file synchronization program. Once installed and configured, it will keep designated directories and their contents synced between multiple devices. I’m currently using Syncthing to sync photos and videos taken with my Android phone with my NetBSD 11.0 desktop.
RE: https://tech.lgbt/@nina_kali_nina/117441043503225633
The new policies for the Linux kernel make it more or less impossible to support a slop-free fork of Linux, so if you're worried about the reliability of your system level software, or have ethical concerns about LLM usage on your computer, the time to act is, well, now.
If you have time this weekend, I recommend you to try one of the slop-free systems: NetBSD, 9front, HyperbolaBSD, Haiku, or OpenBSD. If you're adventurous, you could try new AlpineBSD, or research smaller systems, like FreeDOS. If you don't feel adventurous, you might want to check out anti-AI Linux distributions, like Elementary or Gentoo.
There's no "one solution that fits all". But there's a solution that I chose for myself, and that's NetBSD: it gives me the most freedom, it supports most of my hardware, and can run a great deal of software I need. It's not easy to run, but it's a great learning opportunity. There's quite a few folks around using BSD and capable of giving hints and advice, so if you feel stuck, toot about #netbsd.
1/2
Web browser package availability in #NetBSD challenge. Go!
@netbsd@mastodon.sdf.org
@Vivaldi@vivaldi.net
@librewolf@chaos.social
@Waterfox@mastodon.social