HDTenEightyP/NetNews huggingface dataset:
From: peters@mips2.ma30.bull.com (Dan Peters)
Newsgroups: comp.os.linux
Subject: X-success!
Summary: Got X & gwm working from SLS linux release
Keywords: gwm,X,SLS
Date: 1 Sep 92 13:51:24 GMT
Distribution: comp
Organization: Bull HN Informations Systems Inc.

Hi,

	Thanks to all the great help I received (Doug, Wei, Steve, et.al.).
	I got X running on my 386DX-33 clone, C&T chipset, 8MB mem,
	50MB Linux partition, 9MB swap,Paradise VGA chipset.
	Thanks to Steve for telling me the location of the 'gwm' manual:

		You can get the doc of gwm from:
			xport.lcs.mit.edu 

		in the dir:
		    	~ftp/contrib/gwm

	For enquiring minds, I changed the .xinitrc to start the gwm with
	the additional -p argument to specify the path for the gwm
	lisp files (/usr/lib/X11/gwm).  Now gwm can find all the files
	it needs.
	(I don't even think I needed to copy
	
		/usr/lib/X11/gwm/mwmrc.gwm to $HOME/mwm

	but I am not positive and can't check my linux system at this time).

	With this change my X windows came up and stayed up with no errors.
	An additional change to the Xconfig to change the mouse special file
	to '/dev/ttys1'	and I am up and operational.
	
	Linux is Great!  X is really fun!  SLS made it easy! 
	Thanks, again to all that helped me.

	Dan



-- 

== Dan Peters		 	Bull HN Information Systems Inc.
== (508) 294-3325 (294-3705)	300 Concord Road    MA30/MS850A
== D.Peters@bull.com		Billerica, MA		01821
Newsgroups: comp.os.linux
From: almesber@nessie.cs.id.ethz.ch (Werner Almesberger)
Subject: Re: Problem with find in MSDOS file system
Keywords: DOS FS, linux, find
Organization: Swiss Federal Institute of Technology (ETH), Zurich, CH
Date: Sun, 30 Aug 1992 19:09:22 GMT

In article <3473@ra.nrl.navy.mil> eric@tantalus.dell.com (Eric Youngdale) writes:
> If the i_links field is not accurate, then find screws up.
> I do not know if this is the problem with the msdos fs, but it is fairly
> easy to try.

Yes, the MS-DOS FS has this property. MS-DOS does not know about links and
determining the link count of a directory on the fly can be pretty expensive,
because one has to scan the entire directory for subdirectories.

I'll add this for the next MS-DOS FS release - maybe with an option to turn
it off if it slows the system too much.

- Werner
-- 
   _________________________________________________________________________
  / Werner Almesberger, ETH Zuerich, CH      almesber@nessie.cs.id.ethz.ch /
 / IFW A44  Tel. +41 1 254 7213                 almesberger@rzvax.ethz.ch /
/_BITNET:_ALMESBER@CZHETH5A__HEPNET/CHADNET:_[20579::]57414::ALMESBERGER_/
Newsgroups: comp.os.linux
From: bazyar@teal.csn.org (Jawaid Bazyar)
Subject: Tolkien Ring support (Re: tolken ring support?)
Organization: Colorado SuperNet, Inc.
Date: Thu, 27 Aug 1992 05:04:56 GMT

Mark Diers <UD068690@NDSUVM1.BITNET> writes:

>Hello,
[...]
>  I am currently accessing our mainframe from my dos partition
>  thru a tolken ring card and was wondering if there exists any
>  support for this card on linux. If so, I'd appreciate any help
>  in locating such software.

  While tolken rings are okay, what you _really_ want is Tolkien Ring
support, "One Ring To Network Them" is I believe the product's motto.
The Tolkien Ring networking hardware supports such modern and useful
operations as "wide-area Hobbitcasting".  You can also control the minds
of your coworkers and fellow Ringwielders if you have access on the
SauronServer.

-- 
 Jawaid Bazyar              |   Ask me about the GNO Multitasking Environment
 Procyon, Inc.              |   for the Apple IIgs!   
 bazyar@cs.uiuc.edu         |   P.O Box 620334
 --Apple II Forever!--      |   Littleton, CO 80162-0334   (303) 933-4649
Newsgroups: comp.os.linux
From: hta@boheme.er.sintef.no (Harald Tveit Alvestrand)
Subject: Re: VM386?  Possible?
Reply-To: harald.alvestrand@delab.sintef.no
Organization: SINTEF DELAB, Norway
Date: Wed, 2 Sep 92 08:30:05 GMT

Forgive my ignorance....
what would happen if one did a preprocessing pass through the EXE files when
loading replaced all occurences of POPFD with INT NN (which would trap)?
Of course one would not catch self-modifying code and things that swapped in
code after starting, but still, it seems easier than emulating a 600-point
API....

I would guess that POPFD is a short instruction, that's why I think of
INT NN rather than a subroutine call....

-- 
                   Harald Tveit Alvestrand
Harald.Alvestrand@delab.sintef.no
C=no;PRMD=uninett;O=sintef;OU=delab;S=alvestrand;G=harald
+47 7 59 70 94
Newsgroups: comp.os.linux
From: henan@physun.physics.mcmaster.ca (He Nan)
Subject: Re: Recommendations for a PC to support Linux and X386
Organization: Dept. of Physics & Astronomy, McMaster University
Date: Wed, 2 Sep 1992 21:01:28 GMT

Dear Netters:

     This is the first time I get into this group. Linux seems great from
your articles. May I ask a FAQ question: Could anybody kindly tell me where
is the ftp-site(s) for Linux? Thank you very much and have a good day!


--Norbert N. He
From: bboerner@novell.com (Brendan B. Boerner)
Newsgroups: comp.os.linux
Subject: Re: gdb 4.6 compiled with gcc 2.2.2d
Date: 3 Sep 92 22:17:23 GMT
Organization: Novell, Inc. --Austin

In article <20107@plains.NoDak.edu> grosen@isc.cs.ndsu.nodak.edu (Johannes Grosen) writes:
>Is there a binary of gdb 4.6 compiled with gcc 2.2.2d anywhere?
>I simply don't have the disk space to do it myself.

If someone will point out how I can make this available, I've got
it.

Brendan
-- 
Brendan B. Boerner		Phone: 512/346-8380
Internet: bboerner@novell.com	MHS: bboerner@novell
Please use ^^^^^^^^^^^^^^^^^ if replying by mail.
Newsgroups: comp.os.linux
From: simonich@uservx.plk.af.mil
Newsgroups: comp.os.linux
Subject: Re: help selecting SCSI hardware.
Date: 23 Aug 92 15:06:22 GMT
Organization: Phillips Laboratory - Kirtland AFB

In article <1992Aug23.172424.10606@m.cs.uiuc.edu>, najem@milton.cs.uiuc.edu (Zeyad Najem) writes:
> 
> I'm about to buy the following three items. Linux will be the main OS
> installed on my system (I still need DOS from time to time). I would
> appreciate any comments regarding the selected hardware and/or prices.
> The major use of the system will be LISP/Prolog/TeX/Postscript.
> 
> 
>  o  520MB Fujitsu 3.5" 12ms HD             $1099.00
>  o  Always SCSI controller                 $ 179.00
>  o  Archive Viber 250MB Tape drive         $ 499.00
> 
> 
> The current specs of the system is:
>  
>  o  486/33 ISA
>  o  16MB RAM
>  o  170MB IDE Hard drives. 
> 
> 
> My specific questions are:
> 
>  1) Is the Always controller a good choice ?
> 
>  2) Is there any inheritied limitations in the controller/tape drive
>     that prohibits linux from supporting it in the future ? If enough
>     material is avaialable, I can try writing a driver myself. 
> 
>  3) Do SCSI and IDE coexist ?
> 
> 
>  Thanks for your help and, as always, thanks for everyone who
>  contributed to the success of Linux. 
> 
> 
>  - Ziad

