From: "boyd, rounin" <boyd@insultant.net>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] silly suggestions
Date: Thu, 31 Mar 2005 09:02:56 +0200 [thread overview]
Message-ID: <00b401c535bf$aaee5960$0d35dfd5@kilgore> (raw)
In-Reply-To: <557d92e4adb24fdbb1b4706666b5c674@collyer.net>
> As far as I know, no actual executable's name starts with
> '_', so it's safe to remove /386/bin/_*, for example.
what about various unused services in?
/bin/service
/bin/service/auth
--
MGRS 31U DQ 52572 12604
next prev parent reply other threads:[~2005-03-31 7:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-31 4:34 lucio
2005-03-31 5:21 ` geoff
2005-03-31 7:02 ` boyd, rounin [this message]
2005-03-31 7:16 ` geoff
2005-04-01 4:06 ` lucio
2005-04-01 12:22 ` Russ Cox
2005-03-31 11:57 ` Russ Cox
2005-03-31 17:13 ` Heiko Dudzus
2005-03-31 17:15 ` Russ Cox
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='00b401c535bf$aaee5960$0d35dfd5@kilgore' \
--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).