HDTenEightyP/NetNews huggingface dataset:
From: davidsen@ariel.crd.GE.COM (william E Davidsen)
Newsgroups: comp.unix.shell
Subject: Re: ksh 1, perl 2 - ksh or perl for scripting?
Date: 23 Dec 92 16:04:43 GMT
Reply-To: davidsen@crd.ge.com (bill davidsen)
Organization: GE Corporate R&D Center, Schenectady NY

In article <ASH.92Dec21095237@ulysses.mr.ams.com>, ash@ulysses.mr.ams.com (Alan Harder) writes:
| 
| Hi, all.  We are currently trying to decide if we should move from
| /bin/sh as our language for production scripting to ksh, or if we
| should move to perl instead.  Is anyone out there using perl as their
| production scripting language of choice? 

  You should definitely move!

  Now, as to where, I prefer ksh for most problems, although there are a
number of things which work more easily in perl. I find that ksh does
redirection and argument truncation in a way which is easier to enter
and read (for me) than perl. Things like ${name%.*} are trivial to write
in ksh, but somewhat more verbose in perl. For these reasons I find I
use perl very sparingly, possibly only a few times a month.

  Certainly the retraining will be faster if you go to ksh, since you
can use 100% of the things you already know, and can use the same shell
for programming and interractive use, which speeds learning.

  Perl is more powerful, but seems to provide too many solutions for my
taste, certainly for simple problems. I like a language where there is
one clear way to solve a problem rather than one which has many ways,
since I find that programmers tend to waste a lot of time looking for
the single elegant way to solve the problem, rather than finding one way
which is clearly best and then useing it. This is particularly true of
really clever perl programmers I have known, who seem to feel the need
to write "impressive" code instead of code which just works.

-- 
bill davidsen, GE Corp. R&D Center; Box 8; Schenectady NY 12345
    Keyboard controller has been disabled, press F1 to continue.
From: sanjiv@cse.unl.edu (Sanjiv K. Bhatia)
Newsgroups: comp.unix.shell
Subject: Re: Opening up remote xterm windows?
Date: 22 Dec 1992 18:21:47 GMT
Organization: University of Nebraska--Lincoln	
Distribution: world
NNTP-Posting-Host: cse.unl.edu

Try the following script called xrsh.

----- cut here -----
#!/bin/sh
# xrsh - launch X applications on a remote host.
#
# Usage: xrsh [-v | -vv] [-l userid] [-display display] host [command]
#   If command is omitted, xrsh launches an xterm on the remote host.
#   The -v option turns on verbose mode.  This is useful in finding
#     out why the xrsh command didn't work.
#   The -vv option turns on very verbose mode.  This is useful in finding
#     out why the xrsh command really didn't work.
#   The -l option selects the userid to login as on the remote system.
#   The -display option overrides the DISPLAY environment variable.
#   See the Caveats at the end of this file.
#
#   This version by Felix Lee and Scott Schwartz
#

# Do arguments...
QUIETLY="</dev/null >/dev/null 2>&1"
LOGIN=""
while expr "$1" : '-.*' >/dev/null
do
	# ... Are we verbose?
	case $1 in
	-vv*)	shift; QUIETLY=""; set -x
		;;
	-v*)	shift; QUIETLY=""
		;;
	esac

	# ... Override display?
	case $1 in
	-d*)	shift; DISPLAY=$1; shift ;;
	esac

	# ... Alternate login?
	case $1 in
	-l*)	shift; LOGIN="-l $1"; shift ;;
	esac
done

# ... Set DISPLAY to the local host name, if necessary.
WIN=`expr x$DISPLAY : x".*:\(.*\)"`
case $DISPLAY in
''|:*|unix:*)
#	DISPLAY=`(domainname) 2>/dev/null` &&
#		DISPLAY=`hostname`.${DISPLAY}:${WIN} ||
#		DISPLAY=`hostname`:${WIN}
	DISPLAY=`hostname`.`awk '{print $2} {exit}' /etc/resolv.conf`:0.0
	;;
esac
export DISPLAY

# ... Fix path to include X.
case $PATH in
*X11*) ;;
*) PATH=$PATH:/usr/bin/X11; export PATH;;
esac

# ... With no arguments, just start up an xterm.
case $# in
0)	eval 'xterm -n "`hostname`" ${1+"$@"}' $QUIETLY '&'
	exit
