From: UnixOS2 Archive To: "UnixOS2 Archive" Date: Mon, 9 Dec 2002 04:43:08 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [UnixOS2_Archive] No. 393 ************************************************** Sunday 08 December 2002 Number 393 ************************************************** Subjects for today 1 Re: New NCURSES : Jun Sawataishi 2 Re: New NCURSES : IanM" 3 Zope update : Ted Sikora 4 Zope update : Ted Sikora 5 Re: GCI Errors : Andrew MacIntyre 6 Patch for Perl 5.8.0 - 'has_chown' : Lyn St George" 7 Re: Ncurses build error : John Poltorak 8 More Zope streamlining. : Ted Sikora 9 Re: More Zope streamlining. : Ted Sikora 10 Re: Patch for Perl 5.8.0 - 'has_chown' : John Poltorak 11 Re: Patch for Perl 5.8.0 - 'has_chown' : John Poltorak 12 Re: _hash000030 : Steve Wendt 13 _hash000030 : Ted Sikora 14 Re: Ncurses UnixOS/2 package : John Poltorak 15 TIN : John Poltorak 16 Re: TIN : John Poltorak 17 Re: Ncurses UnixOS/2 package : John Poltorak 18 Building Autoconf from original source : John Poltorak 19 Re: Patch for Perl 5.8.0 - 'has_chown' : Stefan Neis 20 Re: Ncurses UnixOS/2 package : Stefan Neis 21 Re: TIN : Stefan Neis 22 Re: Ncurses UnixOS/2 package : Stefan Neis **= Email 1 ==========================** Date: Mon, 09 Dec 2002 00:03:52 +0900 From: Jun Sawataishi Subject: Re: New NCURSES At Sun, 8 Dec 2002 14:39:26 +0000, John Poltorak wrote: > I've just discovered that NCURSES 5.3 has been released... Yesterday, I tested this way. > sh configure && make SHELL=sh All library files (FOO.a not libFOO.a), and executables were compliled out of the box. Good! # OS/2 is not a question, it's a solution. # SAWATAISHI Jun **= Email 2 ==========================** Date: Mon, 09 Dec 2002 01:54:15 +1100 (EDT) From: "IanM" Subject: Re: New NCURSES Hi John >I've just discovered that NCURSES 5.3 has been released... >It's available from:- >ftp://ftp.gnu.org/pub/gnu/ncurses/ncurses-5.3.tar.gz And ..... ftp://hobbes.nmsu.edu/pub/incoming http://www.os2site.com/sw/new http://unixos2.com/pub/incoming With much thanks to Patrick Ash Cheers IanM http://www.os2site.com/ Those who are without sine shall be transformed... **= Email 3 ==========================** Date: Mon, 09 Dec 2002 02:38:30 -0500 From: Ted Sikora Subject: Zope update I updated the Zope bin and made a ZopeFolder.zip for those that already got the bin. Just unzip into \apps. It includes The Zope Book on how to use it. Run the zopefold.cmd and it puts a cool folder and 'Start Zope' icon on your desktop. It has links for all the Python and misc readmes too. ftp://os2ports.com/pub/os2/unix/internet/Zope/ZopeFolder.zip -- Ted Sikora tsikora at ntplx.net **= Email 4 ==========================** Date: Mon, 09 Dec 2002 02:38:30 -0500 From: Ted Sikora Subject: Zope update I updated the Zope bin and made a ZopeFolder.zip for those that already got the bin. Just unzip into \apps. It includes The Zope Book on how to use it. Run the zopefold.cmd and it puts a cool folder and 'Start Zope' icon on your desktop. It has links for all the Python and misc readmes too. ftp://os2ports.com/pub/os2/unix/internet/Zope/ZopeFolder.zip -- Ted Sikora tsikora at ntplx.net **= Email 5 ==========================** Date: Mon, 9 Dec 2002 07:53:08 +1000 (est) From: Andrew MacIntyre Subject: Re: GCI Errors On Sun, 8 Dec 2002, Ted Sikora wrote: > No Python uses the env command first the scripts use: > > #!/usr/bin/env python /usr/bin/env is supposed to be a more "portable" way of finding python on a wider array of Unix systems - python not being a standard part of any Unix install, it has been installed by local admins in a variety of places (/usr/local, /usr, /opt amongst others). Most systems #! hack effectively requires a full path to the executable to work - /usr/bin is "fairly" standard for env. I've tended on just invoke python directly for Unix python scripts. -- Andrew I MacIntyre "These thoughts are mine alone..." E-mail: andymac at bullseye.apana.org.au | Snail: PO Box 370 andymac at pcug.org.au | Belconnen ACT 2616 Web: http://www.andymac.org/ | Australia **= Email 6 ==========================** Date: Mon, 09 Dec 2002 12:21:10 +0000 From: "Lyn St George" Subject: Patch for Perl 5.8.0 - 'has_chown' Hi all While thinking about how to implement 'has_chown' in perl, I found that the win32/ sources in Perl already had this done, so I simply poached a few lines from there. Perl built OK, and Interchange built fine and runs without problems. I sent the patch off to the perl5-porters and got this reply CC'ed back from Ilya Zakharevich: > > > > Attached is a tiny patch for perl 5.8.0. The end purpose is to make > > it simpler to port and run perl apps such as Interchange, from > > http://www.icdevgroup.org. The patch has been tested with this > > and no problems are noticed or forseen. > > > > Please fold this into the main source for the next release if > > you are happy with it. > > Can I get your OK? How backward/forfard compatible is this? Does > it need (OS) version checks? > > --- perl-5.8.0.orig/os2/os2.c Wed Jun 26 17:30:34 2002 > +++ perl-5.8.0/os2/os2.c Sun Oct 13 15:05:56 2002 > at at -29,16 +29,22 at at > #include "EXTERN.h" > #include "perl.h" > > +int > +chown(const char *path, uid_t owner, gid_t group) > +{ > + return 0; /* noop */ > +} > + > #ifdef USE_5005THREADS [also, added into os2ish.h: #define HAS_CHOWN /* fake */ extern int chown(const char *p, uid_t o, gid_t g);] This is not without consequences... There *is* a concept of ownership in the OS/2 filesystems; as shipped, it is not enabled in the retail versions (do not know what happens in the server version). So the problem with this approach is that a script which is a glorified wrapper for chown() will succeed with this patch, while not doing what it promises. Do not know, need to think about this more. I Cc this to the EMX list, maybe people there have more idea. So: currently Perl on OS/2 supports only one user (with Unix API), one from LOGNAME; so in the above call to chown() we may assume that uid_t is for $LOGNAME, and gid_t is 0. Given we know the name of the user, can one cook a function to switch the ownership (on HPFS386? on JFS?) to the given user? Ilya ===================END FORWARDED MESSAGE=================== There is a binary + patch as ftp://ftp.zolotek.net/os2/perl-5.8.0_os2_ic2.zip Does anyone here have any thoughts on this? - Cheers Lyn St George +--------------------------------------------------------------------------------- + http://www.zolotek.net .. eCommerce hosting, consulting + http://www.os2docs.org .. some 'How To' stuff ... +---------------------------------------------------------------------------------- **= Email 7 ==========================** Date: Mon, 9 Dec 2002 16:49:10 +0000 From: John Poltorak Subject: Re: Ncurses build error On Sat, Dec 07, 2002 at 07:44:19PM -0500, Thomas Dickey wrote: > On Sat, Dec 07, 2002 at 10:49:25PM +0000, John Poltorak wrote: > When I last built on OS/2, I generated the configure script using autoconf > 2.13 + patches; Having just looked through README.emx, I see you are using different patches to the ones used for NCURSES v5.2. Now, after changing my setup to use the newer patches the build appears to go through without a hitch, and fits into my build system quite nicely so that I only need to run:- build ncurses and it seems to build without any errors. I guess I should check my output against the build provided by Pat Ash. > -- > Thomas E. Dickey > http://invisible-island.net > ftp://invisible-island.net -- John **= Email 8 ==========================** Date: Mon, 09 Dec 2002 18:20:44 -0500 From: Ted Sikora Subject: More Zope streamlining. Another new ZopeFolder.zip ftp://os2ports.com/pub/os2/unix/internet/Zope/ZopeFolder-021209.zip Final I hope it includes complete Zope and Python Desktop folders. 'Create Initial User' in the Zope folder and in Python Interactive and Script+Arguments. I wanted to add the Python Documentation Reference but it's huge the bin now stands at a little over 13MB but it is complete. Unzip in \apps like before and run zopefold.cmd. A Warpin package is ready too. The folders are a little sparse but it works! Just install and run. Thanks to Jeff(Robinson) for the wis build scripts. Maybe you should consider it a Beta. The compiled python files are removed and recompiled on installation saving much space. It's a little over 7MB. The bin includes The Zope Book and the final desktop objects otherwise their identical. ftp://os2ports.com/pub/os2/unix/internet/Zope/Zope_2_6_0.wpi -- Ted Sikora tsikora at ntplx.net **= Email 9 ==========================** Date: Mon, 09 Dec 2002 19:03:43 -0500 From: Ted Sikora Subject: Re: More Zope streamlining. Ted Sikora wrote: > > Another new ZopeFolder.zip > ftp://os2ports.com/pub/os2/unix/internet/Zope/ZopeFolder-021209.zip > > Final I hope it includes complete Zope and Python Desktop folders. > 'Create Initial User' in the Zope folder and in Python Interactive and > Script+Arguments. I wanted to add the Python Documentation Reference but > it's huge the bin now stands at a little over 13MB but it is complete. I made the Python 2.2.2 Reference an addon. It's the complete programming and reference guide. Just unzip in /Apps and run bookfold.cmd It adds a nifty icon to your Python Folder. ftp://os2ports.com/pub/os2/unix/internet/Zope/Python222-docs-addon.zip -- Ted Sikora tsikora at ntplx.net **= Email 10 ==========================** Date: Mon, 9 Dec 2002 20:06:30 +0000 From: John Poltorak Subject: Re: Patch for Perl 5.8.0 - 'has_chown' On Mon, Dec 09, 2002 at 12:21:10PM +0000, Lyn St George wrote: > Hi all > > While thinking about how to implement 'has_chown' in perl, I found that > the win32/ sources in Perl already had this done, so I simply poached > a few lines from there. Perl built OK, and Interchange built fine and runs > without problems. I sent the patch off to the perl5-porters and got this > reply CC'ed back from Ilya Zakharevich: > > > This is not without consequences... There *is* a concept of ownership > in the OS/2 filesystems; as shipped, it is not enabled in the retail > versions (do not know what happens in the server version). ????? Can anyone verify this? Is he alluding to SES? > So the problem with this approach is that a script which is a > glorified wrapper for chown() will succeed with this patch, while not > doing what it promises. > > Do not know, need to think about this more. I Cc this to the EMX > list, maybe people there have more idea. I don't remember seeing it on the EMX list... > So: currently Perl on OS/2 > supports only one user (with Unix API), one from LOGNAME; so in the > above call to chown() we may assume that uid_t is for $LOGNAME, and > gid_t is 0. Given we know the name of the user, can one cook a > function to switch the ownership (on HPFS386? on JFS?) to the given user? > > Ilya > ===================END FORWARDED MESSAGE=================== > > There is a binary + patch as ftp://ftp.zolotek.net/os2/perl-5.8.0_os2_ic2.zip > > Does anyone here have any thoughts on this? I'd like to know what Holger thinks about it.... > > > - > Cheers > Lyn St George > +--------------------------------------------------------------------------------- > + http://www.zolotek.net .. eCommerce hosting, consulting > + http://www.os2docs.org .. some 'How To' stuff ... > +---------------------------------------------------------------------------------- > -- John **= Email 11 ==========================** Date: Mon, 9 Dec 2002 20:08:56 +0000 From: John Poltorak Subject: Re: Patch for Perl 5.8.0 - 'has_chown' On Mon, Dec 09, 2002 at 12:21:10PM +0000, Lyn St George wrote: > Hi all > > While thinking about how to implement 'has_chown' in perl, I found that > the win32/ sources in Perl already had this done, so I simply poached > a few lines from there. Perl built OK, and Interchange built fine and runs > without problems. Would anyone other apps immediately benefit from this patch? > - > Cheers > Lyn St George > +--------------------------------------------------------------------------------- > + http://www.zolotek.net .. eCommerce hosting, consulting > + http://www.os2docs.org .. some 'How To' stuff ... > +---------------------------------------------------------------------------------- > -- John **= Email 12 ==========================** Date: Mon, 9 Dec 2002 20:20:15 -0800 (PST) From: Steve Wendt Subject: Re: _hash000030 On Mon, 9 Dec 2002, Ted Sikora wrote: > Off topic I know but my root directory is filling up with these files. Debug version of Netscape 4.61? Did you get one from Testcase? ;) **= Email 13 ==========================** Date: Mon, 09 Dec 2002 21:01:34 -0500 From: Ted Sikora Subject: _hash000030 Off topic I know but my root directory is filling up with these files. What are they? JFS files? My server was just not running right so I took Daniela's latest drivers off and put IBM1S506 back. I'm running the HPT366 controller. Anyone had this experience before? -- Ted Sikora tsikora at ntplx.net **= Email 14 ==========================** Date: Mon, 9 Dec 2002 21:16:03 +0000 From: John Poltorak Subject: Re: Ncurses UnixOS/2 package On Sun, Dec 08, 2002 at 11:20:11AM -0500, Thomas Dickey wrote: > On Sun, Dec 08, 2002 at 10:58:41AM +0000, John Poltorak wrote: > > > > I'd like to put together a UnixOS/2 package for ncurses, but am unsure of > > the directory structure it should contain. > > > > Should $PREFIX be /usr or /usr/local? SlackWare seems to use /usr. > > the former. /usr/local should be used if there's more than one curses > implementation. OK, I propose to put together a UnixOS/2 NCURSES packages with prefix set to $UNIXROOT/usr... Hope everyone is agreeable to that. Incidentally is there any way to set the prefix on the configure ommand line to override the CONFIG_SITE setting? > > Where should includes go? I would prefer them under /usr/include, although > > SlackWare uses /usr/include/ncurses. > > the former if ncurses is the "real" curses implementation I would like ncurses to be the preferred curses implementation on UnixOS/2, which I suppose involves replacing the curses.h and termcap.h which are included with EMX... Am I right in thinking that all the needs to be done is to replace the single line:- ? #include with:- #include Are there any unforeseen implications of doing this? > -- > Thomas E. Dickey > http://invisible-island.net > ftp://invisible-island.net -- John **= Email 15 ==========================** Date: Mon, 9 Dec 2002 21:25:17 +0000 From: John Poltorak Subject: TIN Where is the latest version of TIN? Anyone know if it will build on OS/2? -- John **= Email 16 ==========================** Date: Mon, 9 Dec 2002 22:09:08 +0000 From: John Poltorak Subject: Re: TIN On Mon, Dec 09, 2002 at 10:59:11PM +0100, Stefan Neis wrote: > On Mon, 9 Dec 2002, John Poltorak wrote: > > > Where is the latest version of TIN? > > www.tin.org So, obvious really :-)... > > TIN 1.4.6 (stable) was released on August 16th, 2002 > > TIN 1.5.15 (unstable beta) was released on November 15th, 2002 Yes, I found them. > No idea about its usability on OS/2, though. The build of 1.5.15 seemed to go OK and then it suddenly ran FTP.EXE for some reason - no idea why... Maybe I should read some docs... > Regards, > Stefan > -- > Micro$oft is not an answer. It is a question. The answer is 'no'. > -- John **= Email 17 ==========================** Date: Mon, 9 Dec 2002 22:17:38 +0000 From: John Poltorak Subject: Re: Ncurses UnixOS/2 package On Mon, Dec 09, 2002 at 10:56:32PM +0100, Stefan Neis wrote: > On Mon, 9 Dec 2002, John Poltorak wrote: > > > OK, I propose to put together a UnixOS/2 NCURSES packages with prefix set > > to $UNIXROOT/usr... Hope everyone is agreeable to that. > > Sorry, but you just can't have environment variables in the prefix, it > technically just does not work. No, meant building it using 'configure --prefix=$UNIXROOT/usr' ... I realise the variable is resolved during building. > If you try to, it either just won't compile to a usable result or it might > resolve $UNIXROOT to the value of UNIXROOT _on_your_local_box_, thus > compiling your settings in... > > At most you could modify the code to look up $UNIXROOT and runtime and > dynamically modify the absolute paths whereever they are used... > > (Which essentially Holger's famous libc replacement would automatically > do on the fly, once it exists). Once Holger's LIBEMU is available I can rebuild with just a prefix of /usr but until it gives us something to be going on with. > > #include > > Actually, with ncurses being installed as the default curses library > (i.e. in /usr/include/curses.h, right?), that probably should just be > #include Wouldn't this be recursive? > > Regards, > Stefan > -- > Micro$oft is not an answer. It is a question. The answer is 'no'. > -- John **= Email 18 ==========================** Date: Mon, 9 Dec 2002 22:43:01 +0000 From: John Poltorak Subject: Building Autoconf from original source In the docs for building Autoconf (2.53b), it says:- a) * Developers only - All other people should really skip section II.a) * To recreate the configuration files enter: export EMXSHELL=ksh aclocal -I config automake autoconf Which autoconf does this refer to? Or should I install this version first and then run the commands above? Has anyone managed to get this working? I'm having problems trying to build autoconf from the original source, although It has worked in the past. Since I change almost all my Unix environment fairly frequently, it's difficult to pinpoint why it doesn't work now. -- John **= Email 19 ==========================** Date: Mon, 9 Dec 2002 22:48:07 +0100 (CET) From: Stefan Neis Subject: Re: Patch for Perl 5.8.0 - 'has_chown' On Mon, 9 Dec 2002, John Poltorak wrote: > > This is not without consequences... There *is* a concept of ownership > > in the OS/2 filesystems; as shipped, it is not enabled in the retail > > versions (do not know what happens in the server version). > > ????? > > Can anyone verify this? Is he alluding to SES? More likely to HPFS386 and drives mounted from a server/peer. Also, when you're giving permission to access some files via network, some access control lists are created which again might result in ownership taking a meaning. > > list, maybe people there have more idea. > > I don't remember seeing it on the EMX list... I vaguely remember having seen posts about that subject several times in the past (all with no real conclusion, IIRC), but not recently.. > > gid_t is 0. Given we know the name of the user, can one cook a > > function to switch the ownership (on HPFS386? on JFS?) to the given > > user? Thats probably the key problem. No problems on HPFS or FAT (normally), but other file systems do exist and are normally supported as well... Regards, Stefan **= Email 20 ==========================** Date: Mon, 9 Dec 2002 22:56:32 +0100 (CET) From: Stefan Neis Subject: Re: Ncurses UnixOS/2 package On Mon, 9 Dec 2002, John Poltorak wrote: > OK, I propose to put together a UnixOS/2 NCURSES packages with prefix set > to $UNIXROOT/usr... Hope everyone is agreeable to that. Sorry, but you just can't have environment variables in the prefix, it technically just does not work. If you try to, it either just won't compile to a usable result or it might resolve $UNIXROOT to the value of UNIXROOT _on_your_local_box_, thus compiling your settings in... At most you could modify the code to look up $UNIXROOT and runtime and dynamically modify the absolute paths whereever they are used... (Which essentially Holger's famous libc replacement would automatically do on the fly, once it exists). > #include Actually, with ncurses being installed as the default curses library (i.e. in /usr/include/curses.h, right?), that probably should just be #include Regards, Stefan -- Micro$oft is not an answer. It is a question. The answer is 'no'. **= Email 21 ==========================** Date: Mon, 9 Dec 2002 22:59:11 +0100 (CET) From: Stefan Neis Subject: Re: TIN On Mon, 9 Dec 2002, John Poltorak wrote: > Where is the latest version of TIN? www.tin.org > TIN 1.4.6 (stable) was released on August 16th, 2002 > TIN 1.5.15 (unstable beta) was released on November 15th, 2002 No idea about its usability on OS/2, though. Regards, Stefan -- Micro$oft is not an answer. It is a question. The answer is 'no'. **= Email 22 ==========================** Date: Mon, 9 Dec 2002 23:36:49 +0100 (CET) From: Stefan Neis Subject: Re: Ncurses UnixOS/2 package On Mon, 9 Dec 2002, John Poltorak wrote: > No, meant building it using 'configure --prefix=$UNIXROOT/usr' ... > > I realise the variable is resolved during building. Ah, OK, I started wondering ... ;-) Anyway, $UNIXROOT/usr sounds like the resulting binary will work on systems with the same setting for UNIXROOT as yours whereas --prefix=/usr works at least on one drive of every system (non of the two veriants would sufficient over here, unfortunately). Sounds like UnixOS/2 is not (yet) ideal for distributing precompiled binaries. :-( > > Actually, with ncurses being installed as the default curses library > > (i.e. in /usr/include/curses.h, right?), that probably should just be > > #include > > > Wouldn't this be recursive? Sorry? Oh, I think I misunderstood what you were saying ... Just ignore, what I wrote ... Regards, Stefan -- Micro$oft is not an answer. It is a question. The answer is 'no'.