norden.social

23 posts19 participants1 post today

Jay 🚩 :runbsd:Celebrating NetBSD's 32nd birthday today! Marked the occasion by donating $32 to the <a href="https://bsd.network/@netbsd" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@netbsd</a> Foundation. So much respect for a project that truly lives up to "Of course it runs NetBSD". 💪 Consider donating too! <a href="https://www.netbsd.org/donations/" rel="nofollow noopener noreferrer" target="_blank">https://www.netbsd.org/donations/</a> <a href="https://bsd.network/tags/NetBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NetBSD</a> <a href="https://bsd.network/tags/RunBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RunBSD</a> <a href="https://bsd.network/tags/unix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#unix</a> <a href="https://bsd.network/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> <a href="https://bsd.network/tags/pkgsrc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#pkgsrc</a>

Bitslingers-R-Us<a class="hashtag" href="https://zia.io/tag/netbsd" rel="nofollow noopener noreferrer" target="_blank">#NetBSD</a> <a class="hashtag" href="https://zia.io/tag/pkgsrc" rel="nofollow noopener noreferrer" target="_blank">#pkgsrc</a> 2025Q1 binary package counts for mid April: 9.0: earmv4 2468 (not yet started) 9.0: m68k 1598 (+87) 10.0: aarch64eb 19765 (+3015) 10.0: earmv4 9645 (+55) 10.0: m68k 5408 (+312) 10.0: sh3el 9940 (-24 - cleaned up some stragglers) 10.0: sparc64 13707 (-7 - cleaned up some stragglers) 10.0: vax 8353 (+83)

Daniel Wayne ArmstrongDiscovered today the `last(1)` command in NetBSD (also in Linux) that outputs a list of the last logins of users. Nice! :netbsd:<a href="https://fosstodon.org/tags/Shell" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Shell</a> <a href="https://fosstodon.org/tags/NetBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NetBSD</a>

Stephen Borrill<a href="https://fosstodon.org/@dwarmstrong" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@dwarmstrong</a> Great write-up. I think <a href="https://justfollow.me.uk/tags/NetBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NetBSD</a> dmesg is pretty much the cleanest out there which makes this sort of thing much easier compared to grubbing about in e.g. /dev/disk

TronNerd82<a href="https://fosstodon.org/@linux_mclinuxface" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@linux_mclinuxface</a> I use <a href="https://mastodon.social/tags/NetBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NetBSD</a> from time to time. Good OS, but <a href="https://mastodon.social/tags/Slackware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Slackware</a> is my one true love. I'm 19.

Felix Palmen :freebsd: :c64:Next <a href="https://mastodon.bsd.cafe/tags/swad" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#swad</a> improvement: Make sure to <a href="https://mastodon.bsd.cafe/tags/wipe" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#wipe</a> <a href="https://mastodon.bsd.cafe/tags/passwords" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#passwords</a> from RAM directly after used. That's more of a <a href="https://mastodon.bsd.cafe/tags/security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#security</a> precaution, because there *should* be no way how an attacker can access a running process' memory, but you never know which bugs surface 🙈.Unexpectedly, that posed <a href="https://mastodon.bsd.cafe/tags/portability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#portability</a> issues. <a href="https://mastodon.bsd.cafe/tags/C11" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#C11</a> has <a href="https://mastodon.bsd.cafe/tags/memset_s" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#memset_s</a> ... a pretty weird function, but suitable for wiping. It's there on <a href="https://mastodon.bsd.cafe/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FreeBSD</a> and on <a href="https://mastodon.bsd.cafe/tags/OpenBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenBSD</a>. Not on <a href="https://mastodon.bsd.cafe/tags/NetBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NetBSD</a> though. But NetBSD offers the much saner <a href="https://mastodon.bsd.cafe/tags/C23" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#C23</a> function <a href="https://mastodon.bsd.cafe/tags/memset_explicit" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#memset_explicit</a>. Looking at <a href="https://mastodon.bsd.cafe/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a>, there's neither. But there is the (non-standard!) <a href="https://mastodon.bsd.cafe/tags/explicit_bzero" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#explicit_bzero</a> 🤯 .. and with glibc, it requires _DEFAULT_SOURCE to be defined as soon as you compile with a C standard version given to the compiler. This function exists on some other systems as well, but there's confusion whether it should be declared in string.h or strings.h. 🤪 Here's the full set of compile-tests I'm now doing, only to find the best way to really erase memory: <a href="https://github.com/Zirias/swad/blob/master/src/bin/swad/swad.mk#L6" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/Zirias/swad/blob/master/src/bin/swad/swad.mk#L6</a>And if none of these functions is found, swad uses the "hacky" way that most likely works as well: Access the normal memset function via a volatile pointer.

