HDTenEightyP/NetNews huggingface dataset:
From: yorton@turtle11.rtsg.mot.com (James J. Yorton)
Subject: Re: noclobber
Reply-To: yorton@rtsg.mot.com
Organization: Motorola Inc., Cellular Infrastructure Group
Date: Fri, 24 Jul 1992 14:01:07 GMT

In article <91773@bu.edu>, tesco@bumetb.bu.edu (Dances With Babes) writes:
|> Does anyone know if the "set -o noclobber" command is atomic?
|> I'm trying to implement a semaphore in ksh, and this would be a good way,
|> provided it's atomic (that it,  no two people can create the file at the same time).
|> 
|> If it's not atomic, anyone know of a good way
|> to implement a semaphore using ksh?
|> 
|> 
|> -tesco

Sorry I don't have the answer to your specific question.

But before people go off and try doing things with "set -o noclobber",
I wanted to let people know there is a bug with "set -o noclobber"
in the latest release of ksh from the Toolchest (ksh88g), at least
on some systems, specifically mine (Sun OS 4.1.1).

In a phrase, it doesn't work.  It's as if you have noclobber
disabled, even though set -o shows it's enabled, so overwriting a
file with > redirection silently overwrites that file.

I passed my findings on to David Korn and here was his response:

: Date: Wed, 8 Apr 92 23:39:33 EDT
: 
: This is a serious problem.  The code uses POSIX style
: macros to test file attributes.  However, since the type
: field for regular files can be zero, my code can't
: distinguish between files that don't exist and regular
: files.
: 
: I will have to put together an 'h' point release for
: release very soon.
: 
: Thanks for reporting the problem.  It looks as if
: most people do not use noclobber or else the problem
: would have been reported sooner.
: 

If you're not running ksh88g you should be OK as the problem
is NOT present in previous releases of ksh from the Toolchest.
The Toolchest says the latest release is still 88g and said
ksh-92 is coming.  No mention of ksh88h yet.  If anyone knows
what's going on with 88h, let me know or post it.  Thanks.

--------------------------------------+---------------------------------------
Jim Yorton                            | Telephone:  +1 708-632-6695
Motorola Inc., General Systems Sector |
Cellular Infrastructure Group         | internet:  yorton@rtsg.mot.com
1501 - West Shure Drive               | uucp:      ...!uunet!motcid!yorton
Mail Drop:  IL27-3227                 |
Arlington Heights, IL  60004          |
USA                                   |
Newsgroups: comp.unix.shell
From: Tom Christiansen <tchrist@convex.COM>
Subject: Re: Sort problem . .
Originator: tchrist@convex.convex.com
Reply-To: tchrist@convex.COM (Tom Christiansen)
Organization: CONVEX Realtime Development, Colorado Springs, CO
Date: Wed, 29 Jul 1992 13:25:26 GMT
X-Disclaimer: This message was written by a user at CONVEX Computer
              Corp. The opinions expressed are those of the user and
              not necessarily those of CONVEX.

From the keyboard of Sm@cerberus.bhpese.oz.au (Scott Merrilees):
:Tom Christiansen <tchrist@convex.COM> writes:
:>	ps axu | (read line; echo "$line"; sort +3rn) 
:
:ps axu | sed 1d | sort -nr +3

I was trying to avoid sending the data stream through yet another
process in the chain.  But apparently starting a subshell was too much
trouble:

$ time sh -c 'ps axu | (read line; echo "$line"; sort +3rn)' > /dev/null
    1.508u 1.635s 0:01.89 50.0% 0+0k 46+3io 113pf+0w

$ time sh -c "ps axu | sed 1d | sort -nr +3" > /dev/null
    1.482u 1.534s 0:01.81 50.0% 0+0k 32+5io 106pf+0w

