From: UnixOS2 Archive To: "UnixOS2 Archive" Date: Thu, 6 Mar 2003 05:00:07 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [UnixOS2_Archive] No. 64 ************************************************** Wednesday 05 March 2003 Number 64 ************************************************** Subjects for today 1 Posix/2 update ? : John Poltorak 2 Re: Libtool Status : Stefan Neis 3 Re: ISOFS : Sebastian Wittmeier (ShadoW)" 4 Re: SpamAssassin : Steve Wendt 5 Re: SpamAssassin : Steve Wendt 6 exec family : Dave Saville" 7 Re: exec family : John Poltorak 8 OS/2 TERMCAP from NCURSES : John Poltorak 9 Re: SpamAssassin : Lewis G Rosenthal 10 Re: OS/2 TERMCAP from NCURSES : Thomas Dickey 11 Re: exec family : Dave Saville" **= Email 1 ==========================** Date: Thu, 6 Mar 2003 09:48:40 +0000 From: John Poltorak Subject: Posix/2 update ? I'm aware of the recent release of set of Posix/2 headers and libs, but I was wondering if it might be time for an update of the full Posix/2 package... It's over two years since P2-Alpha3 was uploaded to Hobbes. Personally, I would much rather download a snapshot archive than retrieving files using CVS... I tried sending this to the Posix/2 list but something has changed so that I mail from my server doesn't get through now... -- John **= Email 2 ==========================** Date: Thu, 6 Mar 2003 11:13:05 +0100 (CET) From: Stefan Neis Subject: Re: Libtool Status On Wed, 5 Mar 2003, Andreas Buening wrote: > Solaris supports LD_LIBRARY_PATH unlike other Unixes. Sorry? Which Unixes don't? I know for sure that at least Solaris, HP/UX, Linux and all BSD derivates do support LD_LIBRARY_PATH (though for MacOS X it has a slightly different name, IIRC it's DY_LIBRARY_PATH or something similar) > The library paths > can be hardcoded (though I've never understood the rpath thing) or > you need some weird flags to create a shared library. Sorry, but the hardcoded library paths have _nothing_ to do with library creation. When you're compiling an application you can be using a hard coded location for the libraries on your system via rpath but that needs some additional (mysterious) flags and is complete nonsense anyway (it makes the whole thing unusable on anything but your own box and has no visible benefit). The default behaviour is just fine. > Imagine you link > ~/src/foo-1.2/src/footest with the absolute path of > ~/src/foo-1.2/lib/libfoo.so.1.2.0 in your build directory. Then you > improve your dllar for each platform and finally you end up with > a libtool clone. ;-) I don't think so ... But I admit that supporting anything but gcc which nicely maps "-shared" to whatever flags the native linker requires complicates things _very_ much. That's something I keep forgetting about all the time ... Regards, Stefan -- Micro$oft is not an answer. It is a question. The answer is 'no'. **= Email 3 ==========================** Date: Thu, 06 Mar 2003 12:01:41 +0100 (CET) From: "Sebastian Wittmeier (ShadoW)" Subject: Re: ISOFS On Tue, 4 Mar 2003 17:02:18 +0000, John Poltorak wrote: >It is something I've been looking for for a while, but it won't work for >me. I have tried it on various systems, but it traps on boot while loading >STUBFSD.IFS. IIRC that STUBFSD.IFS is the same as the one included in AEFS (a crypto file system). It redirects all file system calls to a Ring 3 app. Perhaps you have better luck with the original driver. At least it would help to find what's wrong. ftp://ftp.univie.ac.at/systems/os2/leo/drivers/ifs/aefs02.zip Sebastian **= Email 4 ==========================** Date: Thu, 6 Mar 2003 14:56:10 -0800 From: Steve Wendt Subject: Re: SpamAssassin On Fri, 28 Feb 2003, John Poltorak wrote: > Anyone heard of SpamAssassin? > It appears to be written in Perl, so I guess it ought to run on OS/2... > Anyone tried running it? Version 2.5 works great on Linux - dunno about running it on OS/2. **= Email 5 ==========================** Date: Thu, 6 Mar 2003 15:47:34 -0800 (PST) From: Steve Wendt Subject: Re: SpamAssassin On Thu, 6 Mar 2003, Steve Wendt wrote: > > Anyone heard of SpamAssassin? > > It appears to be written in Perl, so I guess it ought to run on OS/2... > > Anyone tried running it? > > Version 2.5 works great on Linux - dunno about running it on OS/2. Hmm... I didn't send this today - why's it showing up again? **= Email 6 ==========================** Date: Thu, 06 Mar 2003 18:24:48 +0000 (GMT) From: "Dave Saville" Subject: exec family Can anyone point me to some docs that explain all the exec calls? All I can find just list the params and don't say what the differences between them are. int execl (const char *name, const char *arg0, ...); int execle (const char *name, const char *arg0, ...); int execlp (const char *name, const char *arg0, ...); int execlpe (const char *name, const char *arg0, ...); int execv (const char *name, char * const argv[]); int execve (const char *name, char * const argv[], char * const envp[]); int execvp (const char *name, char * const argv[]); int execvpe(const char *name, char * const argv[], char * const envp[]); I know that execl* is for fixed number of args, execv* for variable and *e passes an environment. But what is the difference between execv & execp - the parameter list are the same? TIA -- Regards Dave Saville **= Email 7 ==========================** Date: Thu, 6 Mar 2003 18:45:57 +0000 From: John Poltorak Subject: Re: exec family On Thu, Mar 06, 2003 at 06:24:48PM +0000, Dave Saville wrote: > Can anyone point me to some docs that explain all the exec calls? All > I can find just list the params and don't say what the differences > between them are. There is some explanation in emxlib.doc which is included in emxdev1.zip although it isn't extracted when you install UX2BS. > -- > Regards > > Dave Saville > -- John **= Email 8 ==========================** Date: Thu, 6 Mar 2003 18:51:43 +0000 From: John Poltorak Subject: OS/2 TERMCAP from NCURSES Is is possible to generate a TERMCAP file suitable for OS/2 from the NCURSES archive? -- John **= Email 9 ==========================** Date: Thu, 06 Mar 2003 19:27:40 -0500 From: Lewis G Rosenthal Subject: Re: SpamAssassin Yuri, I've been working to try to get SA running with assassind. However, I'm interested in looking at bogofilter. Could you give a little more detail as to how the porting went? Better yet, could you send me the binaries? :-) Yuri Dario wrote: >Hi, > > > >>It appears to be written in Perl, so I guess it ought to run on OS/2... >>Anyone tried running it? >> >> > >I got it running under my build of perl5.8, was not working with previous perl releases. But I got it >working only in standalone mode, e.g. getting email on stdin and output on stdout with headers >changed. The daemon mode is not working, because of errors in socket communications (I think >it is using ascii sockets instead of binary ones). > >So I moved to bogofilter (that is written in C). > > >Bye, > > Yuri Dario > >/* > * member of TeamOS/2 - Italy > * http://www.quasarbbs.net/yuri > * http://www.teamos2.it > * http://www.opera.com/os2/ > */ > > > > > -- Lewis --------------------------------------------------------------------- Lewis G Rosenthal, CNA Rosenthal & Rosenthal : Accountants / Network Consultants New York / Northern Virginia : www.2rosenthals.com Novell Users International : www.whytheylie.com OS/2's new face is eComStation : www.ecomstation.com --------------------------------------------------------------------- This OS/2 system (Apollo) uptime is 0 days 02:24 hours and 29 seconds **= Email 10 ==========================** Date: Thu, 6 Mar 2003 20:09:02 -0500 From: Thomas Dickey Subject: Re: OS/2 TERMCAP from NCURSES On Thu, Mar 06, 2003 at 06:51:43PM +0000, John Poltorak wrote: > > Is is possible to generate a TERMCAP file suitable for OS/2 from the > NCURSES archive? something like infotocap -Cr emx.src >termcap -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net **= Email 11 ==========================** Date: Thu, 06 Mar 2003 22:38:45 +0000 (GMT) From: "Dave Saville" Subject: Re: exec family On Thu, 6 Mar 2003 18:45:57 +0000, John Poltorak wrote: >On Thu, Mar 06, 2003 at 06:24:48PM +0000, Dave Saville wrote: >> Can anyone point me to some docs that explain all the exec calls? All >> I can find just list the params and don't say what the differences >> between them are. > >There is some explanation in emxlib.doc which is included in emxdev1.zip >although it isn't extracted when you install UX2BS. I have that - it just outlines the call lists. -- Regards Dave Saville