From: segaloco via TUHS <firstname.lastname@example.org>
To: The Eunuchs Hysterical Society <email@example.com>
Subject: [TUHS] Re: UNIX co-creator Ken Thompson is a… what, user now?
Date: Sat, 18 Mar 2023 16:21:24 +0000 [thread overview]
Message-ID: <yHokg-YqSNF8x4G68daW0a9Pg9rpsawPmsmT-kVrhd4wBY0HO7Z9g26wOkf0JNLgsivuD4yA_UdHbD1ywH7Vb1Z70RIlknJ792gw7EXfoQkfirstname.lastname@example.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2622 bytes --]
Raspbian is the only "stock" Linux distro I've tried on my RPi, used it as a daily driver for a while. My standing gripes with the system have largely evaporated in the past few years what with formal 64-bit versions and having figured out how to rebase the system on sysvinit pretty well. The base install is pretty well provisioned, I don't recall having to install compilers and such. One of my chronic irks with Linux distros is how most seem to forgo a good chunk of what you'd expect on any UNIX worth its weight: Often no C compiler or needed headers installed, sometimes documentation shunted off to different packages, no yacc, lex, awk, heck I've seen distros without ed and vi, I think Manjaro is in this boat. I found the latter incredibly stupid, submitted an Issue to their Gitlab, and was pretty much ignored and the issue quietly closed with no resolution. Pico/nano will never be the standard editor, people need to stop trying to make it be so...
Do Linux providers even know the POSIX standard exists? No I don't expect them to go pay for certification but geeze, the amount of times in the past few years I've propped up a random distro on a machine or VM and been unable to rely on even the most basic stuff being there is disheartening. No wonder people don't use Linux in the UNIX-y way so often, half the darn system isn't represented in most Linux base installs. Is this the LSBs fault or does nobody look at that anymore either? My experiences recently say not...
- Matt G.
P.S. Got a nasty gram (that I'm not replying to, arguing over the internet is stupid) about some sort of reply all thing, so I'm going to only reply to TUHS and kill the Cc list as an experiment to see if people get livid over words on screens that come to them due to their membership in a list rather than come to them due to their being Ccd on emails that also come by way of a mailing list that they're also members of. If this email reaches you in an unacceptable manner, sorry, I don't know what people want from me, but if it's a problem I'll explore what control I have over the various mechanisms arbitrary email clients and communication conventions are present in the current email landscape (hint: not much)
------- Original Message -------
On Saturday, March 18th, 2023 at 5:51 AM, KenUnix <email@example.com> wrote:
> Interesting Unix related articles.
> WWL 📚
[-- Attachment #2: Type: text/html, Size: 4094 bytes --]
next prev parent reply other threads:[~2023-03-18 16:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-18 12:51 [TUHS] " KenUnix
2023-03-18 16:21 ` segaloco via TUHS [this message]
2023-03-18 20:39 ` [TUHS] " Theodore Ts'o
2023-03-19 3:14 ` James Johnston
2023-03-20 3:11 ` Adam Thornton
2023-03-18 18:51 ` Justin Andrusk
2023-03-18 20:39 Norman Wilson
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).