9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Dan Cross <cross@math.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] webls.c - synthesize directories on the fly.
Date: Wed,  1 Oct 2003 01:39:03 -0400	[thread overview]
Message-ID: <200310010539.h915d3j23173@augusta.math.psu.edu> (raw)
In-Reply-To: Your message of "Wed, 01 Oct 2003 14:21:06 +0900." <8a0a335a1266c14c62a1b5b805dd4079@orthanc.cc.titech.ac.jp>

YAMANASHI Takeshi <uncover@beat.cc.titech.ac.jp> writes:
> just from curiosity.
>
> "On Tue Sep 30 18:34:55 JST 2003, cross@sdgm.net wrote:"
> > It also has support for specifying two files,
> > /sys/lib/webls.allowed and /sys/lib/webls.denied for restricting
> > access to what parts of the web space it will create listings for
>
> why not bind all the desired directories on somewhere,
> let's say /usr/web/webls for example, and make webls services
> only under the directory?
>
> these whatever.^(allowed denied) files remind me of unix somehow.

Hmm, that's an idea.  I'll think about it.  My initial reaction is
that you'd have to do all the binds somewhere, and have a skeletal
directory structure under /usr/web/webls, which strikes me as tedious.
Still, I'll give it some thought.

	- Dan C.



  reply	other threads:[~2003-10-01  5:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-01  5:21 YAMANASHI Takeshi
2003-10-01  5:39 ` Dan Cross [this message]
2003-10-01  5:41   ` Lucio De Re
2003-10-01 11:41     ` Eric Grosse
2003-10-01 16:17       ` Dan Cross
2003-10-07 20:30       ` vdharani
2003-10-08  8:09         ` Fco.J.Ballesteros
2003-10-08  8:45           ` arisawa
2003-10-10  7:18         ` Eric Grosse
  -- strict thread matches above, loose matches on Subject: below --
2003-10-22 12:35 Eric Grosse
2003-10-01  8:05 YAMANASHI Takeshi
2003-09-29  6:14 cross

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=200310010539.h915d3j23173@augusta.math.psu.edu \
    --to=cross@math.psu.edu \
    --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).