esac

# ... First argument is the host.
HOST=$1
shift

# ... Enable access for the host.
eval 'xhost +$HOST >/dev/null' $QUIETLY

# ... If no command is given, start an xterm.
case $# in
0)	COMMAND="xterm"
	;;
*)	COMMAND="$@"
	;;
esac

# ... Try to recognize an xterm command and push a name option on.
set $COMMAND
case $1 in
xterm|*/xterm)
	COMMAND="$1 -n `echo $HOST | sed -e 's/\..*//'`\ "
	shift
	COMMAND="$COMMAND $*"
esac

# ... Fire away.
rsh $HOST $LOGIN -n \
"sh -c 'DISPLAY=$DISPLAY;PATH=$PATH export DISPLAY PATH;($COMMAND) $QUIETLY &'"
exit

# Caveats:
#   Don't try piping to xrsh.  It won't work.
#   Don't try to use quotes in the command.  It's really hairy.
#   xrsh makes a (probably misguided) attempt to recognize "xterm"
#     commands and insert a "-name" specification for you.  This
#     fails ignominiously if you say "xrsh foo 'xterm; xterm'".
#     You're better off putting "-name" in yourself.
#   "xrsh foo" is not quite the same as "xrsh foo xterm".  The
#     first gives xterm the "-ls" option, the second does not.


--
Sanjiv K. Bhatia		Department of Mathematics & Computer Science
sanjiv@redbird.umsl.edu		University of Missouri -- St. Louis
voice: (314)-553-6520		8001 Natural Bridge Road
				St. Louis, MO 63121-4499
From: rob@xyzoom.info.com (Rob Lingelbach)
Newsgroups: comp.unix.shell
Subject: Re: wanted: tutorial about sh programming
Date: 27 Dec 92 07:46:03 GMT
Reply-To: rob@xyzoom.info.com (Rob Lingelbach)
Organization: Altruistic Intentions, Hollywood CA

In article <1992Dec26.210309.11538@Celestial.COM> ray@Celestial.COM (Ray Jones) writes:

>should do the trick.  Variables will be replace inside double quotes,
>however, not inside single quotes.  Therefore;

This answers the question I asked in another thread that follows this
one, regarding quoting in ksh.  Thank you Ray.

-- 
Rob Lingelbach KB6CUN | 2660 Hollyridge Dr LA CA 90068 213 464 6266 (voice) 
rob@xyzoom.info.com   | "I care not much for a man's religion whose dog or 
robl@netcom.com       |  cat are not the better for it."  --Abraham Lincoln
Newsgroups: comp.unix.shell
From: jpr@jpradley.jpr.com (Jean-Pierre Radley)
Subject: Re: stripping cr/lf's
Date: Thu, 31 Dec 1992 21:12:54 GMT
Organization: Unix in NYC

In article <1992Dec31.071312.6153@netcom.com> kasajian@netcom.com (Kenneth Kasajian) writes:
>
>How do I strip the cr's from a text file?  There must be a standard
>unix way of doing it!


SCO, at least, provides dtox, and the reverse, xtod.

In ex, just
	%s/^V^M//

Or use this script:

	:
	# addcr : adds CRs
	# delcr : removes CRs
	[ $# -ne 2 ] && echo Usage\: $0 infile outfile && exit
	case $0 in
		*addcr) sed s+$++ <$1 >$2;;
		*delcr) sed s---g <$1 >$2;;
	esac


or this one:

	:
	# cr+-: adds CR's if they're not present, deletes them if they are.
	# use as a filter
	sed '
	s---g
	t
	s+$++
	t
	'
-- 
Jean-Pierre Radley   Unix in NYC   jpr@jpr.com   jpradley!jpr   CIS: 72160.1341
From: hartman@informix.com (Robert Hartman)
Newsgroups: comp.unix.shell
Subject: Re: find
Keywords: find grep
Date: 31 Dec 92 18:49:29 GMT
Organization: Informix Software, Inc.

In article <1992Dec30.154242.26079@netcom.com> kasajian@netcom.com (Kenneth Kasajian) writes:
>What is the unix command for DOS' 'find'.  I would like to
>display directories only with ls.  so I do an ls -F -1 and
>then display only those lines with a / .
>
>Also.  How do I do I get grep to include in its file list all
>files in the current directory and files in all sub-directories?
>
>kenny