On the other hand, a bit to my surprise, this

    #!/usr/bin/perl
    open(PS, "ps axu |") || die "cannot fork: $!";
    print scalar(<PS>);
    while (<PS>) { push(@lines, $_); push(@idx, (split(' '))[3]); }
    print @lines [ sort { $idx[$b] <=> $idx[$a]; } 0..$#idx ];

runs in this time:

    0.779u 0.107s 0:00.53 50.0% 0+0k 3+0io 82pf+0w

Which is better than either of the pure shell solutions.

--tom

-- 
"GUIs normally make it simple to accomplish simple actions and impossible
to accomplish complex actions."   --Doug Gwyn  (22/Jun/91 in comp.unix.wizards)

     Tom Christiansen           tchrist@convex.com      convex!tchrist
Newsgroups: comp.unix.shell
From: etxmesa@eos.ericsson.se (Michael Salmon)
Subject: Re: TCSH on Solaris
Reply-To: etxmesa@eos.ericsson.se (Michael Salmon)
Organization: Ericsson Telecom AB
Date: Thu, 30 Jul 1992 09:29:34 GMT

In article <17316@autodesk.COM>, 
stevel@Autodesk.COM (Steven W. Litras) writes:
|> Has anybody gotten TCSH 6.02 to run on Solaris 2.0? I'm about to give it
|> a try, but would prefer not to reinvent the wheel.

One of my collegues has been working on it, I'm not sure how happy he
is with it but I use it and it seems to work OK so far. Here is a diff
for the config.h:

*** config.h    Wed May 27 08:35:57 1992
--- config/config.sysv4 Tue May 26 21:10:24 1992
***************
*** 37,43 ****
   * BSDJOBS    You have BSD-style job control (both process groups and
   *            a tty that deals correctly
   */
! #undef BSDJOBS
  
  /*
   * BSDSIGS    You have 4.2-style signals, rather than USG style.
--- 37,43 ----
   * BSDJOBS    You have BSD-style job control (both process groups and
   *            a tty that deals correctly
   */
! #define BSDJOBS
  
  /*
   * BSDSIGS    You have 4.2-style signals, rather than USG style.
***************
*** 51,57 ****
   *            This may or may not be true.  For example, Apple Unix
   *            (OREO) has BSDJOBS and BSDSIGS but not BSDTIMES.
   */
! #undef BSDTIMES
  
  /*
   * BSDNICE    Your system uses setpriority() instead of nice, to
--- 51,57 ----
   *            This may or may not be true.  For example, Apple Unix
   *            (OREO) has BSDJOBS and BSDSIGS but not BSDTIMES.
   */
! #define BSDTIMES
  
  /*
   * BSDNICE    Your system uses setpriority() instead of nice, to
***************
*** 120,126 ****
   *            SYSV_ECHO: Support only sysv escapes (\nnn)
   *            NONE_ECHO: Pure echo.
   */
! #define ECHO_STYLE BOTH_ECHO  /* BSD options only */
  
  /****************** local defines *********************/
  #ifndef BSDTIMES
--- 120,126 ----
   *            SYSV_ECHO: Support only sysv escapes (\nnn)
   *            NONE_ECHO: Pure echo.
   */
! #define ECHO_STYLE BSD_ECHO   /* BSD options only */
  
  /****************** local defines *********************/
  #ifndef BSDTIMES

-- 

Michael Salmon

#include	<standard.disclaimer>
#include	<witty.saying>
#include	<fancy.pseudo.graphics>

Ericsson Telecom AB
Stockholm
Newsgroups: comp.unix.shell
From: chet@odin.INS.CWRU.Edu (Chet Ramey)
Subject: Re: sh equivalent of csh's `source` wanted
Keywords: help
Organization: Case Western Reserve University, Cleveland, OH (USA)
Date: Fri, 31 Jul 92 12:33:58 GMT

In article <ericw.712530389@hobbes> ericw@hobbes.amd.com (Eric Wedaa) writes:
>HELP!!!  One of my users needs the Bourne Shell equivalent of csh's 
>`source` command.  I don't think this is possible?  Any suggestions?

Use `.'.
-- 
``The use of history as therapy means the corruption of history as history.''
	-- Arthur Schlesinger

Chet Ramey, Case Western Reserve University	Internet: chet@po.CWRU.Edu
From: zackx@sco.COM (Zack Xu)
Newsgroups: comp.unix.shell
Subject: Aho, Kernighan & Weinberger paper on awk
Date: 26 Jul 92 20:45:53 GMT
Distribution: na
Organization: SCO Canada, Inc.

Does anyone has the paper 

Awk - A Pattern Scanning and Text Processing Language (Second Edition)

by Aho, Kernighan and Weinberger

online?

If so, can you kindly send it to me via email?

Thanks!

Zack
Newsgroups: comp.unix.shell
From: Tom Christiansen <tchrist@convex.COM>
Subject: Re: Sort problem . .
Originator: tchrist@convex.convex.com
Reply-To: tchrist@convex.COM (Tom Christiansen)
Organization: CONVEX Realtime Development, Colorado Springs, CO
Date: Fri, 31 Jul 1992 11:55:59 GMT
X-Disclaimer: This message was written by a user at CONVEX Computer
              Corp. The opinions expressed are those of the user and
              not necessarily those of CONVEX.

From the keyboard of messina@netcom.com (Tony Porczyk):
:Tom Christiansen <tchrist@convex.COM> writes:
:>I am constantly incensed by massively
:>UNIX-ignorant programmers who inflict brain-damaged software on 
:>the rest of us who actually try to use it.
:
:Have you ever though[t]
:of actually treating this as another solution, renaming the changed
:code and using it when it is called for, or would it be too much to
:ask to use something without "wrappers"?   What I mean is:  Are you
:sure there is always only ONE way to do things?

I'm a pluralistic kind of guy.  I've tried everything, and from 
experience, come to learn that there are some things that don't 
work as well.  That seems pretty easy to understand, doesn't it?

I have a fair number of things in ~/bin that are "fixed-by-hacking"
versions of std utils, and many more such things in ~/scripts that 
are "fixed-by-wrapping" versions of std utils.

Hacking on source is almost always a solution that will come back
to haunt you.  Sometimes things are so broken you have to fix
them, but if you just want to munge the output, heroic measures
are overkill.

Splitting something up ps to put the header to stderr and the rest of
data to stdout is a myopic solution.


--tom

-- 
    Tom Christiansen      tchrist@convex.com      convex!tchrist

    "* Unix is a footnote of AT&T Bell Laboratories."
                             --Barry Shein
From: friedman@gnu.ai.mit.edu (Noah Friedman)
Newsgroups: comp.unix.shell
Subject: Re: file name completion for ksh?
Date: 24 Jul 92 08:20:18 GMT
	<1992Jul23.033602.19925@news.eng.convex.com>
	<1992Jul23.082108.29589@news.acns.nwu.edu>
Distribution: na
Organization: Free Software Foundation, 675 Mass Ave. Cambridge, MA 02139
In-reply-to: navarra@casbah.acns.nwu.edu's message of 23 Jul 92 08:21:08 GMT

In article <1992Jul23.082108.29589@news.acns.nwu.edu> navarra@casbah.acns.nwu.edu (John Navarra) writes:
>In article <1992Jul23.033602.19925@news.eng.convex.com> tchrist@convex.COM (Tom Christiansen) writes:
>>From the keyboard of sjs@netcom.com (Stephen Schow):
>>:The ksh is hands down the best.  As the last response showed, there is usually
>>:a way to do it in the ksh.  In addition, the ksh has tons of over features
>>:that none of the other shells can even touch.  
>>
>>Down boy.  That's overkill.  Read the tcsh man page some day.
>>
>        And zsh has even more features! Ruf! Ruf!

   Ah yes, features.  What would we do without them?  Probably get more
work done, instead of endlessly tweaking our environments to no useful end.

   I probably have the most complicated initialization scripts that anyone
has ever devised (if you don't believe me, email me and we can arrange to
compare).  One of these days, when I come to my senses, I'll switch to rc
and use it vanilla.

   Features?  You need features like you need poison ivy.
From: friedman@gnu.ai.mit.edu (Noah Friedman)
Newsgroups: comp.unix.shell
Subject: Re: Sort problem . .
Date: 31 Jul 92 15:46:26 GMT
	<1992Jul31.115559.11391@convex.com>
Organization: Free Software Foundation, 675 Mass Ave. Cambridge, MA 02139
In-reply-to: tchrist@convex.COM's message of 31 Jul 92 11:55:59 GMT

In article <1992Jul31.115559.11391@convex.com> tchrist@convex.COM (Tom Christiansen) writes:
>Splitting something up ps to put the header to stderr and the rest of
>data to stdout is a myopic solution.

   Agreed.  I consider the header to be "useful" information.  I've used it
plenty of times in shell scripts to decide what field in the rest of the
output was the one I wanted, since it's almost impossible to expect that
different implementations of PS will ever be otherwise compatible. 
It's not just there for humans to read!  Don't mess with it.
From: dd6kdn0@baarsa.bell-atl.com (Maurer)
Newsgroups: comp.unix.shell
Subject: Re: Aho, Kernighan & Weinberger paper on awk
Date: 27 Jul 92 15:06:50 GMT
Distribution: na
Organization: Bell Atlantic

In article <1992Jul26.204553.12851@sco.COM> zackx@sco.COM (Zack Xu) writes:

>Does anyone has the paper 
>Awk - A Pattern Scanning and Text Processing Language (Second Edition)
>by Aho, Kernighan and Weinberger
>online?
>If so, can you kindly send it to me via email?
>Thanks!
>Zack

I am also interested in this, if it is not just a draft of
the APL book.

Thanks

===============================================================
| Name:  Paul T. Maurer                Phone: (908)577-3594   |     
| Comp:  Consultant@Bell Atlantic                             |
| Email: dd6kdn0@baarsa.bell-atl.com                          |
===============================================================
Newsgroups: comp.unix.shell,comp.unix.programmer
From: rvloon@cv.ruu.nl (Ronald van Loon)
Subject: file locking in shell scripts
Originator: rvloon@wodan.cv.ruu.nl
Date: Thu, 23 Jul 1992 12:43:27 GMT
Organization: University of Utrecht, 3D Computer Vision Research Group

I have the following problems:

Somewhere on our system is a log-file. This logfile is used to gather
statistical information. However, it is possible that people write to the file
at the same time, thus resulting in either the merge of the input-streams or
total garbage in the file.

How can I - within a shell script - lock the file exclusive for writing ? If
that's not possible, what do I need to use to do so from C, for example ?

Thanks for your answers in advance.
-- 
Ronald van Loon (rvloon@cv.ruu.nl) 3DCV Group, Utrecht, The Netherlands.

Insanity is not bad in itself as long as there is a system to it. (H.Liberg)
Healthy absurdism once in a while has never hurt anybody (me)
From: ericw@hobbes.amd.com (Eric Wedaa)
Newsgroups: comp.unix.shell
Subject: Re: sh equivalent of csh's `source` wanted
Keywords: help
Date: 31 Jul 92 18:28:08 GMT
Organization: Advanced Micro Devices, Inc.

boyd@prl.dec.com (Boyd Roberts) writes:


>RTFM

I tried that first.  Unfortunately the FM is "Cryptic as Usual"
Maybe I should have read the manpage on csh-source and then 
grepped through the manpage on sh looking for something close.

>>Ericw

(OK, so I win this weeks award for Stupid F!@#$%G Questions ;)
--
Eric Wedaa  -  eric.wedaa@amd.com | Two more kinds of lies...
{ames apple uunet}!amd!ericw      |     Release Dates, and Benchmarks
Advanced Micro Devices, M/S 167 PO Box 3453 Sunnyvale, CA 94088-3453
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Newsgroups: comp.unix.shell
From: Sm@cerberus.bhpese.oz.au (Scott Merrilees)
Subject: Re: Sort problem . .
Organization: BHP, Newcastle, Australia
Date: Wed, 29 Jul 1992 04:46:00 GMT

Tom Christiansen <tchrist@convex.COM> writes:

>From the keyboard of boyd@prl.dec.com (Boyd Roberts):
>:In article <1992Jul27.140110.846@news.eng.convex.com>, Tom Christiansen <tchrist@convex.COM> writes:
>:> ps axu | ( sed 1q ; sort -nr +3 ) 
>:Eh?  Since when does sed do `unbuffered' reads?
>:Nice idea though...
>Hey -- it surprised the heck out of me too!  But it did indeed work
>without losing lines on a test run.  Unforunately, I ran but one test, 
>and must have just gotten lucky, cause now I lose lines.
>This does seem to work:
>	ps axu | (read line; echo "$line"; sort +3rn) 

ps axu | sed 1d | sort -nr +3

Sm
-- 
Scott Merrilees, BHP Information Technology, Newcastle, Australia
Internet: Sm@bhpese.oz.au   Phone: +61 49 40 2132   Fax: ... 2165
Newsgroups: comp.unix.shell
From: chung@cis.ohio-state.edu (Michael Chung)
Subject: How to compile a shell script?
Originator: chung@shaggyman.cis.ohio-state.edu
Organization: The Ohio State University, Department of Computer and Information Science
Date: Tue, 21 Jul 1992 12:18:04 GMT


	Is there any way I can compile a shell script file so that it can
run faster?

	thanx.

--
michael..
Newsgroups: comp.unix.shell,comp.unix.questions
From: Harald.Eikrem@delab.sintef.no
Subject: Re: What's wrong with this sed command?
Organization: SINTEF DELAB, Trondheim, Norway.
	<1992Jul23.090023.17661@physiol.su.OZ.AU>
	<1992Jul23.192253*Harald.Eikrem@delab.sintef.no>
Date: 23 Jul 92 19:45:12

I just sed....:)
! ! 	sed 's?: (\./)*?: ?'		WRONG WRONG WRONG
! 
! You can do that with GNU sed.  One more reason for everybody to rm /bin/sed

Not to mislead anybody, the egrep (...) still becomes \(...\) in GNU sed.
From: tchrist@convex.COM (Tom Christiansen)
Newsgroups: comp.unix.shell
Subject: Re: Sort problem . .
Date: 31 Jul 92 00:08:22 GMT
Reply-To: tchrist@convex.COM (Tom Christiansen)
Organization: CONVEX Realtime Development, Colorado Springs, CO
Originator: tchrist@convex.convex.com
X-Disclaimer: This message was written by a user at CONVEX Computer
              Corp. The opinions expressed are those of the user and
              not necessarily those of CONVEX.

From the keyboard of messina@netcom.com (Tony Porczyk):
:boyd@prl.dec.com (Boyd Roberts) writes:
:>In article <7=pmx9.messina@netcom.com>, messina@netcom.com (Tony Porczyk) writes:
:>> 
:>> BTW, since when is stderr reserved for "non-information"?  Frankly, I
:>> say send to stderr anything that is non-essential in the redirection of
:>> stdout or in piping of stdout, such as sorting.
:
:>Standard error is for _errors_.
:>If it's `non-essential' then don't output it in the first place.
:
:Do you get all those answers from a book?  Let me ask you a question -
:does a usefulness of a utility make any difference, or is it all
:according to what you found written somewhere?  I mean, have you ever
:tried being *flexible* to accomplish your task? 

Boyd is dead right here.  I am constantly incensed by massively
UNIX-ignorant programmers who inflict brain-damaged software on 
the rest of us who actually try to use it.  You know, the ones who
simply don't have any concept of how filters should work, what 
stderr is for, how to parse options, what the exit status 
should be used for, or who only supply an interactive interface.

Expected output should go out to stdout.  Exceptional output related
to diagnostics or other error messages should go out stderr.  

Period.

--tom
-- 
    Tom Christiansen      tchrist@convex.com      convex!tchrist
    If you have ever seen the grim word "login:" on a screen, your mind
    is now a wholly-owned subsidiary of The Death Star.
                John Woods in <14105@ksr.com> of comp.unix.bsd
Newsgroups: comp.unix.shell
From: boyd@prl.dec.com (Boyd Roberts)
Subject: Re: Sort problem . .
Organization: Digital Equipment Corporation - Paris Research Laboratory
Date: Thu, 30 Jul 1992 09:49:25 GMT

In article <1992Jul30.071744.9926@ibmpcug.co.uk>, dylan@ibmpcug.co.uk (Matthew Farwell) writes:
> In article <1992Jul29.191614.18102@news.eng.convex.com> tchrist@convex.COM (Tom Christiansen) writes:
> >
> >*Never* hack source when a wrapper will do. And some (most?) people 
> >don't even have source.
> 
> Of course, if you don't have source, you can always do it with adb :-)
> 

Never adb binaries when a wrapper will do.  And most people don't even
have adb  :-)


