Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!snorkelwacker.mit.edu!bloom-beacon!eru!hagbard!sunic!mcsun!corton!mirsa!taloa!taloa.unice.fr!beust From: beust@taloa.unice.fr (Cedric Beust) Newsgroups: comp.sys.amiga.misc Subject: Re: Newer version of LS? Message-ID: <103@taloa.unice.fr> Date: 14 May 91 12:01:10 GMT References: Sender: news@taloa.unice.fr Reply-To: beust@taloa.unice.fr Organization: University of Nice Sophia-Antipolis Lines: 34 Nntp-Posting-Host: taloa.unice.fr In article , torkell@ifi.uio.no (Torkel Lodberg) writes: : I have a problem with LS (the Un*x 'dir' type program). The thing : normally works perfectly all right, but when I enter 'ls work:' : (work: is the physical device name of my A3000 hard-drive, like : fh0: ...), the da.... thing locks up and I have to reboot the machine. : : I use version 4.0k, is there a later version? ls 4.0 did a very weird thing to me, and I decided to switch back to 3.1. After installing it, I tried a 'ls'. Worked fine. And then a 'cd /' and another 'ls' and there... nothing! I checked out with the old 'dir' command and there was definitely something there. But ls just wouldn't display it. So I tried a 'ls -la 'and everything appeared. And so did the reason of this behavior. ls 4.1 had misinterpreted the protection flags on directories, and read that the 'hidden' flag was on, so it wouldn't display any of them. And of course, there were only directories in the directory where I was. Even now, it seems so enormous that I can hardly imagine I didn't dream, but I tried several times and it happened again and again. Anyone else got this? +------------------------------------------------------------------------+ | Cedric BEUST University of Nice | | INET: beust@taloa.unice.fr $whoami | | UUCP: llaor.unice.fr!arkonis!beust god (personal alias) | | -- "To be, or not to be...", | | That is illogical, captain! | | -- Spock | +------------------------------------------------------------------------+