@andrew_shadura

It's interesting that M. Xu is maintaining two parallel dashes, though. It's not even as though the Debian dash has not tracked Xu dash. There are two different, current, maintained, and significantly divergent, flavours.

https://salsa.debian.org/debian/dash/-/commits/debian/unstable/src/input.c?ref_type=heads

https://git.kernel.org/pub/scm/utils/dash/dash.git/log/src/input.c

I actually haven't tried building the Debian dash on a BSD. I should try it. (#FreeBSD+#OpenBSD ports and pkgsrc use the Xu dash.)

@meluzzy
#Unix #UnixShells #Debian #AlmquistShell #dash #NetBSD

Oh nice, the #Deskflow releases provide tons of native packages for the latest version, so I just updated it to the latest version on this #Debian box.

I'm hoping it will clear up some of the weird glitches I was having connecting from Debian/Plasma/Wayland to #NetBSD/X11/ctwm.

https://github.com/deskflow/deskflow/releases/tag/v1.26.0

Nope, spoke too soon. XD
The super key gets randomly stuck, and the only thing that can fix it is to killall ctwm (bounce X11). Derp. XD

P.S. Thanks to @etam for this solution: https://im-in.space/@etam/117162772780969631

Trotting out old standby #stalonetray to use with #ctwm on my #NetBSD box.

If you're using a WM/DE/compositor that lacks a system tray, [stalonetray] is pretty great. ;)

@stefano 🤩🤩🤩🤩🤩🤩❤️❤️❤️❤️❤️❤️❤️

and even more 🤩🤩🤩🤩🤩 just for running NetBSD in a raspberry pi.

#NetBSD #raspberrypi

littlevps for @lilpoes #runbsd #netbsd

Alt...

running netbsd

@lilpoes yay finally! It turns out I need to pass `vesa on` before booting. #netbsd

@ralen Nope, this is ok because the binary packages in the main repo built from the same pkgsrc tree — so it will be strange if pkgin will be able to distinguish packages from main repo and locally built and installed one and treat them differently during update. This thing must do one job — install binary packages from repo with specified URL and shouldn't know about underlying shenangians, like pkgsrc and locally built packages . And if it see that e.g. "asterisk1337" got update — it will update it and rewrite locally built package with newer package from remote repo.

Common way to avoid the problem described in previous toot — use a local repository with necessary packages and update it first, before issuing `pkgin update`. FreeBSD is using this approach with poudriere.

But a more traditional way — just **don't mix** binary packages and software from ports/pkgsrc — and use solely one of two ways to install software in the system. IIRC, the FreeBSD handbook directly prohibits mixing `pkg install` with ports-based installation method. NetBSD docs mention that there are two main methods of software installation and user may want to choose one of them.

#FreeBSD #NetBSD

trying to install #netbsd to tierhive nat vps, but I can't boot to installer even using boot-com.iso

Finally, the end! I managed to replace binary packages from remote repo with some home-build packages from pkgsrc

#NetBSD #pkgsrc

Alt...

Output in the home server's console: 1.0.2nb2 => Creating binary package /usr/pkgsrc/packages/All/fail2ban-1.0.2nb2.tgz ===> Replacing for fail2ban-1.0.2nb2 ===> Updating using binary package of fail2ban-1.0.2nb2 /usr/bin/env /usr/pkg/sbin/pkg_add -K /usr/pkg/pkgdb -U -D /usr/pkgsrc/security/fail2ban/work/.packages/fail2ban-1.0.2nb2.tgzRR> Packaging fail2ban-1.0.2nb2 ===> Cleaning for fail2ban-1.0.2nb2 RR> Re-checking for unsafe installed packages (unsafe_depends_strict=YES) RR> Packages to rebuild: rr> MISMATCH_TODO=[] rr> REBUILD_TODO=[] rr> UNSAFE_TODO=[] RR> No more packages to replace; done. + fail2ban + munin-master + py312-numpydoc + py312-requests + py312-sphinx drag0n-server#

Been using #Deskflow with my #Debian #Linux #KDE #Plasma #Wayland box as the "server" and my #NetBSD #ctwm #X11 laptop as the "client" or second screen.

It's amazing that it works, but it's buggy. I'll get a few repeat keystrokes, and sometimes the control key gets stuck.

P.S. Thanks to @etam for this solution: https://im-in.space/@etam/117162772780969631

#DontHateTheHashtagPlayaHateTheHashtagGame

@gumnos

Hmmm, "PASS AIR BAG" must be the 2026 version of "Pass the Dutchie/Kouchie" 😄

Hey, you mentioned some compose key wizardry yesterday. How do I export #NetBSD's compose key setup into #OpenBSD? Because +"-"+"-"+"-" does not work properly in OpenBSD for me. :/

