From: forsyth@caldo.demon.co.uk
To: 9fans@cse.psu.edu
Subject: Re: [9fans] find/locate a file
Date: Sat, 11 Nov 2000 17:06:13 +0000 [thread overview]
Message-ID: <20001111161035.BF375199DC@mail.cse.psu.edu> (raw)
i ought to have added that although i used absolute names to
make it clearer which file src was examining, i could have said
src upas/smtpd
or
src smtpd
and let it hunt for it in /bin and /bin/* itself.
it actually works for scripts as well, thus
src tcp7
src tcp25
would track down the services (but you'd have had to know the naming scheme).
try
src src
next reply other threads:[~2000-11-11 17:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-11 17:06 forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-11-11 17:00 forsyth
2000-11-11 16:10 ` Boyd Roberts
2000-11-11 15:02 nigel
2000-11-11 14:51 Ish Rattan
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=20001111161035.BF375199DC@mail.cse.psu.edu \
--to=forsyth@caldo.demon.co.uk \
--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).