Date: Mon, 5 Oct 1998 22:00:20 +1000 From: "Andrew Hannam" <hannama@fan.net.au> To: <owner-freebsd-small@FreeBSD.ORG> Cc: "FreeBSDSmall" <freebsd-small@FreeBSD.ORG>, "AndrzejBialecki" <abial@nask.pl> Subject: RE: Command-line i/f (Re: PicoBSD) Message-ID: <000201bdf057$b991c100$0104010a@andrewh.famzon.com.au> In-Reply-To: <199810050737.AAA00893@dingo.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > >> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?000201bdf057$b991c100$0104010a>