"We use debian, that should be age verification enough"

jamie@fedi.jametek.com

@eris2cats@chaos.social We use Gentoo, by the time the installation has finished we'll be of age. <img class="not-responsive emoji" src="https://fedi.jametek.com/emoji/fsh/gentoo.png" title=":gentoo:" />

qlp@linh.social

@silvermoon82 @eris2cats I come from the time where I cursed when I started seeing bash-isms starting to flood shell scripts, sinice I was still using the ol' /bin/sh on FreeBSD and Solaris.

I also experimented with tcsh and ksh on FreeBSD and AIX as well.

mewsleah@meow.social

@tymwol @silvermoon82 @eris2cats um...

(csh, on the other hand)

mewsleah@meow.social

@mirabilos @kami_kadse @eris2cats @silvermoon82 pdksh.exe

h3artbl33d@exquisite.social

@eris2cats

#OpenBSD here - my daily driver for decades.

Am I a dinosaur now?

fellmoon@bsd.network

@eris2cats how mature needs your OS to be to access pr0n?

mirabilos@toot.mirbsd.org

@silvermoon82 @mewsleah @eris2cats @kami_kadse pdksh has been superceded by mksh, in case you didn’t notice

kami_kadse@don.linxx.net

@mewsleah @mirabilos @eris2cats @silvermoon82

mirabilos@toot.mirbsd.org

@silvermoon82 @eris2cats @kami_kadse @mewsleah there’s even multiple different ways to get an mksh.exe if you’re so inclined:

OS/2 is natively supported, build it with EMX/kLibc or get the binaries from komh
- note komh adds the -T build option which makes it (permissively) use CRLF line endings, but you can also leave it out and run with LF line endings, and that’s the mode upstream supports
there’s a port of mksh R39 (old) to native WinAPI, which is usable if you must, but really only if you must
- uses shm for fork emulation, which likely has security implications, don’t run elevated
for NT, if you have Interix/SFU/SUA, you can build current (R59c or (preferably) CVS HEAD aka just before R60) mksh there and add the .exe suffix so it can be called from Win32 programs; this works very very well
for Windows, otherwise you can build one with Cygwin/MSYS2, AT&T UWIN, PW32, and probably other frameworks like this
- use if you must
- in that case prefer Cygwin/MSYS2 if that can match your environment, they work very well
- UWIN mostly works
- PW32 does not really work well
- likely works worse on DOS-based Windows than on NT
if you have real WSL, you probably can link/copy mksh to mksh.exe like with Interix; this will likely work well
if you have WSL2, you have a badly done Linux VM with minor integration, and renaming is cosmetic *shrug* it’ll work no problem

mirabilos@toot.mirbsd.org

@silvermoon82 @kami_kadse @mewsleah @eris2cats oh, and, while pdksh’s last release was in 1999 (with NetBSD and OpenBSD doing minor cleanups after, for their OSes only), mksh is 22 this year and not subject to age checks

Your Android device also comes with /system/bin/mksh (may be called /system/bin/sh depending on vendor/version), in contrast to the old Android sh it has tab completion. And so much more, in only a few dozen KiB more executable. Enjoy.

And, best of all, it’s AIn’t (no planet-burning slop, ever).