Boyd Roberts			boyd@prl.dec.com

``When the going gets wierd, the weird turn pro...''
From: storm@cs.mcgill.ca (Marc WANDSCHNEIDER)
Newsgroups: comp.unix.shell
Subject: ioctl Screw up w/tcsh under SunOS 4.1.1
Date: 30 Jul 92 00:50:29 GMT
Organization: McGill University, Montreal, Canada




Been trying to get tcsh up and working lately, and have been have some problems
gettin the job control to work.

For some reason, when I first load tcsh, I get the following message:

Warning: no access to tty (Inappropriate ioctl for device).
Thus no job control in this shell.


A trip through the code in sh.c didn't really shed all  that much light
on the matter, and #undef'ing VFORK didn't help.

Has anybody else had this problem, and if so, what can be done to get rid of
it?  I really cannot live without job control....

Marc 'em!

-- 
  storm@cs.mcgill.ca           McGill University         C program run.  Run  
  Marc Wandschneider           Montreal, CANADA          Program run! PLEASE!
      "When 900 years old you reach, look as good you will not." - Yoda
				"Ow!" -J.F.K.~
Newsgroups: comp.unix.shell
From: storm@cs.mcgill.ca (Marc WANDSCHNEIDER)
Subject: Re: ioctl Screw up w/tcsh under SunOS 4.1.1
Organization: McGill University, Montreal, Canada
Date: Thu, 30 Jul 1992 01:03:24 GMT

