HDTenEightyP/NetNews huggingface dataset:
From: messina@netcom.com (Tony Porczyk)
Subject: Re: Sort problem . .
Date: Thu, 30 Jul 92 19:14:36 GMT
Organization: Messina Software

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? 

t.
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: Tue, 28 Jul 1992 10:29:38 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 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?
:
:    prl313 ; @{echo 1 ; echo 2 ; echo 3} | @{sed 1q ; cat}
              ^^                        ^^^^^^
Sure looks like perl to me. :-)

: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) 

I really loathe stdio sometimes, but I'm sure we're stuck with it
until the end of time.  The buffering on both reading and writing 
needs to be controllable without modifying the program or tricking
it into thinking you're a tty.

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

    "* Unix is a footnote of AT&T Bell Laboratories."
                             --Barry Shein
From: tchrist@convex.COM (Tom Christiansen)
Newsgroups: comp.unix.shell
Subject: Re: simple csh question
Date: 28 Jul 92 10:33:00 GMT
Reply-To: tchrist@convex.COM (Tom Christiansen)
Organization: CONVEX Realtime Development, Colorado Springs, CO
Originator: tchrist@pixel.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 bdbryan@eng.clemson.edu:
:Does anyone know why the following shell code snippet for the csh keeps giving
:me a "@: Expression syntax" error message? Code follows:
:
:foreach record (`cat somefile`) # `somefile' contains simple ascii records. one number
:                                # to a line.
:  @ ybacc = $ybacc + ((($record - $bave) * ($record - $bave))/$bcount)
:end
:
:All the above variables are simple integer variables that have been previously
:calculated. 

Would you believe it's because you've no space between your "/" and $bcount?

You can't predict the csh.  You can't trust it.   Just say no.

Thanks for yet another fine entry to csh.whynot .

--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
From: tim@mal-s1.gatech.edu (Tim Shelling)
Newsgroups: comp.unix.shell
Subject: Re: csh/ksh comparison questions?
Date: 22 Jul 92 13:40:07 GMT
Organization: Georgia Tech Res. Inst./Modeling & Analysis Lab

Firstly, expert users of BASH (GNU's Bourne Again SHell) will
be able to give you solutions to all these problems.
Meanwhile, if you must with ksh....

In <1992Jul21.183727.20364@gmuvax2.gmu.edu> rjackson@gmuvax2.gmu.edu (Richard L Jackson Jr) writes:

>I did a simple comparison of CSH and KSH.  I am asking this
>group for solutions to csh feature that ksh appears to lack.
>I am using ULTRIX 4.1, VAX 8530.

>1) set filec or file completion
On the command line, go into the vi-editing mode (I don't know how to do
this in emacs mode), and place the cursor on the name of the file you want to 
expand. Hit '*' which will expand the current filename as if '*' were 
appended to it. Or hit '\' and the current word will be replaced with 
"the longest common prefix of all filenames matching the current word with
an asterik appended." There's a bunch of other nifty things... These features
are present in BASH also.


>2) concurrent sessions inadvertently use the same history
>   file.  Appending a pid to the history file at login may help
>   but there is no logout facility to remove the file.

With KSH you can trap signals and execute programs on reception of
those signals. I've seen someone trap the EXIT  
signal (or something like that) and have it run a shell, which
did exactly that -- it removed a process-dependent sh-history file.
Sometimes the shell was terminated abnormally and hisotry files
would build up. So it's good to put them into a directory and
once a week clean them out.

>3) how does one invoke a .logout script at ksh exit?
See above.


-- 
 --------------------------
