HDTenEightyP/NetNews huggingface dataset:
From: dudley@sam.ksu.ksu.edu (D U D L E Y)
Newsgroups: comp.unix.shell
Subject: testing if an arg is a number
Date: 30 Dec 1992 04:51:41 -0600
Organization: Kansas State University
Distribution: world
NNTP-Posting-Host: sam.ksu.ksu.edu

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.

#!/bin/sh

if [ $# > 0 ]
then

  if echo $1 | egrep -s "^[0-9]+$"
  then

    echo completely numeric

  fi

fi

-- 
                                                    John "Dudley" Hunkins
                                                  dudley@matt.ksu.ksu.edu
Newsgroups: comp.unix.shell
From: ram@court.mentorg.com (Ram Tumuluri)
Subject: File completion in Ksh.
Date: Wed, 30 Dec 1992 20:15:51 GMT
Organization: Mentor Graphics
Keywords: 
Followup-To: 

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

Thanks
ram

-- 
 ----------------------------------------------------------------------------------
 Ramakrishna J. Tumuluri                                                            
 EMAIL         : ram_tumuluri@mentorg.com          VOICE MAIL    : (408)-451-5601  
 #include        <standard.disclaimer>
 #include        <witty.saying>
 #include        <fancy.pseudo.graphics>
 ----------------------------------------------------------------------------------
Newsgroups: comp.unix.shell
From: kasajian@netcom.com (Kenneth Kasajian)
Subject: stripping cr/lf's
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 
Date: Thu, 31 Dec 1992 07:13:12 GMT


How do I strip the cr's from a text file?  There must be a standard
unix way of doing it!
thanks
Newsgroups: comp.unix.shell
From: pbm@fc.hp.com (Peter McLain)
Subject: Re: Exiting KSH with ^D
Date: Wed, 23 Dec 1992 15:55:25 GMT
Organization: Hewlett-Packard Fort Collins Site
X-Newsreader: TIN [version 1.1.3 PL6]

: 
: This problem would occur if your eof is something other than
: ctrl-d.  Look at stty -a output to see what your settings are.
: Here's part of stty -a from my Xenix 2.3.4 system.
: 
: speed extb baud; line = 0; intr = DEL; quit = ^\; erase = ^H; kill = ^U; eof = ^D; eol = ^@; swtch = ^@


    Be careful how you get the stty output.  If you just do "stty -a" from
    the ksh prompt, you will NOT get the settings that ksh uses.  ksh keeps
    track of two sets of tty settings.  One for its own use while it is
    reading input from the user; the other is used as the settings for the
    tty for jobs.

    E.g.,  if I'm on ttyt4, and do:

	$ stty -a                  # done from ttyt4
	... eof = ^D; eol =^@

    But, if from a different window, I do:

	$ stty -a < /dev/ttyt4     # NOT done from ttyt4
	... eof = ^[; eol = ^M

    The first shows the tty settings that ksh sets up for jobs that it
    spawns, the second shows the tty settings that ksh uses for the editing
    modes.

Peter McLain
pbm@fc.hp.com
From: lusol@Lehigh.EDU (Stephen O. Lidie)
Newsgroups: comp.unix.shell
Subject: Re: ksh 1, perl 2 - ksh or perl for scripting?
Date: 21 Dec 92 18:06:10 GMT
Organization: Lehigh University, Bethlehem PA

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? 
>
>
>
>-Alan Harder                
> ash@math.ams.org
>
> My opinions are not the opinions of the American Mathematical Society.
> Did you think they were?
>

Sometimes even I don't use Perl..... but mostly I do.  Gave up all shells/sed
awk/grep/egrep/fgrep long ago.....

Why I use Perl:
	. Perl outperforms ksh and friends essentially all the time
	. Perl has no hidden arbitray limitations - too many scripts
      fail due to line length problems, core dumps, etc.
    . I only have to know one language and one regular expression
      language.  
    . I like lists

Summary:  Perl is my production scripting language.  Perhaps a bit
'notatioanally cluttered', but far better than what else is out there.  Now,
I can't wait for Perl 5 'cause I need user defineable TYPEs/structures!

SOL
Newsgroups: comp.unix.shell
From: rduta@nyx.cs.du.edu (Radu)
Subject: alias probem in tcsh and csh
Organization: Nyx, Public Access Unix @ U. of Denver Math/CS dept.
Date: Sun, 3 Jan 93 18:17:26 GMT

I was trying to create some aliases for ls, and i ran into some minor
problems, well for starters i'll list my aliases:
alias ls 'ls -F \!* | more'
alias dir 'ls -aol '

Ok, her's are the problems: I'd like to put a "more" in the dir alias as well,
but it conflicts with the ls, and the space bar doesn't work for paging any
more.  The second probelm i encountered was doing something like "ls m*", it
listed all the files, then went ahead and started to list the contents of the
files, as thought I did a "more m*".  I'm not sure what the problem is so
if anyone has any ideas on what is going wrong or ways to solve the problem
please let me know. 
(i'd like to add the "\!*" to the dir alias as well)

radu

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

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
but the $1 doesn't expand wildcards properly.  What am I doing wrong?
Kenny
From: dansmith@Autodesk.COM (Daniel Smith)
Newsgroups: comp.unix.shell
Subject: Re: alias probem in tcsh and csh
Date: 4 Jan 93 05:10:38 GMT
Organization: Autodesk Inc., Sausalito CA, USA

In <1993Jan3.181726.3147@mnemosyne.cs.du.edu> rduta@nyx.cs.du.edu (Radu) writes:

> I was trying to create some aliases for ls, and i ran into some minor
> problems, well for starters i'll list my aliases:
> alias ls 'ls -F \!* | more'
> alias dir 'ls -aol '

> Ok, her's are the problems: I'd like to put a "more" in the dir alias as well,
> but it conflicts with the ls, and the space bar doesn't work for paging any

	use absolute pathnames:

if (! $?PAGER) setenv PAGER /usr/ucb/more
alias ls '/bin/ls -F \!* | $PAGER'
alias dir '/bin/ls -aol \!* | $PAGER'

	or:

alias dir '\ls -aol'

				Daniel
-- 
 dansmith@autodesk.com       daniel@world.std.com       dansmith@well.sf.ca.us
        Daniel Smith, Autodesk, Sausalito, California, (415) 332-2344 x 2580
c'mon over and do the twist / overdo it, and have a fit
love you so much, you make me sick /  c'mon over and do the twist  - Nirvana
Newsgroups: comp.unix.shell
From: sacks@netmgr.mot.com (Dennis Sacks)
Subject: Windowing KSH Product information.
Reply-To: sacks@netmgr.mot.com
Organization: Info Enterprises
Date: Tue, 22 Dec 1992 00:09:52 GMT

For people who are interested, here is my understanding of the WKSH
product.

It was developed by USL (Unix System Labs). Basically the fellow who
developed WKSH took the KSH and added the ability to provide access to
Motif and OPEN LOOK widgets and Xt Intrinsics functions.

USL only sells the source code. You must buy the binary from a third
party company who buys it from USL and "productizes" it.

You can call USL to find out who sells WKSH for your machine. Here is
the info for the company that sells it for the Sun Workstation:

The price quote I got was $300 for a single user version of WKSH and
$700 for a multiuser version.

You should contact Acacia Computer yourself for an official quote...

Acacia Computer
Phone: 908-561-0105

Contact: Lynne Collett


Also if you want more details about WKSH, the developer at USL, Stephen Pendergrast,
send me a 13 page paper he presented at one of the Unix conferences that compares
WKSH to WCL, TCL/TK and gives several examples of WKSH code.

Stephen's number can be gotten from the ATT software toolchest (I don't seem to be
able to find this number currently).


---
Dennis Sacks                           The Crunchy Wizard
    is sacks@panther.mot.com           is looking for a better
         at Info Enterprises           .sig
From: larryt@canada.sun.com (Larry Tsui - OpCom Staff)
Newsgroups: comp.unix.shell
Subject: ?tcsh and native language support
Date: 23 Dec 92 21:38:22 GMT
Reply-To: larryt@canada.sun.com
Organization: Sun Microsystems Computer Corp., OPCOM.

I have trouble input multi-byte 8-bit characters with tcsh and cxterm.
I am using tcsh version 6.03.00, cxterm version 11.5.1, Solaris 2.1FCS,
X11R5 patchlevel-16 on Sun 4/75.

If I use csh or sh, I have no trouble inputting multibyte 8-bit
characters (as long as I do a "stty -istrip").

If I use tcsh, I can read multibyte 8-bit characters with no problem
(so the fonts stuff is fine); however, if I try to input a multibyte
8bit character, I get two ascii characters back.

I have read the tcsh manual section 26 on NLS but I am still confused.
Would someone please give any hints?  Thanks!

Larry

---
larry.tsui@canada.sun.com  -or-  sun!suncan!larryt
Newsgroups: comp.unix.shell
From: ray@Celestial.COM (Ray Jones)
Subject: Re: wanted: tutorial about sh programming
Organization: Celestial Software, Mercer Island, WA
Date: Wed, 23 Dec 1992 16:18:30 GMT

In <37Y9SOS@math.fu-berlin.de> richter@ki1.chemie.fu-berlin.de (Thomas Richter) writes:

>Hi,

>has anybody a tutorial about sh programming available by anon. ftp?
>I'm looking for something with examples, useful in classrooms.

Don't know of an anon.ftp, but there is an older book that I think is great.
Lots of examples and lots of stuff you don't normally see in a shell
programming book.
Unix Shell Programming   (??)
by Rod Manis
published by Sam's Books
-- 
INTERNET:  ray@Celestial.COM   Ray A. Jones; Celestial Software
UUCP:   ...!thebes!camco!ray   6641 East Mercer Way
             uunet!camco!ray   Mercer Island, WA 98040; (206) 947-5591
The probability of one or more spelling errors in this missive approaches
From: leisner@wrc.xerox.com ( Marty Leisner)
Newsgroups: comp.unix.shell
Subject: Re: Opening up remote xterm windows?
Date: 30 Dec 92 01:04:31 GMT
Organization: Xerox
X-Newsreader: TIN [version 1.1 PL8]

OK, I'm using xrsh and like it...

(I set XRSH_ENVS_TO_PASS=LD_LIBRARY_PATH PATH so it can at least start an xterm...).

What I want to do is:

1) open an xterm window
2) start a csh shell
3) source my .login file (I set everything up there, don't really care about my
cshrc).
4) exec bash (where I work).

