Date: Sun, 23 May 2004 00:07:31 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [Ux2bs_Archive] No. 330 ************************************************** Saturday 22 May 2004 Number 330 ************************************************** Subjects for today 1 Re: rsync and 213.152.37.92 : Anton Monroe 2 Re: Re: Plans for UX2BS/UnixOS2... : DWParsons at t-online.de (Dave Parsons) 3 Re: rsync and 213.152.37.92 : John Poltorak 4 Re: rsync and 213.152.37.92 : John Poltorak 5 Need help building MAN : John Poltorak 6 Re: Two build branches : Lyn St George" 7 Re: Need help building MAN : Dave Yeo" 8 Re: Need help building MAN : John Poltorak 9 Re: Two build branches : T.Sikora" **= Email 1 ==========================** Date: Fri, 21 May 2004 09:33:33 -0500 From: Anton Monroe Subject: Re: rsync and 213.152.37.92 On Fri, May 21, 2004 at 12:57:21PM +0100, John Poltorak wrote: > > easier that way because the rsync for OS/2 is crippled. > > It would be nice to *un*-cripple it... I've tried building more recent > versions but never got anywhere. I guess some source code changes are > required but it would be nice to see if some of the patches can be removed > and eventually come up with a patch which could be submitted to the RSYNC > developers so that we could expect future versions to build on OS/2 > straight out of the box. Yes! I use rsync for copying backups between my two machines. It's rather a Rube Goldbergish setup-- my OS/2 batch file has to make the zip files, then ssh to the Linux machine and run a script there so the files get pulled from the receiving end. That's the only reason I have an rsync server on the OS/2 machine. > Have you ever tried getting logging to work on OS/2? Yes, and it works. All I log are connections and summaries. I don't tell the OS/2 daemon to log individual transfers. I assume it would work if I added 'transfer logging' to the rsyncd.conf. > The reason for that is that it is reasonable to assume that FTP will > already be installed on the user's system. A reasonable assumption. When I first tried ux2_bootstrap.cmd I couldn't get ftp to work. I got the impression that it doesn't work for some people for unknown reasons. (from reading the list archives? Or maybe from a comment in Ted's package?) I haven't tried ftp-ing lately. My fuzzy memory is that I did duplicate your directory structure and added a user called unixos2 to my ftp server, still couldn't get it to work, and went on to more important problems. > Once you start altering things manually, you are on a slippery slope to > chaos and will be unable to recreate the same environment at a future > time. The whole point of UX2BS is to have an automated system. Oh, I know. But Rodney asked. Also, sometimes manual changes have to be made. UX2BS simply won't work on my machine unless I change the DPATH statement. One nice thing about using rsync to make a local mirror is that I can make experimental changes on my local server and then run ux2_bootstrap.cmd again to see if it works. Any changes I have made are automatically wiped out the next time I rsync to your server, so there is no chance of getting confused by something I forgot to undo. Now that you've added the 'pause' at the end of ux2_bootstrap.cmd, it isn't as important. Anton _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs **= Email 2 ==========================** Date: Fri, 21 May 2004 15:49:31 +0200 (CES) From: DWParsons at t-online.de (Dave Parsons) Subject: Re: Re: Plans for UX2BS/UnixOS2... On Thu, 20 May 2004 18:46:29 +0100, Stefan.Neis at t-online.de wrote: > Hi, > Actually, one of the main problems is the amount of time any given > developper can spend on the project. Personally, I "waste" the time > I have currently available for wxWindows (and I have more and more the > feeling I'm really wasting my time on that PM port, as I'm unable to > even keep up with the changes to the other ports, much less improve the > currently admittedly quite poor quality of the port) and some minor testing I know what you mean. Is anyone else other than you and I either working on or using wxWidgets? BTW: I checked in another patch yesterday. Another SYS3175! Cheers, Dave _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs **= Email 3 ==========================** Date: Fri, 21 May 2004 16:55:05 +0100 From: John Poltorak Subject: Re: rsync and 213.152.37.92 On Fri, May 21, 2004 at 09:33:33AM -0500, Anton Monroe wrote: > On Fri, May 21, 2004 at 12:57:21PM +0100, John Poltorak wrote: > > > easier that way because the rsync for OS/2 is crippled. > > > > It would be nice to *un*-cripple it... I've tried building more recent > > versions but never got anywhere. I guess some source code changes are > > required but it would be nice to see if some of the patches can be removed > > and eventually come up with a patch which could be submitted to the RSYNC > > developers so that we could expect future versions to build on OS/2 > > straight out of the box. > > Yes! I use rsync for copying backups between my two machines. RSYNC is s brilliant program and I'm surprised it isn't more widely used by OS/2'ers. It would be great to get it updated, and maybe even make it handle EAs. > It's rather > a Rube Goldbergish setup-- my OS/2 batch file has to make the zip files, then > ssh to the Linux machine and run a script there so the files get pulled from > the receiving end. That's the only reason I have an rsync server on the OS/2 > machine. That seems a bit convoluted - although I can't really understand whatyou are doing. > > Have you ever tried getting logging to work on OS/2? > > Yes, and it works. All I log are connections and summaries. I don't > tell the OS/2 daemon to log individual transfers. I assume it would > work if I added 'transfer logging' to the rsyncd.conf. I'm glad you posted your rsynd.conf - I've just added logging now and it does work - I didn't know what options to use before. > > The reason for that is that it is reasonable to assume that FTP will > > already be installed on the user's system. > > A reasonable assumption. When I first tried ux2_bootstrap.cmd I > couldn't get ftp to work. I got the impression that it doesn't work for > some people for unknown reasons. (from reading the list archives? Or > maybe from a comment in Ted's package?) It's probably related to passive FTP. I don't know anything about that myself. > > Once you start altering things manually, you are on a slippery slope to > > chaos and will be unable to recreate the same environment at a future > > time. The whole point of UX2BS is to have an automated system. > > Oh, I know. But Rodney asked. Also, sometimes manual changes have to be > made. UX2BS simply won't work on my machine unless I change the DPATH > statement. Any local changes should be made via ux2_local.cmd. It's best to keep things as standardised as possible. > Anton -- John _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs **= Email 4 ==========================** Date: Fri, 21 May 2004 16:57:58 +0100 From: John Poltorak Subject: Re: rsync and 213.152.37.92 On Fri, May 21, 2004 at 10:25:29AM +0100, Rodney Pont wrote: > On Fri, 21 May 2004 09:12:45 +0100, John Poltorak wrote: > > >> I've gone back to this to try and reinstall but I don't get a response > >> from 213.152.37.92 anymore. > > > >Nothing at all? Can you ping it? > > No response to ping from the workstation but it does work from the > server. I do get a response to ping for other sites such as bbc.co.uk. If you can get a response from any machine at your end then it sounds as though my server is working and that the problem must be at your end. > Regards - Rodney Pont > E-mail by PMMail - listm4 at infohitsystems.ltd.uk > > really weird out of context words courtesy of PMMail's spellchecker -- John _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs **= Email 5 ==========================** Date: Fri, 21 May 2004 17:08:16 +0100 From: John Poltorak Subject: Need help building MAN I really need to get MAN built but don't seem to have made any progress with it for a while. There's some source available here:- ftp://ftp.win.tue.nl/pub/linux-local/utils/man/man-1.5g.tar.gz It has a non-standard configure which I can't get to run properly. -- John _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs **= Email 6 ==========================** Date: Sat, 22 May 2004 03:17:42 +0100 (BST) From: "Lyn St George" Subject: Re: Two build branches On Fri, 7 May 2004 20:09:38 +0100, John Poltorak wrote: >On Fri, May 07, 2004 at 07:03:34PM +0100, Lyn St George wrote: >> Hallo all >> >> I've just run Ted's branch of ux2bs again, and this time it worked perfectly. I >> guess that the previous problem was the lack of emx*.dll's on a new machine >> just as it was for John's branch. > >This problem has been corrected now. > >> There has been a huge amount of work gone into both branches, and rather >> than waste any of it I want to merge the two into one updated system. >> >> The basic philosophy will be that a package should be built from source >> whenever possible, and only stuff like EMX should be installed as binary >> packages. > >My aim is to start with a set of 'baseline' tools and as part of the >initial install to replace them with self-built versions, ie so that >\unixos2\bin can disappear as quickly as possible. > >> The system will also default to a \ux2 root so as to avoid any >> possibility of clobbering existing stuff in either \ or \unixos2, with the option >> of moving most of it to \ after testing so as to make a 'live' system. >> Apologies for the delay in following up on this. I've put together a draft of a possible merger of the two branches, which seems to work well enough here. It starts with building the toolkit from pre-ported binaries and then giving you the option of rebuilding it all from sources. You also have the option of building packages from either sources or ports. The installation finishes with building Apache 1.3.31 with mod_php, mod_interchange and mod_rexx, and setting up some local sites for it. Also builds Webmin, and installs Ghostview - all these have options to skip or exit. \ux2\builds\foo has scripts and the source archive in foo \ux2\ports\foo has scripts and the ported binary in foo \ux2\scripts has all build, port, remove, or depend scripts \ux2\system\base, emx, gcc has all system binaries. 'build perl' will build perl5.8.4 from source, build CPAN.pm for interactive installation of modules, and build a list of other useful modules. 'build port perl' will find a ported binary of perl off the port.table and unpack it. 'build remove perl' will deinstall perl 'build depend perl' will install any missing dependencies (this needs a lot of work to straighten out) Try it at ftp://ftp.zolotek.net/ux2/ux2_boot.cmd. Lyn St George _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs **= Email 7 ==========================** Date: Fri, 21 May 2004 23:06:31 -0800 From: "Dave Yeo" Subject: Re: Need help building MAN On Fri, 21 May 2004 17:08:16 +0100, John Poltorak wrote: > > >I really need to get MAN built but don't seem to have made any progress >with it for a while. > >There's some source available here:- > >ftp://ftp.win.tue.nl/pub/linux-local/utils/man/man-1.5g.tar.gz > >It has a non-standard configure which I can't get to run properly. > I managed to get configure to finish by doing it manually, sh configure -ask. Program names need to include the full path (no drive letter) and ..exe or .cmd at end. Had to use -Zexe to force an exe and then die here In file included from e:\emx\include\sys/stat.h:8, from man.c:28: e:\emx\include\sys/types.h:48: warning: empty declaration e:\emx\include\sys/types.h:58: warning: empty declaration In file included from man.c:28: e:\emx\include\sys/stat.h:23: parse error before `st_uid' e:\emx\include\sys/stat.h:23: warning: no semicolon at end of struct or union e:\emx\include\sys/stat.h:24: warning: type defaults to `int' in declaration of `st_gid' e:\emx\include\sys/stat.h:24: warning: data definition has no type or storage class e:\emx\include\sys/stat.h:32: parse error before `}' man.c: In function `is_section': man.c:171: warning: subscript has type `char' man.c:171: warning: subscript has type `char' man.c: In function `main': man.c:1099: `LC_MESSAGES' undeclared (first use in this function) man.c:1099: (Each undeclared identifier is reported only once man.c:1099: for each function it appears in.) make.exe: *** [man.o] Error 1 Interestingly tried with Innoteks GCC and got similar errors In file included from man.c:28: g:/usr.gcc322/include/sys/stat.h:145: parse error before "st_uid" g:/usr.gcc322/include/sys/stat.h:195: parse error before '}' token In file included from man.c:31: g:/usr.gcc322/include/unistd.h:184: parse error before '[' token g:/usr.gcc322/include/unistd.h:425: parse error before '[' token make[1]: *** [man.o] Error 1 make[1]: Leaving directory `X:/usr/src/man-1.5g/src' make: *** [source] Error 2 I got around this by removing the include sys/stat.h and the code that calls chmod using #ifndef __EMX__ etc and got the same problem with manfile.c. Its late here and I should goto bed. If you'd like I can try to continue tomorrow but I can't see it becoming a configure make make install type of solution, at least need patched C source. Drive letter support and OS/2 style manpaths need to be added too I'd imagine Didn't Jun Sawatasha have a patch for MAN? Here http://homepage1.nifty.com/jsawa/linux/man15g.zip which is definately a better port then I could do, even includes support for running in a xterm Dave _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs **= Email 8 ==========================** Date: Sat, 22 May 2004 11:42:46 +0100 From: John Poltorak Subject: Re: Need help building MAN On Fri, May 21, 2004 at 11:06:31PM -0800, Dave Yeo wrote: > On Fri, 21 May 2004 17:08:16 +0100, John Poltorak wrote: > > > > > > >I really need to get MAN built but don't seem to have made any progress > >with it for a while. > > > >There's some source available here:- > > > >ftp://ftp.win.tue.nl/pub/linux-local/utils/man/man-1.5g.tar.gz > > > >It has a non-standard configure which I can't get to run properly. > > > > I managed to get configure to finish by doing it manually, sh configure > -ask. Program names need to include the full path (no drive letter) and > .exe or .cmd at end. I had been hoping to get it to run automatically using the '-d' option. If I can get as far as building a Makefile, I should be OK, I think. > Its late here and I should goto bed. If you'd like I can try to > continue tomorrow but I can't see it becoming a configure make make > install type of solution, at least need patched C source. Creating something for make is the first step. I just can't get 'configure -d' to run properly. > Drive letter > support and OS/2 style manpaths need to be added too I'd imagine > Didn't Jun Sawatasha have a patch for MAN? Here > http://homepage1.nifty.com/jsawa/linux/man15g.zip which is definately a > better port then I could do, even includes support for running in a > xterm I'm hoping to incorporate some of those patches, I just don't like the way the program gets built. It also requires a configuration file being placed in \os2\etc which is undesirable IMV. > Dave -- John _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs **= Email 9 ==========================** Date: Sat, 22 May 2004 08:12:37 -0400 From: "T.Sikora" Subject: Re: Two build branches Lyn St George wrote: > On Fri, 7 May 2004 20:09:38 +0100, John Poltorak wrote: > > >>On Fri, May 07, 2004 at 07:03:34PM +0100, Lyn St George wrote: >> >>>Hallo all >>> >>>I've just run Ted's branch of ux2bs again, and this time it worked perfectly. I >>>guess that the previous problem was the lack of emx*.dll's on a new machine >>>just as it was for John's branch. >> >>This problem has been corrected now. >> >> >>>There has been a huge amount of work gone into both branches, and rather >>>than waste any of it I want to merge the two into one updated system. >>> >>>The basic philosophy will be that a package should be built from source >>>whenever possible, and only stuff like EMX should be installed as binary >>>packages. >> >>My aim is to start with a set of 'baseline' tools and as part of the >>initial install to replace them with self-built versions, ie so that >>\unixos2\bin can disappear as quickly as possible. >> >> >>>The system will also default to a \ux2 root so as to avoid any >>>possibility of clobbering existing stuff in either \ or \unixos2, with the option >>>of moving most of it to \ after testing so as to make a 'live' system. >>> > > > Apologies for the delay in following up on this. > > I've put together a draft of a possible merger of the two > branches, which seems to work well enough here. > > It starts with building the toolkit from pre-ported binaries > and then giving you the option of rebuilding it all from > sources. You also have the option of building packages > from either sources or ports. > > The installation finishes with building Apache 1.3.31 with > mod_php, mod_interchange and mod_rexx, and setting > up some local sites for it. Also builds Webmin, and installs > Ghostview - all these have options to skip or exit. > > \ux2\builds\foo has scripts and the source archive in foo > \ux2\ports\foo has scripts and the ported binary in foo > \ux2\scripts has all build, port, remove, or depend scripts > \ux2\system\base, emx, gcc has all system binaries. > > 'build perl' will build perl5.8.4 from source, build CPAN.pm > for interactive installation of modules, and build a list of > other useful modules. > > 'build port perl' will find a ported binary of perl off the > port.table and unpack it. > > 'build remove perl' will deinstall perl > > 'build depend perl' will install any missing dependencies > (this needs a lot of work to straighten out) > > Try it at ftp://ftp.zolotek.net/ux2/ux2_boot.cmd. > > Lyn St George > I just grabbed it. I'll give it a go this afternoon. -- T.Sikora tsikora at ntplx dot net _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs