search for: perl4

Displaying 5 results from an estimated 5 matches for "perl4".

Did you mean: perl
2001 Apr 17
1
Latest CVS: small portability issues
Hi! I just run a test build of the latest CVS on HP-UX 10.20 and found two issues, both related to the new mdoc2man.pl support: - In Makefile.in, line 122, the construction $(MANPAGES): %.out: % is used. HP's "make" command does not understand this syntax (gmake does). - In configure, the first "perl" command in the PATH seems to be found. On HP-UX this is an
2000 Apr 04
1
Perl v5.6.0 breaks the configure script
Hi, The new version of perl v5.6.0 breaks the configure script. When it tests for the version the current test perl -v| sed -n 's/^.*perl.*version \(.\).*/\1/p' returns null. perl -v now returns: This is perl, v5.6.0 built for ppc-linux Copyright 1987-2000, Larry Wall Perl may be copied only under the terms of either the Artistic License or the GNU General Public License, which
2000 Apr 04
1
Perl v5.6.0 breaks the configure script
Hi, The new version of perl v5.6.0 breaks the configure script. When it tests for the version the current test perl -v| sed -n 's/^.*perl.*version \(.\).*/\1/p' returns null. perl -v now returns: This is perl, v5.6.0 built for ppc-linux Copyright 1987-2000, Larry Wall Perl may be copied only under the terms of either the Artistic License or the GNU General Public License, which
1997 Nov 07
0
Perl script to locate F0 0F C7 C8 bombs
...directory you recursively look at all programs in # for instances of the F0 0F C7 C8 sequence # This script will search for programs with this sequence, which will # help sysadmins take appropriate action against those running such # programs # This script is written (but has not been tested) in Perl4, to # insure maximum compatibility sub findit { local($dir,$file,@files,$data) = @_; undef $/; if(!opendir(DIR,$dir)) { print STDERR "Can not open $dir: $!\n"; return 0; } @files=readdir(DIR); foreach $file (@files) { if($file ne ''.'' &...
1999 Dec 06
1
Ugly patch to openssh-1.2pre15
Hi, I am behind a firewall which does not permit connections to port 22, so I run my ssh server on port 23. :-) Unfortunately, the stupid firewall prints a few lines of junk when you make a connection to port 23 before actually starting the connection. This confuses ssh. Attached is an (ugly) patch against openssh-1.2pre15 which makes it ignore a configurable number of lines while looking for