There are two ways of I can think of offhand to get a list of all
decendent directories:

	find . -type d -print
	ls -RF1 | grep :

-r
Newsgroups: comp.unix.shell
From: jonas@uiag.ch (Jonas Furrer (317))
Subject: Exporting environment variables form nested scripts
Organization: EMCH+BERGER
Date: Wed, 23 Dec 1992 12:09:23 GMT

How can I export environment variables from nested shell scripts?

Here is my trial:  (all scripts are csh-scripts)

% generate ---------+
                    |
                    v /* in generate */

              source project_env ----+
                                     |
                                     v /* in project_env

                                     setenv AMS1 /project/test1
                                     setenv AMS2 /project/test2

                                     |
                    +----------------+
                    |
% <-----------------+
% printenv |grep AMS
% /* nothing */

Thanks. Jonas.


          +---------------------+---------------------------+
          |Jonas Furrer         |E-Mail : jonas@uiag.ch     |
          |Emch + Berger AG     |Tel    : +41 31 25 23 23   |
          |Gartenstrasse 1      |Fax    : +41 31 25 16 85   |
          |3001 BERN (CH)       |                           |
          +---------------------+---------------------------+
From: fnord@panix.com (Cliff Heller)
Newsgroups: comp.unix.shell
Subject: Re: File completion in Ksh.
Date: 31 Dec 92 16:09:22 GMT
Organization: Right Bleedin' Church of Libertine Obfuscatology

In <1992Dec30.201551.201@news.mentorg.com> ram@court.mentorg.com (Ram Tumuluri) writes:

>Is there an equivalent of "set filec" (csh) mechanism in ksh. If not is there
>any easy mechanism to get file completion in ksh.

If you are using emacs command-line editing 
(set -o emacs or export EDITOR=emacs) 

then ESC-ESC does file completion.

I don't know what the equivalent key sequence is in vi editing mode (the
default).

-- 
    / \      Reverend fnord                 | "King Kong died for your sins!"
   /   \     fnord@panix.com                | 
  / <0> \                                   | "Don't just eat a hamburger, 
 /_______\   Church of Obfuscatology, Inc.  |  eat the HELL out of it!"
From: ccsis@sunlab1.bath.ac.uk (Icarus Sparry)
Newsgroups: comp.unix.shell
Subject: Re: trap
Date: 1 Jan 93 17:38:57 GMT
Organization: Bath University Computing Services, UK

In the referenced article, calvin@wshb.csms.com ( WSHB employee) writes:
>
>  trap "rm $LOCATE1/LCK..Order $LOCATE3/$$.*; clear; exit" 0 1 2 9 15
>

Trap 1 is called when the process receives 'SIGHUP'. Typically this
is when you hang up you modem, or disconnect your terminal, close your
X window.

Trap 2 is called when the process receives 'SIGINT'. Typically this is
because you have typed the keyboard interrupt character, Control-C or
Delete are common choices for this character

Trap 9 is never called

Trap 15 is called when the process receives 'SIGTERM'. Typically this is
because you used the 'kill' command to kill this process.

Trap 0 is special. It is called when the script finishes. This is what is
happening in your case. The obvious thing to do is to redefine the trap
command just before you call 'exit 3'. Something like

	trap '' 0 ; exit 3
From: stevet@oakhill.sps.mot.com (Steve Turner)
Newsgroups: comp.unix.shell
Subject: signal traps in Bourne -- HELP!
Date: 21 Dec 92 22:38:04 GMT
Organization: Motorola Inc., Austin, Texas

Is there a good way to tell a signal service routine to know which signal
invoked it?  The script below shows how I'm approaching this, but
surely there is a more elegant way... any suggestions?  Please
send email to me directly. I'll post a summary if there is interest. 

----------------- script follows -------------

#!/bin/sh

sigtrap()
{
	case $SIGNAL in
		1) echo killed by SIGHUP ;;
		2) echo killed by SIGINT ;;
		# etc
	esac
}

sigcatch1() 
{ 
	SIGNAL=1; sigtrap; exit $SIGNAL 
}
sigcatch2() 
{ 
	SIGNAL=2; sigtrap; exit $SIGNAL 
}

# etc for 32 signals

trap sigcatch1 1
trap sigcatch2 2

# etc for 32 signals

# then run the main program below...
read WORD

----------------- end script -----------

