From: Scott Schwartz <schwartz@cse.psu.edu>
To: rc@hawkwind.utcs.toronto.edu
Subject: Re: Update for Debian shells/rc-1.4-2
Date: Tue, 4 Mar 1997 14:08:09 -0500 [thread overview]
Message-ID: <199703041908.OAA22774@cse.psu.edu> (raw)
In-Reply-To: Your message of "Tue, 04 Mar 1997 12:33:09 EST." <9703041733.AA00778@lupine.techfak.uni-bielefeld.de>
Peter Koch <pk@TechFak.Uni-Bielefeld.DE> writes:
| Version 1.5beta was ported to Solaris (2.4) long ago, fixing some ugly
| problems with signal handling.
Aside from the SIGCLD thing and the SIGINT thing, what problems?
| We also started POSIXifying the code,
Posix systems still run traditional code, but not the other way
around. To avoid bunches of ifdefs, that argues for staying
with the traditional code as much as possible.
next prev parent reply other threads:[~1997-03-04 19:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-03-03 19:09 Byron Rakitzis
1997-03-04 3:34 ` David Luyer
1997-03-04 3:51 ` Soren Dayton
1997-03-04 15:22 ` Conceptual Integrity (Re: Update for Debian shells/rc-1.4-2) Richard Brooksby
1997-03-04 17:33 ` Update for Debian shells/rc-1.4-2 Peter Koch
1997-03-04 19:08 ` Scott Schwartz [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-03-04 2:01 Tom Culliton
1997-02-27 19:02 Vincent Broman
1997-02-27 19:55 ` Scott Schwartz
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=199703041908.OAA22774@cse.psu.edu \
--to=schwartz@cse.psu.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).