From: Alan Watson <alan@oldp.nmsu.edu>
To: rc@hawkwind.utcs.toronto.edu
Subject: RE: intr and RC
Date: Tue, 7 Jan 1997 13:00:40 -0500 [thread overview]
Message-ID: <9701071800.AA05608@oldp.nmsu.edu> (raw)
> (As an aside, a SunOS 4.x binary of rc will probably work correctly on
> rc where a Solaris 2.5 binary compiled w/o -lbsd will do the wrong thing.)
My experience is that a SunOS 4.x binary traps the first interrupt
successfully, but then exits on the second.
Regards,
Alan
next reply other threads:[~1997-01-07 18:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-01-07 18:00 Alan Watson [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-01-13 1:33 Scott Schwartz
1997-01-12 23:39 Scott Schwartz
1997-01-13 0:52 ` David Luyer
1997-02-11 13:57 ` Markus Friedl
1997-01-12 23:17 Byron Rakitzis
1997-01-09 21:59 Scott Schwartz
1997-01-08 20:01 Mark K. Gardner
1997-01-09 11:09 ` Tim Goodwin
1997-01-08 7:45 Bengt Kleberg
1997-01-07 19:55 Alan Watson
1997-01-07 17:03 Mark K. Gardner
1997-01-07 17:16 ` Scott Schwartz
1997-01-07 17:46 ` Paul Haahr
1996-12-31 21:53 Mark K. Gardner
1996-12-31 22:01 ` Soren Dayton
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=9701071800.AA05608@oldp.nmsu.edu \
--to=alan@oldp.nmsu.edu \
--cc=rc@hawkwind.utcs.toronto.edu \
/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).