is equivalent to DOS/Warp/M$ 'con' device.
this would allow you to monitor a partial result of the
pipe. 'tee' literally taps off the pipe to send a copy of
the data flowing through the pipe to a file.
Again, without waiting for the end of the whole
set of commands that make up the pipe.
It doesn't have to end to see the results. (literally)
You can do this in OS/2 using queues or some other
construct like named pipes, but we're spinning off into
nebulous realms of no standard notation to use at the
prompt for stuff that would again require some new
shell and it's own set of commands to use this stuff.
Non-UNIX systems that I'm aware of handle this stuff
running one program till completed, storing the results in
some temporary file, and then running the next program in the
pipe, till completed.
Also the process control seems to be an area that OS/2 doesn't
quite have all the fine points that UNIX has.
The little 'go' utility seems to provide rough equivalants
to 'kill', 'ps' and 'fg' (restart in foreground),
but what to replace the suspend character
'^Z' and 'bg' (restart in background) with I don't know -
maybe someone else has some suggestions?
Another area I recall he had to make provision for is
to handle file extensions, which was especially usefull
for .CMD files. The context that korn shell came up
on this list was my finding that he didn't get it perfect,
and some special provision was needed for putting REXX
filters in pipes.
PS>
PS> And just out of curiosity, can ksh (if that's the name) be run _from_
ksh.exe in the world of extensions, but basicly yes that's the name.
On second thought, maybe it was pdksh.exe for 'public domain ksh',
but you can call the executable what you want. :-)
PS> CMD.EXE or do you have to modify the CONFIG.SYS line (SET
PS> OS2_SHELL=x:\OS2\CMD.EXE)?
Either way works fine, as I recall.
My experience was that it's easiest not to completely scrap CMD.EXE,
but to change your thinking about it. It's not a shell but a
library of functions that are still useful in their own right.
Between those, and what sed provides, with a few
wrapper shell functions and alias's, you can emulate
most of the basic UNIX commands, without cluttering up your
file system with an excess of EMX ports of rather minor
programs.
PS>
PS> > The guy who ported it to OS/2 (can't remember his
PS> > name offhand) did a good job from what I could tell,
PS>
PS> And if you contact him, can you find out what source modifications he
PS> had to make?
I think the source is available, but I never looked at it.
Next time I get back to Downey, maybe.
I know somewhere back in Downey, I've got the source for
the shell I wrote for the API class. :-)
PS>
PS> Thanks!
PS>
PS> - Peter
PS>
Regards,
Dallas E. Legan II / dallasii@kincyb.com / leganii@surfree.com
=====================================================
To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-programming".
For problems, contact the list owner at
"rollin@scoug.com".
=====================================================
>> Next Message >>
Return to [ 06 |
March |
2000 ]
The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA
Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS
RESERVED.
SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group.
OS/2, Workplace Shell, and IBM are registered trademarks of International
Business Machines Corporation.
All other trademarks remain the property of their respective owners.
