Patrick Mackinlay writes:
> Is there
> any way for me to see the stdout/stderr of the script that setup is running?
The most recent run of setup logs into /var/log/setup.log.full.
Regards,
Achim.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/
popped up somewhere
> - but not to the foreground?
>
> Thanks,
>
> Maarten Jacobs
>
> ----
>> To: cygwin@cygwin.com
>> From: patr...@spacesurfer.com
>> Subject: Re: upgrades hang forever on 0p_000_autorebase.dash
>> Date
.@spacesurfer.com
> Subject: Re: upgrades hang forever on 0p_000_autorebase.dash
> Date: Sun, 31 Jan 2016 22:45:14 +
>
> Hello,
>
> It seems that the cygwin setup works fine on one of the machines I tried
> (windows 8.1). However on the other machine I have these issues (eve
Hello,
It seems that the cygwin setup works fine on one of the machines I tried
(windows 8.1). However on the other machine I have these issues (even on
a fresh install). The other machine is a work machine (windows 7). I do
not have access to the admin user, I run the install from my account.
How
Patrick Mackinlay spacesurfer.com> writes:
> It requires user input because the file
> /var/cache/rebase/rebase_dyn
> is created read only the first time and then the second time a rm
> requires user confirmation.
When run from setup then rm should not prompt (and it doesn't for my
installations)
Hello,
I tried upgrading some old cygwin installs on a couple of computers
today. I downloaded the very latest setup (32 bit) and ran them. On one
machine I ran the upgrade twice, on this machine the process hanged
forever on 0p_000_autorebase.dash
Running 0p_000_autorebase.dash manually from das
6 matches
Mail list logo
