HDTenEightyP/NetNews huggingface dataset:
From: ash@ulysses.mr.ams.com (Alan Harder)
Subject: Re: Help with directories!
Organization: American Math. Society
	<1992Aug25.142330.13023@news.eng.convex.com>
	<ASH.92Aug25111753@ulysses.mr.ams.com>
	<1992Aug25.153123.21234@news.eng.convex.com>
Date: Tue, 25 Aug 1992 17:48:03 GMT

In article <1992Aug25.153123.21234@news.eng.convex.com> Tom Christiansen <tchrist@convex.COM> writes:


   >:tchrist> But we discussed it ad nauseum just five days ago!!

   ash>:Yes.  But there are those who cannot read the group every day, and
   ash>:don't have the disk space to keep all the postings that occurred while
   ash>:they were on vacation, etc.  Other people don't have the resources or
   ash>:time to read the group on a consistent basis.  And there are new
   ash>:posters and readers.  So then if someone asks a question that was
   ash>:discussed before, he/she gets flamed.  Which makes him/her feel stupid
   ash>:for asking the question.  Which makes him/her less likely to ask
   ash>:another question.  Which reduces the value of the newsgroup for
   ash>:him/her.

   tchrist>What do you propose as a solution to what I perceive as wasted bytes?
   tchrist>Shall we add it to the FAQ?  Shall we post the FAQ biweekly or more,
   tchrist>or maybe its TOC weekly, with a pointer to how to get it?  Shall we 

I never said I had a solution to wasted bytes.  I just don't think
that flaming is a good answer, especially if the question isn't in the
FAQ.  And even if a question is in the FAQ, a polite "Please read the
FAQ, which is posted weekly, or can be obtained via anonymous FTP" is
usually better than the "Read the FAQ, butthead." that I've seen
posted.

This guy just happened to ask a question that was recently discussed.
He had no way of knowing that, since he's a new reader, and so he
didn't deserve the flame.  If the topic had been five months old, he
would've gotten an answer instead of sarcasm.  Do you think he really
deserved the flame?  If not, then why are you defending it?  If so,
then could you please tell me why he deserved it?

I'm just hoping people can respond more politely to those who really
need answers to their questions, but aren't necessarily daily readers
of the group.  

   tchrist>institude a USENET Oracularities mail-in-your-questions system for
   tchrist>UNIX questions?

Maybe we can institute a USENET Oracularities mail-in-your-flames
system instead!
From: kim@wcieng.UUCP (Kim Moran)
Newsgroups: comp.unix.shell
Subject: Re: Daemons started on Reboot Question
Keywords: Daemon tty
Date: 26 Aug 92 17:34:11 GMT
Article-I.D.: wcieng.16153
Reply-To: kim@wcieng.UUCP (Kim Moran)
Organization: Wegener Communications Inc, Atlanta GA


In article <1992Aug24.142632.19324@walter.bellcore.com> dan@bae.bellcore.com writes:
....... lines deleted .....
>/etc/rc.zebra:
>
>#!/bin/ksh
>#
># START ZEBRA daemons
>#
>if [ -f /usr/local/pkg/zebra/bin/zebrad ]
>then
>        echo "Starting ZEBRA Daemons"                    >/dev/console 2>&1
>        /bin/su zebradm -c '/usr/local/pkg/zebra/bin/zebrad'  >/dev/console 2>&1
>fi
>

We had a similiar problem with our target system.  We use XENIX, but this may
also fix your problem.  Try using the minus (-) as the first argument to su, 
that is:
   /bin/su - zebradm -c '/usr/local/pkg/zebra/bin/zebrad'

In XENIX, if the first argument to su is -, the environment is changed to
what would be expected if the user actually logged in as the user specified.

Hope this helps.

Kim
Newsgroups: comp.unix.shell
From: Tom Christiansen <tchrist@convex.COM>
Subject: Re: file removal problem solved.
Originator: tchrist@pixel.convex.com
Date: Wed, 2 Sep 1992 20:41:25 GMT
Reply-To: tchrist@convex.COM (Tom Christiansen)
Organization: Convex Computer Corporation, Colorado Springs, CO
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 jerry@incc.com (Jerry Rocteur):
:1) who rattled your s*it can and asked for your opinion ?

ditto.

