From: "boyd, rounin" <boyd@insultant.net>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] troff port
Date: Sun, 16 May 2004 02:02:05 +0200 [thread overview]
Message-ID: <01ce01c43ad9$065e63e0$6e787d50@SOMA> (raw)
In-Reply-To: <01ba01c43ad5$bc67a290$6e787d50@SOMA>
> marked as BUGGERED until someone gets rid
> of all the compilation warnings.
just the sort of bit you need on various bits of buggered junk on plan 9 ;)
paul vixie, at some point, hacked a firewall kernel so that only root could
give public execute to executables. a neat hack to 'bless' executables.
root is dead now -- it was rooted.
next prev parent reply other threads:[~2004-05-16 0:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-15 6:44 Taj Khattra
2004-05-15 15:35 ` William Josephson
2004-05-15 23:35 ` Russ Cox
2004-05-15 23:38 ` boyd, rounin
2004-05-16 0:02 ` boyd, rounin [this message]
2004-05-16 4:01 ` William Josephson
2004-05-16 8:15 ` William Josephson
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='01ce01c43ad9$065e63e0$6e787d50@SOMA' \
--to=boyd@insultant.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).