From: Jim Chapman <jim.chapman@iname.com>
To: Grant Erickson <grant@borg.umn.edu>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Embedded Perl
Date: Thu, 08 Jun 2000 16:55:46 +0100 [thread overview]
Message-ID: <393FC202.1E5007C9@iname.com> (raw)
In-Reply-To: Pine.SGI.4.21.0006081030590.371275-100000@tigris.borg.umn.edu
Have you looked at the GoAhead embedded web server? It's in the HardHat
distribution. It's intended for small memory footprint requirements and seems
to have mechanisms to do CGI-style stuff without needing perl.
See www.goahead.com
-Jim
Grant Erickson wrote:
> In a target system I was planning on running Perl scripts as a means to
> accomplish a lot of tasks, particularly for driving CGI scripts for
> web-based management. However, it has since dawned on me that an
> installation of Perl is HUGE (12+ MB).
>
> Has anyone had any experience getting PERL shoehorned into an embedded
> environment? How trim were you able to make Perl?
>
> Thanks,
>
> Grant Erickson
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2000-06-08 15:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-08 15:35 Embedded Perl Grant Erickson
2000-06-08 15:55 ` Jim Chapman [this message]
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=393FC202.1E5007C9@iname.com \
--to=jim.chapman@iname.com \
--cc=grant@borg.umn.edu \
--cc=linuxppc-embedded@lists.linuxppc.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).