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

[giggls@karlsruhe-social.de]

@benjamineskola @eris2cats Sorry, this was not meant as an explanation. I just don't understand people who think that they do match in any way.

[hardingar@mindly.social]

@eris2cats @sassdawe Reminds me of when I bought a particularly piney IPA from a corner store in DC, was not carded, asked and was told nobody under 30 would drink that beer.

[eskuero@mstdn.io]

@eris2cats do you mean Slackware

[hi@romanzolotarev.com]

@silvermoon82@wandering.shop @paul@notnull.space @eris2cats@chaos.social
(x) /bin/sh

[chrisjrn@social.coop]

@eris2cats ok but I first debianed at age 16

[keith@mamut.tic-ac.org]

@eris2cats
How about -
I wouldn't touch your shi**y centralised, spying, propaganda pushing "social media" Internet with a barge pole anyway.
That should be age verification enough
And if not, well, i use #debian.

[eris2cats@chaos.social]

@keith That will do!

[eris2cats@chaos.social]

@chrisjrn And how long ago was that.. let's say to the nearest decade

[chrisjrn@social.coop]

@eris2cats ok good point

[paranormal_distribution@fosstodon.org]

@musevg @eris2cats I've been eyeing BSD, was it a pain to set up?

[musevg@23.social]

@paranormal_distribution @eris2cats
That toot up there was a joke

I like working with all three main BSD flavours but only on a server level (that's no pain at all as soon as you understand partition numbering), without GUI.
I have close to 0 experience with BSD on the desktop, with X. Sorry.

[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