The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Steve Nickolas <usotsuki@buric.co>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Photos of University Computer Labs - now off topic
Date: Thu, 23 Dec 2021 22:48:30 -0500	[thread overview]
Message-ID: <YcVDDv9DpTdVo3Nv@mit.edu> (raw)
In-Reply-To: <alpine.DEB.2.21.2112231712350.19418@sd-119843.dedibox.fr>

On Thu, Dec 23, 2021 at 05:13:39PM -0500, Steve Nickolas wrote:
> On Thu, 23 Dec 2021, Larry McVoy wrote:
> 
> > On Thu, Dec 23, 2021 at 10:02:40AM -0600, Warner Losh wrote:
> > > > I had forgotten about control-t - does anything modern still do that
> > > 
> > > FreeBSD does. It's my biggest annoyance with Linux that it doesn't.
> > 
> > Seems like a patch might be nice.
> 
> Yeah, I miss SIGINFO when I'm on Linux.

There have been patches proposed, but it turns out the sticky wicket
is that we're out of signal numbers on most architectures.  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)

Howveer, the current behavior if no signal handler is installed is to
terminate the process --- and it's unclear whether there might be some
user space libraries that might be using these signals for their own
nefarious purposes.  So someone would have to deprecate one of these
signals, and then try to do a code search across the internet to see
if there's any evidence that SIGLOST or SIGSTKFLT is being used (at
least in open source software).

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.

Cheers,

						- Ted

  reply	other threads:[~2021-12-24  3:49 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 [this message]
2021-12-28 21:45                   ` Greg A. Woods
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=YcVDDv9DpTdVo3Nv@mit.edu \
    --to=tytso@mit.edu \
    --cc=tuhs@minnie.tuhs.org \
    --cc=usotsuki@buric.co \
    /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).