Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 06 Oct 1998 11:29:48 +0800
From:      Chris Avis <chris@rama.com.au>
To:        Andrew Hannam <hannama@fan.net.au>
Cc:        owner-freebsd-small@FreeBSD.ORG, FreeBSDSmall <freebsd-small@FreeBSD.ORG>
Subject:   Re: Command-line i/f (Re: PicoBSD)
Message-ID:  <36198EAC.488D6796@rama-tech.com>
References:  <000201bdf057$b991c100$0104010a@andrewh.famzon.com.au>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
I say go with the tiny Web based solution. I think the debate over
command line and web based interfaces was decided long before this
discussion started.

I can guarantee the answer to this question if taken to the Marketing
Division of any organisation. On this issue I believe we go with the
flow or become marginalised. Wether we like it or not the market demands
that "successful" embedded products support a Web Interface.

Option "b" below sounds progressive and a positive step forward. I
propose we adopt this and get something started. I am prepared to
contribute, how do we start this going.

regards
Chris

Andrew Hannam wrote:
> 
> > > >> grouping of commands under another keyword, for example: ip,
> > ipx, dial,
> > > etc...
> 
> As long as you are doing the hierarchy breakdown of commands - why not do it
> as a set of web page constructs. A tiny web server, a few text files (html
> pages - forget pictures) and possibly a command interpreter of any flavour.
> This approach is easier for the administrator (no command set to learn).
> Management of the various parts of the system can be separated into separate
> 'cgi-bin' programs of either compiled or interpreted variety depending on
> the situation.
> 
> The one catch:
> You need to establish an IP address before this will work. Subnet mask can
> initially default to 0.0.0.0 (and similarly gateway in this circumstance is
> not relevant).
> 
> There are two solutions to this...
> a) Have a serial (or something else) connection just to set the initial IP
> address.
> b) Use the scheme that many standalone devices such as print servers use.
> Until an IP address is programmed via the web front end - all non-broadcast
> addresses sent to the ethernet card are accepted. Using a static ARP entry
> for the device with any suitable IP address is then sufficient to talk to it
> in this initial state.
> 
> Comments Please ...
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-small" in the body of the message

-- 
                Chris Avis (c.avis@rama-tech.com)
     _--_|\     RAMA Technologies Pty Ltd, 28 Walters Drive
    /      \    Osborne Park, Western Australia 6017, Australia
    \_.--._/    Tel: +61 8 9445 7999 Fax: +61 8 9445 7666
          v     http://www.rama-tech.com

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-small" in the body of the message



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?36198EAC.488D6796>