[26409] in Perl-Users-Digest
Perl-Users Digest, Issue: 8580 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Thu Oct 27 21:05:18 2005
Date: Thu, 27 Oct 2005 18:05:04 -0700 (PDT)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Thu, 27 Oct 2005 Volume: 10 Number: 8580
Today's topics:
Re: FAQ 3.23 How can I get "#!perl" to work on [MS-DOS <ron@savage.net.au>
Re: FAQ 3.23 How can I get "#!perl" to work on [MS-DOS, <matthew.garrish@sympatico.ca>
Re: FAQ 3.23 How can I get "#!perl" to work on [MS-DOS, <1usa@llenroc.ude.invalid>
Re: Microsoft Hatred FAQ <mscottschilling@hotmail.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Fri, 28 Oct 2005 09:35:06 +1000
From: Ron Savage <ron@savage.net.au>
Subject: Re: FAQ 3.23 How can I get "#!perl" to work on [MS-DOS,NT,...]?
Message-Id: <200510289356.658181@ron>
On Fri, 28 Oct 2005 08:03:01 +1000, PerlFAQ Server wrote:
Hi
Also, if people choose to run the Apache web server under Windows,
and want Apache to run their scripts under Perl, then they need to do 3=
things:
o Have a she-bang line like this:
#!/usr/bin/perl
o Create c:\usr\bin and copy c:\perl\bin\perl.exe into c:\usr\bin.
This works for other drives besides c: of course, if Apache and Perl are
installed on d:, say.
And they can use c:\usr\local\bin\perl.exe in the same way, even at the same=
time, with a she-bang of #!/usr/local/bin/perl.
o Then in httpd.conf, all that's needed is something like:
ScriptAlias /cgi-bin/ "c:/Apache2/cgi-bin/"
<Directory "c:/Apache2/cgi-bin">
AllowOverride None
Options None
=09Order deny,allow
=09Deny from all
=09Allow from 127.0.0.1
</Directory>
------------------------------
Date: Thu, 27 Oct 2005 20:42:26 -0400
From: "Matt Garrish" <matthew.garrish@sympatico.ca>
Subject: Re: FAQ 3.23 How can I get "#!perl" to work on [MS-DOS,NT,...]?
Message-Id: <Nte8f.7615$ki7.543191@news20.bellglobal.com>
"Ron Savage" <ron@savage.net.au> wrote in message
news:200510289356.658181@ron...
On Fri, 28 Oct 2005 08:03:01 +1000, PerlFAQ Server wrote:
> Also, if people choose to run the Apache web server under Windows,
> and want Apache to run their scripts under Perl, then they need to do 3
> things:
>
> o Have a she-bang line like this:
>
> #!/usr/bin/perl
>
That's the default behaviour. There is nothing to configure. You can set
Apache to use the registry to determine what program to use, however
(ScriptInterpreterSource).
> o Create c:\usr\bin and copy c:\perl\bin\perl.exe into c:\usr\bin.
>
> This works for other drives besides c: of course, if Apache and Perl are
> installed on d:, say.
Why on earth would you do that? What's wrong with leaving perl where it is?
The faq was about how to get a shebang to work in Windows, not about moving
the interpreter around to no particular end for Apache. I'm surprised this
is a faq, as I've never seen anyone ask this question or ever come across
anyone on a Windows machine using a shebang to call perl outside of Apache.
It may have been applicable ten years ago, but 95/98/NT are no longer
supported (nor is Win2k, I believe) so even finding machines with these OSes
installed is often a challenge.
Matt
------------------------------
Date: Fri, 28 Oct 2005 00:46:10 GMT
From: "A. Sinan Unur" <1usa@llenroc.ude.invalid>
Subject: Re: FAQ 3.23 How can I get "#!perl" to work on [MS-DOS,NT,...]?
Message-Id: <Xns96FCD34B7B376asu1cornelledu@127.0.0.1>
Ron Savage <ron@savage.net.au> wrote in news:200510289356.658181@ron:
> On Fri, 28 Oct 2005 08:03:01 +1000, PerlFAQ Server wrote:
>
> Hi
>
> Also, if people choose to run the Apache web server under Windows,
> and want Apache to run their scripts under Perl, then they need to do
> 3 things:
>
> o Have a she-bang line like this:
>
> #!/usr/bin/perl
>
> o Create c:\usr\bin and copy c:\perl\bin\perl.exe into c:\usr\bin.
This is completely unnecessary:
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\.pl\Shell\ExecCGI]
"command"="c:\\opt\\perl\\bin\\perl.exe -T \"%1\""
See http://httpd.apache.org/docs/2.0/mod/core.html#scriptinterpretersource
Sinan
--
A. Sinan Unur <1usa@llenroc.ude.invalid>
(reverse each component and remove .invalid for email address)
comp.lang.perl.misc guidelines on the WWW:
http://mail.augustmail.com/~tadmc/clpmisc/clpmisc_guidelines.html
------------------------------
Date: Thu, 27 Oct 2005 23:48:38 GMT
From: "Mike Schilling" <mscottschilling@hotmail.com>
Subject: Re: Microsoft Hatred FAQ
Message-Id: <qHd8f.6518$BZ5.2214@newssvr13.news.prodigy.com>
"David Schwartz" <davids@webmaster.com> wrote in message
news:djppjp$t5s$1@nntp.webmaster.com...
> Mike Schilling wrote:
>
>> "David Schwartz" <davids@webmaster.com> wrote in message
>> news:djpf90$pbm$1@nntp.webmaster.com...
>
>>> There is no different to Microsoft beween a bare computer and one
>>> preloaded with Linux or FreeBSD. One can quickly be converted to
>>> other with minimal cost of effort. In the market, bare PCs really do
>>> compete with Windows PCs.
>
>> There's a huge difference to the non-techy consumer. One of the
>> buggest reasons Linux has had a reputation of being harder to use
>> than Windows was the fact that Linux had to be installed, while
>> Windows just booted up.
>
> Is that really true? I mean, I remember distributions of Linux that you
> could just stick in the CD, boot from CD, and you were up in minutes.
> Installing was as simple as pushing the 'install to hard drive' button.
If all of the hardware is known to Linux, that can work, and Linux has
gotten much better at being able to recognize and auto-configure lots of
devices.
But picture that, when this was less true, you wanted to buy a machine with
the newest-whizbang graphics card or disk controller. For Windows, the
manufacturer would make sure the proper drivers are installed and
configured. For Linux, you the consumer had to find a driver, install it,
configure it (the phrase "drive geometry" sticks in my head) and deal with
the lack of useful feedback if anything goes wrong.
I haven't tried to install Windows since Windows 95 was current. I recall
that as being pretty horrible, but for different reasons. There was a step
where, after the basic OS had been installed onto the hard drive, and it was
time to sense other devices. Half the time, this would simply hang the
computer, and you'd have to start over from scratch. Most of the rest of
the time, it would find most of the devices and make really awful guesses
about the rest, like thinking the sound card was a CD player. I suspect
this works better these days too.
------------------------------
Date: 6 Apr 2001 21:33:47 GMT (Last modified)
From: Perl-Users-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin)
Subject: Digest Administrivia (Last modified: 6 Apr 01)
Message-Id: <null>
Administrivia:
#The Perl-Users Digest is a retransmission of the USENET newsgroup
#comp.lang.perl.misc. For subscription or unsubscription requests, send
#the single line:
#
# subscribe perl-users
#or:
# unsubscribe perl-users
#
#to almanac@ruby.oce.orst.edu.
NOTE: due to the current flood of worm email banging on ruby, the smtp
server on ruby has been shut off until further notice.
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
#To request back copies (available for a week or so), send your request
#to almanac@ruby.oce.orst.edu with the command "send perl-users x.y",
#where x is the volume number and y is the issue number.
#For other requests pertaining to the digest, send mail to
#perl-users-request@ruby.oce.orst.edu. Do not waste your time or mine
#sending perl questions to the -request address, I don't have time to
#answer them even if I did know the answer.
------------------------------
End of Perl-Users Digest V10 Issue 8580
***************************************