In article <1992Jul30.005029.22216@cs.mcgill.ca> storm@cs.mcgill.ca (Marc WANDSCHNEIDER) writes:
>
>
>
>Been trying to get tcsh up and working lately, and have been have some problems
>gettin the job control to work.
>
>For some reason, when I first load tcsh, I get the following message:
>
>Warning: no access to tty (Inappropriate ioctl for device).
>Thus no job control in this shell.

D'oh!  I already have the answer:  Just tried the .02 sources instead, and
found the following in the FAQ:

9.  I compiled tcsh using gcc, and when I start up it says:
    tcsh: Warning no access to tty (Invalid Argument).
    Thus no job control in this shell

    Your <sys/ioctl.h> file is not ansi compliant. You have one of 3 choices:
        a. Run fixincludes from the gcc distribution.
        b. Add -traditional to the gcc flags.
        c. Compile with cc.


SOrry for the bandwidth.  Maybe this will have helped somebody else trying
to build .01

Marc 'em!


-- 
  storm@cs.mcgill.ca           McGill University         C program run.  Run  
  Marc Wandschneider           Montreal, CANADA          Program run! PLEASE!
      "When 900 years old you reach, look as good you will not." - Yoda
				"Ow!" -J.F.K.~
Newsgroups: comp.unix.shell
From: boyd@prl.dec.com (Boyd Roberts)
Subject: Re: Sort problem . .
Organization: Digital Equipment Corporation - Paris Research Laboratory
Date: Thu, 30 Jul 1992 09:44:28 GMT