I tried various permutations on this:
xrsh annapurna xterm -e csh -c "source .login; exec bash"
and I keep getting a flashing xterm window with "too few arguments"

But csh -c "source .login; exec bash" works just fine alone...

What is the appropriate incantation?


--
marty
leisner.henr801c@xerox.com  leisner@eso.mc.xerox.com
Member of the League for Programming Freedom
Newsgroups: comp.unix.shell
From: dman@netcom.com (Dallman Ross)
Subject: Re: Need quick-'n'-dirty syntax lesson in csh
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 
X-Newsreader: TIN [version 1.1 PL8]
Date: Mon, 21 Dec 1992 13:41:45 GMT

Dallman Ross (dman@netcom.com) wrote:

: I'm writing a tiny csh script, and I need to know how the syntax is
: formed in an "if"-statement for:

: 	if <there is no argument3 ...>

: I have the "then"- and "else"-parts down fine, just need the "if"
: syntax.  I grepped through man csh with no real luck.

Thanks so much to the two folks who emailed me answers.  I'll post the
syntax here in case others are curious:

"If the number of arguments is less than three, then . . ."

	if ( $#argv < 3 ) then

"If the number of arguments is equal to three, then . . ."

	if ( $#argv == 3 ) then

"If there is a third argument, but it is empty, then . . ."

	if ( $argv[3] == "" ) then

--
 __D_a l_l m a_n  _ R o_s s _ |dman@netcom.com  /or/  |"You sound like a man|
 l  \\ l\\   /l  /\\  l\\   l |dross@well.sf.ca.us    |with a rubber nose." |
 l   >)l \\ /ll /  \\ l \\  l |vox/fax: 1.510.645.1883| -- One-Lung Bill    |
 l  // l  \X ll/--- \\l  \\ l |350 Perkins St., #108  |     Remmer (deceased)
_l//______________________\\l_|Oakland,_CA__94610-3422|_____________________|_
From: hartman@informix.com (Robert Hartman)
Newsgroups: comp.unix.shell
Subject: Re: shell
Keywords: shell
Date: 31 Dec 92 18:41:56 GMT
Organization: Informix Software, Inc.

In article <1992Dec30.150828.24430@netcom.com> 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
>but the $1 doesn't expand wildcards properly.  What am I doing wrong?
>Kenny

Actually, $1 is behaving as expected.  Your script is performed by a
subshell (child of your current shell).  Your current shell is the
one that expands wild cards, and does so before starting the
subshell that runs your script.  So if you have the following files
in your directory:

	bar
	foo

and you say:

	dir *

the script is invoked with the following arguments:

	dir bar foo

and, as you can see, bar is argument number 1.  If you run csh, you
can set the echo variable to see how the shell expands wild cards.

Rather than using $1, you want to use $*, which expands to all
arguments.  In sh, when you need to include white space within
quoted arguments, "$@" is used in place of $*.  Chances are it will
be a while before you need this, but I wanted to mention it because
it was several years before I knew what "$@" was for.

-r
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: 29 Dec 92 20:15:05 GMT
Reply-To: davidsen@crd.ge.com (bill davidsen)
Organization: GE Corporate R&D Center, Schenectady NY

In article <1992Dec28.235815.21034@netlabs.com>, lwall@netlabs.com (Larry Wall) writes:
| In article <1992Dec23.160443.13103@crd.ge.com> davidsen@crd.ge.com (bill davidsen) writes:
| : 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.
| 
| You can prove anything by counting idiots.

  I don't think it's true that all good perl programmers are idiots.
They tend to be a bit strange, I agree...

  This problem appears in most languages in which there is more than one
reasonable way to solve a problem. Programmers get thinking about the
code and decide they could do it a bit {faster,smaller,better,cleaner}
and go rewrite the code.
-- 
bill davidsen, GE Corp. R&D Center; Box 8; Schenectady NY 12345
    Keyboard controller has been disabled, press F1 to continue.
Newsgroups: comp.unix.shell
From: lwall@netlabs.com (Larry Wall)
Subject: Re: ksh 1, perl 2 - ksh or perl for scripting?
Organization: NetLabs, Inc.
Date: Thu, 31 Dec 1992 20:37:24 GMT

In article <1992Dec29.201505.8229@crd.ge.com> davidsen@crd.ge.com (bill davidsen) writes:
: In article <1992Dec28.235815.21034@netlabs.com>, lwall@netlabs.com (Larry Wall) writes:
: | In article <1992Dec23.160443.13103@crd.ge.com> davidsen@crd.ge.com (bill davidsen) writes:
: | : 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.
: | 
: | You can prove anything by counting idiots.
: 
:   I don't think it's true that all good perl programmers are idiots.

I don't think you think it's true that all good perl programmers are idiots.

: They tend to be a bit strange, I agree...

*I'm* never strange...

:   This problem appears in most languages in which there is more than one
: reasonable way to solve a problem. Programmers get thinking about the
: code and decide they could do it a bit {faster,smaller,better,cleaner}
: and go rewrite the code.

Nothing the matter with that.  We all optimize for various and sundry
reasons, and those reasons can change over time.  I don't think there's
even anything terribly wrong with optimizing for impressive obfuscation
when the fit takes you.  It's only when the fit takes you inappropriately
that it can be considered antisocial.  These are the folks I was thinking
of.

I would argue that these same people tend to obfuscate their C, their sh,
their nroff, too.  There are, in fact, multiple ways to solve problems
in these languages too, though I won't quarrel with you if you want
to assert that Perl gives you a slightly richer basic toolset than C,
and that this may have some influence on a programmer's thinking.  The
linguists have been debating this question longer than most of us are old.

I do quarrel with logic that says, "Stupid people are associated with X,
therefore X is stupid."  Stupid people are associated with everything.

Mind you, I'm not accusing you of expressing exactly that sentiment,
but it was close enough that I could trot out the epigram that had been
burning a hole in my noggin for several days.  :-)