Stefano MarinelliMmm parallel seem to have some troubles on NetBSD. Sometimes it's just stuck, doesn't start to process the task. For now, when BSSG will detect it's running on NetBSD, it will use the slower but more reliable sequential build process<a href="https://mastodon.bsd.cafe/tags/BSSG" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BSSG</a> <a href="https://mastodon.bsd.cafe/tags/NetBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NetBSD</a>

Daniel Wayne ArmstrongDisable password logins on the SERVER in favour of using SSH keys for authentication. Create the necessary SSH keys on a NetBSD CLIENT that will be used to secure access to remote devices:<a href="https://www.dwarmstrong.org/netbsd-ssh-keys/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.dwarmstrong.org/netbsd-ssh-keys/</a><a href="https://fosstodon.org/tags/SSH" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SSH</a> <a href="https://fosstodon.org/tags/NetBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NetBSD</a> <a href="https://fosstodon.org/tags/RunBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RunBSD</a> <a href="https://fosstodon.org/tags/Encryption" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Encryption</a>

Felix Palmen :freebsd: :c64:Today, I implemented the <a href="https://mastodon.bsd.cafe/tags/async" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#async</a> / <a href="https://mastodon.bsd.cafe/tags/await" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#await</a> pattern (as known from <a href="https://mastodon.bsd.cafe/tags/csharp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#csharp</a> and meanwhile quite some other languages) ...... in good old <a href="https://mastodon.bsd.cafe/tags/C" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#C</a>! 😎 Well, at least sort of.* It requires some standard library support, namely <a href="https://mastodon.bsd.cafe/tags/POSIX" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#POSIX</a> user context switching with <a href="https://mastodon.bsd.cafe/tags/getcontext" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#getcontext</a> and friends, which was deprecated in POSIX-1.2008. But it's still available on many systems, including <a href="https://mastodon.bsd.cafe/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FreeBSD</a>, <a href="https://mastodon.bsd.cafe/tags/NetBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NetBSD</a>, <a href="https://mastodon.bsd.cafe/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> (with <a href="https://mastodon.bsd.cafe/tags/glibc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#glibc</a>). It's NOT available e.g. on <a href="https://mastodon.bsd.cafe/tags/OpenBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenBSD</a>, or Linux with some alternative libc.* I can't do anything about the basic language syntax, so some boilerplate comes with using it.* It has some overhead (room for extra stacks, even extra syscalls as getcontext unfortunately also always saves/restores the signal mask)But then ... async/await in C! 🥳 Here are the docs: <a href="https://zirias.github.io/poser/api/latest/class_p_s_c___async_task.html" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://zirias.github.io/poser/api/latest/class_p_s_c___async_task.html</a><a href="https://mastodon.bsd.cafe/tags/C" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#C</a> <a href="https://mastodon.bsd.cafe/tags/coding" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#coding</a>

Felix Palmen :freebsd: :c64:I finally eliminated the need for a dedicated <a href="https://mastodon.bsd.cafe/tags/thread" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#thread</a> controlling the pam helper <a href="https://mastodon.bsd.cafe/tags/process" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#process</a> in <a href="https://mastodon.bsd.cafe/tags/swad" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#swad</a>. 🥳 The building block that was still missing from <a href="https://mastodon.bsd.cafe/tags/poser" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#poser</a> was a way to await some async I/O task performed on the main thread from a worker thread. So I added a class to allow exactly that. The naive implementation just signals the main thread to carry out the requested task and then waits on a <a href="https://mastodon.bsd.cafe/tags/semaphore" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#semaphore</a> for completion, which of course blocks the worker thread.Turns out we can actually do better, reaching similar functionality like e.g. <a href="https://mastodon.bsd.cafe/tags/async" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#async</a> / <a href="https://mastodon.bsd.cafe/tags/await" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#await</a> in C#: Release the worker thread to do other jobs while waiting. The key to this is user context switching support like offered by <a href="https://mastodon.bsd.cafe/tags/POSIX" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#POSIX</a>-1.2001 <a href="https://mastodon.bsd.cafe/tags/getcontext" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#getcontext</a> and friends. Unfortunately it was deprecated in POSIX-1.2008 without an obvious replacement (the docs basically say "use threads", which doesn't work for my scenario), but still lots of systems provide it, e.g. <a href="https://mastodon.bsd.cafe/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FreeBSD</a>, <a href="https://mastodon.bsd.cafe/tags/NetBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NetBSD</a>, <a href="https://mastodon.bsd.cafe/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> (with <a href="https://mastodon.bsd.cafe/tags/glibc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#glibc</a>) ...The posercore lib now offers both implementations, prefering to use user context switching if available. It comes at a price: Every thread job now needs its private stack space (I allocated 64kiB there for now), and of course the switching takes some time as well, but that's very likely better than leaving a task idle waiting. And there's a restriction, resuming must still happen on the same thread that called the "await", so if this thread is currently busy, we have to wait a little bit longer. I still think it's a very nice solution. 😎 In any case, the code for the PAM credential checker module looks much cleaner now (the await "magic" happens on line 174): <a href="https://github.com/Zirias/swad/blob/57eefe93cdad0df55ebede4bd877d22e7be1a7f8/src/bin/swad/cred/pamchecker.c" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/Zirias/swad/blob/57eefe93cdad0df55ebede4bd877d22e7be1a7f8/src/bin/swad/cred/pamchecker.c</a><a href="https://mastodon.bsd.cafe/tags/C" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#C</a> <a href="https://mastodon.bsd.cafe/tags/coding" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#coding</a>

