From owner-freebsd-small Fri Oct 2 05:02:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA13821 for freebsd-small-outgoing; Fri, 2 Oct 1998 05:02:48 -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 FAA13750 for ; Fri, 2 Oct 1998 05:02:23 -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 OAA05563; Fri, 2 Oct 1998 14:06:28 +0200 (CEST) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Fri, 2 Oct 1998 14:06:27 +0200 (CEST) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Chris Avis cc: freebsd-small@FreeBSD.ORG Subject: Re: IOS/SHiva's SpiderSoftware In-Reply-To: <3614627D.AAD3E521@rama-tech.com> 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 Fri, 2 Oct 1998, Chris Avis wrote: > Could someone who knows what this interface looks like/ > behaves post a quick description to the group. I'm not > sure what is being proposed here. I don't know it, but here's what I want to do. I'd like to have some kind of command-line interface which would allow for complete configuration of a {pico,Free}BSD box. I don't mind if we end up with totally incompatible layout of config file (note: a single file, not a bunch of scripties), as long as we have some generic enough tool to either convert it to the standard ones, or to perform the task of bringing up the system itself, basing on this description. Since I'm pretty familiar with the Cisco's IOS, this was the first example that came to my mind. I'm certainly open for other models, as long as they provide for: * consistent structure, and view of the system properties * ease of use, and possible customization * programmability * ability to perform automated tasks I'm asking for much, I know, but we can evaluate various candidates... For a full-fledged system someone proposed to use LDAP, but for embedded applications it's a total overkill - we need something even more light-weight ;-) 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