The Always IN-2000 is a solid controller.  However, the Always company
absolutly will not provide specs for it.  Therefore, no SCSI driver
is expected.  The Adaptec 1542 is an even better driver and
it is supported.
  >    najem@cs.uiuc.edu
Newsgroups: comp.os.linux
From: bhenning@wimsey.bc.ca (Bill Henning)
Subject: Re: 0.97p2
Organization: Wimsey 
Date: Sun, 30 Aug 1992 16:29:47 GMT

If some of the speed problems are due to the page tables being swapped in
and out it may be worthwhile to allow a compile time option for the kernal
to keep page tables locked in memory...

Bill

Newsgroups: comp.os.linux
From: adam@microware.com (Adam Goldberg)
Subject: Re: Kalok 3100
Organization: Microware Systems Corp., Des Moines, Iowa
Date: Wed, 26 Aug 1992 13:53:44 GMT

In article <15850@star.cs.vu.nl> jwromei@cs.vu.nl (John Romein) writes:
>Can anyone send me the right WPcom and LZone values of the Kalok 3100 ?  
>I cannot get Linux work properly with this disk (I often get the message
>'HD timeout - HD-controller reset' and occasionally 'Unexpected HD interrupt')
>and was wondering weather this drive is bad or if I set these values wrongly
>(at the moment both zero)  My Seagate ST-157A works without problems but is
>too small and a little slow.

