From: "Steve Simon" <steve@quintile.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] non-truncating create
Date: Mon, 9 Oct 2006 08:30:29 +0100 [thread overview]
Message-ID: <0f63dfdff8450df787f23dcddf6528e2@quintile.net> (raw)
In-Reply-To: <670cd94c9c214091df90d0585d739af1@plan9.jp>
> Probably not. The interesting part of sysfatal is the
> terminating the program, not the printing of the error.
I believe this depends upon the life expectancy of the
program, I have written a shell for another OS and found
syswarn() quite "handy"; this OS didn't have %r though.
-Steve
next prev parent reply other threads:[~2006-10-09 7:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-09 6:46 Joel “chesky” Salomon
2006-10-09 7:30 ` Steve Simon [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-10-09 22:38 G. David Butler
2006-10-09 23:36 ` Joel Salomon
2006-10-10 0:03 ` Russ Cox
2006-10-09 3:13 Joel “chesky” Salomon
2006-10-09 3:13 Joel “chesky” Salomon
2006-10-09 3:13 Joel “chesky” Salomon
2006-10-09 4:00 ` Russ Cox
2006-10-09 6:09 ` Joel “chesky” Salomon
2006-10-09 15:57 ` Russ Cox
2006-10-09 4:01 ` Felipe Bichued
2006-10-09 5:39 ` Joel Salomon
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=0f63dfdff8450df787f23dcddf6528e2@quintile.net \
--to=steve@quintile.net \
--cc=9fans@cse.psu.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).