From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=HTML_MESSAGE, MAILING_LIST_MULTI,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 17065 invoked from network); 2 Jul 2022 23:02:01 -0000 Received: from minnie.tuhs.org (50.116.15.146) by inbox.vuxu.org with ESMTPUTF8; 2 Jul 2022 23:02:01 -0000 Received: from minnie.tuhs.org (localhost [IPv6:::1]) by minnie.tuhs.org (Postfix) with ESMTP id 5794C40CFB; Sun, 3 Jul 2022 09:01:53 +1000 (AEST) Received: from mail.lazo.ca (mail.lazo.ca [45.79.111.222]) by minnie.tuhs.org (Postfix) with ESMTPS id 30AD840881 for ; Sun, 3 Jul 2022 09:01:49 +1000 (AEST) Received: from [127.0.0.1] (S010690aac3cf6cf3.cc.shawcable.net [96.54.220.64]) (authenticated bits=0) by mail.lazo.ca (8.15.2/8.15.2/Debian-8+deb9u1) with ESMTPSA id 262N1mSc018304 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT) for ; Sat, 2 Jul 2022 16:01:48 -0700 Date: Sat, 02 Jul 2022 16:01:43 -0700 From: Mark Sutton To: tuhs@tuhs.org User-Agent: K-9 Mail for Android In-Reply-To: References: <180245D1-0DCD-4C2C-A26A-EF68578FD548@canb.auug.org.au> Message-ID: <4FC15BF4-B7A8-4CE6-B3B8-FF52F1517219@lazo.ca> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary=----4WT4UKDM9YJ44RA9NTS0VHLW9X05F8 Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.11 (mail.lazo.ca [45.79.111.222]); Sat, 02 Jul 2022 16:01:48 -0700 (PDT) Message-ID-Hash: TIDSJI3X2TCBZZN6X3QBJUHYLMY4EVHV X-Message-ID-Hash: TIDSJI3X2TCBZZN6X3QBJUHYLMY4EVHV X-MailFrom: mes@lazo.ca X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tuhs.tuhs.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.6b1 Precedence: list Subject: [TUHS] Re: "9 skills our grandkids won't have" - Is this a TUHS topic? List-Id: The Unix Heritage Society mailing list Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: ------4WT4UKDM9YJ44RA9NTS0VHLW9X05F8 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Thanks for asking Ori, I was just working up the courage to express my igno= rance=20 On July 1, 2022 6:05:30 AM PDT, Ori Idan wrote: >On Thu, Jun 30, 2022 at 7:38 PM Paul Winalski >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=2E > >> > > >> o why CTRL/S and CTRL/Q are used for flow control in a shell command >> line session >> >Also would be happy to know=2E > > >> >> o why an application memory dump after an application crash is called >> a core file >> >> -Paul W=2E >> ------4WT4UKDM9YJ44RA9NTS0VHLW9X05F8 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable Thanks for asking Ori, I was just working up the c= ourage to express my ignorance

On July 1= , 2022 6:05:30 AM PDT, Ori Idan <ori@heliconbooks=2Ecom> wrote:

=
On Thu, Jun 30, 2022 at 7:38 PM Paul Winalski <paul=2Ewinalski@gmail=2Ecom>= 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=2E 
 

o why CTRL/S and CTRL/Q are used for flow control in a shell command
line session
Also would be happy to know=2E
 

o why an application memory dump after an application crash is called
a core file

-Paul W=2E
------4WT4UKDM9YJ44RA9NTS0VHLW9X05F8--