From: "Greg A. Woods" <woods@robohack.ca>
To: The Unix Heritage Society mailing list <tuhs@tuhs.org>
Subject: Re: [TUHS] Photos of University Computer Labs - now off topic
Date: Tue, 28 Dec 2021 13:45:14 -0800 [thread overview]
Message-ID: <m1n2KHS-0039XwC@more.local> (raw)
In-Reply-To: <YcVDDv9DpTdVo3Nv@mit.edu>
[-- Attachment #1: Type: text/plain, Size: 1362 bytes --]
At Thu, 23 Dec 2021 22:48:30 -0500, "Theodore Ts'o" <tytso@mit.edu> wrote:
Subject: Re: [TUHS] Photos of University Computer Labs - now off topic
>
> There have been patches proposed, but it turns out the sticky wicket
> is that we're out of signal numbers on most architectures.
Huh. What an interesting "excuse"! (Not that I know anything useful
about the implementation in Linux....)
> There are
> code points that potentially could be repurposed, since they aren't
> actually signaled from the kernel:
>
> SIGLOST - Term File lock lost (unused)
> SIGSTKFLT - Term Stack fault on coprocessor (unused)
If SIGLOST were used/needed it would seem like a very bad system design.
> It's not impossible to deal with this, but no one has cared enough to
> really try to push this through as a new feature.
I personally can't stand using Linux, even casually for a very short
sys-admin task, because of this missing feature. I think I would find
it nearly impossible to go back to SysVr4 without SIGINFO too. It's
just too damn convenient and useful, especially with ever more tools and
utilities gaining interesting support for it.
--
Greg A. Woods <gwoods@acm.org>
Kelowna, BC +1 250 762-7675 RoboHack <woods@robohack.ca>
Planix, Inc. <woods@planix.com> Avoncote Farms <woods@avoncote.ca>
[-- Attachment #2: OpenPGP Digital Signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2021-12-28 21:45 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-22 15:11 [TUHS] Photos of University Computer Labs Alexander Jacocks via TUHS
2021-12-22 20:31 ` josh
2021-12-22 21:07 ` Rob Pike
2021-12-22 21:15 ` Rob Pike
2021-12-23 4:28 ` Warren Toomey
2021-12-23 4:31 ` Alexander Jacocks via TUHS
2021-12-23 4:45 ` Rob Pike
2021-12-22 21:14 ` Win Treese
2021-12-23 0:48 ` Adam Thornton
2021-12-23 1:30 ` Adam Sampson
2021-12-23 2:18 ` Larry McVoy
2021-12-23 13:05 ` Michael Kjörling
2021-12-23 14:19 ` Larry McVoy
2021-12-23 15:29 ` [TUHS] Photos of University Computer Labs - now off topic Dr Iain Maoileoin
2021-12-23 16:00 ` Larry McVoy
2021-12-23 16:28 ` Dr Iain Maoileoin
2021-12-23 16:35 ` Larry McVoy
2021-12-23 16:47 ` Dr Iain Maoileoin
2021-12-23 22:15 ` Steve Nickolas
2021-12-24 20:57 ` Derek Fawcus
2021-12-23 16:02 ` Warner Losh
2021-12-23 16:19 ` Larry McVoy
2021-12-23 22:13 ` Steve Nickolas
2021-12-24 3:48 ` Theodore Ts'o
2021-12-28 21:45 ` Greg A. Woods [this message]
2021-12-29 16:58 ` Theodore Ts'o
2022-01-09 19:04 ` Stuart Remphrey
2021-12-25 0:00 ` [TUHS] Photos of University Computer Labs Mike Markowski
2021-12-29 2:44 ` Alexander Jacocks via TUHS
Reply instructions:
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m1n2KHS-0039XwC@more.local \
--to=woods@robohack.ca \
--cc=tuhs@tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).