:2) since when are you the moderator of free speech ?

he was right -- your signature is too long, and your quoted
material was inappropriately long.

--tom
-- 
    Tom Christiansen      tchrist@convex.com      convex!tchrist
    "...this does not mean that some of us should not want, in a rather
    dispassionate sort of way, to put a bullet through csh's head."
		Larry Wall in <1992Aug6.221512.5963@netlabs.com>
Newsgroups: comp.unix.shell,comp.unix.questions
From: martin@datacomm.ucc.okstate.edu (Martin McCormick)
Subject: Re: Shell Scripts vs. C programs
Keywords: shell script, C
Organization: Oklahoma State University, Stillwater, OK
Date: Tue, 1 Sep 1992 17:50:31 GMT


I always thought you should code your program in C because it executes so
much faster.  Since I am a beginner at C, I always code in shell scripts,
when possible, but that is mainly because it is easier to read, later.
I would like to see the answers to this question posted to the group.

Martin McCormick WB5AGZ   Stillwater, OK
O.S.U. Computer Center Data Communications Group
Newsgroups: comp.unix.shell
From: digdon@ug.cs.dal.ca (Mike Digdon)
Subject: Re: Help with directories!
Organization: Math, Stats & CS, Dalhousie University, Halifax, NS, Canada
Date: Wed, 26 Aug 1992 15:53:06 GMT

>
>The point is that you can't volunteer everyone to act as the archive master
>for the group, sending threads to hapless new posters.  What is so horribly
>bad about reading a group for a few weeks before you post?
>
>--Dave

The answer to the above question is very simple.. what if you need the
information NOW, and not a few weeks from now?
If you were working on a school assignment or something for work, and no one
was around you knew the answer.. you would certainly go looking thru news to
see if you could find some group that is catering to your needs.. Now,
netiquette says "Don't post until you are familiar.." The boss says, "Find the
answer before lunch or you will be reading net.jobs.." I think you would post
before you were supposed to..

And since no one here knows of this guys situation, all of this senseless
flaming and waste of bandwidth is quite unnecessary and uncalled for.. so
why don't we just let it drop and get down to what we are supposed to really
be talking about here..

-- 
	     Mike Digdon - Vice Prez DSCSS - Dalhousie University
		     digdon@ug.cs.dal.ca  -- Halifax, NS
		 - Real programmers never work nine to five -
Newsgroups: comp.unix.shell
From: dhami@cs.ubc.ca (Mandeep S Dhami)
Subject: > alias problems
Summary: problem solved.
Keywords: problem solved.
Organization: Computer Science, University of B.C., Vancouver, B.C., Canada
Date: Mon, 31 Aug 92 01:34:37 GMT


Mickey <mickey@sfera.kharkov.ua>:
>
>  there is a little problem to write alias in such way:
>  alias md "sh -c 'for f in \!*;do mkdir $f ; cd $f;done'"
>  it have to do:
>	make directory, than cd to it;
>  call:
>	cd ~
>	md 1 2 3 4 5 6
>  result:
>	cwd = ~/1/2/3/4/5/6
>
>  In such way implementation there are a couple of errors reported,
>  including "f": variable not found, and so on...
>

As already pointed out sh -c can NEVER work as, under UNIX, the
child can not touch the parents env. So you want to source OR in
*sh use function and in csh an alias which does NOT cd in a
subshell.

So one possible solution (csh for you) is:
alias xx 'set x=`echo \!*| tr " " "/"`; mkdir -p $x; cd $x;unset x;'
Note:
  1. cd in parent shell's context and
  2. -p in mkdir.

Or same as a better function in sane shells (*sh).