This is not a problem with your WPcom and Landing Zone.  This is a problem
with the HD driver...I had this problem all the way back in 0.13, but
was able (with lots of help from Linus) to get it to go away.  I'd look
into the HD driver, at the timeout code.  Perhaps make it longer, perhaps
muck with it awhile.



-- 
Adam G.
adamg@microware.com, or ...!uunet!mcrware!adamg
The above is not to be construed in any way as the official or unofficial
statements of Microware, or any Microware employees.
Newsgroups: comp.os.linux
From: fjh@munta.cs.mu.OZ.AU (Fergus James HENDERSON)
Subject: Re: Recommendations for a PC to support Linux and X386
Keywords: Linux, X386, munlin
Organization: Computer Science, University of Melbourne, Australia
Date: Thu, 27 Aug 1992 05:39:50 GMT

tdunbar@vttcf.cc.vt.edu (Thomas Dunbar) writes:


> >is anyone keeping track of which machines Linux/X386 is known to run on?
>    i was for a while..wasnt enough demand/need to continue. hilites:
>       avoid DTK motherboards, get ide hd or one of the supported scsi,
>       et4000 based video for X (note the new X386 has a speedup mode 
>       specifically for et4000 cards)
>    get a boot and root floppy to try out the machine if u wish.

How can I get a boot floppy for linux?

Would it be possible to download some DOS program that would create a boot
floppy?

-- 
Fergus Henderson             fjh@munta.cs.mu.OZ.AU      
This .signature virus is a self-referential statement that is true - but 
you will only be able to consistently believe it if you copy it to your own
.signature file!
From: ctne_ltd@uhura.cc.rochester.edu (Chris Newbold)
Newsgroups: comp.os.linux
Subject: Re: Extended partition is not recongnized when boot from HD
Date: 28 Aug 92 14:09:47 GMT
Organization: University of Rochester - Rochester, New York

In <1992Aug26.193610.24951@athena.cs.uga.edu> hal@pollux.cs.uga.edu (Hal N. Brooks) writes:

>In article <1992Aug26.144800.6995@cmcl2.nyu.edu> wuwei@acf3.nyu.edu (Wei Wu) writes:

...

>>However, if I boot the same image from hard disk, (shoelace installed)
>>at boot up, it stated that the primary partitions are OK, the logical
>>partition on IDE is recongnized, but for the SCSI disk, the primary
>>partitions are recongnized , the logical partitions on the extended
>>partitions are NOT recongnized, it gives error messages 'cann't read
>>partition table on device 804' or something like that. Then I cann't 
>>access the extended partition on SCSI disk.  
>>Note that when I boot from floppy everything is fine, I CAN access 
>>the extended partition on the SCSI disk just fine.

...

>I have the same problem.  I posted about my problem a couple of
>weeks ago, but the only responses I got were email messages from
>others (including Wei Wu) who are having the same problem.  I ONLY
>have a SCSI drive, and I was using logical partitions for Linux /usr
>and swap.  Everything's fine if I boot from floppy, but when I boot
>from HD, I get a "Unable to read partition table of device 0801"
>message.