Also, unrelated, but for some weird reason, I have to do this in NetBSD, otherwise things like quotation marks come out looking like gibberish (both in uxterm and lxterminal, with any font I've tried):

case $uname in
	(...)
	NetBSD)
				#Somehow, having these variables exported breaks things,
				# so unset them and redefine them without being exported
				unset LANG LC_ALL
				LANG=en_US.UTF-8
				LC_ALL="en_US.UTF-8"
				(...)

I export all those variables by default, but somethow that messes up things on NetBSD (and only NetBSD).

#bsd #netbsd

First installation ...

I have the problem to install bsd on my disk.
When I start the boot stick(iso) green text scrolls down and stopps at
boot device: <unknown>
root device :

any idea??

dropQbsd has been moved from GitHub – where a copy will remain – to Sourcehut, its natural home.

I’d like to thank Drew DeVault for welcoming my project onto his platform.

For free spirits, dropQbsd — compartmentalization without virtualization, based on BSD — can be found here: https://git.sr.ht/~nobraininside/dropQbsd

#OpenBSD #freebsd #netbsd #openSource #privacy #sourcehut #digitalsovereignty

Alt...

dropQbsd, the flying fortress - ASCII Art

dropQbsd has been moved from GitHub – where a copy will remain – to Sourcehut, its natural home.

I’d like to thank Drew DeVault for welcoming my project onto his platform.

For free spirits, dropQbsd can be found here: https://git.sr.ht/~nobraininside/dropQbsd

#OpenBSD #freebsd #netbsd #openSource #privacy #sourcehut #digitalsovereignty

Alt...

dropQbsd, the flying fortress - ASCII Art

dropQbsd has been moved from GitHub – where a copy will remain – to Sourcehut, its natural home.

I’d like to thank Drew DeVault for welcoming me onto his platform.

For free spirits, dropQbsd can be found here: https://git.sr.ht/~nobraininside/dropQbsd

#OpenBSD #freebsd #netbsd #openSource #privacy #sourcehut #digitalsovereignty

Alt...

dropQbsd, the flying fortress - ASCII Art

Anyway, the #golang #NetBSD #aarch64 builder now runs NetBSD 11 and Python 3.14!

Note to self: don't use "sysupgrade auto" when updating from #NetBSD 10 to 11. The etcupdate will fail because the running kernel is incompatible with the etcupdate binary. Ouch.

#NetBSD GSoC 2026 Improving RAIDframe

https://blog.netbsd.org/tnf/entry/gsoc2026_raidframe

Latest 𝗩𝗮𝗹𝘂𝗮𝗯𝗹𝗲 𝗡𝗲𝘄𝘀 - 𝟮𝟬𝟮𝟲/𝟬𝟴/𝟮𝟰 (Valuable News - 2026/08/24) available.

https://vermaden.wordpress.com/2026/08/24/valuable-news-2026-08-24/

Past releases: https://vermaden.wordpress.com/news/

#verblog #vernews #news #bsd #freebsd #openbsd #netbsd #linux #unix #zfs #opnsense #ghostbsd #solaris #vermadenday

Second: The EOF character causes the #Debian #AlmquistShell to print the message about using the exit command, multiple times, and then the shell exits anyway.

This doesn't happen on Debian, only on the BSDs. I've built on Debian, #NetBSD, and #FreeBSD.

My first thought is that this is a libedit difference between the BSD version and the Debian port. It's the same tokenizer code in the shell in all three, so that doesn't seem a likely locus.

#UnixShells

First: I don't know what #glob and #fnmatch add to the #Debian #AlmquistShell. Nothing stands out as different with those features turned on.

The #NetBSD and #FreeBSD flavours of the Almquist shell don't use glob() and fnmatch() at all, and the BusyBox flavour is different, so this does appear (without checking the source history) to be a Debianism of some kind. It's unclear what it achieves, though, although it might that the reasoning does not apply nowadays.

#UnixShells

https://lobste.rs/s/a23bk3/netbsd_my_life_2005

A great real-world story from 2005 about NetBSD, reliability, and how keeping infrastructure simple can make a real difference.

One story among thousands from that era, I imagine. It also makes me wonder how we ended up adding so much complexity to infrastructure over the last 15 years to solve many problems that aren't exactly new.

#bsd #netbsd

NetBSD/news68k 11.99.7
NWB-225 framebuffer on NWS-1750
wscons framebuffer console
#NetBSD

As part of my ongoing efforts to commit atrocities upon the Internet, I hereby announce two useless bots: @lsl1quotes and @lsl1comedian.

