HDTenEightyP/NetNews huggingface dataset:
From: bas@phys.uva.nl (Bas de Bakker)
Subject: Re: If shell command switches.
Organization: Institute for Theoretical Physics, Amsterdam, the Netherlands
	<22412@sybase.sybase.com> <4755@daily-planet.concordia.ca>
Date: Tue, 18 Aug 1992 15:02:06 GMT

>>>>> On 17 Aug 92 17:19:24 GMT, gsa@alcor.concordia.ca ( CON U GRADUATE STUDENTS' ASSOC ) said:

cugsa>does anyone know where I can find the complete switch listing 
cugsa>of the "if" statement?  I can't seem to find it anywhere..ie:
cugsa>man csh/tcsh/ksh.., yet I know of the if [-f] and if [-r] 
cugsa>only because I saw it used in other scripts.  There are other
cugsa>switches..but apparently sparse documentation as to what they 
cugsa>are and do.

The if statement just looks whether its 'argument' is true or not. All
these -f like switches between [ ] are really processed by the
test(1) command. '[ expression ]' is equivalent to 'test expression'.

So, to get a list of these switches, do 'man test'.

(Some shells have a builtin test, but these take at least the switches
of the system test and if there are more the shell manual should
mention them.)

Bas de Bakker.
From: donn@carson.u.washington.edu (Donn Cave)
Newsgroups: comp.unix.shell
Subject: Re: recursive mkdir
Date: 18 Aug 92 16:17:44 GMT
Organization: University of Washington

john@physiol.su.OZ.AU (John Mackin) writes:

| I get really tired of people who don't understand portability.

Ain't it the truth.  Alas, however, all it takes is some obscure old feature
that you won't find on any platform at your disposal.  The script you posted
fails under DYNIX 3.1, on a Sequent Symmetry:

 $ sh mkdir ding/dong/ding/dong
 mkdir: ding/dong/ding/dong: No such file or directory
 mkdir: mkdir failed in directory /u1/donn

This is basically a BSD 4.2 system, and the shell is so old that not only
does it lack shell functions, it also behaves a bit different with separator
characters.  My recollection is that it specifically exempts "/" from the
separator characters when expanding expressions, for some reason.

| IFS="/$IFS"
...
|    for d in $arg
|    do
|	if test ! -d $d
|	then
|	    if mkdir $d

	Donn Cave, University Computing Services, University of Washington
	donn@cac.washington.edu
Newsgroups: comp.unix.shell
From: nummer_5@obh.in-berlin.de (Christian Wierzbicki)
Subject: How can I rm a file with a '&' ????
Organization: obh - private bbs in Berlin/Germany
Date: Fri, 14 Aug 92 22:03:04 GMT

Can anybody answer this question... Please be quick cos this file is about
3 megs of size...

Ciao...
    nummer_5@obh.in-berlin.de


Newsgroups: comp.unix.shell
From: john@physiol.su.OZ.AU (John Mackin)
Subject: recursive mkdir
Organization: Department of Physiology, University of Sydney, Australia
Date: Tue, 18 Aug 1992 03:30:48 GMT

In article <glaze.093@glaze> glaze@cs.mu.oz.au (Glaze) writes:

> The -p option requesting that mkdir create any missing parent directories.
> However, older mkdir's don't support it, so here's a small script I
> whipped up for you:

The provided script began with "#!/bin/sh", yet used shell functions.

I get really tired of people who don't understand portability.

I append to this message a _portable_ recursive mkdir written in plain
vanilla sh.  As an added bonus, it even has error checking!  Gosh!

-- 
John Mackin <john@physiol.su.oz.au>
`A Systems Programmer spends his life getting into tense situations.'  -Boyd

--- begin Mkdir
#!/bin/sh

name=`basename $0`
case $# in

	0) echo usage: $name directory ... >&2
	   exit 1
	   ;;

	1) cwd=. ;;		# no need to waste time

	*) cwd=`pwd` ;;

esac

IFS="/$IFS"
for arg
do

    case "$arg"
    in
	\/*) cd "/" ;;
    esac

    for d in $arg
    do
	if test ! -d $d
	then
	    if mkdir $d
	    then	: fall through
	    else
		echo $name: mkdir failed in directory "`pwd`"
		exit 1
	    fi
	fi

	# if builtin cd $d
	if cd $d
	then : ok, go on
	else
	    echo $name: cd failed in directory "`pwd`"
	    exit 1
	fi
    done

    # builtin cd "$cwd"
    cd "$cwd"

done
--- end Mkdir
Newsgroups: comp.unix.shell
From: ckd@eff.org (Christopher Davis)
Subject: Re: Octal chmod status
Organization: Electronic Frontier Foundation Tech Central
	<104.22185@incc.com>
Date: Thu, 20 Aug 1992 01:43:49 GMT

Jerry> == Jerry Rocteur <jerry@incc.com> 

 Jerry> Please excuse my ignorance but is perl a shell ????? is this not
 Jerry> comp.unix.shell ?? I may be wrong but *who* want to be pestered
 Jerry> with perl tidbits ?? I don't, if I did I would join a perl
 Jerry> newsgroup ??

Perl is suitable for many of the tasks that shell scripts (in sh, ksh,
bash, or *blech* t/csh) are often written to solve.  It's also usable as
a shell with a little work, but it's not primarily an interactive shell.
(Not that there are that many people I know using the Bourne shell
interactively anymore, if they can help it.)

 Jerry> I work on Pyramid, SCO, AT&T 3B2, Ultrix, Sun and I have not
 Jerry> seen perl on any of these machines, now these companies may be
 Jerry> wrong for not supplying what seems to be a great product, but it
 Jerry> is not on the popular systems and I subscribe to
 Jerry> comp.unix.shell.

You edit with vi (or ex or ed), I presume.  You use sh, or csh if you
have a BSDish vendor.  You put up with vendor-supplied mailers.  You use
and enjoy NIS for host resolution on a Sun.  You don't do any networking
on the 3B2.  You use OpenWindows instead of MIT X.  You don't plan on
compiling anything on Solaris 2.0.

If any of the preceding are false, what's wrong with perl?  It's not
supplied with those systems, well, too bad, TCP/IP isn't supplied with
the 3B2, emacs doesn't come with any of those machines, Sun doesn't ship
MIT X or a resolving libc.so...and you'll never have a C compiler if you
move to Solaris 2.0 :)

Where'd you get your news software?  I didn't know it was supplied with
any of those systems...

perl is freely available from archive sites, CD-ROM distributors, and
the like.  It *runs* on the popular systems, and even MS-Loss.  If we
limited ourselves to what was shipped by the vendor, we'd get that much
less use out of our Unix systems.

 Jerry> If perl *is* a shell, then I apologize, but if perl *is* a shell why
 Jerry> is this person doing 'perl -e .......' ????

Ever do sh -c .....?
--
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: charless@sco.COM (charles stross)
Subject: Re: Echoing Shell Variables
Organization: The Somewhat Contagious Operation, Inc.
Date: Wed, 12 Aug 1992 10:46:38 GMT


In article <2647@nlsun1.oracle.nl> rgasch@nl.oracle.com (Robert Gasch) writes:
>
>I have a little problem that's quite annoying. I have written
>a shell script which receives as it's argument than name of
>a shell variable (ex: PATH) via $1.
>
>The big question is: How can I echo the contents of the variable
>whose name I get? For example: If $1 contains the string PATH,
>I want to be able to do the equivalent of saying "echo $PATH" at
>the command prompt so that I receive a list of directories 
>which are in the path.
> 
>For some reason I can't figure this one out. The only thing
>I've been able to get is PATH (the contents of the argument)
>and errors.
> 
>Any help on this will be much appreciated
>---> Rob
>

Try this:

#!/bin/ksh
eval echo \$$1

(It works for me :)

Attempted explanation:

The eval command reads and executes the Korn shell command line that 
follows it. You use it to induce the shell to scan the command line 
twice before executing it. On the first pass, the shell replaces \$ 
with a literal $ and expands $1 (say, PATH). On the second pass it 
sees the command echo $PATH.

-- 
Charlie Stross   aka  charless@scol.sco.com
UNIX-oriented text mangler
This 'ere is my opinion;
now't t'do wi' SCO.
From: ask@cbnews.cb.att.com (Arthur S. Kamlet)
Newsgroups: comp.unix.shell
Subject: Re: Password protection for terminal via shell.
Date: 12 Aug 92 22:06:56 GMT
Organization: AT&T Bell Laboratories,  Columbus, Ohio

In article <4734@daily-planet.concordia.ca> gsa@alcor.concordia.ca ( CON U GRADUATE STUDENTS' ASSOC ) writes:
>Someone sent me a shell script that is supposed to password
>protect your terminal, yet for some reason it doesn't seem
>to be working.  Can someone tell me what's wrong with this?

Lots of possibilities.  Need more traps for one thing.


Here is a pretty good version of a SysV  ksh  script.

The "cs" command is machine dependent and does a clear - many screen
clearing commands can be used instead.

On a dumb terminal (no windows, no mouse)  it seems to work, though
I'd be curious if it can be broken by non-root users.

Like most scripts, anyone who can get to your terminal for a few
seconds while it isn't protected, can just cat the file, and root
can always read it.  But for everyday stuff, it seems to work as
good as a shell script can work.


Be sure to chmod 700 this script



==== cut here ===

# Copyright (C) Arthur S. Kamlet, 1992
# May be reproduced for private use only as long as this copyright
# notice is intact
#
# chmod 700 for this file



keyword="SECRET_WORD"



case $TERM in
	*hp* | *2621*)
		echo "\033H\033J\c"  #clears the screen
		;;
	615 | 620 | 630 | 730 )
		echo "\033[2J\033[H"
		;;
	*)
		test -s /usr/local/bin/cs && /usr/local/bin/cs
		 test -s ~/bin/cs && ~/bin/cs
		;;
esac
stty ignbrk -brkint -isig -echo
systemname=`uname -n`
while true
do
	echo "$@ \c"
	echo "\n$systemname:  Keyboard is locked. Enter key: \c"
	read word
	case $word in
		"$keyword")
			stty -ignbrk brkint isig echo
			echo ""
			break
			;;
		"cs")
			test -s /usr/local/bin/cs && /usr/local/bin/cs
		 	test -s ~/bin/cs && ~/bin/cs
			;;
		"date")
			/bin/date
			;;
		"who")
			echo
			/bin/who -u
			;;
		*)
			;;
	esac
done

#===========================  cut here ===============

>#
>trap "echo Working on Process;stty echo;kill $$" 2 15
>SECRET="secret"
>stty -echo
>echo "Lock string: \c"
>read BUF1
>echo
>while :
>do
> BUF2= `line < /dev/tty`
>if [ "$BUF2" = "$BUF1" ]
>then break
>elif [ "$BUF2" = "$SECRET" ]
>then break
>fi
>echo "^G\c"
>done
>stty echo
>
>---------
>Dan.


-- 
Art Kamlet  a_s_kamlet@att.com  AT&T Bell Laboratories, Columbus
Newsgroups: comp.unix.shell
From: mitch@clsi (Mitchell N. Perilstein)
Subject: Re: searching for 1st occurrence
Organization: CAD Language Systems, Inc.
Date: 16 Aug 92 15:37:42

> In article <15m8aqINN6ci@seven-up.East.Sun.COM> ltaylor@blinky.East.Sun.COM (Laura Taylor) writes:
>Inside a shellscript, I would like to search for only the
>first occurrence of a particular string, or in otherwords,
>just one occurrence of the same string so I can set it to
>a variable.
>
>For example, say in file called systems, there is a list of
>all the system architectures something like...
>
>SS2
>SS1
>SS2
>4/75

You can just skip the grep and do it in one step:

    awk '/SS2/ {print; exit}' < systems

You might want a better regexp, like /^SS2$/.
---
 Mitchell N. Perilstein                          5457 Twin Knolls Rd
 CAD Language Systems, Inc.                      Suite 101
 410-992-5700                                    Columbia, MD 21045-3259
From: boyd@prl.dec.com (Boyd Roberts)
Newsgroups: comp.unix.shell
Subject: Re: How can I rm a file with a '&' ????
Date: 21 Aug 92 21:55:57 GMT
Organization: Digital Equipment Corporation - Paris Research Laboratory

In article <28300003@tisdec.tis.tandy.com>, kevinl@tisdec.tis.tandy.com writes:
> 
> just use:
> 
> 	rm big\&cow
> 

No, no.  A file with an & requires removal with:

    rm 'big&cow' &


Boyd Roberts			boyd@prl.dec.com

``When the going gets wierd, the weird turn pro...''
From: smr@hitkw14.pki-nbg.philips.de (S.Riehm)
Newsgroups: comp.unix.shell
Subject: Re: Parameter Passing
Date: 17 Aug 92 13:00:46 GMT

rgasch@nl.oracle.com (Robert Gasch) writes:

>I have written a shell script which accepts one parameter. The first
>thing it does after making sure that it is /bin/sh and not some
>other shell is check if the parameters are OK.
>If I call it as
>	ap STRING_ARG
>	sh ap STRING_ARG
>everything is fine. The parameter is recognized and life is great.

>Here comes the confusion: As soon as I call it as
>	. ap STRING_ARG
>the parameter is not recognized anymore. Even supplying it with 
>2 or more parameters does not change the fact that $# is equal to 0. 

>Could some kind soul out there explain what is going on and why
>I get these strange reactions.

I don't know if you would call me a kind soul, but here goes.

the calls:
ap STRING_ARG
sh ap STRING_ARG

are both starting new processes, with the full command line parameter
handling, globbing and what not.

. ap STRING_ARG

on the other hand is invoking an inbuilt command of the shell, 
I guess the guess that wrote the . routine didn't bother checking for
params. ( curiously enough, '. ap args' works on this machine, but I
know the /bin/sh is already broken, so I don't trust it )

You might like to try:

set STRING_ARG
. ap

This also worked for me.. again sending parameter to functions doesn't
work properly so this could be unique to HP's concept of /bin/sh

catchya

-----------------------------------------------------------------
Stephen Riehm		Configuration Management	   _-_|\ 
smr@pki-nbg.philips.de	Philips Kommunikations Industrie  /     \
Work: +49 911 526 2975	Nuernberg, Germany		  \_.-.*/
Fax:  +49 911 526 2095	"I was there, now I am here!"	       v 
"My company speaks another language, I CAN'T speak on it's behalf"
Newsgroups: comp.unix.shell
From: mju@mudos.ann-arbor.mi.us (Marc Unangst)
Subject: Re: Octal chmod status
Date: Wed, 19 Aug 1992 05:11:29 GMT
Organization: The Programmer's Pit Stop, Ann Arbor MI

In article <1992Aug18.181609.8988@news.eng.convex.com> tchrist@convex.COM (Tom Christiansen) writes:
>You might, and people might even use it if they want to lug
>another huge a.out and overly large and misplaceable foo.c 
>around with them wherever they go.  I'd just use this:
>
>    perl -e 'printf("%04o\n", (stat($ARGV[0]))[2] & 07777)'

Hmm.  Huge a.out, huh?  Overly large foo.c, huh?  Hmm.

mju@mudos:~$ ls -l getperms getperms.c
-rwxr-xr-x   1 mju      group       4780 Aug 19 01:06 getperms
-rw-r--r--   1 mju      group        445 Aug 15 01:08 getperms.c
mju@mudos:~$ cd /usr/local/bin
mju@mudos:/usr/local/bin$ ls -l perl*
lrwxrwxrwx   1 root     other          9 Aug 19 01:07 perl -> perl4.019
-rwxr-xr-x   1 bin      bin       283992 Aug 19 01:06 perl4.019
mju@mudos:/usr/local/bin$ cd ../src
mju@mudos:/usr/local/src$ ls -l perl-4.019.tar.Z
-rw-r--r--   1 mju      mju       801616 Aug 10 13:04 perl-4.019.tar.Z
mju@mudos:/usr/local/src$ exit

Sure looks like my program is smaller.  Could just be an optical
illusion, though...

-- 
Marc Unangst                | Real men don't make backups.  Real men never
mju@mudos.ann-arbor.mi.us   | accidentally delete files that they're going
                            | to need later.
Newsgroups: comp.unix.shell
From: john@physiol.su.OZ.AU (John Mackin)
Subject: Re: Sed with shell variables
Summary: Incorrect solution corrected
Reply-To: John Mackin <john@civil.su.oz.au>
Organization: Department of Physiology, University of Sydney, Australia
Date: Fri, 21 Aug 1992 01:36:04 GMT

In article <1992Aug20.105737.29473@ccu1.aukuni.ac.nz>,
	ecmtwhk@ccu1.aukuni.ac.nz (Thomas Koenig) writes:

> rgasch@nl.oracle.com (Robert Gasch) writes:
>
>>The problem I ran into is that I can't get shell variables to
>>work as arguments. When I type
>>	echo $something|sed 's/$this_pattern_var/$that_pattern_var/'
>
>>sed throws up on me. I've tried various combinations of quotation
>>marks without success. Is there an easy way of doing this??
>
> echo $something | sed -e s/$this_pattern/$that_pattern/

Unfortunately, Thomas's solution is wrong.  Since Robert doesn't
say what shell he is concerned about, we can only suppose that he
wants a solution for a `conventional' shell, such as sh or csh
(and not, for example, rc, where Thomas's solution would be right,
but for the wrong reasons).  These shells are macro languages that
re-scan their arguments for delimiters (usually, white space)
after variable substitution.  So the solution presented above
will only work as long as the values of the two pattern variables
don't contain any whitespace (space or tab characters).

Next time, Robert, please do say what shell you are asking about.
I hope, though, that the same solution is correct in this instance
for both sh and csh.  I know it is correct in sh.

Worked example (": mod; " is the prompt):

#
# Set variables
#
: mod; from='from pat'
: mod; to='to pat'

#
# Demonstrate that Thomas's idea does not suffice
#
: mod; echo "from pat to bill it's all a thrill" | sed s/$from/$to/
command garbled: s/from

#
# Give the correct solution
#
: mod; echo "from pat to bill it's all a thrill" | sed "s/$from/$to/"
to pat to bill it's all a thrill

That's the way double-quotes work in sh (and, I think, in csh).
Great, isn't it?  Change to rc now, while you're still impressionable
(you _must_ be impressionable, I hope, if you didn't know how to
do this), and reap the benefit of _only one kind of quoting_!!!

-- 
John Mackin <john@civil.su.oz.au>
        case '\7': *((char *)(384*1024L+062)) = 2;      /* beep */
Newsgroups: comp.unix.shell
From: jal41820@uxa.cso.uiuc.edu (Smiley)
Subject: Re: How to make tcsh the login shell w/0 bothering operator? !FAQ
Organization: University of Illinois at Urbana
Date: Thu, 20 Aug 1992 18:58:35 GMT

friedman@gnu.ai.mit.edu (Noah Friedman) writes:
:)In article <Bsr2Jy.oD@news.cso.uiuc.edu> tinsel@uiuc.edu (Thomas Aaron Insel) writes:
:)> I built the tcsh myself and can have it run by typing "tcsh" in a csh
:)> (the login shell). Now, I want to make tcsh the default login shell,
:)> BUT do it without bothering the system operator. Trust me, I've done
:)> some homework, read the faq and fine-manual, but I can't find an
:)> answer.

