From: nigel@9fs.org
To: 9fans@cse.psu.edu
Subject: Re: [9fans] find/locate a file
Date: Sat, 11 Nov 2000 15:02:45 +0000 [thread overview]
Message-ID: <E13ucB4-000LvW-0W@anchor-post-32.mail.demon.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 197 bytes --]
One might normally use the src(1) command,
however,
src echo
finds the source to the echo(1) command.
cat /rc/bin/service/tcp7
shows the real command for tcp echo. It its cat(1).
[-- Attachment #2: Type: message/rfc822, Size: 1448 bytes --]
From: Ish Rattan <ishwar@pali.cps.cmich.edu>
To: 9fans@cse.psu.edu
Subject: [9fans] find/locate a file
Date: Sat, 11 Nov 2000 09:51:04 -0500 (EST)
Message-ID: <Pine.BSF.4.21.0011110949080.18795-100000@pali.cps.cmich.edu>
Is there a way to find (discover the path) of a file
in the source tree? For example, source for echo server
running on port 7 (if the name is echo.c??).
- ishwar
next reply other threads:[~2000-11-11 15:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-11 15:02 nigel [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-11-11 17:06 forsyth
2000-11-11 17:00 forsyth
2000-11-11 16:10 ` Boyd Roberts
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=E13ucB4-000LvW-0W@anchor-post-32.mail.demon.net \
--to=nigel@9fs.org \
--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).