|Timothy J. Shelling, CmpE |"Paired opposites define your longings --
|  tim@mal-s2.gatech.edu   |  and those longings imprison you."
| gt2540b@prism.gatech.edu |				    -- Zensunni Whip
Newsgroups: comp.unix.shell
From: chet@odin.INS.CWRU.Edu (Chet Ramey)
Subject: Re: [ vs. [[ in ksh
Organization: Case Western Reserve University, Cleveland, OH (USA)
Date: Tue, 21 Jul 92 11:49:28 GMT

In article <Brp7Lr.AI5@root.co.uk> gwc@root.co.uk (Geoff Clare) writes:

>The work-around for this one is [ X"$X" = X"$Y" ], which is pretty robust.
>However, there are some things that are even harder to protect against,
>and you begin to wonder whether it's worth it.  Consider [ -f "$FILE" ],
>a very common usage, and what happens when FILE contains `='.

The Posix.2 specification of test contains a much more robust algorithm
based on the number of arguments to the test command that avoids many
of the traditional problems.

Bash implements this algorithm; so does the standalone GNU shellutils
`test'.

Chet
-- 
``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: steimann@quando.quantum.de (Ulrich Steimann)
Newsgroups: comp.unix.shell
Subject: Re: Setting variables to ASCII codes in csh scripts
Keywords: CSH ASCII ESCAPE CODES VARIABLES
Date: 31 Jul 92 09:15:45 GMT
Organization: Quantum Software GmbH, Dortmund, Germany

In article <1992Jul30.180327.10859@galileo.cc.rochester.edu> eric@prodigal.psych.rochester.edu (Eric Hansen) writes:
>
>I'd like to 'echo' a table of variables to standard output, and since
><tab> doesn't always move to the same location on the screen (not in Unix,
>anyways), I'd like to do a carriage return (no linefeed), and then move
>the cursor right to a specific column.  Sort of like this:
>
>echo -n $CODE1$VAR1
>echo -n $CODE2$VAR2
>echo $CODE3$VAR3
First, you have to do 
	echo "$CODE$VAR"
because the shell strips multiple blanks and gets confused with
special characters.

>Does anyone know how to set variables to ASCII sequences of escapes and
>what not?!  I could just 'echo' them out if it would be easier, but
>it seems difficult to embed escape sequences in a file using vi (to put
>the clear sequence in an 'echo' statement, I had to 'clear >> FILE' and
>then cut and past!).

Move the cursor to an empty line and type
	!clear
The output of clear is then placed in the line. (try "man vi")
For Cursor right, switch to input-mode and type CTRL-V followed by
your cursor-right-key. The cursor-right-sequence is then palced in the
text.

Is everybody on your machine using a vt100-Terminal? Hard-coded
Sequences may cause strange effects on other terminals.

>Also, where can I get a listing of all the vt100
>control codes and escape sequences?

man terminfo, termcap, untic, tput, ...

>
>Thanks greatly!
>
>- Eric

Greetings,
	 UST
-- 
Ulrich Steimann, Quantum GmbH, D-4600 Dortmund | Warum heiraten ?
email: steimann@quantum.de                     | 
FAX: 0231-75441-115                            | Leasing ist doch
-----------------------------------------------| so einfach !
From: tim@mal-s1.gatech.edu (Tim Shelling)
Newsgroups: comp.unix.shell
Subject: Re: csh/ksh comparison summary. Thanks!
Date: 28 Jul 92 15:13:25 GMT
Organization: Georgia Tech Res. Inst./Modeling & Analysis Lab

In <1992Jul24.142605.16455@gmuvax2.gmu.edu> rjackson@gmuvax2.gmu.edu (Richard L Jackson Jr) writes:

>|> I did a simple comparison of CSH and KSH.  I am asking this
>|> group for solutions to csh feature that ksh appears to lack.
>|> I am using ULTRIX 4.1, VAX 8530.
>|> 
>|> 1) set filec or file completion

>In ksh, using vi-style command line editing, try

><ESC>* or <ESC>\ 

>where <ESC> is the ESCAPE key.
>There is a slight difference.  I'm not a tcsh user, but users tell
>me that <ESC>\ is quite similar to tcsh's file name completion.

>In ksh, using emacs-style command line editing, try

><ESC><ESC>

One more thing... In BASH, in either editing mode, you can start typing
in the name of a file, then hit <TAB>, and if the shell can complete it
with an existing file, it will print them and add a space. If not, it
will list the files that match if * were appended to it.

So let's say you have these files in a directory:
-rw-r--r--  1 tim          3180 Jul 28 10:46 3_ai.doc
-rw-r--r--  1 tim          2565 Jul 28 10:47 3_ai_1.doc
-rw-r--r--  1 tim         11451 Jul 28 10:48 3_ai_2.doc
-rw-r--r--  1 tim          4675 Jul 28 10:49 3_ai_3.doc

If you type:
more 3_<TAB>

the shell will list the matching files for you: 
3_ai.doc    3_ai_2.doc
3_ai_1.doc  3_ai_3.doc  

If you type in some more characters, you'll get:
You > more 3_ai_1<TAB>
BASH> more 3_ai_1.doc

If you type in the name of a directory instead of a file, 
BASH will complete that directory name and add '/'.

-- 
 --------------------------
|Timothy J. Shelling, CmpE |"Paired opposites define your longings --
|  tim@mal-s2.gatech.edu   |  and those longings imprison you."
| gt2540b@prism.gatech.edu |				    -- Zensunni Whip
From: ericw@hobbes.amd.com (Eric Wedaa)
Newsgroups: comp.unix.shell
Subject: sh equivalent of csh's `source` wanted
Summary: help, I need this
Keywords: help
Date: 30 Jul 92 21:06:29 GMT
Organization: Advanced Micro Devices, Inc.

HELP!!!  One of my users needs the Bourne Shell equivalent of csh's 
`source` command.  I don't think this is possible?  Any suggestions?

>>Ericw

--
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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Xref: sparky comp.unix.shell:3079 comp.unix.questions:9252
From: montnaro@ausable.crd.ge.com (Skip Montanaro)
Newsgroups: comp.unix.shell,comp.unix.questions
Subject: What's wrong with this sed command?
Date: 21 Jul 92 21:03:21 GMT
Reply-To: montanaro@crd.ge.com (Skip Montanaro)
Followup-To: poster
Distribution: comp
Organization: GE Corporate Research & Development, Schenectady, NY


I'm trying to use sed to trim off all leading "./" patterns from source
filenames in make rules. On an IBM RS6000 the following works as I expected:

   echo 'enquire.o: ./././enquire.c' | sed 's?: \(\./\)\{1,\}?: ?'

yielding

   enquire.o: enquire.c

On our other systems (Sun-4, HP, SGI, and Motorola 68040) it prints
different results. The HP doesn't trim any "./" patterns, while the Sun,
Moto, and SGI all trim one pattern.

Have I incorrectly specified the sed command or are one (or more) of the
vendors' sed implementations incorrect? If so, which one(s)? I'm inclined to
believe the IBM is correct and the others are bugged.

(I suppose this is another argument for perl...)

Thanks,

--
Skip (montanaro@crd.ge.com)
From: tlg@uknet.ac.uk (Tim.Goodwin)
Newsgroups: comp.unix.shell
Subject: Re: Where does the sugar go? (was Re: Sort problem )
Date: 31 Jul 92 09:41:57 GMT
Organization: UKnet

In article <84902@netnews.upenn.edu> chip@eniac.seas.upenn.edu (Charles H. Buchholtz) writes:
>I agree, but I often wonder what to do with the output "sugar", such
>as prompts or headers, which are not well suited for filtering.
>...

UNIX is (was) a diet OS.  Sugar free.

I fume every time I want to say

    sccs delget `sccs info`

but can't.  This "sugar" is bitter to my taste.

Pragmatically, why not turn on the sugar with a command line flag?

Tim.
-- 
The GNU is in fact the legendary and much-berated | ; who am i
feeping creature - Malcolm Wallace.               | uknet.ac.uk!tlg
Newsgroups: comp.unix.shell
From: etxmesa@eos.ericsson.se (Michael Salmon)
Subject: Re: Sort problem . .
Reply-To: etxmesa@eos.ericsson.se (Michael Salmon)
Organization: Ericsson Telecom AB
Date: Fri, 31 Jul 1992 09:15:53 GMT

In article <33pmgah.messina@netcom.com>, messina@netcom.com 
(Tony Porczyk) writes:
|> 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? 
|> 
|> t.

I have seen very many flexible solutions to problems, many of them were
even good solutions, for a while at least. The usual result is that
some time in the future the flexible solution breaks and someone has to
do it right. 

I wish that I could quote the fortune on experience but my memory is
being a little too flexible today.

-- 

Michael Salmon

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

Ericsson Telecom AB
Stockholm
Newsgroups: comp.unix.shell
From: boyd@prl.dec.com (Boyd Roberts)
Subject: Re: Ron Heiby's ksh pushd and popd
Organization: Digital Equipment Corporation - Paris Research Laboratory
Date: Mon, 27 Jul 1992 10:47:48 GMT

In article <1992Jul24.191246.11410@ddsw1.mcs.com>, dattier@ddsw1.mcs.com (David W. Tamkin) writes:
> The normal prompt
> when logged in and in your home directory is:   host: hh:mm:ss [~]
>                                                 nn>

Sheesh...  But I want _micro-second_ resolution!


Boyd Roberts			boyd@prl.dec.com

``When the going gets wierd, the weird turn pro...''
From: smr@iti.org (Stephen Riehm)
Newsgroups: comp.unix.shell
Subject: Re: tcsh in the future - what should it be like?
Date: 29 Jul 92 14:12:10 GMT

Harald.Eikrem@delab.sintef.no writes:

>! I'd like to see a history mechanism that works like VMS' RECALL, i.e. 
>! type something like !vi .cs  and get the last vi command that edits 
>! .cshrc.  Simple, powerful concept; only a single command to learn. 

>It's there.  You just need to try.

care to enlighten us?? or are you still telling failed entrepreneurs
that there is a pot of gold at the end of every rainbow?

>! Also, the history list should save a command only if it is different 
>! from the last one.

>No way.  You will be able to reach the next *different* command in the

DISAGREE!
if you are developing something, and you get into a debug mode, the
usual sequence of commands goes something like:
    edit
    compile
    run ( or debug )
    edit
    compile
    ... ( ad infinitum )

if after doing this 30 times, the last 100 entries in your history are
the same three commands over and over, what if you then want to do
that really complicated sequence of commands which sets up a real
input file for this program, which has just been booted out of the
history list because you filled it up with the same commands repeated
n times. since most people I know ( myself EXcluded ) seem to have
histories of 50 commands, it doesn't give you much of a 'history' does
it? ( my history sits at around 250 at the moment, there are times
when I really want to boot it up to 500 too! )

Also, I would really love a 'merge_histories' feature, this is relevant
only if you have many tcsh's running at the same time, because when I
quit my XWindows session, by dumb luck or whatever, the last tcsh to
save the history seems to be the one I used the least, with all the
most boring, and least used commands in the history, any solutions?
anyone come up with some sort of .logout hack?

>! If both these questions have solutions already it only shows that tcsh 
>! has too many features.  I can't remember them so I don't use them.

>You have probably never made the attempt to find out.

it has been scientifically proven that the human mind can only comfortably
cope with between 5 and 7 things at one time ( under good stress free
situations, add stress it goes down to about .5 ), this being the case,
it is not a simply matter of reading the tcsh manual to find all the
features, I have read it many times, and i still find new things every
time, such is the price for not having hard disks in our heads!

catchya

-----------------------------------------------------------------
Stephen Riehm				   smr@pki-nbg.philips.de
PS: I know my From: line is wrong, but I don't know WHY!
"I used to be apathetic, but now i just don't care anymore" - me
Newsgroups: comp.unix.shell
From: erude@casbah.acns.nwu.edu (Erick Rudiak)
Subject: Re: Aho, Kernighan & Weinberger paper on awk
Organization: Northwestern University, Evanston, Illinois
Distribution: na
Date: Mon, 27 Jul 1992 15:10:27 GMT

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


	How about posting it if you get it?  Awk is my very most favoritest thing
to use in shell scripts, but the man page is much, much, much too meager.  Most
of the things I have learned about awk aren't even in the man page.  I learned
them second-hand from people who also learned them second-hand.  It's becoming a 
dubious tradition.

-- Erick
_____________________________________________________________________
                                                | 
I tell myself, hey, only fools rush in          | Erick Rudiak
Only time will tell if we stand the test of time| erude@nwu.edu
And all I know, you've got to run to win        |____________________
And I'll be damned if I'm left                  | "I'm not worthy..."
    caught up on the line                       |      \o/      \o/
    -- Van Halen, "Why Can't This Be Love"      | O__   \\  O__  \\
________________________________________________|_/__|__||__/__|_||__

Newsgroups: comp.unix.shell
From: rsalz@osf.org (Rich Salz)
Subject: Re: tcsh in the future - what should it be like?
Organization: Open Software Foundation
Date: Fri, 31 Jul 1992 16:32:27 GMT

In <1992Jul31.010903*Harald.Eikrem@delab.sintef.no> Harald.Eikrem@delab.sintef.no writes:
>! if after doing this 30 times, the last 100 entries in your history are
>! the same three commands over and over, what if you then want to do
>
>Have you ever seen a windowing environment?

If "history" were kept as an external file to which the shell appended,
you could use standard Unix utilities on it.  Many shells work this
way (ksh, bash, rc to name three (and omit others)).

Hacking [t]csh to use a real file-based history would be a lot of work,
but it could be done.

(On the other hand, I really wish someone would implement my proposed
/dev/mem hacker that would go in and change someone else's history...)
	/r$
Xref: sparky comp.unix.shell:3154 comp.unix.aix:8223
From: tesco@bumetb.bu.edu (Dances With Babes)
Newsgroups: comp.unix.shell,comp.unix.aix
Subject: Named pipes
Date: 27 Jul 92 20:05:23 GMT
Reply-To: tesco@bumetb.bu.edu (Dances With Babes)
Followup-To: comp.unix.programmer
Organization: Boston University


I have recently discovered named pipes but can't seem to get them to do
what I want.  Is it possible to use a background process to read from a
named pipe while many other processes write to that named pipe.
When i try to test this capability in the unix k shell the background
process ends.

ex. 
mknod testpipe p
cat testpipe &
ls > testpipe
The "cat" process ends after the ls is sent to the screen.

I've been told by IBM tech support that this is the way it supposed to work.
This is on an RS6000 running AIX ver 3.2.2. 

thanx
-tesco
From: zzassgl@uts.mcc.ac.uk (Geoff Lane)
Newsgroups: comp.unix.shell
Subject: Re: Learning from Unix shell sources
Date: 27 Jul 92 13:54:36 GMT
Organization: Manchester Computing Centre, Manchester, England, M13 9PL.


Thanks to everyone who replied.

Of those who offered an opinion all but two suggested that
the best place to learn shell implementation techniques was
from the sources to "rc" (the Unix re-implementation of the 
Plan 9 shell; the sources of the latest version were posted
recently.)  Many also commented that the sources to sh and 
bash were hairy in the extream and not good examples to
work from.

If you are curious, the two alternate suggestions were ksh
and/or tcsh from one person and a warning to avoid AT&T
source code if I ever wanted to distribute anything that I
wrote as a result (this wasn't sent from AT&T :-))

A book was also suggested ...

                Advanced UNIX programming
                Marc J. Rochkind
                Prentice-Hall 1985
                ISBN 0-13-011818-4
                ISBN 0-13-011800-1 (pbk.)


Apparently this book uses the construction of a shell based
on a subset of sh as a major example of programming
techniques.

-- 
Geoff. Lane.                                  Janet: zzassgl@uk.ac.mcc.uts
UTS Sys Admin, Manchester Computing Centre, Oxford Rd, Manchester, M13 9PL
Newsgroups: comp.unix.shell
From: etxmesa@eos.ericsson.se (Michael Salmon)
Subject: Re: Setting variables to ASCII codes in csh scripts
Keywords: CSH ASCII ESCAPE CODES VARIABLES
Reply-To: etxmesa@eos.ericsson.se (Michael Salmon)
Organization: Ericsson Telecom AB
Date: Fri, 31 Jul 1992 11:46:10 GMT

In article <1992Jul31.091545.15162@quando.quantum.de>,
steimann@quando.quantum.de (Ulrich Steimann) writes:
|> In article <1992Jul30.180327.10859@galileo.cc.rochester.edu> eric@prodigal.psych.rochester.edu (Eric Hansen) writes:
[...]
|> >Does anyone know how to set variables to ASCII sequences of escapes and
|> >what not?!  I could just 'echo' them out if it would be easier, but
|> >it seems difficult to embed escape sequences in a file using vi (to put
|> >the clear sequence in an 'echo' statement, I had to 'clear >> FILE' and
|> >then cut and past!).
|> 
|> Move the cursor to an empty line and type
|> 	!clear

I guess that you mean !!clear

|> The output of clear is then placed in the line. (try "man vi")
|> For Cursor right, switch to input-mode and type CTRL-V followed by
|> your cursor-right-key. The cursor-right-sequence is then palced in the
|> text.
|> 
|> Is everybody on your machine using a vt100-Terminal? Hard-coded
|> Sequences may cause strange effects on other terminals.
|> 
|> >Also, where can I get a listing of all the vt100
|> >control codes and escape sequences?
|> 
|> man terminfo, termcap, untic, tput, ...

Also, recently posted to comp.sources.3b1, there is techo that combines
tput with echo. 

-- 

Michael Salmon

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

Ericsson Telecom AB
Stockholm
Newsgroups: comp.unix.shell