X-Spam-Check-By: sourceware.org
Date: Tue, 28 Mar 2006 18:43:04 -0500 (EST)
From: Igor Peshansky <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: jack <lists AT qnorth DOT net>
cc: cygwin AT cygwin DOT com
Subject: Re: Installation problem on windows 2000 server
In-Reply-To: <442988BB.4070703@qnorth.net>
Message-ID: <Pine.GSO.4.63.0603281828330.23185@access1.cims.nyu.edu>
References: <44287FE0 DOT 1030605 AT qnorth DOT net> <4428AA86 DOT 40708 AT cygwin DOT com>  <442988BB DOT 4070703 AT qnorth DOT net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On Tue, 28 Mar 2006, jack wrote:

> Larry Hall (Cygwin) wrote:
> > jack wrote:
> > > Hola,
> > >
> > > I'm trying to install cygwin on a windows 2000 terminal server
> > > (remote administration mode).
> > > [snip]
> > > The install finishes fine with no errors, but when I go to double
> > > click on the Cygwin icon, i see the black DOS box for a split
> > > second, then its gone.
> > >
> > > Going in via cmd.exe and trying to launch anything does nothing:
> > > [snip]
> > > Any ideas?
> >
> > Sure.  Read over:
> > > Problem reports:       http://cygwin.com/problems.html
> >
> > Pay particular attention to the part about *attaching* the output of
> > cygcheck. You'll also want to look at the output of
> > /var/log/setup.log*.  Look for any error messages at the end
> > suggesting that any package didn't install properly. Look for scripts
> > in /etc/postinstall/ without a .done extension.  If there are any,
> > just rerun setup without selecting any new packages and then recheck.
> > All the postinstall scripts should have run and been renamed *.done.
> >
>
> OK, there are no files in /etc/postinstall without a .done extension.

Larry's advice is good for the future, but the current version of setup
always renames scripts to .done, even if they returned a non-zero exit
code.  The only case in which the scripts would not be renamed in the
current version is if you cancelled out of setup before the scripts got a
chance to run.

> setup.log has the following that's repeated 17402 times:
> io_stream_cygfile: fopen failed 2 No such file or directory

Those messages are harmless and can be ignored.  They come from the time
you didn't have the setup installed packages database.  This is fixed in
the latest setup snapshot (which is worth trying in any case).

> the setup.log is 1.4 megs:
> http://www.qnorth.net/jack/setup.log

That's the accumulated log of all setup runs.  Can you please also post
setup.log.full from the failed installation (it's overwritten every time
you run setup).

> As far as the output of cygcheck goes, this i'm not clear on:
> Not Found: bash
>
> yet:
> C:\>dir cygwin\bin\bash.exe
>  Volume in drive C has no label.
>  Volume Serial Number is 5419-D3B7
>
>  Directory of C:\cygwin\bin
>
> 12/26/2005  07:12a             451,072 bash.exe
>                1 File(s)        451,072 bytes
>                0 Dir(s)   5,472,993,792 bytes free
> C:\>

Since you don't have c:\cygwin\bin in your PATH, I wouldn't worry about
the "not found" messages.  However, I believe it's already been suggested
that cygcheck should prepend "c:\cygwin\bin" to the PATH before making all
of these checks...

> here's the full output for 'cygcheck -s -v -r':
> (also found here: http://www.qnorth.net/jack/cygcheck.out)

In the future, please *attach* the output of cygcheck, as it creates fewer
false positives in archive searches.  If necessary, we can include the
relevant bits from an attachment just as easily as we can from inline
output.

> Output from C:\cygwin\bin\id.exe (nontsec)
> UID: 400(jack)   GID: 401(mkpasswd)
> 401(mkpasswd)
>
> Output from C:\cygwin\bin\id.exe (ntsec)
> UID: 400(jack)   GID: 401(mkpasswd)
> 401(mkpasswd)

Here's one problem.  Your postinstall scripts obviously haven't completed.
Try reinstalling the "base-passwd" package using setup.  I would also
reinstall the "bash" and "cygwin" packages, for good measure.

The rest of your cygcheck output looks ok.

You said that bash actually does nothing and simply returns to the
prompt...  Do other applications work, e.g., if you type
"c:\cygwin\bin\echo hi", does it print "hi"?  What does "cygcheck bash"
print, when run from "c:\cygwin\bin"?

I wonder if your problem is caused by using the terminal server...  Is
there any way you can get physical access to that machine, and try
running the installed Cygwin programs from the console login?
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_	    pechtcha AT cs DOT nyu DOT edu | igor AT watson DOT ibm DOT com
ZZZzz /,`.-'`'    -.  ;-;;,_		Igor Peshansky, Ph.D. (name changed!)
     |,4-  ) )-,_. ,\ (  `'-'		old name: Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/