From: Greg 'groggy' Lehey <grog@lemis.com>
To: Ori Idan <ori@heliconbooks.com>
Cc: Paul Winalski <paul.winalski@gmail.com>, COFF <coff@minnie.tuhs.org>
Subject: [COFF] Re: "9 skills our grandkids won't have" - Is this a TUHS topic?
Date: Sat, 2 Jul 2022 10:12:09 +1000 [thread overview]
Message-ID: <20220702001209.GC32390@eureka.lemis.com> (raw)
In-Reply-To: <CACyhTRHyUJ8aBLyzQCm5iBANs_b1F8xfr1y-0drSVsCKZ+MToQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1247 bytes --]
[Redirecting to COFF]
On Friday, 1 July 2022 at 16:05:30 +0300, Ori Idan wrote:
> On Thu, Jun 30, 2022 at 7:38 PM Paul Winalski <paul.winalski@gmail.com>
> wrote:
>
>>
>> o why a memory access violation is reported as "segmentation fault" or
>> "bus error", and the difference between the two
>>
>> o why CTRL/D is used to end a shell command line session
>
> I am not sure I know that, I'd be happy to know.
It's the ASCII control character EOT (end of transmission).
>> o why CTRL/S and CTRL/Q are used for flow control in a shell command
>> line session
>>
> Also would be happy to know.
Also ASCII control characters: XON (^S) and XOFF (^Q).
https://en.wikipedia.org/wiki/C0_and_C1_control_codes#Device_control
tells me:
DC1 and DC3 (known also as XON and XOFF respectively in this usage)
originated as the "start and stop remote paper-tape-reader"
functions in ASCII Telex networks. This teleprinter usage became the
de facto standard for software flow control.[13]
Greg
--
Sent from my desktop computer.
Finger grog@lemis.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed. If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA.php
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 163 bytes --]
prev parent reply other threads:[~2022-07-02 0:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <180245D1-0DCD-4C2C-A26A-EF68578FD548@canb.auug.org.au>
2022-06-30 14:23 ` [COFF] Re: [TUHS] " Michael Kjörling
2022-06-30 22:02 ` Charles H Sauer (he/him)
[not found] ` <CAFwmL87EKBmA-7umAjS4Hmj++jpE0SaRWMJyM7T=XMK++VPWPQ@mail.gmail.com>
[not found] ` <ef9644e7-0d91-76a9-491e-f8a33c8d0644@stanford.com.au>
[not found] ` <DCA1EA08-3901-4D14-9563-46B6BDEAE93A@mac.com>
[not found] ` <20220630212153.GD11191@mcvoy.com>
[not found] ` <CALQ0xCA4fH6Jp9N+_fg4h3wuxqNmGuSynnVFsSbXtAyZKS-ueQ@mail.gmail.com>
[not found] ` <CAO2qRdNnFi3HNP-cDZe_8GU1-D8AkMK0PoaKWEurLQUOm8iaOA@mail.gmail.com>
[not found] ` <20220630215445.GF11191@mcvoy.com>
[not found] ` <171E1A5A-268F-44EE-967E-5EF49004F824@csp-partnership.co.uk>
[not found] ` <CAKr56SwaAO3cXMp6hpfapCghdRR2q942nk90BtnWjpYNt2w=DQ@mail.gmail.com>
2022-07-02 0:04 ` [COFF] " Greg 'groggy' Lehey
[not found] ` <20220701004118.GA22338@tau1.ceti.pl>
[not found] ` <67e0d22c-e70b-e9bb-4614-eb1426bf2bd0@gmail.com>
2022-07-02 0:08 ` Greg 'groggy' Lehey
[not found] ` <C8A3B9E1-1A2B-4882-B2C6-A7E0C9E55500@gmail.com>
2022-07-02 1:26 ` [COFF] Safelights (was: "9 skills our grandkids won't have") Greg 'groggy' Lehey
2022-07-02 2:24 ` [COFF] " Charles H. Sauer
2022-07-02 2:35 ` Larry McVoy
2022-07-02 2:43 ` Greg 'groggy' Lehey
2022-07-02 2:49 ` Dave Horsfall
2022-07-06 9:00 ` Peter Jeremy via COFF
2022-07-06 14:06 ` [COFF] Re: Kodachrome [was Re: Safelights (was: "9 skills our grandkids won't have")] Dan Halbert
2022-07-02 5:21 ` [COFF] Re: Safelights (was: "9 skills our grandkids won't have") Adam Thornton
2022-07-02 5:35 ` Greg 'groggy' Lehey
[not found] ` <CABH=_VTyWKc9N1ARR6du3XLWkoNUzHB=8VDkxic2jUG6ofxs8A@mail.gmail.com>
[not found] ` <CACyhTRHyUJ8aBLyzQCm5iBANs_b1F8xfr1y-0drSVsCKZ+MToQ@mail.gmail.com>
2022-07-02 0:12 ` Greg 'groggy' Lehey [this message]
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=20220702001209.GC32390@eureka.lemis.com \
--to=grog@lemis.com \
--cc=coff@minnie.tuhs.org \
--cc=ori@heliconbooks.com \
--cc=paul.winalski@gmail.com \
/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).