From owner-freebsd-small Mon Oct 5 15:17:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA14466 for freebsd-small-outgoing; Mon, 5 Oct 1998 15:17:41 -0700 (PDT) (envelope-from owner-freebsd-small@FreeBSD.ORG) Received: from smtp02.wxs.nl (smtp02.wxs.nl [195.121.6.60]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA14440 for ; Mon, 5 Oct 1998 15:17:35 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from diabolique ([195.121.59.34]) by smtp02.wxs.nl (Netscape Messaging Server 3.6) with SMTP id AAB16AD; Tue, 6 Oct 1998 00:17:32 +0200 Message-Id: X-Sender: skywise@pop.wxs.nl X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Demo Date: Tue, 06 Oct 1998 00:12:02 +0200 To: "Andrew Hannam" From: Jeroen Ruigrok/Asmodai Subject: RE: Command-line i/f (Re: PicoBSD) Cc: "FreeBSDSmall" , "AndrzejBialecki" Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 At 14:00 05-10-98 , you 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. At this point, I find WWW pages not the top priority, the idea might be very useful later on in the development, offcourse, one could keep sidenotes about implementing it in order to ease it's process later on, but at this point I say, let's start with an engine first and then enhance it... [snip of catch] >There are two solutions to this... >a) Have a serial (or something else) connection just to set the initial IP >address. Like configuring a Cisco/Shiva router for the first time... >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. Sounds acceptable... Jeroen Ruigrok van der Werven / Asmodai ICQ-UIN: 1564317 .:. Ninth Circle Enterprises Network/Security Specialist /==|| FreeBSD and picoBSD, the Power to Serve ||==\ -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 6.0 for non-commercial use iQA/AwUBNhk084Y752GnxADpEQIgKgCg343ysxyfJyegWsTvqR87OV7IK0cAoPUr vwo+Ukms4LmnYm/T9/aD961c =WIDD -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message