SCOUG Logo


Next Meeting: Sat, TBD
Meeting Directions


Be a Member
Join SCOUG

Navigation:


Help with Searching

20 Most Recent Documents
Search Archives
Index by date, title, author, category.


Features:

Mr. Know-It-All
Ink
Download!










SCOUG:

Home

Email Lists

SIGs (Internet, General Interest, Programming, Network, more..)

Online Chats

Business

Past Presentations

Credits

Submissions

Contact SCOUG

Copyright SCOUG



warp expowest
Pictures from Sept. 1999

The views expressed in articles on this site are those of their authors.

warptech
SCOUG was there!


Copyright 1998-2024, 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.

The Southern California OS/2 User Group
USA

SCOUG-Programming Mailing List Archives

Return to [ 06 | March | 2000 ]

<< Previous Message <<


Date: Mon, 6 Mar 2000 13:31:23 PST
From: "Steven Levine" <steve53@earthlink.net >
Reply-To: scoug-programming@scoug.com
To: scoug-programming@scoug.com
Subject: SCOUG-Programming: Re: korn shell

In , on 03/06/00
at 12:25 AM, dallasii@kincyb.com said:

>The thing in my mind that defines UNIX at the command line prompt is that
>each stage in a pipe occurs as a process that happens in parallel to the
>other stages of the pipe.
>As far as I know, this is not the case for all versions of
>DOS, OS/2, and any products from M$.

OS/2 handles pipe like UNIX. DOS can't because it can't multitask.

The hard part about porting the ksh to OS/2 is not the pipe; it's the
process model.

UNIX creates processes by forking and image of the and then overwriting
the "child" image with the executable. This can be emulated in OS/2, but
it takes work.

>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?

The OS/2 API's are there. For example Process Command provides command
line tools to do this stuff. It's more that CMD.EXE is a child of
COMMAND.COM and that COMMAND.COM is a very limit shell. The features were
just not put in.

>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.

CMD.EXE replacements such as 4OS2 support executable extensions. CMD.EXE
even support execproc which is roughly equivalent to the UNIX #!.

Steven

--
----------------------------------------------------------------
"Steven Levine" MR2/ICE 2.08 #10183 Warp4/FP11
----------------------------------------------------------------

=====================================================

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".

=====================================================


<< Previous 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.