:)   Just out of curiosity, why not get your sysadmin to put the appropriate
:)magic in /etc/shells?  It's what, 20 seconds of work?

I know at uiuc, most (read all :) of the admins like to not have anything
like that in a joe-user's directory, nor do they simply want to copy a
compiled program, meaning they have to compile it themself. However,
they don't want to be bothered with finding the source code. Usually
here a person (in this case) would have to find the source code, set it
up in /tmp, and ask *very* nicely.  :)
-- 
        Josh Laff              #     #      
email to: smiley@uiuc.edu     _       _     Hello! I am a signature virus!  
      (217) 384-6249         |#\_____/#|    Join the fun and copy mo*#(*&^!>.
                              \#######/     
Newsgroups: comp.unix.shell
From: barr@pop.psu.edu (David Barr)
Subject: Re: Octal chmod status
Organization: Penn State Population Research Institute
Distribution: na
Date: Sat, 22 Aug 92 23:15:32 GMT

In article <1992Aug20.161528.13941@shell.shell.com> rgh@pern (Richard G. Hash) writes:
>This tends to ignore how long it takes you to compile and install
>perl on every machine you want *it* to run on...

Yes, but the point is you do it _once_ and forget about it.

>Let's see, I have to worry about sun{3,4}, hp9000s{3,7,8}00, dec3100,
>Cray YMP, Ncube, RS6000, Apollo, Amhdahl UTS, VAX (Ultrix), and I'm
>sure there's some others I can't recall right now. Yup, use 'em all, all
>the time.  Gee Tom, if you could just ship me some ready-to-install
>perl distributions for ALL those machines I'll being using it tomorrow.

