From owner-freebsd-small Mon Oct 5 20:37:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA18030 for freebsd-small-outgoing; Mon, 5 Oct 1998 20:37:22 -0700 (PDT) (envelope-from owner-freebsd-small@FreeBSD.ORG) Received: from opera.iinet.net.au (opera.iinet.net.au [203.59.24.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA18019; Mon, 5 Oct 1998 20:37:12 -0700 (PDT) (envelope-from chris@rama-tech.com) Received: from grunge.iinet.net.au (grunge.iinet.net.au [203.59.24.9]) by opera.iinet.net.au (8.8.5/8.8.5) with ESMTP id LAA26935; Tue, 6 Oct 1998 11:36:51 +0800 Received: from jupiter.rama.com.au (reggae-13-44.nv.iinet.net.au [203.59.73.44]) by grunge.iinet.net.au (8.8.5/8.6.12) with ESMTP id LAA32389; Tue, 6 Oct 1998 11:36:41 +0800 Received: from rama-tech.com (chris [192.156.249.56]) by jupiter.rama.com.au (8.8.7/8.8.5) with ESMTP id LAA00976; Tue, 6 Oct 1998 11:31:45 +0800 Message-ID: <36198EAC.488D6796@rama-tech.com> Date: Tue, 06 Oct 1998 11:29:48 +0800 From: Chris Avis Organization: RAMA Technologies Pty Ltd X-Mailer: Mozilla 4.04 [en] (Win95; I) MIME-Version: 1.0 To: Andrew Hannam CC: owner-freebsd-small@FreeBSD.ORG, FreeBSDSmall Subject: Re: Command-line i/f (Re: PicoBSD) References: <000201bdf057$b991c100$0104010a@andrewh.famzon.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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