>I sounds like it must be SCSI related.  Perhaps some horrid thing
>that OS/2 does (yes, I'm guilty), maybe because of a HPFS logical
>partition?  I'm also using the 1542B, a Fujitsu M2624FA, and 0.97.

I also two two SCSI disks, with extended partitions for OS/2, Windows and
Linux. I haven't got the thing booting Linux of the hd yet, so no comment
here.

BUT, I ran into the same problem when I tried adding the CD-ROM filesystem
to the kernel, it could no longer read any of my extended paritions.

I'm working with the authors of the  CD-ROM stuff to find out exactly
what is is that breaks, but this makes it look more like a generic problem
with the SCSI drivers and extended partions.

-Chris

-- 
>>>> Chris Newbold <<<< * "If you fool around with a thing for very long you *
University of Rochester	*  		  will screw it up."		     *
Disclaimer: "All warranties expire upon payment of invoice."                
ctne_ltd@uhura.cc.rochester.edu * uhura.cc.rochester.edu!ctne_ltd@uunet
Newsgroups: comp.os.linux
From: jwinstea@fenris.claremont.edu (Jim Winstead Jr.)
Subject: Re: Less gives false warnings
Keywords: termcap, less
Organization: Harvey Mudd College, WIBSTR
Distribution: comp
Date: Wed, 2 Sep 1992 16:20:59 GMT

In article <1992Sep2.105254.15291@kth.se> d88-jwn@dront.nada.kth.se (Johan W}hlin) writes:
>In article <C-AMB.92Sep1101734@solitude.math.utah.edu> c-amb@math.utah.edu (Mark B. Alston) writes:
>>	When ever I use less, in either vga or svga modes, it warns me
>>that the terminal can't clear to line, move up, ...  But, once I hit
>>enter to continue, less is able to perform all of these functions.  I
>>am using the termcap from the 0.97.1 root disk.  Is there a way to
>>tell less that it really can perform these tricks?
>
>I had this problem and copied the entry for the 80x25 term into the terminal
>mode I always use. The construct with refering to that entry did thus not work.
>I did not fiddle around since I always use this term mode.

The problem that both of you had is a less compiled with an old
termcap library that did not know how to handle the :tc=con-unk:
entries in most of the termcap virtual terminal entries.

The best fix is to get the source for less (from prep.ai.mit.edu or
elsewhere) and recompile less, and I also suspect the version from the
MCC interim version does not have this problem.