Have you even tried to compile it on half of these machines?  So you're
trying to say that it's easier for you to write one C solution for all
those machines than it is for Perl?  Personally, I've found Perl to be
one of the easiest packages to compile, especially on odd machines.

>Face it, perl isn't everywhere (though I would like for it to be),
>and it's not *always* the answer to everything.

True, but it's a lot easier to write a portable Perl script than it
is to write a portable C program, agreed?  This becomes even more true
as the complexity of the program increases.

--Dave
-- 
System Administrator, Population Research Institute    barr@pop.psu.edu
  "An analogy is like instant coffee: it can wake you up, but it's
  not the real thing"  -- Peter da Silva
From: barnett@grymoire.crd.ge.com (Bruce Barnett)
Newsgroups: comp.unix.shell
Subject: ignoring parity using stty?
Date: 18 Aug 92 22:10:12 GMT
Reply-To: barnett@crdgw1.ge.com
Organization: GE Corp. R & D, Schenectady, NY

I am trying to find the right option for stty(1) to ignore parity.

Reproduction of problem (SunOS 4.1.1)
	FILE is an ASCII file where some of the characters have the
		8th bit set. 
The commands:
	stty  istrip
	cat FILE
does not remove the 8th bit from the file when it 
is displayed on the terminal (actually xterm or cmdtool). I have tried
various parameters to stty but none seem to work. Perhaps I have a
conceptual problem......