Larry
Newsgroups: comp.unix.shell
From: jefouger@nyx.cs.du.edu (Jim  Fougeron)
Subject: Re: Help using find with wildcards
Organization: University of Denver, Dept. of Math & Comp. Sci.
Date: Thu, 31 Dec 92 04:34:45 GMT

markn@ssd.comm.mot.com (Mark Nowak) writes:

>Anybody know how to find files, directories, etc. when you
>don't know the exact name of the file you're looking for.
>For example, I'm looking for file abcde in some directory
>tree, but the only characters I know for sure are bcd.  Is
>there a wat to use find to locate this file?

>I'm thinking of something along the lines of:

>find . -name *bcd* -print

try:    find . -name \*bcd\* -print

>but that doesn't work.


Jim Fougeron   jefouger@nyx.cs.du.edu
Newsgroups: comp.unix.shell
From: cslee@pds.nchu.edu.tw (Lee Chee Siong)
Subject: How to make Restrict Shell more safely?
Organization: NCHU Computer Center
Date: Mon, 4 Jan 1993 11:06:09 GMT

Hi,
  I want to creat a few accounts in Restrict Shell enviroment. In this 
account, only a few command(e.g. vi, ftp, mail, news) can be used. Is
there any suggestion to creat this environment to make it more security
in my system?
  Any comming is appreciate.


