Anything that uses Win32::* modules will need to be rewritten. For example,
scripts that use Win32::ODBC will need to be rewritten using DBI instead.
Scripts that run as services can easily be installed into specific
run-levels by your UNIX administrator.
Anything that uses OLE to Windows appl
Title: RE: Win32 to UNIX
in that case, you don't have time to be reading email -- you'd better get started re-writing!!!
;-)
> -Original Message-
> From: Briggs, Larry [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, November 20, 2002 07:10
> To: 'Simon
unfortunately we used Win32::* through out. And set up some programs a
services.
-Original Message-
From: Simon Oliver [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 20, 2002 7:03 AM
To: Briggs, Larry
Cc: '[EMAIL PROTECTED]'
Subject: Re: Win32 to UNIX
Briggs, Larry w
Briggs, Larry wrote:
Hi All
My office has decided to listen to the hardware guys instead of the
developers/programers. So I have be asked to find out what it would take to
convert all of our perl programs from win32 to UNIX. I currently have a web
system in place running ActiveState Perl v5.6.1
Hi All
My office has decided to listen to the hardware guys instead of the
developers/programers. So I have be asked to find out what it would take to
convert all of our perl programs from win32 to UNIX. I currently have a web
system in place running ActiveState Perl v5.6.1 build 633 on two NT
Eric,
The Berkeley DB format is not the same from
platform to platform.
When I ran into this problem, I needed to dump each
record
(using Data::Dumper, and use eval) to enter it into
the new database.
There may be other ways, but this quick and dirty
way solved the problem
> My DB_File is version 1.73 whereas the Unix one is 1.76.
But the underlying database format isn't reflected in the DB_File version. Use
dbinfo.pl (included with the Unix version of db_file.pm I believe) to determine
that. I get file version 6 on Windows NT and file version 3 on Unix, and am
a
