This is the mail archive of the
mailing list for the Cygwin project.
Re: After installing 1.7.7 command ls is null --now with cygcheck.out
- From: Gerry Reno <greno at verizon dot net>
- To: cygwin at cygwin dot com
- Date: Mon, 31 Jan 2011 11:02:02 -0500
- Subject: Re: After installing 1.7.7 command ls is null --now with cygcheck.out
- References: <4D46D1FC.firstname.lastname@example.org>
On 01/31/2011 10:15 AM, JÃrgen Steensgaard wrote:
> I have just installed 1.7.7 after several unsuccessful attempts.
> Several auxiliary libraries were not included in the installation
> after setup finished. OK -- so I had to locate and rerun setup
> At some point I succeeded in having a terminal running with a
> bash-shell. It was probably my own fault not to have 'find' and 'sed'
> included, since that obviously is supposed to be common knowledge.
> Finally with the terminal running the shell -- including, finally,
> usual command editing facilities -- one problem remains
> ls gives me no reaction at all :-(
> I can type other commands and get the expected behaviour, but not ls
> -- and who knows what others.
> Quite an experience! With patience I might become as pleased with 1.7
> as with a 1.5 on another machine.
> Any suggestions? I include a cygcheck.out, the generation of which
> followed the message:
> garbled output from 'id' command - no uid= found
> JÃrgen Steensgaard
I'm having this exact same problem. And in my cygcheck Cygwin DLL is
reporting as 1.7.5.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple