Running Perl Scripts in SFU

News	Softpanorama Perl Page	See also	Recommended Links	Recommended Articles	Reference
Komodo integration	SlickEdit integration				Humor

Among scripting languages SFU 3.5 provides Perl 5.6.1:

$ perl -v

This is perl, v5.6.1 built for x86-interix-thread

The following dynamic modules have been included:

B
ByteLoader
DB_File
Data/Dumper
Devel/DProf
Devel/Peek
File/Glob
GDBM_File
IO
IPC/SysV
NDBM_File
Opcode
POSIX
SDBM_File
Socket
Sys/Hostname
Sys/Syslog
attrs
re

This version is pretty adequate for most applications but, of course, does not understand extensions introduced in version 5.8. This is actually ActiveState Perl implementation, and you can get a newer version of Interix Perl from the Interopsystems tool warehouse.

Perl Version 5.8.3 for SFU 3.5
binary: /pkgs/3.5/perl-current-bin.tgz
src: /src/perl
Added: 2004-06-18

This is the latest stable release of the most popular scripting language, complete with the DBI database interface module, DBD::ODBC for connecting via ODBC, and DBD::Sybase to connect to any Sybase or SQL Server using FreeTDS.

I am wondering if direct replacement by a newer version from ActiveState will also work.

SFU features include extensions to Perl that allow direct manipulation of the Windows Registry. You can use this to edit registry keys on the fly, without forcing a reboot – a useful tool when tuning applications. You can also use SFU to add Windows Management Instrumentation to your UNIX applications, allowing you to use tools like Microsoft Operations Manager 2005 to control your ported applications, without writing extra management code.

Remember, SFU is a collection of UNIX software components. Some of it is Win32 based software (like NFS client and ActiveState Perl). Some of it is Interix based software. Interix is a UNIX subsystem that runs on top of Windows. It is a completely separate subsystem from Win32. In the Interix environment you use UNIX conventions and you expect UNIX behavior. In the Win32 environment, you use Windows conventions and you expect Windows behavior.

Notes:

This is a Spartan WHYFF (We Help You For Free) site written by people for whom English is not a native language. Some amount of grammar and spelling errors should be expected.
The site contain some broken links as it develops like a living tree... Please try to use Google, Open directory, etc. to find a replacement link (see HOWTO search the WEB for details). We would appreciate if you can mail us a correct link.

Google Search
Open directory	Research Index

News

HP/Name Service Migration Scripts

This section describes the shell and perl scripts that can migrate your name service data either from source files or NIS maps to your Active Directory. These scripts are found in /opt/ldapux/migrate/ads. The two shell scripts migrate_all_online.ads.sh and migrate_all_nis_online.ads.sh migrate all your source files or NIS maps, while the perl scripts migrate_passwd_ads.pl, migrate_hosts_ads.pl, migrate_networks_ads.pl, migrate_protocols_ads.pl, migrate_rpc_ads.pl, migrate_services_ads.pl, and migrate_group_ads.pl and so forth migrate individual maps. The shell scripts call the perl scripts.
The migration scripts require perl, version 5 or later, which is installed with the NIS/LDAP Gateway in /opt/ldapux/contrib/bin/perl.

Perl Version 5.8.3 for SFU 3.5

This is the latest stable release of the most popular scripting language, complete with the DBI database interface module, DBD::ODBC for connecting via ODBC, and DBD::Sybase to connect to any Sybase or SQL Server using FreeTDS.
binary: /pkgs/3.5/perl-5.8.3-bin.tgz
src: /src/perl

running windows perl script in SFU.

Q: I am facing problem in executing perl scrits, that are windows specific, in Interix. In my perl script I have a command
use Win32::OLE

When I try to run the perl script it says “Can't locate Win32/OLE.pm in @INC”.
I have cross checked that I have installed ActiveState perl in SFU custom installation.
Any help would be appreciated.

A: I think it needs to be determined that you are running the Perl you think you are.
There is an Interix version of Perl and a Win32/ActiveState Perl.
From your message it looks like the Interix Perl is running.
The ActiveState Perl is a standalone thing.
If you want to run the AS-Perl from Interix then you will need to do some configuration out of the norm.
- remove the Interix Perl
- create an interfacing script (a la /usr/contrib/win32/bin scripts) to AS-Perl

bash perl and php on windows

Juha Saarinen juha at saarinen.org
Thu Mar 4 02:00:21 EST 2004

Previous message: bash perl and php on windows
Next message: bash perl and php on windows
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Bret Hughes wrote:

> I have had an inquiry about running our primary application on windows
> rather than linux.  The app consists of a bunch of shell (sh) scripts
> and some perl and a whole boot load of php for the primary user
> interface.  Oh yeah postgresql db too.
> 
> Is there a general rule for how big a deal this is going to be?   Anyone
> done it or something similar? There is quite a bit of filesystem access
> and the first thing I thought of is the frigging / vs \ as a directory
> separator.

Funny how much this sort of question pops up... try the freely 
downloadable Windows Services For UNIX 3.5 (SFU).

http://www.microsoft.com/windows/sfu/default.asp

I've got a Bash prompt, plus Perl running on WinXP here. Performance 
with SFU is within 10% of Win32 according to Microsoft, so it may be 
what you're looking for.

-- 
Juha

Anil Dash Microsoft nix

What if Microsoft shipped "Linux for Windows"?

On Friday, Microsoft released a free download of Windows Services for Unix version 3.5, a significant upgrade to the Unix integration product they've been offering for about 5 years. I've used it before, mostly as an NFS client, but there's some remarkable changes this time around.

The Services for Unix (SFU) are free to download and consist of an entire Unix environment installed as a native subsystem on Windows. For those of you who don't know your Windows NT/2000/XP/2003 history, the NT kernel has always supported running multiple subsystems, and NT has always shipped with a Posix-compliant command-line subsystem, largely for checklist compatibility with some now-obsolete government requirements. Unlike tools like Cygwin, which run on top of the standard Windows shell, SFU implements the Interix subsystem as a true peer to the Windows shell.

But to that base SFU 3.5 adds some extraordinary new features. Both the Korn and C shells are included. A single rooted file system is now supported, finally abandoning the need to include drive paths in applications or scripts. And speaking of scripts, SFU includes Perl 5.6.1. There's even the full complement of standard Unix utilities, including awk, grep, sed, tr, cut, tar, cpio, less, at, cron and batch. Essential applications like bind, sendmail and ftp? Present. Even gcc, gdb, and make are in the package.

There's a lot of other stuff, of course, including the first tools to expose Windows' long-dormant file system support for junctions as symbolic links in the Interix environment. There's the above-mentioned NFS support. There's all kinds of user account synchronization features. A real version of telnet.

But what's most astounding, perhaps, is not the fact that I can now untar most perl scripts as-is and have them run on Windows. (I'll be testing out Movable Type shortly, of course.) What amazes me is that this product has slipped under the radar for so long. Any bets as to whether Longhorn includes this functionality out of the box? And It seems to me that this collection of functionality will rapidly allow Windows users to cover 90% of the things that OS X users are doing with Darwin. Interesting.

Running Perl Scripts in SFU

News

Recommended Links