As the names might give away, this is about Leisure Suit Larry: In The Land of the Lounge Lizards. About once or twice a week, these bots will post or boost a narrator quote (the former) and a quote from the (terrible) comedian in the game Casino (the latter).

Follow away and boost away, but do so at your own cringe^Wrisk! Also, they're hosted off of a 486[1] running #NetBSD so they will be slow..

I take no responsibility for the way in wich none of the quotes have aged particularly well, nor do I claim authorship - this is all taken out of the game's resource files or collected during actual play. I guess if the current IP owners, or Al Lowe, aren't happy they'll let me know and I'll take it down..

[1] https://larry.weirdr.net/

#Sierra #Retrogaming #Larry

RT: https://larry.weirdr.net/lsl1quotes/p/1787491021.765986

A decade ago I worked with a guy whose opinion on tech I respected a lot. He was one of the most anal people I've ever known, in a (mostly) good way. His OS of choice was BSD.

Linus and crew's recent nonsense got me doing searches for OSes with no-AI policies. Lo and behold, seems that Iain was on to something all this time!

Got my first system up with NetBSD and my preferred Mate desktop this morning. It was fun, and a little challenging. :-) Reminded me of working with Solaris years ago, and of my first experiments with Linux (on PPC!) even more years ago. Installing and configuring NetBSD is not hard, but it does require me to pay attention, read a bit of documentation, and make decisions. I love that!

Thanks, Linus, for pointing me at what may be my new favorite OS. And thank you, Iain, for planting the seed that made me decide to give it a serious look this time around.

#linux #noai #NetBSD #SystemAdministration

I’ve been enjoying my time testing out #Caddy running on my #NetBSD server. As much as I love #OpenBSD, NBSD is really grabbing my interest as of late 😎

@meluzzy

I still use the Almquist shells for scripts. Having none of the heavyweight interactive and extensions stuff to initialize is a definite advantage, as Debian/Ubuntu found out years ago.

I am glad that yet another person has learned of the #WatanabeShell .

Line editing, via libedit, and history work in the BSD flavours of the #AlmquistShell, by the way. Debian simply builds it with editing and history disabled.

#UnixShells #Unix #NetBSD #FreeBSD

If you don't want your house looking like this support #antiai #noai projects like #NetBSD

I forgot to set up the keybindings for the external monitor.
Now I can mess around with two monitors even on NetBSD 🤣

If anyone is interested (replace --output parameter if necessary)

# xrandr keybindings for external monitor

bindsym $mod+Ctrl+s   exec --no-startup-id xrandr --output DP2 --primary --mode 1920x1080 --left-of  eDP1
bindsym $mod+Ctrl+d   exec --no-startup-id xrandr --output DP2 --primary --mode 1920x1080 --right-of eDP1
bindsym $mod+Shift+s  exec --no-startup-id xrandr --output HDMI2 --primary --mode 1920x1080 --left-of eDP1
bindsym $mod+Shift+d  exec --no-startup-id xrandr --output HDMI2 --primary --mode 1920x1080 --right-of eDP1
bindsym $mod+Ctrl+o   exec --no-startup-id xrandr --output DP2 --off
bindsym $mod+Shift+o  exec --no-startup-id xrandr --output HDMI2 --off

P.S. Thanks, xrandr!

#bsd #netbsd #bsdunix #unix #unixITA #unixitalia #guuf #guufxmpp #guufITA #linux #linuxITA #linuxitalia

Alt...

A laptop and a monitor on a wodden table

@jrdepriest #NetBSD is my preference, with #FreeBSD a close second.

Running #NetBSD 11.0 (from this year) on my 1997 Pentium MMX 233 MHz system out of curiosity, and it's facinating how the OS can boot relatively fast, text mode applications still usually launch snappily, but it takes five minutes for fontconfig to update the cache.

It also fails the "can this play Doom" test amusingly with Chocolate Doom: Chocolate Doom's setup program is too much for it to handle under Xorg between the S3 Virge GPU, 128 MB of RAM, and CPU.

Still really cool it works as well as it does on a system this old and supports all the hardware in it, though. And it can even touch the internet without me being worried of it being killed by long-lasting internet background malware radiation from the 90's!

#retrocomputing

👾 NetBSD 11 Is AWESOME on 1990s PC's! // Ionic1k

https://www.youtube.com/watch?v=px8xP7ns8XA

#netbsd #bsd #opensource

@lukasrotermund On #NetBSD, depending on the file system type, backups are usually done by taking an FFS snapshot with fss(4), and dumping the snapshot using dump(8), or using ZFS snapshots, and zfs sending them somewhere. See https://wiki.netbsd.org/tutorials/how_to_use_snapshots/