From bill at fccj.org Thu Apr 1 15:21:44 1999 From: bill at fccj.org (Bill Jones) Date: Thu Aug 5 00:03:02 2004 Subject: Fwd: Hats here soon! Message-ID: <199904012121.QAA14286@astro.fccj.cc.fl.us> On the Jax.PM jacksonville-pm-list 1.94.4; "Bill Jones" wrote - >From PM HQ, brian d foy writes: > > hats will be here soon so says the distributor! i've set the prices at > $10/hat for orders of 10 or more hats. individual hats will cost $15/hat > plus shipping. > > i've only ordered 200 of these hats and am not planning on ordering more > anytime soon, so if you want some, you'd better reserve some, and the only > way to do that is to pay for 'em. half of them are already spoken for... > ;) Any of you guys want a hat ? Let me know! :] ________________________________________________________________________ Bill Jones | FCCJ Webmaster | http://www.fccj.org/cgi/mail?webmaster FCCJ | 501 W State St | Jacksonville, FL 32202 | 1 (904) 632-3089 Jacksonville Perl Mongers http://jacksonville.pm.org jax@jacksonville.pm.org The Jacksonville Perl Monger's Group is operated by - Bill -Sneex- Jones ( sneex@usa.net ), to whom send all praises, complaints, or comments... From bill at fccj.org Thu Apr 1 15:33:58 1999 From: bill at fccj.org (Bill Jones) Date: Thu Aug 5 00:03:02 2004 Subject: FW: Brian gets even more famous Message-ID: <199904012133.QAA14471@astro.fccj.cc.fl.us> On the Jax.PM jacksonville-pm-list 1.94.4; "Bill Jones" wrote - http://www.salonmagazine.com/21st/ Oops! :] ________________________________________________________________________ Bill Jones | FCCJ Webmaster | http://www.fccj.org/cgi/mail?webmaster FCCJ | 501 W State St | Jacksonville, FL 32202 | 1 (904) 632-3089 Jacksonville Perl Mongers http://jacksonville.pm.org jax@jacksonville.pm.org ---------- >From: Rasmus Lerdorf >To: new-httpd@apache.org >Subject: Brian gets even more famous >Date: Thu, Apr 1, 1999, 10:52 AM > > You know you are cool when you get spoofed... > > From: http://www.salonmagazine.com/21st/ > > Brian Behlendorf of the Apache Project issued a press release detailing a > new plan to levy a micropayment tax on every Web page delivered by the > widely deployed Apache Web server. "This great software has been doing its > job on millions of computers without ever asking for anything in return," > Behlendorf said. "The free ride is over -- it's time to pay the piper." > > -Rasmus > > The Jacksonville Perl Monger's Group is operated by - Bill -Sneex- Jones ( sneex@usa.net ), to whom send all praises, complaints, or comments... From bill at fccj.org Fri Apr 2 03:20:26 1999 From: bill at fccj.org (Bill Jones) Date: Thu Aug 5 00:03:02 2004 Subject: Perl 5.005_3 out Message-ID: <199904020920.EAA18786@astro.fccj.cc.fl.us> On the Jax.PM jacksonville-pm-list 1.94.4; "Bill Jones" wrote - Newsgroups: comp.lang.perl.moderated,comp.lang.perl.announce,comp.lang.perl.misc From: Graham Barr Subject: Perl 5.005: Maintenance update 03 is available Approved: gbarr@pobox.com (per instructions from merlyn@stonehenge.com) Lines: 333 Message-ID: Date: Fri, 02 Apr 1999 00:42:08 GMT NNTP-Posting-Host: 216.2.128.36 X-Trace: news2.giganews.com 923013728 216.2.128.36 (Thu, 01 Apr 1999 18:42:08 CDT) NNTP-Posting-Date: Thu, 01 Apr 1999 18:42:08 CDT Path: usenet.fccj.cc.fl.us!newsfeed.mia!newsfeed.atl!cpk-news-hub1.bbnplanet.com!n ews.gtei.net!news-xfer.newsread.com!netaxs.com!newsread.com!nntp.giganews.co m!news2.giganews.com.POSTED!not-for-mail Xref: usenet.fccj.cc.fl.us comp.lang.perl.moderated:1889 comp.lang.perl.announce:1005074 comp.lang.perl.misc:1645700 The third maintenance update for Perl 5.005 was released on March 28 1999, and is now available from the Comprehensive Perl Network Archive (CPAN) sites worldwide. To select from a list of sites, go to: http://www.perl.com/CPAN Note the absence of a trailing `/'. The actual file can be found at: http://www.perl.com/CPAN/authors/id/GBARR/perl5.005_03.tar.gz This release is binary compatible with previous 5.005 releases. For a brief overview of what is new in the 5.005 series and other important information about reporting problems, see the release announcement for 5.005: http://www.perl.com/CPAN/authors/id/GSAR/perl5.005.announce More detailed information on changes can be found in "pod/perldelta.pod" and "Changes" files in the distribution. WARNING: Perl 5.005 and later are NOT BINARY COMPATIBILE with releases prior to 5.005. You will need to recompile all extensions that require a C compiler to build (i.e. those that contain XSUBs). See the "INSTALL" document for detailed instructions on how to cope. If you like the spirit in which Perl is made, help cultivate that spirit. Reveal the sources! Set knowledge free! --The Perl Porters ---------------------------------------------------------------------------- SUMMARY OF CHANGES IN MAINTENANCE UPDATE 3 ---------------------------------------------------------------------------- CONFIGURATION CHANGES Possible to Configure so that installperl skips installing Perl into /usr/bin/perl (Configure -Uinstallusrbinperl) NEW PLATFORM SUPPORT DYNIX/ptx: a high-availability UNIX variant from Sequent Computer Systems, http://www.sequent.com/ GNU/Hurd: the GNU Project's replacement for UNIX kernel, http://www.gnu.org/software/hurd/hurd.html MiNT: an operating system extension that adds UNIX-like features to ATARI TOS. Originally available only for m68k-based microcomputers sold by ATARI in the 80's but later available also for Mac and VME boards. More information available from http://www.modeemi.cs.tut.fi/~puujalka/mint.html Stratus VOS: a fault-tolerant OS from Stratus Computer, http://www.stratus.com/ U/WIN: a UNIX compatibility environment for Windows NT, available from AT&T, http://www.research.att.com/sw/tools/uwin/ PLATFORM ENHANCEMENTS BeOS: dynamic loading now supported (tested only on BeOS R4 x86). SCO: dynamic linking now supported. Linux: now works with installations that have only installed "runtime" versions (as opposed to "developer" versions) of some libraries such as GDBM. FreeBSD: 4.0 supported. ELF executable format supported. NetBSD: those platforms that support shared libraries have the support now also in Perl. OpenSTEP 4.2: i386 machines are now better supported. NextSTEP: SysV IPC (from ftp://ftp.nluug.nl/pub/comp/next/SysVIPC/) now supported. Win32: sysread() and syswrite() now work on sockets. rename() works across drive boundaries on Windows NT and is generally more compatible with its semantics on Unix. OS/2: Numerous patches. EBCDIC: Character class ranges ([a-z]) now work in non-ASCII platforms. NEW MODULES Dumpvalue Perl5 module replacement for old perl4 dumpvar.pl UPDATED MODULES CPAN 1.48 CGI 2.46 Data::Dumper 2.101 Getopt::Long 2.19 DB_File 1.65 Test 1.122 Benchmark timesum() method added. Can also run tests until N seconds. Config $Config{sig_num_init} now contains the signal numbers corresponding to the signal names of $Config{sig_name_init}. Math::Complex 0**0 is now 1, not undefined. Math::Trig Radial/spherical trigonometry functions added. Pod::Html Locale-aware which e.g. means that =headN can contain non-ASCII alphabetic characters. Pod::Text Ditto. Carp Added cluck() - warns with stacktrace MakeMaker PL_FILES now supports multiple targets from a single source AutoSplit fixed to know that pod starts with /^=\w+/ (not just /^=/) FindBin now works correctly with Win32 UNC pathnames NEW DOCUMENTATION perlreftut Tutorial on references. perlopentut Tutorial on open(). perlthrtut Tutorial on threads. UPDATED DOCUMENTATION All Perl FAQs. Many typos fixed in the documentation of core modules. perlport 1.39 ENHANCED FUNCTIONS sort $coderef @array now works. sort() now respects overloading. If /dev/urandom is available as a source of random bits, Perl will use it automatically to seed the random number generator. Note: /dev/random is not used by default because it may block if not enough entropy is available. If you prefer Perl to block in such circumstances, you can compile Perl with -DPERL_RANDOM_DEVICE=\"/dev/random\". pack/unpack now support Z for null terminated ascii strings that are null padded CHANGED BEHAVIOUR Better CR-handling on #! line and in formats. Overload syntax is no longer experimental. The LENGTH argument to syswrite() is now optional. ENHANCED UTILITIES h2ph is now much more robust. BUG FIXES Many multi-threading fixes. But multi-threading is still considered experimental. Work around a bug in Digital UNIX C compiler that caused the 'x' operator to produce garbage under certain circumstances. (This bug caused e.g. the tests of Digest::MD5 to fail.) The "Used only once" warning will now only be output once for each variable. With $/ set to undef, slurping an empty file returns a string of zero length (instead of undef, as it used to) for the first time the HANDLE is read. Subsequent reads yield undef. $a and $b are only exempt from warnings if sort with a user specified subroutine has been seen. SECURITY FIXES Setuid scripts from nosuid mounted filesystems now rejected. POSIX::strftime() buffer overflow avoided. KNOWN PROBLEMS lib/anydbm...FAILED at test 12 This test failure commonly encountered on glibc-2.1 systems where db won't accept a null key. ULTRIX /bin/sh Configure cannot be run on ULTRIX with /bin/sh, use sh5 instead. OS2 threads On OS2 the use of threads, socket and fork together causes a panic. sfio If perl is compiled with sfio op/die_exit.t fails all tests. ---------------------------------------------------------------------------- TESTED PLATFORMS ---------------------------------------------------------------------------- This release is known to build and pass all tests (with some noted exceptions) on the following platforms: PLATFORM CC OPTIONS -------- -- ------- AIX 4.2.1.0 cc AIX 4.2.1.0 cc -Doptimize=-O AIX 4.2.1.0 cc_r -Dusethreads AIX 4.2.1.0 gcc 2.8.1 AIX 4.1.5 cc -ders AIX 4.1.5 xlc_r -Dusethreads -ders alpha-dec_osf 4.0 cc alpha-dec_osf 4.0 cc -Dusethreads alpha-dec_osf 4.0 gcc 2.8.1 alpha-dec_osf 5.0 cc alpha-dec_osf 5.0 cc -Dusethreads AT386-gnu i386 0.2 egcs-1.1.1 AViiON-dgux r4.11mu02 gcc 2.6.3 CRAY_J90-unicos 10.0.0.2 cc Debian Linux 2.1 gcc 2.7.2.3 -ders -Dusethreads -Doptimize=-g Digital UNIX 4.0D cc -ders Digital UNIX 4.0D cc -Dusethreads -ders Digital UNIX 4.0E cc -ders Digital UNIX 4.0E cc -Dusethreads -ders dynixptx i386 4.2.1 cc FreeBSD i386 2.2.7-release gcc 2.7.2.1 FreeBSD i386 2.2.8-release gcc 2.7.2.1 FreeBSD i386 2.2.8-release gcc 2.7.2.1 -Dusethreads FreeBSD i386 3.0-stable gcc 2.7.2.1 FreeBSD i386 3.0-stable gcc 2.7.2.1 -Dusethreads FreeBSD i386 3.1-stable gcc 2.7.2.1 FreeBSD i386 3.1-stable gcc 2.7.2.1 -Dusethreads FreeBSD i386 4.0-current gcc 2.7.2.1 FreeBSD i386 4.0-current gcc 2.7.2.1 -Dusethreads HP-UX 11.0 cc -ders HP-UX 11.0 cc -Dusethreads -ders IP22-irix 5 cc IP32-irix 6.5 gcc 2.8.1 IP32-irix 6.5 gcc 2.8.1 -Dusethreads IRIX 6.5 cc -ders IRIX 6.5 cc -Dusethreads -ders Linux i386 2.0.36 gcc 2.7.2.3 Linux i386 2.0.36 gcc 2.7.2.3 -Dusethreads Linux i486 1.2.13 gcc 2.7.2.2 Linux i586 2.2.0-pre2 gcc 2.7.2.3 -Dusethreads Linux i586 2.2.5 gcc 2.7.2.3 Linux i586 2.2.5 gcc 2.7.2.3 -Dusethreads Linux i686 2.0.32 gcc 2.8.1 Linux i686 2.0.36 egcs-1.1.1 Linux i686 2.0.36 gcc 2.7.2.3 Linux i686 2.0.36 gcc 2.7.2.3 Linux i686 2.0.36 gcc 2.7.2.3 -Dusethreads Linux ppc 2.2.1 egcs-1.1.2 Linux ppc 2.2.1 egcs-1.1.2 -Dusethreads machten powerpc 4.1.1 gcc 2.8.1 NetBSD i386 1.3k egcs-1.1.1 NetBSD i386 1.3.2 gcc 2.7.2.2 -ders NetBSD mac68k 1.3k egcs-1.1.1 NetBSD macppc 1.3k egcs-1.1.1 NetBSD sparc 1.3.3 gcc 2.7.2.2+myc1 Next OpenStep Mach cc OpenBSD 2.5 gcc 2.8.1 OpenVMS Alpha 7.1 Dec C 6.0 OpenVMS Alpha 7.1 Dec C 6.0 -Dusethreads OS2 2.30 gcc 2.8.1 OS390 05.00 c89 OS390 06.00 c89 PA-RISC2.0 11.00 egcs-1.1.2 PA-RISC2.0 11.00 egcs-1.1.2 -Dusethreads powerux ppc 4.3 /bin/cc RM400-svr4 /bin/cc -W0 sco i386 3.2v5.0.4 cc Solaris 2.3 gcc 2.4.5 Solaris 2.5.1 gcc 2.7.2 Solaris 2.5.1 gcc 2.8.1 Solaris 2.5.1 gcc 2.8.1 -Dusethreads Solaris 2.6 gcc 2.7.2.3 -ders Solaris 2.6 gcc 2.8.1 Solaris 2.6 gcc 2.8.1 -Dcc=gcc -ders Solaris 2.6 gcc 2.8.1 -Dcc=gcc -Dusethreads -ders Solaris 2.6 cc Solaris 2.6 egcs-1.1.1 Solaris 2.6 egcs-1.1.1 -Dusethreads Solaris 2.6 gcc 2.8.1 Solaris 2.7 egcs-1.1.2 Solaris 2.7 SC5.0 SunOS 4.1.3 gcc 2.8.1 SunOS 4.1.3_u1 gcc 2.8.1 SunOS 4.1.4 egcs-1.1.2 svr4 i386 /bin/cc UNICOS 9.0.1ai cc -ders Windows NT 4.0 Borland 5.02 -DUSE_THREADS Windows NT 4.0 Borland 5.02 Debug Windows NT 4.0 Borland 5.02 Debug -DPERL_OBJECT -DPERLCRT Windows NT 4.0 VC 5.0 -DPERL_OBJECT -DPERLCRT Windows NT 4.0 VC 5.0 Debug -DUSE_THREADS -DPERL_MALLOC Windows NT 4.0 VC 5.0 none Windows NT 4.0 VC 6.0 -DPERLCRT Optimise Enjoy! -Sneex- :] ________________________________________________________________________ Bill Jones | FCCJ Webmaster | http://www.fccj.org/cgi/mail?webmaster FCCJ | 501 W State St | Jacksonville, FL 32202 | 1 (904) 632-3089 Jacksonville Perl Mongers http://jacksonville.pm.org jax@jacksonville.pm.org The Jacksonville Perl Monger's Group is operated by - Bill -Sneex- Jones ( sneex@usa.net ), to whom send all praises, complaints, or comments... From bill at fccj.org Tue Apr 6 16:15:57 1999 From: bill at fccj.org (Bill Jones) Date: Thu Aug 5 00:03:02 2004 Subject: FW: NSPR: Mozilla post-mortem? Message-ID: <199904062115.RAA23153@astro.fccj.cc.fl.us> On the Jax.PM jacksonville-pm-list 1.94.4; "Bill Jones" wrote - Attached is an interesting read, to say the least. ________________________________________________________________________ Bill Jones | FCCJ Webmaster | http://www.fccj.org/cgi/mail?webmaster FCCJ | 501 W State St | Jacksonville, FL 32202 | 1 (904) 632-3089 Jacksonville Perl Mongers http://jacksonville.pm.org jax@jacksonville.pm.org ---------- >From: TOKILEY@aol.com >To: new-httpd@apache.org >Subject: Re: NSPR: Mozilla post-mortem? >Date: Tue, Apr 6, 1999, 3:18 PM > > > Looks like (G)othra may have gotten (M)ozilla... > > Here is Jamie's resignation letter as of a few days ago. > > Interesting read. He has not soured on > open source ( read last paragraph ) but > there may be some lessons here for Apache... > especially with regards to recent discussions about > 'incorporating Apache'. > > Sorry about the length of the post but this comes > directly from Jamie's site and he put a (C) Copyright > symbol on it which means any reproduction of the > document should/must not be altered. > > Source URL: http://www.jwz.org/gruntle/nomo.html > > TOP DEVELOPER LEAVES MOZILLA... > > resignation and postmortem. > (c) 1999 Jamie Zawinski > > April 1st, 1999 will be my last day as an employee of the Netscape > Communications division of America Online, and my last day working for > mozilla.org. > Netscape has been a great disappointment to me for quite some time. When we > started this company, we were out to change the world. And we did that. > Without us, the change probably would have happened anyway, maybe six months > or a year later, and who-knows-what would have played out differently. But > we were the ones who actually did it. When you see URLs on grocery bags, on > billboards, on the sides of trucks, at the end of movie credits just after > the studio logos -- that was us, we did that. We put the Internet in the > hands of normal people. We kick-started a new communications medium. We > changed the world. > But we did that in 1994 and 1995. What we did from 1996 through 1999 was > coast along, riding the wave caused by what we did before. > Why? Because the company stopped innovating. The company got big, and big > companies just aren't creative. There exist counterexamples to this, but in > general, great things are accomplished by small groups of people who are > driven, who have unity of purpose. The more people involved, the slower and > stupider their union is. > And there's another factor involved, which is that you can divide our > industry into two kinds of people: those who want to go work for a company > to make it successful, and those who want to go work for a successful > company. Netscape's early success and rapid growth caused us to stop getting > the former and start getting the latter. > In January 1998, Netscape hit one of of its blackest periods -- the first > round of layoffs. It was quite a wake-up call. Netscape, darling of the > computer industry, the fastest-growing company in the world, was not > invincible. > More concretely, this was when we realized that we had finally lost the so > called ``browser war.'' Microsoft had succeeded in destroying that market. > It was no longer possible for anyone to sell web browsers for money. Our > first product, our flagship product, was heading quickly toward irrelevance. > And then the unexpected happened: the executive staff decided to release the > source code. I won't re-hash the history of the creation of the mozilla.org > project, but suffice it to say that, coming as it did only two weeks after > the layoffs, it was a beacon of hope to me. Here was Netscape doing > something daring again: here was the company making the kind of change in > strategy that I never thought they'd be able to make again. An act of > desperation? Perhaps, but still a very interesting and unexpected one. It > was so crazy, it just might work. I took my cue and ran with it, registering > the domain that night, designing the structure of the organization, writing > the first version of the web site, and, along with my co-conspirators, > explaining to room after room of Netscape employees and managers how free > software worked, and what we had to do to make it work. > At this point, I strongly believed that Netscape was no longer capable of > shipping products. Netscape's engineering department had lost the > single-minded focus we once had, on shipping something useful and doing it > fast. That was no longer happening. Netscape was shipping garbage, and > shipping it late. > And daring move or no, this was not going to change: Netscape no longer had > the talent, either in engineering or management, to ship quality products. > The magic was gone, as the magicians had either moved on to more compelling > companies, or were having their voices lost in the din of the crowd, swamped > by the mediocrity around them. > The Netscape I cared about was dead. > But I saw mozilla.org as a chance to jettison an escape pod -- to give the > code we had all worked so hard on a chance to live on beyond the death of > Netscape, and chance to continue to have some relevance to the world. > Beyond that, I saw it as a chance for the code to actually prosper. By > making it not be a Netscape project, but rather, be a public project to > which Netscape was merely a contributor, the fact that Netscape was no > longer capable of building products wouldn't matter: the outsiders would > show Netscape how it's done. By putting control of the web browser into the > hands of anyone who cared to step up to the task, we would ensure that those > people would keep it going, out of their own self-interest. > But that didn't happen. For whatever reason, the project was not adopted by > the outside. It remained a Netscape project. Now, this was still a positive > change -- it meant that Netscape was developing this project out in the > open, in full view of the world, and the world was giving important and > effective feedback. Netscape made better decisions as a result. > But it wasn't enough. > The truth is that, by virtue of the fact that the contributors to the > Mozilla project included about a hundred full-time Netscape developers, and > about thirty part-time outsiders, the project still belonged wholly to > Netscape -- because only those who write the code truly control the project. > And here we are, a year later. And we haven't even shipped a beta yet. > In my humble but correct opinion, we should have shipped Netscape Navigator > 5.0 no later than six months after the source code was released. But we (the > mozilla.org group) couldn't figure out a way to make that happen. I accept > my share of responsibility for this, and consider this a personal failure. > However, I don't know what I could have done differently. > I can come up with a litany of excuses and explanations for why we are so > late (heaven knows I've been making these excuses to the media for half the > lifetime of the project.) Some of them are: > Excuse #1: > It's a really large project, and it takes a long time for a new developer to > dive in and start contributing. > Excuse #1a: > Because of this, what happens is, someone will try to make a small change, > find that it's taking them longer than a few hours, and will give up and do > something else instead. > Excuse #2: > People only really contribute when they get something out of it. When > someone is first beginning to contribute, they especially need to see some > kind of payback, some kind of positive reinforcement, right away. For > example, if someone were running a web browser, then stopped, added a simple > new command to the source, recompiled, and had that same web browser plus > their addition, they would be motivated to do this again, and possibly to > tackle even larger projects. > We never got there. We never distributed the source code to a working web > browser, more importantly, to the web browser that people were actually > using. We didn't release the source code to the most-previous-release of > Netscape Navigator: instead, we released what we had at the time, which had > a number of incomplete features, and lots and lots of bugs. And of course we > weren't able to release any Java or crypto code at all. > What we released was a large pile of interesting code, but it didn't much > resemble something you could actually use. > Excuse #3: > The code was just too complicated and crufty and hard to modify, which is > why people didn't contribute. This was a believable excuse for a while, > which is why, six months ago, we switched from the old layout engine to the > new layout engine (Gecko/Raptor). By being a cleaner, newly-designed code > base, so the theory went, it was going to be easier for people to understand > and contribute. And this did get us more contributors. But it also > constituted an almost-total rewrite of the browser, throwing us back six to > ten months. Now we had to rewrite the entire user interface from scratch > before anyone could even browse the web, or add a bookmark. > Excuse #4: > It didn't contain a mail reader. There is surely a large class of users who > would be interested in working on Communicator that are less interested in > Navigator, but we never really found that out, since we never shipped the > source code to communicator (for a number of reasons, none very good, some > downright pathetic.) Now, as a result of the Gecko/Raptor rewrite, the > mail/news reader is being rewritten as well. Maybe it will even ship > someday. > Excuse #5: > Netscape failed to follow through on their own plans. During 1998, Netscape > sunk a huge amount of engineering effort into doing the 4.5 release: working > on a dead-end proprietary code base, the source of which would never be > released to the world, and would never benefit from open source development. > This was a huge blow to the Mozilla project, since for the first half of the > year, we weren't even getting full-time participation from Netscape. > This isn't even so much an excuse as a stupid, terrible mistake, considering > we should have learned our lessons about doing parallel development like > this in the past, with the abortive ``Javagator'' project. > The worst part about all this is, for the last year, I've spent much of my > time striving to convince people that mozilla.org is not netscape.com. I've > told people again and again that the mozilla.org organization does not serve > only the desires of the Netscape client engineering group, but rather, > serves the desires of all contributors to the Mozilla project, no matter who > they are. And that's certainly true. But the fact is, there has been very > little contribution from people who don't work for Netscape, making the > distinction somewhat academic. > Now, to be fair, in this first year, we did do some very good things: > * We showed the world how to operate a large software project out in the > open. Whatever else happened, we did maintain a high level of communication > between geographically and organizationally separate contributors and other > interested parties. We transitioned from a secretive and proprietary > development model to a very public one. We showed that it can be done. > * Though we didn't get a whole lot of participation in the form of source > code, we did get a lot of feedback about the directions the software was > going. And the right feedback at the right time can easily be far more > valuable than source code. By doing development out in the open, and > ``living in a fishbowl,'' I believe that Netscape made better decisions > about the directions of development than would have been made otherwise. > * We released the source code to a number of ancillary tools, such as our > bug system, source-control interface, and build tools. These are very good > (and complete!) tools in their own right. Though they were critical to us in > the development of Mozilla, and we created them in support of Mozilla, they > are not tied to Mozilla, and others are finding them useful with their own > non-Mozilla-related projects. These tools, and the development model they > represent, are a valuable contribution in their own right. > * And merely by being who we are and doing what we did, we played a big part > in bringing the whole open source development model to the attention of the > world at large. We didn't start the mainstream media interest in open source > (Linux did that, mostly), but I think we did legitimize it in the eyes of a > lot of people, and we did tell the story very well. Lending the Netscape > name to this software development strategy brought it to the attention of > people who might otherwise have dismissed it. > But despite all this, in the last year, we did not accomplish the goals that > I wanted to accomplish. We did not take the Mozilla project and turn it into > a network-collaborative project in which Netscape was but one of many > contributors; and we did not ship end-user software. For me, shipping is the > thing. > Perhaps my goals were unreasonable; perhaps it should have been obvious to > me when we set out on this project that it would take much longer than a > year to reach these goals, if we ever did. But, it wasn't obvious to me > then, or now. These are the goals I was aiming for, and they have not yet > been met. > And so I'm giving up. > The Mozilla project has become too depressing, and too painful, for me to > continue working on. I wanted Mozilla to become something that it has not, > and I am tired of fighting and waiting to make it so. I have felt very > ineffectual, and that's just not a good feeling. > For those of you who choose to continue, I wish you all the best of luck. > I must say, though, that it feels good to be resigning from AOL instead of > resigning from Netscape. It doesn't really feel like quitting at all. I was > the 20th person hired at Mosaic Communications Corporation (All Praise the > Company), and of those twenty, only five remain. The company I helped build > has been gone for quite some time. We, Netscape, did some extraordinary > things. But we could have done so much more. I feel like we had a shot at > greatness, and missed. > My biggest fear, and part of the reason I stuck it out as long as I have, is > that people will look at the failures of mozilla.org as emblematic of open > source in general. Let me assure you that whatever problems the Mozilla > project is having are not because open source doesn't work. Open source does > work, but it is most definitely not a panacea. If there's a cautionary tale > here, it is that you can't take a dying project, sprinkle it with the magic > pixie dust of ``open source,'' and have everything magically work out. > Software is hard. The issues aren't that simple. > Jamie Zawinski, 31-Mar-1999 > > > The Jacksonville Perl Monger's Group is operated by - Bill -Sneex- Jones ( sneex@usa.net ), to whom send all praises, complaints, or comments... From bill at fccj.org Tue Apr 6 16:24:46 1999 From: bill at fccj.org (Bill Jones) Date: Thu Aug 5 00:03:02 2004 Subject: Perl Newsgroup Message-ID: <199904062124.RAA23247@astro.fccj.cc.fl.us> On the Jax.PM jacksonville-pm-list 1.94.4; "Bill Jones" wrote - Maybe, maybe not. :) Can I/we stay here in Jax, Fl and telecommute to the job site? What kinds of Perl/Unix stuff do/es you/your clients want? I may have others who might be interested. Just curious, -Sneex- :] ________________________________________________________________________ Bill Jones | FCCJ Webmaster | http://www.fccj.org/cgi/mail?webmaster FCCJ | 501 W State St | Jacksonville, FL 32202 | 1 (904) 632-3089 Jacksonville Perl Mongers http://jacksonville.pm.org jax@jacksonville.pm.org ---------- >From: "Elizabeth A. Nelson" >To: bill@fccjmail.fccj.cc.fl.us >Subject: Perl Newsgroup >Date: Tue, Apr 6, 1999, 4:00 PM > > I got your e-mail address off of a Perl newsgroup posting. My name is > Elizabeth Nelson and I am a recruiter for the Maxim Group, an > Information Technology Consulting firm. We currently have a number of > openings for Perl/Unix and other skill sets that I thought you might be > interested in. I realize this is a random message, but thought you or > someone you know might be interested. Thanks for your attention. > Sincerely, > Elizabeth Nelson > The Jacksonville Perl Monger's Group is operated by - Bill -Sneex- Jones ( sneex@usa.net ), to whom send all praises, complaints, or comments... From bill at fccj.org Thu Apr 8 08:04:57 1999 From: bill at fccj.org (Bill Jones) Date: Thu Aug 5 00:03:02 2004 Subject: [TPI News] April 07, 1999 Message-ID: <199904081304.JAA11015@astro.fccj.cc.fl.us> On the Jax.PM jacksonville-pm-list 1.94.4; "Bill Jones" wrote - FYI to Jax PM members: Below is the epitaph of The Perl Institute. ________________________________________________________________________ Bill Jones | FCCJ Webmaster | http://www.fccj.org/cgi/mail?webmaster FCCJ | 501 W State St | Jacksonville, FL 32202 | 1 (904) 632-3089 Jacksonville Perl Mongers http://jacksonville.pm.org jax@jacksonville.pm.org ---------- Fwd Msg Begins ---------- >From: TPI News Pumpking >To: TPI News List >Subject: [TPI News] April 07, 1999 >Date: Wed, Apr 7, 1999, 3:32 PM > > ------------------------------------------------------------------------ > > > 07 April 1999 > ------------- > > Sorry About This [Other] > We've been less than diligent lately in providing the news > every day. Well, we won't make excuses, we are just really > busy. > > Perl Institute Board Votes to Dissolve [Institute] > On March 1, 1999, the Board of Directors of The Perl Institute > unanimously voted to dissolve The Perl Institute. > > The specific reasons why have not yet been made public, as The > Perl News currently only has access to the meeting minutes, > which will be posted on [0]www.perl.org. However, the minutes > do speak to the Institute being ineffectual: Larry Wall > discussed at the meeting the differences between "top-down" and > "bottom-up" development, and that he cited the Institute as an > attempt at a "top-down" approach, while Perl culture mandates a > "bottom-up" approach. > > The minutes note that the Institute has no known outstanding > debts. The Perl Institute's assets, including the domain names > perl.org and cpan.org, are to be gifted to [1]Perl Mongers. It > is unclear whether, if Perl Mongers does receive these assets, > it will continue to use those domains to provide some or all of > the services TPI currently provides (such as Perl News, bug > tracking, mailing lists, CPAN Testers, and access to CPAN > itself) to the Perl community. > > What is clear is that in some way or another, most or all of > these services will continue somewhere. Perl News will > continute mostly unaffected, as will CPAN Testers, and access > to CPAN will, if all else fails, still be available through > dozens of other sites around the world. > > The minutes mention that Wall and Randal Schwartz will post a > press release on perl.org. When it is posted, it will be > mentioned in Perl News, and any other information we receive > will be passed along too, so watch this space. > > INTERCAL to Perl Compiler Released [Links] > From the same people who brought us [2]dd-sh (the one true > programming language) and [3]The Perl Filesystem now comes > CLC-INTERCAL, a INTERCAL interpreter implemented entirely in > Perl. > > Released on April 1, CLC-INTERCAL, consists of the module > Language::INTERCAL and supporting modules for EBCDIC and Baudot > code processing. It was developed on Perl 5.004 but should run > on versions 5.002 and above. Intercal compilers can be embedded > in and integrated into other applications; preliminary work on > the INTERCAL ORB is now in progress. See the [4]Assurdo web > site for more information. > > > All You Mongers Show Your Faces [User Groups] > * Bakersfield.pm (Bakersfield, CA) <[5]lalvey@ffguide.com> > * CGI.pm (Cape Girardeau, MO) <[6]mike808@mo.net> > * Cleveland.pm (Cleveland, OH) <[7]colossus@lightstream.net> > * PalmCoast.pm (Palm Coast, FL) <[8]hpepper@mindspring.com> > * SantaMaria.pm (Santa Maria, CA) > <[9]perlgroup@one-click.com> > * SantaMonica.pm (Santa Monica, CA) <[10]adam@cnation.com> > * Ottawa.pm (Ottawa, Ontario Canada) > <[11]spurkis@engsoc.carleton.ca> > * Manila.pm (Manila, Philippines) <[12]fred@skyinet.net> > * Braga.pm (Braga, Portugal) <[13]tiago@um.geira.pt> > * Koebenhavn.pm (Koebenhavn, Denmark) <[14]ask@netcetera.dk> > * Leipzig.pm (Leipzig, Germany) <[15]hoehne@hotpop.com> > * Pacos-de-Ferreira.pm (Pacos de Ferreira, Portugal) > <[16]phantom@mobile.8m.com> > * Zurich.pm (Zurich, Switzerland) <[17]wesi@acm.org> > Codez-vous francais? [Links] > > We were alerted to a [18]project to translate the Perl docs to > French, and thought, hey, we could have translated most of > [19]perlhist! > > It is only conjecture, as I'm many years removed from my high > school French classes, but I imagine they would accept help > from like-minded (and like-languaged) individuals. > > > New Modules 2-6 April 1999 [Module News] > * [20]Apache-ASP-0.09_1 > * [21]Apache-DB-0.03 > * [22]Apache-Session-0.99.8 > * [23]CGI-SpeedyCGI-1.6 > * [24]Crypt-HCE_MD5-0.40 > * [24]Crypt-HCE_SHA-0.40 > * [25]Event-0.34 -- Perl event loop > * [26]File-chmod-0.20 > * [27]Filesys-Statvfs_Df-0.56 > * [28]Fortune-0.1 > * [29]Geo-WeatherNOAA-4.33 -- Current/forecast weather from > NOAA > * [30]Getopt-EvaP-2.3.4 -- Long/short options, multilevel > help > * [31]Metadata-0.23 > * [32]Net-Traceroute-0.9 > * [33]ORAC-DBA-0.05 > * [34]Object-Persistence-0.34 > * [35]Parse-Yapp-0.30 -- Generates OO LALR parser modules > * [36]PerlMagick-4.22 > * [37]PerlQt-2.002 > * [38]Pod-DocBook-0.05 > * [39]PostScript-EPSF-0.01 > * [40]SQL-Statement-0.1012 -- Small SQL parser and engine > * [41]ShadowHash-0.05 > * [40]Text-CSV_XS-0.18 -- Fast 8bit clean version of > Text::CSV > * [42]Text-Merge-0.24 > * [30]Tie-Watch-1.0 -- Watch variables, run code when > read/written > * [43]Tk-Clock-0.05 > * [44]Tk-Multi-1.002 > * [45]Tk-TIFF-0.04 > * [46]Tk800.014 > * [47]XML-Parser-2.22 > ------------------------------------------------------------------------ > References: > 0. http://www.perl.org/ > 1. http://www.pm.org/ > 2. http://dd-sh.assurdo.com/ > 3. http://dd-sh.assurdo.com/perlfs/ > 4. http://www.assurdo.com/ > 5. mailto:lalvey@ffguide.com > 6. mailto:mike808@mo.net > 7. mailto:colossus@lightstream.net > 8. mailto:hpepper@mindspring.com > 9. mailto:perlgroup@one-click.com > 10. mailto:adam@cnation.com > 11. mailto:spurkis@engsoc.carleton.ca > 12. mailto:fred@skyinet.net > 13. mailto:tiago@um.geira.pt > 14. mailto:ask@netcetera.dk > 15. mailto:hoehne@hotpop.com > 16. mailto:phantom@mobile.8m.com > 17. mailto:wesi@acm.org > 18. http://www.enstimac.fr/~gaborit/Perl/ > 19. http://www.enstimac.fr/~gaborit/Perl/perlhist.html > 20. http://www.perl.com/CPAN/authors/id/C/CH/CHAMAS/ > 21. http://www.perl.com/CPAN/authors/id/DOUGM/ > 22. http://www.perl.com/CPAN/authors/id/JBAKER/ > 23. http://www.perl.com/CPAN/authors/id/H/HO/HORROCKS/ > 24. http://www.perl.com/CPAN/authors/id/E/EE/EESTABROO/ > 25. http://www.perl.com/CPAN/authors/id/JPRIT/ > 26. http://www.perl.com/CPAN/authors/id/P/PI/PINYAN/ > 27. http://www.perl.com/CPAN/authors/id/I/IG/IGUTHRIE/ > 28. http://www.perl.com/CPAN/authors/id/GWARD/ > 29. http://www.perl.com/CPAN/authors/id/MSOLOMON/ > 30. http://www.perl.com/CPAN/authors/id/LUSOL/ > 31. http://www.perl.com/CPAN/authors/id/D/DJ/DJBECKETT/ > 32. http://www.perl.com/CPAN/authors/id/H/HA/HAG/ > 33. http://www.perl.com/CPAN/authors/id/A/AN/ANDYDUNC/ > 34. http://www.perl.com/CPAN/authors/id/V/VI/VIPUL/ > 35. http://www.perl.com/CPAN/authors/id/F/FD/FDESAR/ > 36. http://www.perl.com/CPAN/authors/id/JCRISTY/ > 37. http://www.perl.com/CPAN/authors/id/AWIN/ > 38. http://www.perl.com/CPAN/authors/id/ADESC/ > 39. http://www.perl.com/CPAN/authors/id/GAAS/ > 40. http://www.perl.com/CPAN/authors/id/JWIED/ > 41. http://www.perl.com/CPAN/authors/id/RRA/ > 42. http://www.perl.com/CPAN/authors/id/S/SH/SHARRIS/ > 43. http://www.perl.com/CPAN/authors/id/H/HM/HMBRAND/ > 44. http://www.perl.com/CPAN/authors/id/DDUMONT/ > 45. http://www.perl.com/CPAN/authors/id/SREZIC/ > 46. http://www.perl.com/CPAN/authors/id/NI-S/ > 47. http://www.perl.com/CPAN/authors/id/C/CO/COOPERCL/ > > * To unsubscribe, send message with body "unsubscribe daily-news" to * > * majordomo@perl.org. For current and recent news, and news archives, * > * see . Send feedback and news * > * to news@perl.org. * > The Jacksonville Perl Monger's Group is operated by - Bill -Sneex- Jones ( sneex@usa.net ), to whom send all praises, complaints, or comments... From bill at fccj.org Sat Apr 24 10:58:12 1999 From: bill at fccj.org (Bill Jones) Date: Thu Aug 5 00:03:02 2004 Subject: Y2K Software Conversion Tools Message-ID: <199904241557.LAA16642@astro.fccj.cc.fl.us> On the Jax.PM jacksonville-pm-list 1.94.4; "Bill Jones" wrote - No, we would not be interested, thanks. (I did CC the jax-pm list, in case one of our members are interested, however.) As PERL has no Y2k issues, your tool(s) really has no market (cannot speak for C; I use it, but very little lately...) However, if your tool(s) can actually read a programmer's code and 'know' what they are thinking - where do I sign up? (I've been looking for a 'mind-reading' perl parser :) Short answer - you can't parse Perl and say that this code is Y2k safe and that code isn't. Either the programmer wrote good code or they didn't. Hope this explains 'perl' better. :] NNTTM, -Sneex- :] ______________________________________________________________________ Bill Jones Data Security Specialist http://www.fccj.org/cgi/mail?dss http://certserver.pgp.com:11371/pks/lookup?op=get&search=0x37EFC00F http://www.networksolutions.com/cgi-bin/whois/whois?BJ1936 Jacksonville Perl Mongers http://jacksonville.pm.org jax@jacksonville.pm.org ---------- >From: Michael Rynas >To: "'sneex@fccj.org'" >Subject: Y2K Software Conversion Tools >Date: Fri, Apr 23, 1999, 6:37 PM > > Hello, > > I am not sure who to contact at Perl User Groups, so I am sending this info > to you. Please let me know if there maybe interest within your group in > this type of Y2K Tool. Thankyou. > > > Y2K Software Conversion Tools for Perl > > The Unravel 2000 is a comprehensive family of multi-platform/multi-language > tools designed to address all phases of Year 2000 software conversion > projects. The technology software is based on a sophisticated parsing engine > which includes multi-level propagation of suspected date variables. The > parsing is based on a seed list (include/exclude). This list can be tuned. > The date variables impacted are highlighted in the code allowing the > programmer to identify the variable easily. The source code data repository > allows for repetitive reporting functions, changes to project plans, and > fast remediation of your date variable. > > UNRAVEL 2000 tools impact assessment which includes 5 steps. > Step 1. Inventory all programs and load the source code repository > Step 2. Tune the include and exclude list > Step 3. Parse the code > Step 4. Review the suspect date variables to determine whether the variable > is in fact a date variable > Step 5. Create a project plan for remediation using the automated generator > in Unravel 2000 > > Perl Tools > > UNRAVEL 2000 - Impact Analysis, Browser, Project Tracking, and Compliance > Editor: > > Part Number Description Unit > Price per Seat > > U2Perl Perl > $2,995 > > Client/Server Tools > > C and C++, Visual Basic, Unix Shell Scripts (C, Korn, Bourne), PowerBuilder, > Sybase Transact SQL, and FoxPro > > > If you have any questions about this software or need further information, > please give me a call. > > Thank you for your time and attention. > > Mike Rynas > Ravel Software Corporation > 408-548-0692 > > > > > The Jacksonville Perl Monger's Group is operated by - Bill -Sneex- Jones ( sneex@usa.net ), to whom send all praises, complaints, or comments... From bill at fccj.org Sun Apr 25 11:53:12 1999 From: bill at fccj.org (Bill Jones) Date: Thu Aug 5 00:03:02 2004 Subject: Sun Enterprise 10000 spec Message-ID: <199904251652.MAA24080@astro.fccj.cc.fl.us> On the Jax.PM jacksonville-pm-list 1.94.4; "Bill Jones" wrote - Scott/Daniel: Please find attached the 'server' specifications Rob has requested for a bid meeting. The information included is as complete as I can make it on short notice and without being able to meet with appropriate industry systems engineers to help discuss key design issues for the proposed new FCCJ Data Center server. While I do not have concrete pricing data, I can estimate the cost of the posed system should typically fall with the $1 to 3 Million range. This cost is can be spread over a 2-3 year Fiscal period. FCCJ typically receives a 40% pricing break on hardware and 90% on software. If either of you should know of more information or have any knowledge, do not hesitate to contact me at your earliest convienence. I would appreciate input. Thx, -Sneex- :] ______________________________________________________ "Never Mind" -- I'll improvise, adapt, and overcome; everything else will be deleted. Jacksonville Perl Mongers http://jacksonville.pm.org jax@jacksonville.pm.org -------- Specifications ---------- Florida Community College at Jacksonville (FCCJ) is searching for a scalable symmetrical multiprocessing (SMP) computer system running an operating system which is industry compatible with the SVR4 operating system (UNIX? System V, Release 4). Such a system will be Year 2000 (Y2k) compliant and ready, both at the hardware level and at the operating system level, to include any accompanying application software shipped as part of such system. Said system will prove to be an ideal, general-purpose application and data server for host-based or client-server applications such as on-line transaction processing (OLTP), decision support systems (DSS), data warehousing, communications services, and/or multimedia services. Such system should be scalable with up to 64 processors, up to 64GB of memory, over 60TB of on-line disk storage, and prove compatible with a wide range of UNIX application software commonly available in the competitive Unix? market. All functional areas of the system are to be field upgradeable, and most upgrades must be performable without disrupting users or requiring halting the system. The system should incorporate high reliability, availability, and serviceability features that are unique for proposed server. Examples of such a system would include dynamic reconfiguration (without system disruption) and dynamic system partitioning (whereby the system can be logically partitioned into multiple smaller servers). At a minimum, the proposed system should be scalable as shown below: * Such system should have from 1 to 16 system boards * 4 to 64 processors (with 4 CPUs minimum per system board) * Each processor should operate at 400MHz minimum * Each processor should have a minimum of 4MB Cache * The system should be scalable to a minimum of 64GB RAM * The internal disk should be scalable to a minimum of 280GB * The internal system 'back-plane should operate at a minimum of 100MHz and provide up to 12.5GB of data throughput * The system total disk storage should be scalable beyond 60TB * The system should be scalable to a minimum of 32 PCI slots * The system should be scalable to a minimum of 64 Sbus slots * The proposed system should include as many of these features as deemed appropriate - ? On-line hot swap of boards, power, and cooling components ? Fault-tolerant power and cooling ? Redundant AC line cords and breakers ? Monitoring tools ? Automatic system recovery ? Partitionable System Boards ? ECC-protected data paths ? ECC on memory and Interconnect ? Complete parity checking ? Environmental monitoring ? Remote console support ? Redundant consoles ? Interconnect data path resiliency ? Interconnect address path resiliency ? Redundant ?housekeeping? functions ? Redundant option for all hardware components * The proposed system's reliability, availability and serviceability features should result in uptimes greater than 99.95 percent. ? No single points of hardware failure: No single component (with the exception of the control board) will prevent a properly configured system from automatically reconfiguring itself to resume execution after a failure. ? Error correction interconnect: Data and address buses are to be protected by a combination of error correcting codes and parity. ? Dynamic system partitioning: Groups of system boards should be arrangeable in multiprocessor system groups that can run independent copies of the vendor's proposed operating system, concurrently. ? Each system partition should be completely isolated from all software errors, and most hardware failures that might occur in another system partition. ? Dynamic reconfiguration: Enables the system administrator to add, remove, or replace system components or create/remove system partitions on line without disturbing production usage. ? Hot swapping: Power supplies, fans, and most board-level system components should be exchangeable while ?hot?; that is, while the system is on line and in operation. * The proposed system should support 10/100 Ethernet, GigaBit Ethernet, ATM, FDDI, HiPPI, ISDN, and traditional high-speed serial connections. While FCCJ has determined the the ideal system will have a base enclosure and physical dimensions of 70" high, 50" wide, and 39" deep; each vendor providing bids should include necessary environmental system requirements as well as physical dimensions of the respective proposed system. Such data will provide, at a minimum, the following - ? System's physical dimensions and suggested housing requirements ? System's power & cooling requirements, consumption ? System's environmental needs and other requirements ? Additional system specific information deemed appropriate Each bidding vendor will provide references of clients who are currently operating such proposed system(s); matching as closely as possible both the hardware and software proposed. -------- End of Specification list -------- The Jacksonville Perl Monger's Group is operated by - Bill -Sneex- Jones ( sneex@usa.net ), to whom send all praises, complaints, or comments... From bill at fccj.org Sun Apr 25 19:06:31 1999 From: bill at fccj.org (Bill Jones) Date: Thu Aug 5 00:03:02 2004 Subject: A New Member! Message-ID: <199904260006.UAA25985@astro.fccj.cc.fl.us> On the Jax.PM jacksonville-pm-list 1.94.4; "Bill Jones" wrote - Everyone please welcome Doug Howk! Hi Doug! -Sneex- :] _________________________________________________________________________ Bill Jones | Data Security Specialist | http://www.fccj.org/cgi/mail?dss FCCJ | 501 W State St | Jacksonville, FL 32202 | 1 (904) 632-3089 Mentoring: http://tesla.fccj.cc.fl.us/cgi-bin/mentors.pl?cmd=show&uid=24 Jacksonville Perl Mongers http://jacksonville.pm.org jax@jacksonville.pm.org The Jacksonville Perl Monger's Group is operated by - Bill -Sneex- Jones ( sneex@usa.net ), to whom send all praises, complaints, or comments... From bill at fccj.org Sun Apr 25 19:16:57 1999 From: bill at fccj.org (Bill Jones) Date: Thu Aug 5 00:03:02 2004 Subject: Weekly Perl Script Message-ID: <199904260016.UAA26030@astro.fccj.cc.fl.us> On the Jax.PM jacksonville-pm-list 1.94.4; "Bill Jones" wrote - Hi All :] As a new benefit for the Jacksonville Perl Monger membership (now at 4 :) I present the kick off of the "Weekly Perl Script" series. Each Week, around Saturday or Sunday, I will submit to the list a Perl Script which does something useful, but one which isn't too hard to follow along with and can be modified to attend other tasks. I will post a script to the Jax-PM listserv and allow one week for the group to discuss it; after the week has passed I will either post a follow-up, one which will help describe the functioning of the prior weeks post or we will move on to a new script to discuss that week. Fair enough? BTW: The 'other' members may post script and/or questions here as well. I'm not saying that any of them will be answered - but together I am sure we can discover a solution! Here is this weeks offering for your review - #!perl -w use strict; use diagnostics; use Net::Telnet (); my $t = new Net::Telnet (Timeout => 2, Errmode => 'return', Prompt => '/bash\$ $/'); my $domainNumber = "207.203."; my $netWork = 46; # Starting place... my $hostNumber = 0; my $testTelnet = ''; my $msg = ''; my $ctr = 0; $| = 1; # Flush the buffer... while (1) { if ($hostNumber > 253) { if ($netWork == 47) { $netWork = 60; } elsif ($netWork == 63) { $netWork = 76; } elsif ($netWork == 87) { $netWork = 94; } elsif ($netWork == 95) { $netWork = 206; } elsif ($netWork == 211) { $netWork = 218; } elsif ($netWork == 223) { exit; # Done... } else { $netWork++; } $hostNumber = 0; # Reset it... } $hostNumber++; $testTelnet = $domainNumber . $netWork . "." . $hostNumber; $t->open("$testTelnet"); $msg = $t->errmsg; print $ctr++, "\r"; print "\nMaybe \@ $testTelnet\n\n" unless $msg; } Look at it, think it over, and if you have any questions, please post to the list. Enjoy! -Sneex- :] _________________________________________________________________________ Bill Jones | Data Security Specialist | http://www.fccj.org/cgi/mail?dss FCCJ | 501 W State St | Jacksonville, FL 32202 | 1 (904) 632-3089 Mentoring: http://tesla.fccj.cc.fl.us/cgi-bin/mentors.pl?cmd=show&uid=24 Jacksonville Perl Mongers http://jacksonville.pm.org jax@jacksonville.pm.org The Jacksonville Perl Monger's Group is operated by - Bill -Sneex- Jones ( sneex@usa.net ), to whom send all praises, complaints, or comments... From bill at fccj.org Sun Apr 25 19:50:43 1999 From: bill at fccj.org (Bill Jones) Date: Thu Aug 5 00:03:02 2004 Subject: The Jax PM Site was updated. Message-ID: <199904260050.UAA26193@astro.fccj.cc.fl.us> On the Jax.PM jacksonville-pm-list 1.94.4; "Bill Jones" wrote - Hi all :] In case anyone would like to know, I've updated some items on the http://jacksonville.pm.org/ Jacksonville Perl Monger's Web Site. O'Reilly http://perl.oreilly.com/ has donated two fine Perl books; go check them out! Thx, -Sneex- :] _________________________________________________________________________ Bill Jones | Data Security Specialist | http://www.fccj.org/cgi/mail?dss FCCJ | 501 W State St | Jacksonville, FL 32202 | 1 (904) 632-3089 Mentoring: http://tesla.fccj.cc.fl.us/cgi-bin/mentors.pl?cmd=show&uid=24 Jacksonville Perl Mongers http://jacksonville.pm.org jax@jacksonville.pm.org The Jacksonville Perl Monger's Group is operated by - Bill -Sneex- Jones ( sneex@usa.net ), to whom send all praises, complaints, or comments...