benzDoes <a href="https://mastodon.sdf.org/tags/NetBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NetBSD</a> support ZRAM?

Daniel Wayne ArmstrongIn regards to DNS domains, previously when setting up Linux machines on the LAN I have just gone with whatever the installer chose as the default: "home", "lan", etc.NetBSD amd64 installer defaults to "home" and, in reading a bit about such domains I discovered RFC 8375, which designates "'.home.arpa.'... as a special-use domain name... for non-unique use in residential home networks."I'm using it now.<a href="https://datatracker.ietf.org/doc/html/rfc8375" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://datatracker.ietf.org/doc/html/rfc8375</a><a href="https://fosstodon.org/tags/Networking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Networking</a> <a href="https://fosstodon.org/tags/NetBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NetBSD</a>

Daniel Wayne ArmstrongFor my NetBSD install I wanted to include _disk encryption_ to protect personal data in case the device is lost or stolen.Its not really enough to simply encrypt home directories. Passphrases and sensitive data can linger and be extracted from locations such as system logs and swap memory. There is a trade-off to be made between how much to encrypt, the convenience of operating the system, and the ability for the system to boot.This is how I do it...<a href="https://www.dwarmstrong.org/netbsd-encrypt-install/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.dwarmstrong.org/netbsd-encrypt-install/</a><a href="https://fosstodon.org/tags/NetBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NetBSD</a> <a href="https://fosstodon.org/tags/RunBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RunBSD</a>

Bitslingers-R-Us<a class="hashtag" href="https://zia.io/tag/netbsd" rel="nofollow noopener noreferrer" target="_blank">#NetBSD</a> <a class="hashtag" href="https://zia.io/tag/pkgsrc" rel="nofollow noopener noreferrer" target="_blank">#pkgsrc</a> 2025Q1 package building continues! An unexpected power outage has caused some work to need to be restarted, plus has indicated that some new UPS batteries need to be purchased :P Some new build machines will be coming online soon :)

Felix Palmen :freebsd: :c64:About the <a href="https://mastodon.bsd.cafe/tags/random" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#random</a> thingie ... I need random data in <a href="https://mastodon.bsd.cafe/tags/swad" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#swad</a> to generate unpredictable <a href="https://mastodon.bsd.cafe/tags/session" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#session</a> IDs.I previously had an implementation trying the <a href="https://mastodon.bsd.cafe/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a>-originating <a href="https://mastodon.bsd.cafe/tags/getrandom" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#getrandom</a> if available, with a fallback to a stupid internal <a href="https://mastodon.bsd.cafe/tags/xorshift" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#xorshift</a> <a href="https://mastodon.bsd.cafe/tags/PRNG" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PRNG</a>, which could be disabled because it's obviously NOT cryptographically secure, and WAS disabled for the generation of session IDs.Then I learned <a href="https://mastodon.bsd.cafe/tags/arc4random" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#arc4random</a> is available on many systems nowadays (<a href="https://mastodon.bsd.cafe/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FreeBSD</a>, <a href="https://mastodon.bsd.cafe/tags/NetBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NetBSD</a>, even Linux with a recent-enough glibc), so I decided to add a compile check for it and replace the whole mess with nothing but an arc4random call IF it is available.arc4random originates from <a href="https://mastodon.bsd.cafe/tags/OpenBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenBSD</a> and provides the only sane way to get cryptographically secure random data. It automatically and transparently (re-)seeds from OS entropy sources, but uses an internal CSPRNG most of the time (nowadays typically <a href="https://mastodon.bsd.cafe/tags/ChaCha20" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ChaCha20</a>, so it's a misnomer, but hey ...). It never fails, it never blocks. It just works. Awesome.