I want to use stty instead of a filter because a shell script is going
to call expect, which will call script(1) followed by a telnet to a
modem pool, which will then dial out to a remote site. I am currently
filtering the output of script to remove parity bits.
--
Bruce Barnett <barnett@crd.ge.com> uunet!crdgw1!barnett
Newsgroups: comp.unix.shell
From: messina@netcom.com (Tony Porczyk)
Subject: Re: Octal chmod status
Date: Wed, 19 Aug 92 14:12:03 GMT
Organization: Messina Software

Tom Christiansen <tchrist@convex.COM> responds to Marc Unangst:

>Big deal.  That infinitesimal time difference is surely not
>worth all the hassle of writing a C program for each and every little

Even though I agree that the perl solution was fine (by being so
small), but I do not understand the bruhaha about the "hassle" of
writing a C program for small tasks.  It is often much simpler and
*faster* to write the C code than to implement other solutions.  At
least it is much more *readable* than the aformentioned perl script... 

t.
From: mauricio@MOZART.AERO.UFL.EDU
Newsgroups: comp.unix.shell
Subject: Compilation problem with acm 2.0
Date: 12 Aug 92 18:26:07 GMT


	During the compilation of acm, I receive the following error message:

cc -systype bsd43 -I../V/lib -O -Wf,-XNh2000 -Olimit 2000 -I../V/lib -I/usr/incl
ude     -DSIGVOID -DXAW_BC -c acm.c
rm -f acm
cc -o acm acm.o -systype bsd43 -I../V/lib -O -Wf,-XNh2000 -Olimit 2000 -L/local/
lib ../V/lib/libV.a -lm -lX11
ld:
Can't open: /bsd43/usr/lib/cmplrs/cc/crt0.o (No such file or directory)
*** Error code 1

