home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!charon.amdahl.com!pacbell.com!ames!agate!doc.ic.ac.uk!uknet!mucs!mcchpc.mcc.ac.uk!zlsiimw
- From: zlsiimw@mcchpc.mcc.ac.uk (Mark Whidby)
- Newsgroups: comp.infosystems.gopher
- Subject: Re: execing shell scripts
- Message-ID: <6773@m1.cs.man.ac.uk>
- Date: 17 Nov 92 13:45:53 GMT
- References: <6749@m1.cs.man.ac.uk> <1992Nov16.144653.4835@engr.LaTech.edu> <1992Nov16.181914.29310@trentu.ca>
- Sender: news@cs.man.ac.uk
- Reply-To: M.Whidby@mcc.ac.uk
- Organization: Manchester Computing Centre
- Lines: 12
-
- In article <1992Nov16.181914.29310@trentu.ca>, ccksb@trentu.ca (Ken Brown)
- writes:
- |> If this is so, how do I stop bin from being seen by clients as a
- |> directory entry in the top level? After all, /usr/local/gopherdata
- |> contains other entries I wish to display but I don't wnat to display the
- |> bin dir.
-
- The directory bin (and others) are a special case; when gopher is parsing
- the directory structure it skips over bin (and core, dev, etc, usr).
- --
- _____________________________________________________________
- Mark Whidby, Distributed Systems, Manchester Computing Centre
-