BTW, the error you had above is due to the brain dead parsing
in csh (refer to Tom Christiansen's wonderful critique of csh).
Maybe Tom should make it a regular posting!

Mandeep.
--
__________________________________________________________________
"I'm very brave generally," he went on in a low voice:
"only to-day I happen to have a headache."
                                      -- Lewis Carroll
Newsgroups: comp.unix.shell,comp.unix.questions
From: nurban@tjhsst ()
Subject: Shell Scripts vs. C programs
Keywords: shell script, C
Organization: Virginia's Public Education Network (Fairfax)
Date: Mon, 31 Aug 92 21:17:38 GMT


I've heard that if at all possible, code a program as a shell script
rather than coding it in C.  Can someone explain the rationale behind
this philosophy?


-- 
-------------------------------------------------------
Nathan Urban                  nurban@tjhsst.vak12ed.edu
Thomas Jefferson High School for Science and Technology
-------------------------------------------------------
Newsgroups: comp.unix.shell,comp.unix.questions
From: navarra@casbah.acns.nwu.edu (John Navarra)
Subject: Re: Shell Scripts vs. C programs
Keywords: shell script, C
Organization: Northwestern University, Evanston Illinois.
Date: Tue, 1 Sep 1992 04:44:34 GMT

In article <119@steiny.com> steiny@steiny.com (Don Steiny) writes:
>nurban@tjhsst writes:
>
>
>>I've heard that if at all possible, code a program as a shell script
>>rather than coding it in C.  Can someone explain the rationale behind
>>this philosophy?
>
>	BZZZ - shell scripts are non-portable
>
	Huh? Why are shell scripts non-portable? Unless you are using
a non-standard shell, shell scripts are HIGHLY portable! Even if you
aren't using a non-standard shell, say [ba|k|z|]sh, it is highly portable.
For one, most [ba|k|z]sh scripts will run in sh and vice versa. And, if you 
need to, you can always get shell X and compile it on your machine. This is
*usually* easier than rewriting C-code to accomodate your OS. 

> there is no error checking,

	There isn't? What does this mean? You write error checking
into the shell program just like you write it into C program. 

>and they have many other problems.

	And translating your C code using compiler X to OS Y is any
easier? Perhaps you are thinking of Csh? Then, yeah, you suck. 

>For very short programs shell 
>might be better, but in general C is better for many reasons.

	Even for long programs, shell scripts can be better. Yes, they
will run slower but if you can saves days, weeks, or months writing
the shell script, which is better then? It generally takes much longer
to write the same code in C as it does in a shell, perl, or awk. And,
once you have that script written, it is generally trivial to port it
to another machine -- especially if that machine runs the SAME SHELL!

-tms
-- 
You can get further with a kind word | You can get further with a kind word
and a gun than a kind word alone.    | and a phaser than a kind word and a gun.
          --al capone                |           -- John Navarra
=======From the Lab of the MaD ScIenTIst....navarra@casbah.acns.nwu.edu========
Newsgroups: comp.unix.shell
From: oklein@smallo.bo.open.de (Olaf Klein)
Subject: Re: How can I rm a file with a '&' ????
Organization: smallo.bo.open.de Fido-SubNet-Gate : 2:245/5800.12
Date: Fri, 28 Aug 1992 19:52:27 GMT

>> 	You can try 'rm -i *', or you can try using a hex editor on your
>> directory and changing the files name slightly, like replacing the '&'
>> with an 'A', and then removing the file.
>> 	You could also try piping a directory listing through awk like
>> this:
>> 	ls -l | awk '{if(index($8, "&")) system("rm " $8)}'
[silly ideas erased]

Under 'csh' for a file 'a&b' simply do : `rm a\&b`

Bys, Olaf

-- 
Olaf Klein     smallo.bo.open.de       2:245/5800.12
Newsgroups: comp.unix.shell
From: ash@ulysses.mr.ams.com (Alan Harder)
Subject: Re: Help with directories!
Organization: American Math. Society
	<1992Aug25.153123.21234@news.eng.convex.com>
	<ASH.92Aug25124803@ulysses.mr.ams.com>
	<1992Aug25.172821.4769@news.eng.convex.com>
Date: Tue, 25 Aug 1992 19:30:21 GMT

In article <1992Aug25.172821.4769@news.eng.convex.com> Tom Christiansen <tchrist@convex.COM> writes:


   :Do you think he really
   :deserved the flame?  


   >I believe my quote, somewhat milder than Boyd's which still didn't
   >seem particularly out of line, was 

    >   But we just discussed this 5 days ago!

   >If you consider this a flame, then we certainly have different 
   >standards for what constitutes such.

The "flame" I was referring to was Boyd's sarcastic response asking
how many minutes the poster had been reading the group.  Your
statement "But we just discussed this 5 days ago!" was in response to
my complaint about Boyd's post.  I took it as a defense of Boyd's
post, rather than a flame in it's own right.  I was not trying to
claim that you flamed the original poster, or me, which of course you
did not do.

In any case, you've answered the question "Do you think he really
deserved the flame?" (from Boyd) by saying it "didn't seem
particularly out of line".  We each have, and deserve, our own
opinions.  I therefore withdraw any criticisms I may have ever
levelled at anyone, ever, except for my mother-in-law.

Newsgroups: comp.unix.shell
From: ckd@eff.org (Christopher Davis)
Subject: Re: Shell Scripts vs. C programs
Followup-To: comp.unix.shell
Organization: Electronic Frontier Foundation Tech Central
	<1992Sep1.044434.7193@news.acns.nwu.edu> <121@steiny.com>
	<1992Sep1.173604.15563@u.washington.edu>
	<FRIEDMAN.92Sep2045423@nutrimat.gnu.ai.mit.edu>
Date: Thu, 3 Sep 1992 04:28:57 GMT

NF> == Noah Friedman <friedman@gnu.ai.mit.edu> 

 NF> (using "unless" and violating the general condition->consequent
 NF> order of expression is evil, especially since this is not a fundamental
 NF> paradigm of the language). 

There's a lot to be said for being able to optimize code for readability
with that construct; I find myself writing stuff like this:
  &flameUser($loudly) unless $feeling_lenient;

 NF>    Incidentally, I have a public domain Scheme implementation
 NF> written in Perl.  It's missing continuations among other things,
 NF> but it's still rather interesting... Anyone have any idea who wrote
 NF> it?  There wasn't any author listed in the copy I found.

I think Felix Lee did that one.  Ask in comp.lang.perl, or flee@cs.psu.edu.
--
Christopher Davis * ckd@eff.org * System Administrator, EFF * +1 617 864 0665
            ``Ed Gruberman, you fail to grasp Ti Kwan Leep.
            Approach me that you might see.'' -- The Master
Newsgroups: comp.unix.shell
From: Harald.Eikrem@delab.sintef.no
Subject: Re: TCSH: completions for talk ?
Organization: SINTEF DELAB, Trondheim, Norway.
Date: 2 Sep 92 22:22:02

! I want something like:
! 
!      > talk @[TAB]
!      ws1 ws2 ws3 ws4 
!      > talk @ws3
!      > talk @ws3[TAB]
!      user1 user2 user3 user4
!      > talk user1@ws3
! 
! One problem is, that when i manage to get the workstations, i don't
! get the users. I use something like:
! 
!     complete talk \
! 	c/@/\$hosts/ \
! 	c/@*/\`finger\ \$:1\ \|\ awk\ \'\{print\ \$1\ \}\'\ \|\ sort\ -u\ \`/ \
! 	p/1/\`finger\ \$:1\ \|\ awk\ \'\{print\ \$1\ \}\'\ \|\ sort\ -u\ \`/ \
! 
! any hints ?

Hmmmmmm.  That seems unworkable.  However, if rwhod is running on the
machines of interest to you, I have the following suggestion for a
completion command:

   complete talk 'p?1?`rwho | sed "s/:.*//; s/  */@/" | uniq`?'


  ~~harald E.
Newsgroups: comp.unix.shell
From: rod@philips.oz.au (Rod Roberts)
Date: Wed, 2 Sep 92 01:08:25 GMT
Organization: Philips Public Telecommunications Systems, Melbourne, Australia
Subject: shell to "C" compilers, any out there??
Summary: see subject
Keywords: shell C compiler

I have been wondering if there is such a thing as a shell script
compiler either commercial or pd/freeware. I have heard of such beasts
but havn't seen one. I imagine it would take a shell script is input
and generate a "C" source file. Can anyone point me in the right
direction. ThanX in advance.
                                                        Rod
-- 
Rod Roberts
e-mail: rod@philips.oz.au | Phone: +61 (3) 881 3574 | Fax: +61 (3) 881 3577
Philips Public Telecommunications Systems
23 Lakeside Drive, Burwood East 3151, Melbourne, Victoria, AUSTRALIA
Newsgroups: comp.unix.shell
From: mcook@fendahl.dev.cdx.mot.com (Michael Cook)
Subject: Re: cant delete file!
Keywords: funny filenames!
Organization: Motorola Codex, Canton, Massachusetts
Date: Thu, 27 Aug 1992 15:11:40 GMT

vidya-v@acsu.buffalo.edu (vidyaranya) writes:

>-rw-r--r--  1 vidya-v         0 Aug 24 12:02 A??LN???N???-@??-

>How do I delet it?

Please see the FAQ list:

2)  How do I remove a file with funny characters in the filename ?

Michael.
From: friedman@gnu.ai.mit.edu (Noah Friedman)
Newsgroups: comp.unix.shell
Subject: Re: cant delete file!
Date: 29 Aug 92 05:17:13 GMT
Organization: Free Software Foundation, 675 Mass Ave. Cambridge, MA 02139
In-reply-to: vidya-v@acsu.buffalo.edu's message of 26 Aug 92 18:13:02 GMT

In article <BtLrxr.77G@acsu.buffalo.edu> vidya-v@acsu.buffalo.edu (vidyaranya) writes:
>A file has been created in my directory accidentally, possibly while
>reading disk on a SparcStation IPC. I am unable to remove it. The file
>name appears as:
>
>-rw-r--r--  1 vidya-v         0 Aug 24 12:02 A??LN???N???-@??-
>
>How do I delet it? I tried escaping the '?' and '@' as follows:

   That's not going to work, because "?" is not the character that's really
appearing in the filename.  Mostly likely, your `ls' is converting
"unprintable" 8-bit characters into question marks on output to avoid
causing possible insanity with your terminal.

   One way to find out exactly what the characters are in the file name is
to use the `-b' option with ls; that's assuming your ls has such an option.
You then have a variety of choices (using your shell) to construct the
filename.  You might be able to quote something using echo and octal
characters, or use C-v (ctrl-v) prefixes to insert literal control
characters in your input.

   You can also try "rm -i ./A*" in the directory where the file appears,
but this has a few inherit dangers, like accidentally responding "y" to
files you didn't actually mean to delete. 
Newsgroups: comp.unix.shell
From: mcook@fendahl.dev.cdx.mot.com (Michael Cook)
Subject: Re: in Korn/Bourne how do you double substitute an env var???
Organization: Motorola Codex, Canton, Massachusetts
Date: Thu, 27 Aug 1992 15:12:47 GMT

fish@daacdev1.stx.com writes:

>if i had:
>foo=bar
>barfly=fish
>echo ${${foo}fly}	# i want fish as the output but my syntax is bad here

>help

Use "eval".

 eval echo \${${foo}fly}

Michael.
Xref: sparky comp.unix.shell:3740 comp.unix.questions:10616
From: tchrist@convex.COM (Tom Christiansen)
Newsgroups: comp.unix.shell,comp.unix.questions
Subject: Re: Shell Scripts vs. C programs
Keywords: shell script, C
Date: 1 Sep 92 19:35:33 GMT
Reply-To: tchrist@convex.COM (Tom Christiansen)
Organization: Convex Computer Corporation, 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 donn@carson.u.washington.edu (Donn Cave):
:I have wondered if it would be possible to develop a reasonably usable shell
:language that would have "software engineering" features for writing large
:systems.  For me, that would mean some level of typing, structured types,
:functional scoping, and some way to deal with code in separate modules,
:but I'm sure there's more to it if one were to consult some standard texts
:on this issue.  Would be nice to be able to create somewhat complex data
:types, e.g., trees, and store "pointers" to functions, but not necessarily
:the way C does it, maybe more like Lisp.  It would of course need to be
:able to run fairly efficient code.  Seriously, it would also want to have
:a little style, rather than being a grab-bag amalgam of every known
:programming language, which can impair readability.  (Tom, I'm not hostile
:to perl, so don't be bashful about saying perl has all of these things and
:more, but jeez it looks messy.)  My rather simplistic attitude is that good
:code can be fiddled with in one place, without unanticipatable side effects
:in other places.
:
:If there's any advantage to such a thing, over C, it would be the sort of
:padded environment that allows programs to be written fairly quickly without
:worrying about dereferencing null pointers and things like that.  Ideally,
:it would also be possible to convert straight to C without much re-design,
:so it could be used for prototyping.

Who me, bashful?  :-) Your criteria do describe perl rather well.  

Of the things you mention, perl is not big on types, structured or
otherwise.  You can do it, but it's not much fun.  I believe this will 
be ameliorated in perl5.  Of the things you mentioned, what perl does 
do well is:

    shell-style language w/ software engineering features for writing
	large programs, as follows...
    functional scoping (i think -- what does functional mean here?) 
    code in separate modules (protected namespaces, module init code) 
    pointers to functions 
    fairly efficient code 
    quick protoyping 
    no worries on null pointers

--tom

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

 "Unix is simple, but it takes a genius to understand the simplicity."
			    --Dennis Ritchie
Newsgroups: comp.unix.shell
From: etxmesa@eos.ericsson.se (Michael Salmon)
Subject: Re: Awk question
Reply-To: etxmesa@eos.ericsson.se (Michael Salmon)
Organization: Ericsson Telecom AB
Date: Wed, 2 Sep 1992 07:36:36 GMT

In article <BtxLJ3.BzE@nntp-sc.Intel.COM>, 
brodesky@td2cad.intel.com (Michael Brodesky) writes:
|> 
|> 
|> I would like to get the current year into my awk program. Any
|> clues into doing this?
|> 
|> Do I need to 
|> date |nawk -f code inputfile
|> 
|> 
|> code
|> {
|> print $6
|> }
|> 
|> 
|> Only problem is it does not work.

I think that you need to insert a - to tell nawk to read stdin, however
this is perhaps a better solution:

 eos6c02 xanim 40 > nawk 'BEGIN { print year }' `date +year=%y`
92

-- 

Michael Salmon

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

Ericsson Telecom AB
Stockholm
From: dave@tetra.co.uk (David Sussman)
Newsgroups: comp.unix.shell
Subject: Korn shell and file descriptors
Date: 25 Aug 92 09:43:57 GMT
Organization: Tetra Ltd., Maidenhead, UK


I have an interesting Korn Shell problem.  I have a script containing:

	echo stream 1 >&1
	echo stream 2 >&2
	echo stream 3 >&3
	echo stream 4 >&4

Under the Bourne Shell this works ok, but the Korn Shell produces:

	stream 1
	stream 2
	./ksh[3]: 3: bad file unit number
	./ksh[4]: 4: bad file unit number

Why?
From: stuart@wstuart (Stuart Hood)
Newsgroups: comp.unix.shell
Subject: Re: alias problems
Date: 2 Sep 92 18:48:06 GMT
Reply-To: stuart@siesoft.co.uk
Organization: Siemens Nixdorf Information Systems Ltd.
X-Newsreader: Tin 1.1 PL4

mickey@sfera.kharkov.ua (Mickey Serg Antonoff) writes:
: 
: alias md "sh -c 'for f in \!*;do mkdir $f ; cd $f;done'"
: 
:   it have to do:
: 	make directory, than cd to it;
:   call:
: 	cd ~
: 	md 1 2 3 4 5 6
:   result:
: 	cwd = ~/1/2/3/4/5/6
: 

This doesn't work because "sh -c" starts up a new process.
New processes inherit their parent's environment (including
"cwd") but cannot (sensibly) alter their parent's environment.

A common "trick" to get round this problem is for the child
process to "echo" the result of its task and for the parent
to use that output in some way.  Something like:

    cd `sh -c 'for f in 1 2 3 4 5 6; \
	    do mkdir $f; cd $f; echo -n $f/; done; echo'`

would change the "cwd" of the current process.  So an alias
along the lines of:

    alias md cd \`sh -c \'for f in \!\* \; \
	    do mkdir \$f \; cd \$f \; echo -n \$f/ \; done \; echo\'\`

should do what is required.

Note: the use of '\' is needed to avoid the problem of:
      "f": variable not found

This looks too messy to my mind so I would prefer to use
"source" and a file.  Given the file:

    # $HOME/.md
    foreach d ( $list )
	mkdir $d
	cd $d
    end

then we can implement the simple alias:

    alias md 'set list = "\!*" ; source ~/data/md'

Stuart.
-
--
S I E M E N S  Stuart Hood === Siemens Nixdorf House, Bracknell, Berks, UK
-------------  Phone: + 44-344-850892          Email: stuart@siesoft.co.uk
N I X D O R F  - Never let ignorance stand in the way of a good argument -
Newsgroups: comp.unix.shell,comp.unix.questions