<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
<>   CS Lee	(Lee Chee Siong)		<>  If you can give	<>
<>   National Chung Hsing University,		<>	  nothing else, <>
<>   Taichung, Taiwan, Republic of China.	<>  at least give a	<>
<>   Internet Address: cslee@pds.nchu.edu.tw	<>	  cheerful face <>
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
Newsgroups: comp.unix.shell
From: ray@Celestial.COM (Ray Jones)
Subject: Re: wanted: tutorial about sh programming
Organization: Celestial Software, Mercer Island, WA
Date: Sat, 26 Dec 1992 21:03:09 GMT

In <1992Dec23.191853.24899@nosc.mil> mcdono@nosc.mil (Tim McDonough CSC Room 191 Phone 553 3102 ) writes:


>I'd like the following line to produce the output below it.

>echo "Hostname is " $system "   Host id is " $hostid

>Hostname is foo     Host id is 78454
>Hostname is fooobar Host id is 89000

>I tried removing the quotes to no avail, any ideas?
>mcdono@sunspot.nosc.mil
Assuming $system and $hostid vars are set, 

echo "Hostname is $system	Host id is $hostid"

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

echo 'Hostname is $system	Host id is $hostid'

will produce,

Hostname is $system	Host id is $hostid
-- 
INTERNET:  ray@Celestial.COM   Ray A. Jones; Celestial Software
UUCP:   ...!thebes!camco!ray   6641 East Mercer Way
             uunet!camco!ray   Mercer Island, WA 98040; (206) 947-5591