Happy Holidays,
-- 
 Steve Turner                     Motorola, Inc.
 stevet@risc.sps.mot.com          RISC Design Automation
 512.891.8728                     Austin, TX
From: cek@sdc.boeing.com (Conrad Kimball)
Newsgroups: comp.unix.shell
Subject: Re: quoting in scripts: ksh
Date: 27 Dec 92 20:00:41 GMT
Distribution: na
Organization: Boeing Computer Services (ESP), Seattle, WA

In article <1992Dec27.032422.14161@xyzoom.info.com> rob@xyzoom.info.com (Rob Lingelbach) writes:

[ describes problem passing quoted arguments to commands in a script ]

>mg $OPTS $* $FILE | less

Try:
mg $OPTS "$@" $FILE | less

See the manpage for details on how $* and $@ differ when enclosed in quotes.
-- 
--
Conrad Kimball       | Client Server Tech Services, Boeing Computer Services
cek@sdc.boeing.com   | P.O. Box 24346, MS 7A-35
(206) 865-6410       | Seattle, WA  98124-0346
From: mike@pacsoft.com (Mike Stefanik)
Newsgroups: comp.unix.shell
Subject: Re: Handling of '&' by shell
Date: 29 Dec 92 18:02:42 GMT
Organization: Pacific Software Group, Riverside, CA

In article <1992Dec28.162641.11402@pt.com> mliu@pt.com (Fred Liu) writes:
>I am just wondering why the shell creates a background process first if
>the '&' is at the end of a command line.  It would be nice to have the
>shell check the command first and then fire up the process. [...]

What happens when you're dealing with something more complex than a
single command and it's arguments.  For example:

	$ ( while read line; do echo $line; done < file ) | wc -l &

