From owner-freebsd-current Fri Jun 21 17:07:39 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA13195 for current-outgoing; Fri, 21 Jun 1996 17:07:39 -0700 (PDT) Received: from covina.lightside.com (covina.lightside.com [207.67.176.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id RAA13189; Fri, 21 Jun 1996 17:07:37 -0700 (PDT) Received: by covina.lightside.com (Smail3.1.28.1 #6) id m0uXGEY-0004JeC; Fri, 21 Jun 96 17:07 PDT Date: Fri, 21 Jun 1996 17:07:25 -0700 (PDT) From: Jake Hamby To: Poul-Henning Kamp cc: Andreas Klemm , current@FreeBSD.ORG Subject: Re: The FreeBSD Way In-Reply-To: <28918.835400506@critter.tfs.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 21 Jun 1996, Poul-Henning Kamp wrote: > >> On Fri, 21 Jun 1996, Andreas Klemm wrote: > >> > >> > Generally I share your sight, but even SunSofts Solaris 2.x uses > >> > tk in the main system... > >> > >> Uh, no... Solaris uses Motif for installation, etc.. TCL and Tk are a > >> product of SunLabs, yes, but they haven't seen fit to include either into > >> Solaris (at least, not as of Solaris 2.5). > > > >Hmm, I thought, that many sysadmin tools were written in tk... > >admintool, swmtool ... Am I so wrong ??? > > no, you are right. Sun were one of the first companies to embrace > tcl/tk. They even made an incredibly bogus openwin version of tk. Whoa, Poul, I think you are wrong, at least as far as Solaris 2.5. Maybe originally they used TCL/Tk, but in Solaris 2.3, admintool was pure OPEN LOOK, and as of Solaris 2.4, it was Motif. Herewith, the proof: # uname -a SunOS aris 5.5 Generic_103093-02 sun4m sparc SUNW,SPARCstation-20 # ldd /usr/bin/admintool libprinter.so.2 => /usr/snadm/lib/libprinter.so.2 libserial.so.2 => /usr/snadm/lib/libserial.so.2 libadmldb.so.2 => /usr/snadm/lib/libadmldb.so.2 libadmutil.so.2 => /usr/snadm/lib/libadmutil.so.2 libadmapp.so.2 => /usr/snadm/lib/libadmapp.so.2 libmp.so.1 => /usr/lib/libmp.so.1 libsocket.so.1 => /usr/lib/libsocket.so.1 libnsl.so.1 => /usr/lib/libnsl.so.1 libinstall.so.2 => /usr/snadm/lib/libinstall.so.2 libsw.so.2 => /usr/snadm/lib/libsw.so.2 libadm.so.1 => /usr/lib/libadm.so.1 libXm.so.3 => /usr/dt/lib/libXm.so.3 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ libXt.so.4 => /usr/lib/libXt.so.4 libX11.so.4 => /usr/lib/libX11.so.4 libc.so.1 => /usr/lib/libc.so.1 libkvm.so.1 => /usr/lib/libkvm.so.1 libdl.so.1 => /usr/lib/libdl.so.1 libintl.so.1 => /usr/lib/libintl.so.1 libelf.so.1 => /usr/lib/libelf.so.1 libXext.so.0 => /usr/openwin/lib/libXext.so.0 libw.so.1 => /usr/lib/libw.so.1 See /usr/dt/lib/libXm.so.3 in that mess above? If they're using Motif, they can't also be using Tk! And I saw nothing in my casual inspection of all those /usr/snadm/lib shared libraries to suspect that TCL is linked in either. So where exactly is this supposed TCL/Tk? Certainly not in Solaris 2.4 or 2.5! ---Jake