From owner-freebsd-small Mon Oct 5 05:19:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA29217 for freebsd-small-outgoing; Mon, 5 Oct 1998 05:19:00 -0700 (PDT) (envelope-from owner-freebsd-small@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA29209; Mon, 5 Oct 1998 05:18:50 -0700 (PDT) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id OAA11798; Mon, 5 Oct 1998 14:22:27 +0200 (CEST) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Mon, 5 Oct 1998 14:22:27 +0200 (CEST) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Andrew Hannam cc: owner-freebsd-small@FreeBSD.ORG, FreeBSDSmall Subject: RE: Command-line i/f (Re: PicoBSD) In-Reply-To: <000201bdf057$b991c100$0104010a@andrewh.famzon.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 5 Oct 1998, 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. 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... > > 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. Ugh... If you go to such measures as connecting it via serial console, what prevents you from using a PPP connection on it, and do all the job using serial console? > 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... Andrzej Bialecki -------------------- ++-------++ ------------------------------------- ||PicoBSD|| FreeBSD in your pocket? Go and see: Research & Academic |+-------+| "Small & Embedded FreeBSD" Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/ -------------------- ~-+==---+-+ ------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message