Now certainly, the shell could go through all sorts of gyrations to make
sure that the `while' loop is correctly formed and that the `wc' program
actually exists.  Consider if there was more than an `echo' inside the
above loop -- for example, what if there was another nested loop similar
to the one above?

What happens is that you have made a relatively simple function in the
shell (ie: forking in the background) an order of magnitude more complex,
for no better reason than aesthetics.  IMHO, it is far better to fork and
let the child shell do it's own complaining.

-- 
Mike Stefanik  mike@pacsoft.com  ...!uunet!pacsoft!mike  (909) 681-2623
Pacific Software Group, Riverside, CA
Newsgroups: comp.unix.shell
From: eswgcs%v8.decnet@v7.vitro.com
Subject: killing process by UID
Reply-To: cstump@vitro.com
Organization: Vitro Corporation
Date: Wed, 30 Dec 1992 14:01:12 GMT

I am looking for the best way to detect all processes owned by a given user
and kill them.  I would appreciate any ideas in both C and in shell code.

Thanks, 
   Chuck Stump
From: kevinl@tisdec.tis.tandy.com
Date: 31 Dec 92 07:59 CST
Newsgroups: comp.unix.shell
Subject: Re: File completion in Ksh.
Message-ID: <28300012@tisdec.tis.tandy.com>
Nf-ID: #R:news.mentorg.com:201:tisdec.tis.tandy.com:28300012:000:955
Nf-From: tisdec.tis.tandy.com!kevinl    Dec 31 07:59:00 1992


	I'm not sure if this is what you're looking for, but this is
the only method of file completion in Korn that I know:

$ ls
Makefile
back
ls.out
main.cxx
main.o
string
string.cxx
string.hxx
string.o

$ mai

After you type in mai, press ESC and then the '*' key.  It will expand
the command line as follows:

$ main.cxx main.o

If you just want to see what files _would_ complete to match what
you've typed, press the '=' key and you will get something like this:

$ mai
1) main.cxx
2) main.o
$ mai

Just as an aside, the ESC puts you into a VI editing mode, so most
of the normal VI keys work, like 'k'(up) is your previous command,
'j'(down) is the next command, '/{pattern}' will search for a command,
etc.  The man page tells most of it's abilities, but if you have any
more questions, e-mail me and I'll be glad to help.
--
Kevin K. Lewis             | My opinions may be unreasonable
kevinl@tisdec.tis.tandy.com| but such is the voice of inspiration

Newsgroups: comp.unix.shell
From: anatoly@boulder.Colorado.EDU (Ulyanov Anatoly)
Subject: Re: shell
Keywords: shell 
Organization: University of Colorado, Boulder
Date: 30 Dec 92 18:21:20 GMT

kasajian@netcom.com (Kenneth Kasajian) writes:

>I'd like to have a shell program (using c-shell) called "dir" that works
>like ls -l -F so I created a file called dir with the exec attribute with
>the following contents:
>ls -l -F $1


		Try ls -l -F $*
Newsgroups: comp.unix.shell
From: rduta@nyx.cs.du.edu (Radu)
Subject: need a bit of help in
X-Disclaimer: Nyx is a public access Unix system run by the University
	of Denver for the Denver community.  The University has neither
	control over nor responsibility for the opinions of users.
Organization: Nyx, Public Access Unix at U. of Denver Math/CS dept.
Date: Fri, 1 Jan 93 19:50:22 GMT


Ok, tow things:
1) I want a method of copying whole directories.  I'm used to the mac where
   you can just drag folders form one dir to another and it moves it or
   copies it.  I want something similar for unix.  The thing is that I
   Haven't the slightest idea how to start.

2) I was wandering what is the easiest way to do a recursive grep, where
   it searches all the files in all dirs.  I was thinking something along
   the lines of "grep -R string *" but the "-R" flag is not an option.

any ideas?

--
********************************************************************************
I only kill to know I'm alive!
Newsgroups: comp.unix.shell
From: kasajian@netcom.com (Kenneth Kasajian)
Subject: find
Keywords: find grep
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 
Date: Wed, 30 Dec 1992 15:42:42 GMT

What is the unix command for DOS' 'find'.  I would like to
display directories only with ls.  so I do an ls -F -1 and
then display only those lines with a / .

Also.  How do I do I get grep to include in its file list all
files in the current directory and files in all sub-directories?

kenny
From: davidsen@sixhub.UUCP (Wm E. Davidsen Jr)
Newsgroups: comp.unix.shell
Subject: Re: testing if an arg is a number
Date: 31 Dec 92 12:44:19 GMT
Reply-To: davidsen@sixhub.UUCP (bill davidsen)
Organization: *IX Public Access UNIX, Schenectady NY

In article <1hruvtINNbap@sam.ksu.ksu.edu> dudley@sam.ksu.ksu.edu (D U D L E Y) writes:
| Was curious, and didn't see it in the FAQ...how would you identify if an
| argument to a script is *entirely* numeric?
| 
| So "12" would return true while "12a" would return false.
| 
| The only way I found was to use egrep.

See also expr.

  expr "$n" : "^[0-9][0-9]*$" > /dev/null && echo numeric || echo other

The output of the expr is the number of digits, thus the redirection.
-- 
bill davidsen - davidsen@sixhub.uucp (uunet!crdgw1!sixhub!davidsen)
    sysop *IX BBS and Public Access UNIX
"I haven't had time to read the manual, I've been too
   busy fighting with the install" -Nevius
From: Kari.Hurtta@Helsinki.FI (Kari E. Hurtta)
Newsgroups: comp.unix.shell
Subject: Re: killing process by UID
Date: 31 Dec 92 08:19:11 GMT
Organization: Department of Computer Science, University of Helsinki, Finland

In article <1992Dec30.090112.1@sep.vitro.com> eswgcs%v8.decnet@v7.vitro.com wrote:
> I am looking for the best way to detect all processes owned by a given user
> and kill them.  I would appreciate any ideas in both C and in shell code.

su user -c "kill -signal -1"

--
- K E H                                      /  Eldmd on monimutkaista
  Kari.Hurtta@Helsinki.FI
From: kevinl@tisdec.tis.tandy.com
Date: 31 Dec 92 07:42 CST
Newsgroups: comp.unix.shell
Subject: Re: Help using find with wildcards
Message-ID: <28300011@tisdec.tis.tandy.com>
Nf-ID: #R:lmpsbbs.comm.mot.com:22976:tisdec.tis.tandy.com:28300011:000:190
Nf-From: tisdec.tis.tandy.com!kevinl    Dec 31 07:42:00 1992


Just put quotes around the expression containing wildcards.
--
Kevin K. Lewis             | My opinions may be unreasonable
kevinl@tisdec.tis.tandy.com| but such is the voice of inspiration
From: junzhang@crayola.rutgers.edu (junbiao zhang)
Newsgroups: comp.unix.shell
Subject: why biff does not work?
Date: 30 Dec 92 17:14:59 GMT
Organization: Rutgers Univ., New Brunswick, N.J.

I turned biff on in my .login file but when new mail comes the terminal has no
sign to notice me. I checked with biff and it said " biff is y" . What's the
problem?

I will be grateful if you can give your reply through email:
	junzhang@paul.rutgers.edu

Thanks in advance.

J. Zhang
From: calvin@wshb.csms.com ( WSHB employee)
Newsgroups: comp.unix.shell
Subject: trap
Date: 30 Dec 92 16:04:55 GMT
Organization: WSHB, Herald Broadcasting Syn., Inc., Cypress Creek, SC, USA


	I am writting a program here and included a trap
  statement that went like this.

  trap "rm $LOCATE1/LCK..Order $LOCATE3/$$.*; clear; exit" 0 1 2 9 15

	I later give an exit statement that says exit 3.  What ends up
  happening is that the trap statement is executed and it rm's the files.
  I didn't want it to remove the files on this exit code.  Is my trap
  messed up, am I giving an incorrect exit code, or does the computer
  have a boo boo?  Any help would be apprecitated.  Thanks!


-- 
...calvin@wshb.csms.com.        If it wern't for bad luck,
kamikazi"calvin"                I'd have no luck at all! 
>From a warped mind comes a warped product.
These are not my employers opinions.  In fact I don't know if there mine!
Newsgroups: comp.unix.shell
From: elliott@quando.quantum.de (David Elliott)
Subject: Re: Opening up remote xterm windows?
Organization: Quantum Software GmbH, Dortmund, Germany
X-Newsreader: Tin 1.1 PL5
Date: Wed, 23 Dec 1992 09:39:46 GMT

Sanjiv K. Bhatia (sanjiv@cse.unl.edu) wrote:
: Try the following script called xrsh.
: 
[large script deleted]
:

And what's wrong with the command xon ?

Dave
-- 
 David Elliott | Yorkshireman in exile | elliott@quantum.de | here is nothing
---------------+-----------------------+--------------------+-----------------
And now - the .signature that the world has been waiting for! How YOU TOO can
make millions - all in the space of one .signature! Step 1 - first of all you
Newsgroups: comp.unix.shell
From: gary@netcom.com (Gary Messenbrink)
Subject: How do you determine what shell is in use from a program?
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 
Distribution: us
Date: Thu, 31 Dec 1992 06:26:48 GMT

Hi,
I need to determine the shell that would be used to execute
a line that is produced from within a program.  An example is
	eval 'some-program'
where some-program returns a shell command to be executed.
The program needs to know what shell will be used so it
can generate a compatible command.  I hope this explanation
is reasonable.  Please respond if possible via email to
gary@netcom.com since I don't always get a chance to read
this group.  I have looked through some of the FAQ's but
haven't located anything on this subject.

Thanks in advance,
Gary
-- 
========================================================================
|   Gary Messenbrink                 gary@netcom.com [192.100.81.100]  |
========================================================================
Newsgroups: comp.unix.shell
From: darla@shell.portal.com (Kuby Downs)
Subject: Re: .cshrc vs .login in csh
Keywords: csh .login .cshrc newbie
Organization: Portal Communications Company
Date: Wed, 30 Dec 1992 10:51:28 GMT


 Brian,

Hi! Hope you don't mind me jumping in here, but I've been using and
getting to know 'bout Cshell and unix using Doug Topham's The
First Book of Unix. So in advance, I ask you to forgive my stupid
questions. 

=>2) Anything that doesn't get exported to children should be done in the
=>.cshrc file.

What do you mean by 'children' in these sentences?


               ____    
              /    \__                    Darla
  |\         /    @   \
  \ \_______|    \  .:|>     Portal: darla@shell.portal.com
   \      ##|    | \__/              darla@cup.portal.com         
    |    ####\__/   \           AOL: kuby2u@aol.com
    /  /  ##       \|                darlaiam@aol.com
   /  /__________\  \           WIX: darla   |GENIE: KUBY    
   L_JJ           \__JJ   



--
                    ()|||()    Portal darla@cup.portal.com     
                   \\ . . //          darla@shell.portal.com
                   === v ===   AOL kuby2u@.aol.com
                   //`---'\\   WIX darla GEnie KUBY
Newsgroups: comp.unix.shell