The probability of one or more spelling errors in this missive approaches
Newsgroups: comp.unix.shell
From: chip@tct.com (Chip Salzenberg)
Subject: Re: timing piped commands
Date: Tue, 22 Dec 1992 18:04:29 GMT
Organization: TC Telemanagement, Clearwater, FL

According to xiaobing@cs.sfu.ca (Xiaobing Chen):
>	% time 'ls -lR | fgrep root'	# failed of course

You can get close with

	% time sh -c 'ls -lR | fgrep root'

-- 
Chip Salzenberg at Teltronics/TCT  <chip@tct.com>, <73717.366@compuserve.com>
  "you make me want to break the laws of time and space / you make me
   want to eat pork / you make me want to staple bagles to my face /
   and remove them with a pitchfork" -- Weird Al Yankovic, "You Make Me"
Newsgroups: comp.unix.shell
From: mliu@pt.com (Fred Liu)
Subject: Handling of '&' by shell
Organization: Performance Technologies, Incorporated
Date: Mon, 28 Dec 1992 16:26:41 GMT

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 do
you think of the following conversation:

	$ abcd &
	[3] 1234
	$ abcd: Command not found.
	<Return>
	[3]    Exit 1			abcd

-- 
Fred Liu, Performance Technologies Incorporated		mliu@pt.com
315 Science Parkway, Rochester, New York 14620		uupsi!ptsys1!mliu
Newsgroups: comp.unix.shell
From: root@n1gva (The Nefarious Dr. Sponge)
Subject: Re: stripping cr/lf's
Organization: Evil Weather Machines LTD
Date: Sat, 2 Jan 93 12:45:25 GMT

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!
: thanks