Kevin Karhan :verified:<a href="https://mastodon.social/@dec_hl" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@dec_hl</a> I know.Besides <a href="https://infosec.space/tags/RaspberryPiOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RaspberryPiOS</a> there's like <a href="https://linuxrocks.online/@bunsenlabs" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@bunsenlabs</a> / <a href="https://infosec.space/tags/BunsenLabs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BunsenLabs</a> and me dabbling (<a href="https://infosec.space/@OS1337" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@OS1337</a>) tho technically they all are <a href="https://infosec.space/tags/i486" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#i486</a> as they use <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> kernels beyond the cutoff date for <a href="https://infosec.space/tags/i386" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#i386</a> support.<ul><li><a href="https://infosec.space/tags/NetBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NetBSD</a> propably still supports i386 and potentially even i286...</li></ul>

vermadenLatest 𝗩𝗮𝗹𝘂𝗮𝗯𝗹𝗲 𝗡𝗲𝘄𝘀 - 𝟮𝟬𝟮𝟱/𝟬𝟰/𝟭𝟰 (Valuable News - 2025/04/14) available. <a href="https://vermaden.wordpress.com/2025/04/14/valuable-news-2025-04-14/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://vermaden.wordpress.com/2025/04/14/valuable-news-2025-04-14/</a>Past releases: <a href="https://vermaden.wordpress.com/news/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://vermaden.wordpress.com/news/</a><a href="https://mastodon.bsd.cafe/tags/verblog" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#verblog</a> <a href="https://mastodon.bsd.cafe/tags/vernews" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#vernews</a> <a href="https://mastodon.bsd.cafe/tags/news" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#news</a> <a href="https://mastodon.bsd.cafe/tags/bsd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bsd</a> <a href="https://mastodon.bsd.cafe/tags/freebsd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#freebsd</a> <a href="https://mastodon.bsd.cafe/tags/openbsd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openbsd</a> <a href="https://mastodon.bsd.cafe/tags/netbsd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#netbsd</a> <a href="https://mastodon.bsd.cafe/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a> <a href="https://mastodon.bsd.cafe/tags/unix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#unix</a> <a href="https://mastodon.bsd.cafe/tags/zfs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#zfs</a> <a href="https://mastodon.bsd.cafe/tags/opnsense" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#opnsense</a> <a href="https://mastodon.bsd.cafe/tags/ghostbsd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ghostbsd</a> <a href="https://mastodon.bsd.cafe/tags/solaris" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#solaris</a> <a href="https://mastodon.bsd.cafe/tags/vermadenday" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#vermadenday</a>

BSD NL📢 Exciting news! 📢We've set up a Signal 📱 announcement group to keep you all in the loop about the upcoming events and talks. 🚀Join us to stay connected and never miss a 🐡😈⛳ bit! Announcements: <a href="https://signal.group/#CjQKIPCuAMW0SvteNYtoyndOVEy2xYPIozPWlzpeAqSfmHE4EhCDjTBBLEftyzv28_Ny4SdT" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://signal.group/#CjQKIPCuAMW0SvteNYtoyndOVEy2xYPIozPWlzpeAqSfmHE4EhCDjTBBLEftyzv28_Ny4SdT</a><a href="https://mastodon.bsd.cafe/tags/BSDNL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BSDNL</a> <a href="https://mastodon.bsd.cafe/tags/RUNBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RUNBSD</a> <a href="https://mastodon.bsd.cafe/tags/BSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BSD</a> <a href="https://mastodon.bsd.cafe/tags/OpenBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenBSD</a> <a href="https://mastodon.bsd.cafe/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FreeBSD</a> <a href="https://mastodon.bsd.cafe/tags/NetBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NetBSD</a> <a href="https://mastodon.bsd.cafe/tags/HardenedBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HardenedBSD</a> <a href="https://mastodon.bsd.cafe/tags/SecBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SecBSD</a> <a href="https://mastodon.bsd.cafe/tags/DragonflyBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DragonflyBSD</a>

sinzaLook at my makeshift exhibit at <a href="https://bitbang.social/tags/IndyClassic" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IndyClassic</a>!<a href="https://bitbang.social/tags/NetBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NetBSD</a> <a href="https://bitbang.social/tags/retrocomputing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#retrocomputing</a>

Stefan SchollOops, almost forgot. My first <a href="https://mastodon.social/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> was S.u.S.E. Linux April 1995. That was 30 years ago.Before that, I had <a href="https://mastodon.social/tags/NetBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NetBSD</a> on my <a href="https://mastodon.social/tags/Amiga" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Amiga</a> 3000, but I only booted into it to play Hack.

Recent searches

Search options

Administered by:

Server stats:

#netbsd