lt;[EMAIL PROTECTED]>
cc:
Subject: RE: converting NT batch files to Unix shell
... re-write those in Perl. Test the Perl version on NT. It will work on
UNIX as well :)
Am I right, Jared?
- Kirti
(Perl Newbie)
-Original Message-
Sent: Wednesday, February 19, 200
. re-write those in Perl. Test the Perl version on NT. It will work on UNIX as
well :)
Am I right, Jared?
- Kirti
(Perl Newbie)
-Original Message-
Sent: Wednesday, February 19, 2003 6:10 PM
To: Multiple recipients of list ORACLE-L
The best thing to do is document the logic in th
hi sree!
since the shells (whether korn, bash or any other) are very powerful
and cmd.exe is a rather poor thing, i would suggest the following:
either:
find someone who is capable of shell programming and has been on NT
or can read the screen after typing HELP in cmd.exe
he will have no problem
The best thing to do is document the logic in the script,
throw it away, and rewrite it in the shell of your choice.
Unless of course you can find some automated utility
to convert batch files to shell.
Jared
kommareddy sreenivasa <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
02/19/2003 01
> see what the NT script was doing. (I'm a 'reformed' MCSE, so
> I'm not speaking from the standpoint of a Unix bigot, I just
> know a better world when I see it.)
Aaah - you have seen the Light! Welcome aboard.
Srinivas,
The answer unfortunately is 'no', but knowing a little bit about the
'i
This may not be what one wants to hear when given this task (at one time I wouldn't),
in the absence of any super tools, being that Unix commands are so powerful and
feature rich compared to NT, I would take each NT script, determine its purpose and
write the Unix script from scratch with that g