Stop.
*** Error code 1

Stop.
mauricio@beethoven: tcsh 302>

	I checked our system and found that the file crt0.o is not
located at	/bsd43/usr/lib/cmplrs/cc/crt0.o but at
/usr/lib/cmplrs/cc/crt0.o; how can I tell about the real location of
crt0.o to the (I)makefile?
From: mfg@castle.ed.ac.uk (M Gordon)
Newsgroups: comp.unix.shell
Subject: Re: challenge: hex sort
Date: 13 Aug 92 11:18:49 GMT
Organization: Edinburgh University

fitzgb@mml0.meche.rpi.edu (Brian Fitzgerald) writes:

>For your amusement: :-)
>Write a shell script to sort hex in numerical order.

#!/bin/sh
awk '{printf("%200s\n",$0)}' | sort -f | sed -e 's/ *\(.\)/\1/'

Change the 200 to whatever the maximum length of the numbers you want
to sort is.

-- 
                                                         _   _   _    _   _	
Michael Gordon - mfg@castle.ed.ac.uk OR ee.ed.ac.uk     | |_| |_| |__| |_| |   
EE Dept, Edinburgh University                           | . . . .      . . |    
It's not an optical illusion, it just looks like one    |_________|~~|_____|    
From: kevinl@tisdec.tis.tandy.com
Date: 20 Aug 92 07:37 CDT
Newsgroups: comp.unix.shell
Subject: Re: How can I rm a file with a '&' ????
Message-ID: <28300003@tisdec.tis.tandy.com>
Nf-ID: #R:<S025H1G@obh.in-berlin.de>:-26:tisdec.tis.tandy.com:28300003:000:107
Nf-From: tisdec.tis.tandy.com!kevinl    Aug 20 07:37:00 1992


	I just tried it and, if your file name was, say, 'big&cow',
just use:

	rm big\&cow

This is much easier.

Newsgroups: comp.unix.shell