From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <62c0dde05800ea93317896e1676d7362@brasstown.quanstro.net>
References: <CAG3N4d9b=7pRHSPbv0f7nBSWsXU4qfQ2MeFQMF--znGKxT_JBQ@mail.gmail.c>
	<7b91c25159e2f83bbf6632726c978d2d@kw.quanstro.net>
	<CAP6exYKyMipMjJVfBbsWTrXchWjdKQMXpjGn963h93EWrDwYNA@mail.gmail.c>
	<62c0dde05800ea93317896e1676d7362@brasstown.quanstro.net>
Date: Tue, 28 Aug 2012 09:02:08 -0700
Message-ID: <CAP6exY+VEV_3CLK53oycH47CADvzNXyWpNn+_E74Sz88TQjkcA@mail.gmail.com>
From: ron minnich <rminnich@gmail.com>
To: erik quanstrom <quanstro@quanstro.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: 9fans@9fans.net
Subject: Re: [9fans] syscall tracing: errstr
Topicbox-Message-UUID: b2d85ecc-ead7-11e9-9d60-3106f5b1d025

I'll say it again: if a syscall is supported, it should be possible to
trace it. If you remove a system call from Plan 9, then by all means
remove the syscallfmt support, of course. But if a system call is
still valid, and can be called, deprecated or not, I don't see the
point of not being able to trace it. I note that your patch was
against 9, not nix. Did you remove those system deprecated system
calls when you removed support for printing them?

ron