public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: New cygwin install hanging on postinstall
Date: Thu, 21 Jan 2016 08:02:00 -0000	[thread overview]
Message-ID: <56A02A77.6050409@cornell.edu> (raw)
In-Reply-To: <B8D164BED956C5439875951895CB4B2250BAE63C@CAFRFD1MSGUSRJH.ITServices.sbc.com>

On 1/20/2016 7:06 PM, KARR, DAVID wrote:
> I was installing cygwin for the first time on a Win7-32bit box.  It is hanging in postinstall, with "0/Perpetual" and "/etc/postinstall/0p_texlive_prep.dash.  I've tried this twice now, and it hangs effectively forever on this step (waited 15-20 minutes each time).  What other information could I provide?  I looked at the end of the setup.log file, but that just indicates that installation was complete.

Check setup.log.full.  If that doesn't help, try running the script 
manually to see what happens (most likely a fork failure requiring a 
full rebase).

Ken

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

  parent reply	other threads:[~2016-01-21  0:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-21  5:34 KARR, DAVID
2016-01-21  5:42 ` Stephen John Smoogen
2016-01-21 19:09   ` KARR, DAVID
2016-01-21 21:29     ` Ken Brown
2016-01-21 21:51     ` Achim Gratz
2016-01-22  3:12       ` KARR, DAVID
2016-01-22  7:30         ` David Stacey
2016-01-22 17:32     ` Andrey Repin
2016-01-22 18:50       ` KARR, DAVID
2016-01-22 20:07         ` Mark Geisert
2016-01-22 20:14         ` Andrey Repin
2016-01-21  8:02 ` Ken Brown [this message]
2016-01-21 13:18   ` Achim Gratz
2016-01-21 21:17     ` Ken Brown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56A02A77.6050409@cornell.edu \
    --to=kbrown@cornell.edu \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).