In article <7=pmx9.messina@netcom.com>, messina@netcom.com (Tony Porczyk) writes:
> 
> BTW, since when is stderr reserved for "non-information"?  Frankly, I
> say send to stderr anything that is non-essential in the redirection of
> stdout or in piping of stdout, such as sorting.

Standard error is for _errors_.

If it's `non-essential' then don't output it in the first place.


Boyd Roberts			boyd@prl.dec.com

``When the going gets wierd, the weird turn pro...''
Newsgroups: comp.unix.shell
From: Harald.Eikrem@delab.sintef.no
Subject: Re: tcsh in the future - what should it be like?
Organization: SINTEF DELAB, Trondheim, Norway.
	<1992Jul27.031238.10376@chpc.utexas.edu>
	<1992Jul27.215202*Harald.Eikrem@delab.sintef.no>
	<smr.712419130@hitkw14>
	<1992Jul31.010903*Harald.Eikrem@delab.sintef.no>
Date: 31 Jul 92 15:29:29

tcsh hints --

You may bind e.g. F-keys to perform your 500-times-a-day commands by

   bindkey -c key-seq command

and it wont even hit the command history, if that's what you so badly want
to avoid.  You may even

   bindkey -c key-seq \!$EDITOR

if you know what I mean.

And a history-search-backward + newline function might be set up as

   bindkey -s key-seq '\ep\n'

