From: UnixOS2 Archive To: "UnixOS2 Archive" Date: Sun, 16 Feb 2003 04:53:30 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [UnixOS2_Archive] No. 46 ************************************************** Saturday 15 February 2003 Number 46 ************************************************** Subjects for today 1 man pages on non-Linux systems : John Poltorak 2 Re: Python's libraries : John Poltorak 3 Re: man pages on non-Linux systems : Stefan Neis 4 Re: Portscanner : Maynard" 5 Re: [Mailman-os2] Mailman 2.1.1 update : John Poltorak 6 Re: Portscanner : John Poltorak 7 Re: Python's libraries : Andrew MacIntyre 8 Re: EXPAT : Andrew MacIntyre **= Email 1 ==========================** Date: Sun, 16 Feb 2003 12:06:58 +0000 From: John Poltorak Subject: man pages on non-Linux systems If anyone has access to a non-Linux Unix system, can you determine the source of the MAN program? I'm not sure if the definitive version is here:- ftp://ftp.win.tue.nl/pub/linux-local/utils/man Having a directory such as 'linux-local' makes me a little suspicious about proper Unix conformity... -- John **= Email 2 ==========================** Date: Sun, 16 Feb 2003 12:52:10 +0000 From: John Poltorak Subject: Re: Python's libraries On Sun, Feb 16, 2003 at 09:45:45PM +1000, Andrew MacIntyre wrote: > On Sat, 15 Feb 2003, John Poltorak wrote: > > > Python seems to use quite a few libraries including Berkeley DB, Readline, > > zlib, gnuufc, gdbm etc. > > > > Is there a list of versions of the libraries used? Some of them seem old, > > and I wondered if the would be any problems introduced by bringing them > > uptodate? > > For the binary installation package I release, I identify all the versions > used. At the moment, all external libraries are statically linked in this > distribution, because the extensions themselves are DLLs, and it saves > people from DLL version dependency headaches. > > I am attempting to make sure that Python 2.3 will be released with a > recent build of BSDDB (4.0.14 at least; possibly 4.1.25 which I think is > the current Sleepycat release). Unfortunately, this will introduce DB > file format incompatibility, so there is extra work needed. > > I'm using an old version of Readline (2.1?) - I want to update this. I > have a copy of IlyaZ's port of Readline 4.1, but haven't experimented with > this - a quick look suggests I'm going to have to look closely at linkage. I've attempted to build v4.3 straight from source using my build system and did manage to create a 'libreadline.a' and 'libhistory.a' although there were a couple of errors in the build, but I'm not sure how significant they were. Besises that, I don't know the first thing about the app itself and wouldn't know how to test the libs... > Zlib is 1.1.4. > > The gdbm (1.7.3), gnuufc (aka crypt, 2.0.4) and gnump (aka mpz, 2.0.2) > were the latest I could find at the time. If you know of later ports, > please let me know. The latest source is available from:- http://www.swox.com But I have come across a port by Henry Sobotka which is fairly recent, and he said he managed to build it straight out of the box, although I didn't manage it myself with the latest version... > If you build Python yourself, you can try later versions if you have > them. In general, Python's external library extensions are maintained to > be compatible with the current upstream sources. > > Unfortunately, I've found that to maximise interoperability of various > modules within a Python script, I have to (re-)build the ports with > consistent build specifications. > > With UX2, as you are working towards an integrated distribution, this > should be less painful. What I'm trying to do with the UnixOS/2 Build System is start from a very old minimal 'baseline' set of tools and build everything up from there. It is starting to take reasonable shape and a fully integrated system is the hoped for outcome. Also, with it being fully automated, then any errors should be easily reproducible by anyone else because a standard, known build environment is being used. There is a ux2bs mailing list for anyone intersted in trying out this system. Details are availble here:- http://powerusersbbs.net/mailman/listinfo/ux2bs You are very welcome to join. > -- > 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 > -- John **= Email 3 ==========================** Date: Sun, 16 Feb 2003 13:33:52 +0100 (CET) From: Stefan Neis Subject: Re: man pages on non-Linux systems On Sun, 16 Feb 2003, John Poltorak wrote: > If anyone has access to a non-Linux Unix system, can you determine the > source of the MAN program? Typically included in the OS distribution, which probably implies that the freely available flavors are those from *BSD and Linux (with the Linux version most likely based on an BSD implementation). Regards, Stefan **= Email 4 ==========================** Date: Sun, 16 Feb 2003 13:53:47 -0600 (CST) From: "Maynard" Subject: Re: Portscanner John, >What portscanner would anyone recommend for use on OS/2? I've been using TCP/IP Portscanner - Version 1.8 (c) Copyright Ralf Christen 1997,1998 while anticipating nmap -- Maynard **= Email 5 ==========================** Date: Sun, 16 Feb 2003 15:25:37 +0000 From: John Poltorak Subject: Re: [Mailman-os2] Mailman 2.1.1 update On Sat, Feb 15, 2003 at 12:20:04PM -0500, Ted Sikora wrote: > language.Oh yeah you need to add mailman to group/passwd. I used: > > passwd = mailman;*;28;28;Mailman;D:/Apps/mailman;D:/bin/sh > grp = mailman;;28; If a PASSWD file is required then I suggest it uses the format proposed by Nicholas Sheppard in his PINE port. We should try and conform to a standard format and use standard passwd access routines rather than them being specific to Python. I don't know if this would need source code changes to Python ... > -- > Ted Sikora > tsikora at ntplx.net -- John **= Email 6 ==========================** Date: Sun, 16 Feb 2003 20:32:33 +0000 From: John Poltorak Subject: Re: Portscanner On Sun, Feb 16, 2003 at 01:53:47PM -0600, Maynard wrote: > John, > > >What portscanner would anyone recommend for use on OS/2? > > I've been using > TCP/IP Portscanner - Version 1.8 > (c) Copyright Ralf Christen 1997,1998 > > while anticipating nmap There is one on Netlabs... It's just a command line program at the moment. I tried it fairly recently but couldn't get anywhere with it though... > -- Maynard -- John **= Email 7 ==========================** Date: Sun, 16 Feb 2003 21:45:45 +1000 (est) From: Andrew MacIntyre Subject: Re: Python's libraries On Sat, 15 Feb 2003, John Poltorak wrote: > Python seems to use quite a few libraries including Berkeley DB, Readline, > zlib, gnuufc, gdbm etc. > > Is there a list of versions of the libraries used? Some of them seem old, > and I wondered if the would be any problems introduced by bringing them > uptodate? For the binary installation package I release, I identify all the versions used. At the moment, all external libraries are statically linked in this distribution, because the extensions themselves are DLLs, and it saves people from DLL version dependency headaches. I am attempting to make sure that Python 2.3 will be released with a recent build of BSDDB (4.0.14 at least; possibly 4.1.25 which I think is the current Sleepycat release). Unfortunately, this will introduce DB file format incompatibility, so there is extra work needed. I'm using an old version of Readline (2.1?) - I want to update this. I have a copy of IlyaZ's port of Readline 4.1, but haven't experimented with this - a quick look suggests I'm going to have to look closely at linkage. Zlib is 1.1.4. The gdbm (1.7.3), gnuufc (aka crypt, 2.0.4) and gnump (aka mpz, 2.0.2) were the latest I could find at the time. If you know of later ports, please let me know. If you build Python yourself, you can try later versions if you have them. In general, Python's external library extensions are maintained to be compatible with the current upstream sources. Unfortunately, I've found that to maximise interoperability of various modules within a Python script, I have to (re-)build the ports with consistent build specifications. With UX2, as you are working towards an integrated distribution, this should be less painful. -- 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 8 ==========================** Date: Sun, 16 Feb 2003 21:53:32 +1000 (est) From: Andrew MacIntyre Subject: Re: EXPAT On Sat, 15 Feb 2003, John Poltorak wrote: > EXPAT is another library used in Python, and doubtless other places. > > I just found out that it is now a SourceForge project... > > You can download the latest version (v1.95.6) from: > > > http://prdownloads.sourceforge.net/expat/expat-1.95.6.tar.gz > > > I have no idea how easily it builds on OS/2, but I'll give it a try. It shouldn't be hard. The source patches for Expat 1.2 I've been distributing with the Python 2.2.2 source patches may be useful. Expat is being distributed with Python from v2.3, and Python's expat module will be built from the source included in the Python distribution. Python's expat module doesn't include all the Expat options though. If you build Expat yourself, Python's expat module should link against your library. -- 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