-- 
                                    +      Jim Winstead Jr. (CSci '95)
                                    |      Harvey Mudd College, WIBSTR
                                    |   jwinstea@jarthur.Claremont.EDU
                                    + or jwinstea@fenris.Claremont.EDU
From: paulz@starfish.Convergent.COM (Paul Zimmerman)
Newsgroups: comp.os.linux
Subject: Re: Background processes not dying on parent exit
Date: 31 Aug 92 20:59:40 GMT
Organization: Unisys Unix Systems Group, San Jose, CA

In <1992Aug31.071011.15546@u.washington.edu> barr@hardy.u.washington.edu (David Barr) writes:

>hammond@kwhpc.caseng.com (Kevin W. Hammond) writes:

>>I'm not sure if this is a shell problem or OS problem.

>Neither; the behavior you are about to describe is normal.

>>  I'll start with the
>>OS....

>>I ran a process in the background from tcsh with the ampersand (&).
>>I would have expected that when I logged out of the shell that my
>>background processes would have died as well, but they didn't.

>>Is the shell responsible for killing the background processes, or,
>>since the shell is the parent of them and has been terminated,
>>shouldn't the OS kill the processes automatically?

>The processes are not supposed to go away unless they are suspended
>for some reason.  Another thing to watch out for: if someone logs in
>on the tty you were on when you started the jobs, they will get the
>output from your program.

Umm, I'm pretty sure your background processes are supposed to get a
SIGHUP when you log out, unless they are started with nohup or they ignore
the SIGHUP signal. At least it works that way on my SVR3 system here at
work. Is this different under POSIX? BSD?

Curious,
Paul
-- 
Paul Zimmerman  --  paul@colosus.Convergent.COM
"I toast, therefore I am."  - AI toaster from _Red Dwarf_
Newsgroups: comp.os.linux
From: drew@ophelia.cs.colorado.edu (Drew Eckhardt)
Subject: Re: tweaking the kernel
Keywords: HD controllers
Organization: University of Colorado at Boulder
Date: Thu, 27 Aug 1992 03:13:55 GMT

In article <6027@pdxgate.UUCP> moyerg@rigel.cs.pdx.edu (gary a moyer) writes:
>I am in the process of trying to get the kernel to compile.  Due to 
>limited memory size I would like to squeeze the kernel down to the
>essesntials.  My question is this:  can I omit the scsi drivers by
>modifying the config.dist.h and removing all the scsi #def's?  I
>am only using and IDE controller so I see no need for any of the
>scsi drivers.
>           Thanks.
>

You could, but as soon as the next Linux version comes out, you'll
have to do it again.  The way this works is you #undef CONFIG_DISTRIBUTION
in config.h, and tailor the config.site.h to suit your tastes.  

Default is for no SCSI drivers, normal hard disk, etc.

Theoretically, you will be able to keep the same config.site.h 
throughout the next N Linux releases, until some one puts in 
something you want.

Also, if you aren't using SCSI support, until a decent config utility
is used, you might want to remove the scsi.a reference and scsi reference
from the makefile after doing the configuration trick - this will cut compile
time some what.

-- 
Microsoft is responsible for propogating the evils it calls DOS and Windows, 
IBM for AIX (appropriately called Aches by those having to administer it), but 
marketing's sins don't come close to those of legal departments.
Boycott AT&T for their absurd anti-BSDI lawsuit.
Newsgroups: comp.os.linux
From: drew@ophelia.cs.colorado.edu (Drew Eckhardt)
Subject: Re: RISC approach to OS - Re: GNU kids on the block?
Organization: University of Colorado at Boulder
Date: Fri, 28 Aug 1992 17:47:43 GMT

In article <1992Aug28.171744.6460@rz.uni-karlsruhe.de> S_TITZ@iravcl.ira.uka.de (Olaf Titz) writes:
>
>While the Linux kernel does its job well, its being monolithic is a
>problem since all of the parts are interdependent, and to comprehend
>the work of one of them, you have to know the whole system. This may
>work for Linux but is unacceptable for bigger systems.

This isn't true - although the kernel is one big chunk of 
code, it is subdivided into smaller modules, such as the VM 
code, each one of the file systems, each device driver, etc.  Some of these
modules have incestous relationships with eachother due to various
kludges and hacks, but this isn't necessary.

You do have to understand some basic "common" things used in the 
kernel - ie, how the fs register points into user space, how 
sleep/wakeup work, etc, but to say you have to understand the 
whole kernel to write a device driver is a gross overstatement.

	<deleted>

>>    I like the Linux RISC-like approach, do only a few things, but very
>>  well and very fast. Build the complex functions out of sequences of
>>  simple operations. To me this means simple kernel calls and the library
>>  providing the complex stuff.
>
>I completely agree, and I wonder why this issue now is raised again by
>Linux where this was the design principle of the original UNIX 20
>years ago.  And now UNIX is a huge giant with a lot of memory donuts
>:-) needed to feed him.

I agree too - 1.5 - 3M for a typical vendor's kernel is outrageous, 
when it doesn't do anything that a generic 500K BSD or Linux kernel
can't do.

>
>>    Don't take this as a rejection of multi-server by me, I'm unconvinced
>>  rather than convinced against. Sort of a software agnostic.
>
>Again: Computers are NOT the right place to practice religion. :-)
>Better an agnostic than determinedly believing in something that can
>possibly be proven wrong. :-)
>

Blasphemy! There is nothing but the one true EMACS! :-)

-- 
Microsoft is responsible for propogating the evils it calls DOS and Windows, 
IBM for AIX (appropriately called Aches by those having to administer it), but 
marketing's sins don't come close to those of legal departments.
Boycott AT&T for their absurd anti-BSDI lawsuit.
Newsgroups: comp.os.linux
From: "Louis J. LaBash, Jr." <A200%SIUEMUS.BITNET@mitvma.mit.edu>
Subject: U*nx Book for DOS usr | newbie
Reply-To: A200%SIUEMUS.BITNET@mitvma.mit.edu
Organization: The Internet
Date: Wed, 2 Sep 1992 17:10:59 GMT

Hi,
Saw your request inquiring about a U*ix book for beginners.
I just started using a u*ix system earlier this year.  Before
that it was DOS since its inception.  I've found the following
book to be very good:

   UNIX System V Release 4, An Introduction, by Rosen,
    Rosinski, & Farber; publisher Osborne McGraw-Hill
    ISBN 0-07-881552-5; price $29.95 US; 1228 pages