See?  You enter the start of the command you want reexecuted and hit
the chosen key.....  Pling.

  ~~h
Newsgroups: comp.unix.shell
From: Tom Christiansen <tchrist@convex.COM>
Subject: Re: Sort problem . .
Originator: tchrist@pixel.convex.com
Reply-To: tchrist@convex.COM (Tom Christiansen)
Organization: CONVEX Realtime Development, Colorado Springs, CO
Date: Wed, 29 Jul 1992 12:54:41 GMT
X-Disclaimer: This message was written by a user at CONVEX Computer
              Corp. The opinions expressed are those of the user and
              not necessarily those of CONVEX.

From the keyboard of Harald.Eikrem@delab.sintef.no:
:I can't think of a way to get a SVID2 ps to produce anywhere
:close to what that the requester obviously wanted to sort on, i.e. %CPU
:and %MEM.

There's a lesson here, folks.

--tom
-- 
    Tom Christiansen      tchrist@convex.com      convex!tchrist

    "* Unix is a footnote of AT&T Bell Laboratories."
                             --Barry Shein
From: stevel@Autodesk.COM (Steven W. Litras)
Newsgroups: comp.unix.shell
Subject: TCSH on Solaris
Date: 28 Jul 92 17:26:39 GMT
Organization: Autodesk Inc., Sausalito CA, USA

Has anybody gotten TCSH 6.02 to run on Solaris 2.0? I'm about to give it
a try, but would prefer not to reinvent the wheel.


Thanks,
Steve

--
Steven W. Litras          /\     |                                     /\
Autodesk, Inc.	         //\\    |                                    //\\
stevel@autodesk.com     ///\\\   |                                   ///\\\
(415)332-2344x2510     Autodesk  |                                  Autodesk
Newsgroups: comp.unix.shell