home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.os2.misc
- Path: sparky!uunet!haven.umd.edu!darwin.sura.net!wupost!gumby!destroyer!ubc-cs!unixg.ubc.ca!kakwa.ucs.ualberta.ca!news
- From: kurtk@ee.ualberta.ca (Kurt Klingbeil)
- Subject: Using CMD.EXE instead of PMSHELL.EXE
- Message-ID: <1992Aug12.155015.14039@kakwa.ucs.ualberta.ca>
- Sender: news@kakwa.ucs.ualberta.ca
- Nntp-Posting-Host: bode.ee.ualberta.ca
- Organization: University Of Alberta, Edmonton Canada
- Date: Wed, 12 Aug 1992 15:50:15 GMT
- Lines: 23
-
- Could someone please explain what core functionality PMSHELL provides;
- i.e. apart from GUIness... ?
-
- If one uses CMD.EXE as the primary shell, does one lose such features
- as being able to start the DOS box, and switch between concurrent tasks,
- or is it just that I haven't figured it out yet?
-
- I guess I'm not in bad company... it seems the MKS hasn't figured it out
- yet either. Job control isn't supportted in their korn shell. They said
- that as soon as IBM provides the hooks, they will do job control.
-
- It would appear that the DOS box, along with task management are PM
- apps, and that as it stands, how to do these things with the OS/2 kernel
- is either undocumented, or just too complex (i.e. write it all yourself) ?
-
- Maybe it is just that CMD.EXE is unnessarily primitive... It seems to me
- that ina multitasking OS, something as basic and fundamental as
- job control from the CLI should come out-of-the-box and not require
- detailed explorations of internal nuances, and ftp-forays; procs and killem,
- and the not-yet-extant fgem, bgem, and niceem should have been in the initial
- release. Or not?
-
- -- k(sup)2
-