From owner-freebsd-small Sun Oct 4 13:59:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA26573 for freebsd-small-outgoing; Sun, 4 Oct 1998 13:59:33 -0700 (PDT) (envelope-from owner-freebsd-small@FreeBSD.ORG) Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA26553 for ; Sun, 4 Oct 1998 13:59:27 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from diabolique ([195.121.59.64]) by smtp01.wxs.nl (Netscape Messaging Server 3.6) with SMTP id AAA536E; Sun, 4 Oct 1998 22:59:03 +0200 Message-Id: X-Sender: skywise@pop.wxs.nl X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Demo Date: Sun, 04 Oct 1998 22:35:19 +0200 To: "Louis A. Mamakos" From: Jeroen Ruigrok/Asmodai Subject: Re: Command-line i/f (Re: PicoBSD) Cc: Jerry Hicks , FreeBSD Small , Andrzej Bialecki In-Reply-To: <199810032345.TAA21910@whizzo.transsys.com> References: Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 At 01:45 04-10-98 , Louis A. Mamakos wrote: > >> 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. > >I can certainly see how having an extensible shell would be a very >attractive thing. But if you expect mere mortals to be able to >run (and extend) the thing, I think a FORTH-based approach is doomed >to fail (again). > >Why wouldn't something based on TCL be a better choice? Sysadmins are >probably more likely to be familiar with it (perhaps due to experience >with "expect"). It has a pretty reasonable syntax, and perhaps >a more familair procedural type model. Well the whole issue is NOT the language, but the UI and that UI should be an executable which can alter all the nessecary files (UID of root nessecary or would that be done by daemoning it?). The goal we have to reach is providing a usable frontend regardless of which language we use... As such I have a few suggestions already based on IOS/Shiva SpiderSoftware command syntax: grouping of commands under another keyword, for example: ip, ipx, dial, etc... Also, will we be using autocompletion of partially typed commands? 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/AwUBNhfN94Y752GnxADpEQIecgCg/B9yHuuhrTB5LT3qSfirJ5152pYAoN5x VRz2IaB2lNjpNU4grU+7PHYM =AdjK -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message