From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] new bounties posted
Date: Sat, 21 Dec 2019 15:26:42 +0100 [thread overview]
Message-ID: <F8E7504BE8B9022E76EEFD68647C6A80@felloff.net> (raw)
In-Reply-To: <acb3f659-9736-45fe-9824-5b464c1797f9@www.fastmail.com>
i dont know where you got the idea from that execfs only serves one
file.
you specify a rule file in execfs maps regular expression on the file
path to a command.
theres a example rule file to serve manual pages in html:
/man2html/([0-9])/([a-zA-Z0-9\.]+) troff -manhtml /sys/man/\1/\2 | troff2html -t '\2(\1)'
execfs is kind of just a toy i wrote to serve manpages from tcp80.
ironically, execfs itself has no manpage.
what it does not do is provide directory listings.
it is probably not what you'd want for a vcardfs where you want
to parse all the files, deduplicate and provide like a index
structure so you can efficiently query the set.
--
cinap
next prev parent reply other threads:[~2019-12-21 14:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AA6EE3B60CE1D15090F71392CEDD3B98@ewsd.inri.net>
2019-12-21 13:52 ` Ethan Gardener
2019-12-21 14:26 ` cinap_lenrek [this message]
2019-12-21 15:53 ` Ethan Gardener
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=F8E7504BE8B9022E76EEFD68647C6A80@felloff.net \
--to=cinap_lenrek@felloff.net \
--cc=9front@9front.org \
/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).