Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!samsung!cs.utexas.edu!ut-emx!mjl
From: mjl@ut-emx.UUCP (mjl)
Newsgroups: comp.sys.amiga.tech
Subject: Re:  ls bugs (was: Strange filesystem prob. w/2.0)
Message-ID: <35192@ut-emx.UUCP>
Date: 5 Aug 90 10:28:20 GMT
References: <adTy02UEb9Vf01@amdahl.uts.amdahl.com> <6633.26aa3109@jetson.uh.edu> <c5jz023A010m01@JUTS.ccc.amdahl.com> <hclausen.2109@adspdk.CBMNET>
Reply-To: mjl@emx.UUCP (Maurice LeBrun)
Organization: UTexas Computation Center, Austin, Texas
Lines: 20

In article <hclausen.2109@adspdk.CBMNET> hclausen@adspdk.CBMNET (Henrik Clausen) writes:

[problems with ls 3.1 and ls 4.0 under AmigaDos 2.0 discussed]
>
>   I've only used V3.1 yet. I get more ordinary, random guru's.
>
>   It dies on my A3000 as well, which uses a 2091A controller (of course),
>and I've tried both Q40 and Q105 drives. My 2.0 is a Beta5, Beta6 RSN.


To add to the confusion..

On my Amiga 3000 (Q105 drive), I believe I could get a system crash
using ls 3.1 by doing a "ls -l env:" immediately after bootup (under
2.0).  I switched to ls 4.0 and have had no problems since.

BTW, what version of the OS is the most recent?

Maurice LeBrun                Institute for Fusion Studies  
mjl@fusion.ph.utexas.edu      University of Texas at Austin