9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: forsyth@caldo.demon.co.uk
To: 9fans@cse.psu.edu
Subject: Re: [9fans] find/locate a file
Date: Sat, 11 Nov 2000 17:00:50 +0000	[thread overview]
Message-ID: <20001111160512.A1C6A199DC@mail.cse.psu.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 794 bytes --]

for compiled executables, try src(1).

in this particular case, however, the services are implemented by shell scripts.
see listen(8) for details, but they are found in /rc/bin/service and /rc/bin/service.auth,
in files named using an obvious naming scheme (eg, /rc/bin/service/tcp7).

	term% cat /bin/service/tcp7
	#!/bin/rc
	/bin/cat

so much for that one.  others such as tcp25 invoke specialised commands
with appropriate argument shuffling:

	term% cat /bin/service/tcp25
	#!/bin/rc
	#smtp serv net incalldir user

	user=`{cat /dev/user}
	exec upas/smtpd -n $3

and then you can do
	src /bin/upas/smtpd
to pop the source of the command into an acme frame, or use
src -n just to print the name:

	term% src -n /bin/upas/smtpd
	/sys/src/cmd/upas/smtp/smtpd.c:71


[-- Attachment #2: Type: message/rfc822, Size: 1736 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


             reply	other threads:[~2000-11-11 17:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-11 17:00 forsyth [this message]
2000-11-11 16:10 ` Boyd Roberts
  -- strict thread matches above, loose matches on Subject: below --
2000-11-11 17:06 forsyth
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=20001111160512.A1C6A199DC@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).