Date: Thu, 18 Nov 2004 00:04:20 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [UnixOS2_Archive] No. 451 ************************************************** Wednesday 17 November 2004 Number 451 ************************************************** Subjects for today 1 Re: Debugging tar : Yuri Dario" 2 Re: Debugging tar : John Poltorak 3 Re: Debugging tar : Yuri Dario" 4 GCC v3.3.5 / LIBC v0.6 - Alpha 3 : Knut St. Osmundsen" 5 Re: GCC v3.3.5 / LIBC v0.6 - Alpha 3 : Dave Yeo" 6 Re: GCC v3.3.5 / LIBC v0.6 - Alpha 3 : Dave Yeo" 7 Re: GCC v3.3.5 / LIBC v0.6 - Alpha 3 : Dave Yeo" **= Email 1 ==========================** Date: Sun, 14 Nov 2004 23:10:47 +0100 (CET) From: "Yuri Dario" Subject: Re: Debugging tar Hi John, >You can get a GUI for tar - PMGTAK... where? >BTW have you ever used IBM's ADSM? I tried it a couple of times and it >seemed pretty neat, but was incredibly slow with tapes - no idea why - >maybe I didn't configure it properly. yes, but now it is abandoned-ware.... >The idea was to copy unique files to a database with an index pointing to >where they should be restored to, so that if you had ten systems with >identical copies of something like OS2KRNL for instance, you would only >store a single backup copy but have pointers showing which systems needed IBM PSNS (shipped with WSeB) works as described, but it is no longer updated/available. Bye, Yuri Dario /* * member of TeamOS/2 - Italy * http://www.os2power.com/yuri * http://www.teamos2.it */ **= Email 2 ==========================** Date: Tue, 16 Nov 2004 14:18:50 +0000 From: John Poltorak Subject: Re: Debugging tar On Sun, Nov 14, 2004 at 11:10:47PM +0100, Yuri Dario wrote: > Hi John, > > >You can get a GUI for tar - PMGTAK... > > where? Oops. Sorry about the name. I imagined what it should have been. This is what I meant:- http://hobbes.nmsu.edu/pub/os2/util/archiver/tarfnt23.zip This also may be of interest:- http://hobbes.nmsu.edu/pub/os2/util/wps/wpssafe1.zip > >BTW have you ever used IBM's ADSM? I tried it a couple of times and it > >seemed pretty neat, but was incredibly slow with tapes - no idea why - > >maybe I didn't configure it properly. > > yes, but now it is abandoned-ware.... > >The idea was to copy unique files to a database with an index pointing to > >where they should be restored to, so that if you had ten systems with > >identical copies of something like OS2KRNL for instance, you would only > >store a single backup copy but have pointers showing which systems needed > > IBM PSNS (shipped with WSeB) works as described, but it is no longer updated/available. I'd never heard that it behaved like that. I may take another look. I'm not too concerned about lack of updates unless is doesn't work or stops working. Upgrading software every week is really tiresome. I'm quite pleased when some products stabilise... > Bye, > > Yuri Dario > > /* > * member of TeamOS/2 - Italy > * http://www.os2power.com/yuri > * http://www.teamos2.it > */ -- John **= Email 3 ==========================** Date: Tue, 16 Nov 2004 16:08:28 +0100 (CET) From: "Yuri Dario" Subject: Re: Debugging tar Hi, >http://hobbes.nmsu.edu/pub/os2/util/archiver/tarfnt23.zip I know this one. >http://hobbes.nmsu.edu/pub/os2/util/wps/wpssafe1.zip this is new, I will look at it. >I'd never heard that it behaved like that. I may take another look. I'm >not too concerned about lack of updates unless is doesn't work or stops >working. it doesn't recognize some tape units (e.g. internal scsi tr-5 from ibm), but otherwise it works well. The user interface is really nice, really user-oriented (but sometimes it can be confused). >Upgrading software every week is really tiresome. I'm quite >pleased when some products stabilise... I agree. Bye, Yuri Dario /* * member of TeamOS/2 - Italy * http://www.os2power.com/yuri * http://www.teamos2.it */ **= Email 4 ==========================** Date: Tue, 16 Nov 2004 16:34:45 +0100 From: "Knut St. Osmundsen" Subject: GCC v3.3.5 / LIBC v0.6 - Alpha 3 Hi! There is a new GCC / LIBC alpha out: ftp://ftp.netlabs.org/pub/gcc/GCC-3.3.5-alpha3.zip Enjoy, knut PS. Here are the missing release notes: GCC v3.3.5 / LIBC v0.6 - Alpha 3: --------------------------------- This release have been timebombed and will stop working at the end of December 2004. The reason for this is that data structures shared between LIBC 0.6 and all future LIBC versions are not yet quite finalized. (For your comfort the timebomb will go away when the betas start, and this is the last planned LIBC v0.6 alpha.) New Features: o Updated GCC to version 3.3.5. o Replaced the signal implementation. The new implementation is much closer to the POSIX specs and implements a lot of new interfaces. o Experimental delayed loading import libraries. emximp have a new -l option for generating such libraries. At present emximp can only generate a.out libraries of this kind - so use emxomf to convert to OMF. o The dlfcn.h functions are in LIBC now. o New functions: getgrouplist(), initgroups(), memalign(), valloc(), mprotect(), _signal_os2(), _signal_sysv(), __sigpause_bsd(), bsd_signal(), killpg(), psignal(), sigaltstack(), sigblock(), sighold(), sigignore(), siginterrupt(), sigpause(), sigrelse(), sigsetmask(), sigtimedwait(), sigvec(), sigwait(), sigwaitinfo(), sigqueue(), sigset(), getgrgid(), getpwnam(), getpwuid(), setegid(), seteuid(), setregid(), setresgid(), setresuid(), setreuid(), setrgid(), setruid(), waitid(), wait3(), wait4() and getopt_long_only(). Bug fixes; o Sockets were broken on some systems. Hopefully, this should be corrected now. o stat() failed on a file open for writing. o fork() didn't work for processes which allocated lot's of memory. Fixed incorrect syncing of memory objects. o ... Known Limitiations/Problems: o Static linking not possible - will be fixed. o alarm() is still missing. Code is 90% done but didn't make it for the release. o Job control will only be applied to thread 1 in a process. This won't change. o Missing some process group interfaces required for job control. They'll show up soon. **= Email 5 ==========================** Date: Tue, 16 Nov 2004 22:20:07 -0800 From: "Dave Yeo" Subject: Re: GCC v3.3.5 / LIBC v0.6 - Alpha 3 On Tue, 16 Nov 2004 16:34:45 +0100, Knut St. Osmundsen wrote: >Hi! > >There is a new GCC / LIBC alpha out: > ftp://ftp.netlabs.org/pub/gcc/GCC-3.3.5-alpha3.zip > >Enjoy, > knut Hi Knut, looking at your symlink support I notice it uses the EA LIBC.SYMLINK. I wonder if it would be possible to make this work with Linux which uses the EAs GID = E8 03 SYMLINK = 2F 68 6F 6D 65 2F 64 61 76 65 /home/dave This is for a symlink from F:\home\dave\linux_home to /home/linux with my GID. Linux does preserve EAs so you could have both EAs LIBC.SYMLINK and SYMLINK and set GID to 0 (which IIRC is root) or preserve GID if it is already set. Thanx Dave **= Email 6 ==========================** Date: Tue, 16 Nov 2004 22:27:59 -0800 From: "Dave Yeo" Subject: Re: GCC v3.3.5 / LIBC v0.6 - Alpha 3 On Tue, 16 Nov 2004 16:34:45 +0100, Knut St. Osmundsen wrote: >Hi! > >There is a new GCC / LIBC alpha out: > ftp://ftp.netlabs.org/pub/gcc/GCC-3.3.5-alpha3.zip > >Enjoy, > knut HI Knut, trying to build the gnu file utils (old version, I don't have the bandwidth to do much downloading) I get this error while building dd gcc.exe -s -Zmt -Zcrtdll -Zbin-files -Zexe -o dd dd.o ../intl/libintl.a .../lib/libfu.a -lsocket -lgcc dd.o: Undefined symbol _IsLower referenced from text segment dd.o: Undefined symbol _ToUpper referenced from text segment dd.o: Undefined symbol _IsUpper referenced from text segment dd.o: Undefined symbol _ToLower referenced from text segment make[1]: *** [dd] Error 1 Which I don't understand as you have _islower, _toupper etc defined in libc06a3 and all the references in dd.c are lower case. Perhaps need an alias? Dave **= Email 7 ==========================** Date: Tue, 16 Nov 2004 22:11:05 -0800 From: "Dave Yeo" Subject: Re: GCC v3.3.5 / LIBC v0.6 - Alpha 3 On Tue, 16 Nov 2004 16:34:45 +0100, Knut St. Osmundsen wrote: >Hi! > >There is a new GCC / LIBC alpha out: > ftp://ftp.netlabs.org/pub/gcc/GCC-3.3.5-alpha3.zip > >Enjoy, > knut > > >PS. Here are the missing release notes: Thanks for getting this out. Had a few things I wanted to try but wanted to do it with this .... > Known Limitiations/Problems: > o Static linking not possible - will be fixed I don't understand the context of this. Dave