From owner-freebsd-small Sat Oct 3 15:35:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA10151 for freebsd-small-outgoing; Sat, 3 Oct 1998 15:35:24 -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 PAA10129 for ; Sat, 3 Oct 1998 15:35:17 -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 AAA07583; Sun, 4 Oct 1998 00:39:32 +0200 (CEST) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Sun, 4 Oct 1998 00:39:32 +0200 (CEST) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Jeroen Ruigrok/Asmodai cc: Jerry Hicks , FreeBSD Small Subject: Re: Command-line i/f (Re: PicoBSD) In-Reply-To: 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 Sat, 3 Oct 1998, Jeroen Ruigrok/Asmodai wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > At 07:59 02-10-98 , Andrzej Bialecki wrote: > >On Thu, 1 Oct 1998, Jerry Hicks wrote: > > > >> YAPL with some pretty desirable attributes for this sort of application. > I > >> believe you're right on track Adrzej. > > > >Heh.. Thanks for confirmation :-) Well, I know it's not _that_ popular > >, but it gives tremendous programmability and > >flexibility, compared to what /bin/sh gives with much more bloat. And I'd > >rather not invent YAPL, tripping over the same pitfalls as others did - > >Forth is very mature and well defined. > > Never played with Forth, what does it compare to? Hard to tell... It's definitely different than other popular languages. It's built around a concept of stack (all operations are done on its internal stacks), it's a cross between compiler and interpreter, uses a Reverse Polish Notation for most of its operations (now, this is not the reason I started to play with it :-)), etc, etc, - see www.forth.org for more info. > That wasn't my suggestion, but the current setup of FreeBSD is too limiting > or too scattered throughout directories to be of any use for the picoBSD > setup. Exactly! This is the issue I want to address. > But I think that's the question, how far are ye willing to go to > preserve usability on the picoBSD setups, as far as I now can foresee, we > use these disks for quick and 'dirty' routers. How much use is there to > support every known command that don't actually add on to the purpose of > which the disks were designed (correct me if wrong offcourse =). As I see > it, we should/could use the FreeBSD cores, extend it with things like Zebra > and the likes and modify the UI/shell to resemble configuration commands > like IOS and Shiva/SpiderSoftware routing stuff... Again, I fully agree with you - that's also my intention. And I see a Forth -based shell as a means to accomplish it - to glue all these elements together, at the same time giving it flexibility and programming abilities far beyond those of /bin/sh. 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