I have to do this alot with MS-DOS text files. :-(

Try:	tr -d "\015" < file_with_cr.s > new_file_wo_cr.s

See also the man page on 'tr'.

Fred

-- 
< Fred Floberg - N1GVA >         Evil Weather Machines LTD.      <
> 136 West Spring St.  <                                         >
< West Haven, CT 06516 >        My employer has no opinions.     <
> USA                  < email: ...!uunet!hsi!a3bee2!n1gva!n1gva >
Newsgroups: comp.unix.shell
From: lwall@netlabs.com (Larry Wall)
Subject: Re: ksh 1, perl 2 - ksh or perl for scripting?
Organization: NetLabs, Inc.
Date: Mon, 28 Dec 1992 23:58:15 GMT

In article <1992Dec23.160443.13103@crd.ge.com> davidsen@crd.ge.com (bill davidsen) writes:
: 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.

You can prove anything by counting idiots.

Larry Wall
lwall@netlabs.com
From: green@.Kodak.COM (Russell Green)
Newsgroups: comp.unix.shell
Subject: Re: Opening up remote xterm windows?
Date: 21 Dec 92 21:53:17 GMT
Organization: Eastman Kodak Co., Rochester, NY

In article <1992Dec20.215237.3151@spectrum.xerox.com>, leisner@wrc.xerox.com ( Marty Leisner) writes:

>[1]+  Stopped (tty input)     rsh $1 ./dologin "xterm -title $1 -display `hostname`:0 -e bash "

rsh -n $1 ./dologin "xterm -title $1 -display `hostname`:0 -e bash " &
    ^^                                                               ^

RTFM on rsh






>Or is there a better way of doing what I'm trying to do?
>
>--
>marty
>leisner.henr801c@xerox.com  leisner@eso.mc.xerox.com
>Member of the League for Programming Freedom

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~ Russell J. Green         | Rochester Distributed Computer Services ~
~ Mail Stop 01826          |                                         ~
~ Eastman Kodak Company    | --------------------------------------- ~
~ Rochester, NY 14650-1826 |   Internet mail: green@.Kodak.COM       ~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~