Actually, I've been using Ultrix 2.4, DEC's variant of U*ix, an
old version at that, and have found answers to most questions
in the aforementioned book.  The book even point out some of the
differences between DOS syntax and U*ix, as well as discusses PC
U*ix variants, and is written in tutorial style.

 -ljl-
 ---------------------------------------------------------
      /* No group wants equality; only supremacy. */
                          -ljl-
      A200@SIUEMUS.BITNET   |   labashl@vax3.siue.edu
      Louis J. LaBash, Jr., Southern Ill. Univ. @ Edw.
         MS 1052, Edwardsville, IL 62026-1052 USA
Newsgroups: comp.os.linux
From: dje@cygnus.com (Doug Evans)
Subject: Re: QIC 40 / QIC 80 ?
Organization: Cygnus Support
Date: Fri, 04 Sep 1992 15:24:37 GMT
X-Newsreader: Tin 1.1 PL5

Bill Parquet (billp@jupiter.cse.utoledo.edu) wrote:
: I've seen a lot of discussion about this.  The people who were working on
: that for 386bsd complained that the timing requirements were extremely tight
: for running qic 40/80... At least too tight for a multitasking environment.
: 
: If it were really necessary, I'd much rather have a tape backup program that
: ran in some sort of exclusive mode than nothing at all.

CMS wrote a device driver for SCO Unix and Xenix and it runs fine for me
in both single user mode and full multitasking mode.

--
Doug Evans        | With views like these ...
dje@cygnus.com    |                           who needs disclaimers.
Newsgroups: comp.os.linux
From: thoth@uiuc.edu (Ben Cox)
Subject: Re: Linux Project Registry (3 September, 1992) v1.1
Originator: btc30679@uxa.cso.uiuc.edu
Reply-To: thoth@uiuc.edu (Ben Cox)
Organization: Ancient Illuminated Sears of Bavaria
Date: Fri, 4 Sep 1992 02:53:10 GMT

callison@uokmax.ecn.uoknor.edu (James P. Callison) writes:

>2) Keyboard key switching	in fridge  	thoth@uiuc.edu
>   (Ctrl -> Caps Lock, etc.)

I have pulled this out of the fridge and dumped it in the dumpster out
back, since I won't have time to do much hacking with Linux in the
near future.  Sorry about that.

Thanks for the listing; I do think it is a service to the Linux
community!

--
Ben Cox
thoth@uiuc.edu
From: tytso@Athena.MIT.EDU (Theodore Ts'o)
Newsgroups: comp.os.linux
Subject: Re: BUG with bash and Linux-0.97 pl 2
Date: 30 Aug 92 16:24:44 GMT
Reply-To: tytso@Athena.MIT.EDU
Organization: The Internet

Interesting; I'll have to try recompiling the shell under 0.97PL2, then.
It's only when you unset SHLVL and you try exec'ing a program that the
shell core dumps, and it definitely works under PL1.  I wonder what
changed between PL1 and PL2, though.

							- Ted
Newsgroups: comp.os.linux
From: jwiegand@moe.eng.temple.edu ()
Subject: Re: BUG with bash and Linux-0.97 pl 2
Organization: Temple University EE Dept.
Summary: I don't see this.
Date: Sun, 30 Aug 1992 03:10:26 GMT
X-Posted-From: moe.eng.temple.edu
X-Posted-Through: sol.ctr.columbia.edu

In article <1992Aug29.054016.28156@athena.mit.edu> tytso@ATHENA.MIT.EDU (Theodore Ts'o) writes:
>I just recently upgraded to Linux 0.97 patchlevel 2, and after I did, I
>found that xinit wasn't working anymore.  I finally traced it down to my
>.xinitrc file, and to the following specific bug.
>
>If you type the following at bash under 0.97 PL2:
>
>unset SHLVL
>exec /bin/sh
>
>The existing shell will core dump without managing to exec the prgram
>you ask it to exec.
>If you take the same bash binary and run under 0.97 PL 1, the shell will
>*not* core dump and exec the request program instead.  (This is the
>correct behavior).
>This behavior can be duplicated using either the MCC 0.96c /bin/bash, or
>the /bin/bash on the 0.97 rootimage disk.
[stuff deleted]
>							- Ted

Hey! It doesn't do this for me! I have recently rebuilt bash (out of the
box) to deal with the extfs. Maybe your shell is out of date.
jim