From owner-freebsd-small Sun Oct 4 14:39:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA02761 for freebsd-small-outgoing; Sun, 4 Oct 1998 14:39:21 -0700 (PDT) (envelope-from owner-freebsd-small@FreeBSD.ORG) Received: from smtp03.wxs.nl (smtp03.wxs.nl [195.121.6.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA02755 for ; Sun, 4 Oct 1998 14:39:17 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from diabolique ([195.121.59.64]) by smtp03.wxs.nl (Netscape Messaging Server 3.6) with SMTP id AAA2916; Sun, 4 Oct 1998 23:38:53 +0200 Message-Id: X-Sender: skywise@pop.wxs.nl X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Demo Date: Sun, 04 Oct 1998 23:40:34 +0200 To: Andrzej Bialecki From: Jeroen Ruigrok/Asmodai Subject: Re: Command-line i/f (Re: PicoBSD) Cc: Jerry Hicks , FreeBSD Small In-Reply-To: References: Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 At 00:39 04-10-98 , Andrzej Bialecki wrote: >On Sat, 3 Oct 1998, Jeroen Ruigrok/Asmodai wrote: >> At 07:59 02-10-98 , Andrzej Bialecki wrote: >> >On Thu, 1 Oct 1998, Jerry Hicks wrote: >> >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. Reverse polish notation? I know of Hungarian notation, but not Polish, want to enlighten me? >> 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. Then I understood ye correctly ;) >> 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. Dang, have to learn Forth than don't I? =) How far do we need to adhere to Cisco's IOS/Shiva's SpiderSoftware command syntaxing? Most of it is good and usable. Regards, 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/AwUBNhfdQ4Y752GnxADpEQKTAgCfYL7FQY3gTx4TuhPqNgNDlsywNAMAnR+G sUK1KxdBi06fR3PrcKBGUAmC =zKNr -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message