On Friday 21 of January 2005 18:25, Giridhar Pemmasani wrote:
> Thanks for sharing it. Perl itself may be big, but it is installed on
> most computers. PHP with web interface is probably easier to use. I
> don't know much about this, but if this script can made to work to
> accept INF and SYS/BIN files with web interface, we could probably
> switch to it.
No, it's not a web interface :) - it acts *exactly* like the original
> I am curious to know what project it is.
An embedded Linux distribution targetted at routers, especially 802.11 ones.
On Friday 21 of January 2005 20:19, David Kaplan wrote:
> It has been a while since I have used php, but wouldn't using it require
> everyone to have a working web server with php installed?
> I am guessing that this is no longer the case from Pawel's email and that
> it now has a command-line interface.
Exactly, during configure time you can choose whether (apart of a webserver
module) you want to build a CLI (default) or CGI. My script works both with
CLI and CGI version (in the second case it's using a few tricks to disable
printing of HTTP headers, to turn off output buffering, etc, so it acts
exactly as a CLI).
> Even so, php is not part of the default install
> of many distributions, especially on a laptop, and the php package isn't
> that much lighter than perl or python.
My PHP executable weights only 1MB. I think PHP is a good choice for embedded
solutions, as it can be used both to create a web interface and command line
It wasn't my intention to replace the original tool, I just wanted to provide
an alternative one.