From owner-freebsd-small Mon Oct 5 15:17:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA14460 for freebsd-small-outgoing; Mon, 5 Oct 1998 15:17:40 -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 PAA14431; Mon, 5 Oct 1998 15:17:34 -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 AAA16AD; Tue, 6 Oct 1998 00:17:30 +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:18:20 +0200 To: Andrzej Bialecki , Andrew Hannam From: Jeroen Ruigrok/Asmodai Subject: RE: Command-line i/f (and versioning) Cc: owner-freebsd-small@FreeBSD.ORG, FreeBSDSmall In-Reply-To: References: <000201bdf057$b991c100$0104010a@andrewh.famzon.com.au> Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 At 14:22 05-10-98 , Andrzej Bialecki wrote: >On Mon, 5 Oct 1998, Andrew Hannam wrote: >> 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. >I personally am a big hater of WWW config interfaces... but that's just >me. IMHO it's useful mostly for marketing hype and (maybe) for people who >are complete newbies, but for those who want to get the job done it just >stands in the way... OTOH, perhaps I had just a bad experience - that one >I tried to use was completely useless, because I could do the same job >much quicker using command-line i/f with completion... I myself am a sucker for textbased commandline configurating... WWW interfaces require too much point and click, then again, it might be better suited for those that aren't that wellgifted with CLI's =) >> 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. > >Hmmm... This would probably require putting the interface in promiscuous >mode, and using some kind of BPF thing to read the packets... Lame statement though: we are going to make disks, we boot using a disk, so we probably have a keyboard nearby? Correct me if wrong, but the resources might be lying around ;) Also, let's get the picoBSD internals as stable as possible and then continue onwards to enhancing the interface. So my vote for now is, discuss and plan enhancements, yet stick with CLI's now. Also, how are we seperating the STABLE and CURRENT-derived picoBSD's from each other? do they also have a prefix? 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/AwUBNhk3nYY752GnxADpEQIdnACgzlBsI4EUlvVrcSHPRDrmjN/El/MAoOKX ZxOJJHzR6SJNHfvwdUpDA30E =YcAn -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message