in install
---
- Original Message -
From: "Christopher Faylor"
To:
Sent: Monday, December 28, 2009 2:19 AM
Subject: Re: No go after update to 1.7.1
On Sun, Dec 27, 2009 at 11:23:16AM +0100,
On Tue, Dec 29, 2009 at 7:08 PM, Dave Korn wrote:
> Take a look in /etc/postinstall. If you see lots of files named "*.sh",
> then you can simply re-run setup.exe and click right through it without
> changing any of the settings from last time and it will finish off running any
> scripts that it
On Tue, Dec 29, 2009 at 06:08:50PM +, Dave Korn wrote:
>Of course, this means that it's all someone else's fault and Cygwin is
>perfect :-) and I'm not saying that under any kind of duress or
>gravitationally-inspired threat from any kind of even-toed aquatic
>ungulant whatsoever ...
Gentlemen
Bernd Bartmann wrote:
> Now how to go on to get the cygwin installation fixed? As Larry
> pointed out - because bash could not be run during the setup process
> the postinstall scripts couldn't be run.
> Shall I just reinstall all packages but the core cygwin package?
Take a look in /etc/postin
On Tue, Dec 29, 2009 at 6:05 PM, Dave Korn wrote:
> We have a suspect:
>
>> "11:09:08,3362588","bash.exe","3396","CreateFileMapping","C:\Programme\BitDefender\BitDefender
>> 2010\Active Virus Control\midas32-v2_58\PLUGIN_NT.M32","SUCCESS","SyncType:
>> SyncTypeOther"
>
> That's listed on BLODA.
Bernd Bartmann wrote:
>
> procmon to monitor what bash is actually doing. As it seems it stops
> because it can't find /etc/passwd and /etc/fstab which indeed are
> missing. Shouldn't they have been created during the setup process?
> Also, /etc does not contain any files just some sub-directorie
[ Cc'ing the list back in now, FTR. ]
Bernd Bartmann wrote:
>> Looks like your post didn't make it through to the list; there's nothing in
>> the archive for your message with ID
>> <6c18a4f0912280230k601eca9me32c056e09117...@mail.gmail.com>. Probably
>> something somewhere down the line though
On 12/29/2009 10:57 AM, Bernd Bartmann wrote:
Obviously my last post didn't make it through the mailing list
probably because of a .csv attachment. So, here's the original text
again:
Setting the PATH to C:\cygwin\bin only doesn't help either. So I tried
procmon to monitor what bash is actually
Obviously my last post didn't make it through the mailing list
probably because of a .csv attachment. So, here's the original text
again:
Setting the PATH to C:\cygwin\bin only doesn't help either. So I tried
procmon to monitor what bash is actually doing. As it seems it stops
because it can't fin
On Mon, Dec 28, 2009 at 11:30 AM, Bernd Bartmann wrote:
> On Mon, Dec 28, 2009 at 12:31 AM, Christopher Faylor
> wrote:
>> I'd suggest at this point that you run sysinternals procmon to see if
>> you can figure out why bash isn't starting. You might also try running
>> with a trimmed down PATH.
>
On Sun, Dec 27, 2009 at 05:58:20PM -0500, Larry Hall (Cygwin) wrote:
>On 12/27/2009 01:00 PM, Bernd Bartmann wrote:
>> On Sun, Dec 27, 2009 at 6:56 PM, Andy Koppe wrote:
>>> Except for cygwin1.dll of course. Try reinstalling the cygwin package
>>> itself as well.
>>
>> Reinstalling cygwin-1.7.1-1
On 12/27/2009 01:00 PM, Bernd Bartmann wrote:
On Sun, Dec 27, 2009 at 6:56 PM, Andy Koppe wrote:
Except for cygwin1.dll of course. Try reinstalling the cygwin package
itself as well.
Reinstalling cygwin-1.7.1-1 doesn't help either.
I'd recommend getting the output of 'cygcheck -s -r -v' and
On Sun, Dec 27, 2009 at 6:56 PM, Andy Koppe wrote:
> Except for cygwin1.dll of course. Try reinstalling the cygwin package
> itself as well.
Reinstalling cygwin-1.7.1-1 doesn't help either.
Best regards,
Bernd.
--
Problem reports: http://cygwin.com/problems.html
FAQ: htt
2009/12/27 Bernd Bartmann:
>> What does:
>>
>> c:\cygwin\bin\cygcheck c:\cygwin\bin\bash.exe
>>
>> show? It will probably show that you're missing some basic dlls
>> which, for some reason, will need to be (re)installed.
>>
>> You can find the packages which hold the missing dlls by going to
>> ht
On Sun, Dec 27, 2009 at 4:19 PM, Christopher Faylor
wrote:
> What does:
>
> c:\cygwin\bin\cygcheck c:\cygwin\bin\bash.exe
>
> show? It will probably show that you're missing some basic dlls
> which, for some reason, will need to be (re)installed.
>
> You can find the packages which hold the missi
On Sun, Dec 27, 2009 at 11:23:16AM +0100, Bernd Bartmann wrote:
>On Sun, Dec 27, 2009 at 12:35 AM, Christopher Faylor
> wrote:
^^^
Please don't quote email addresses in the body of your message.
>> What happens if you just
>>
>> cd c:\cygwin\bin
>> .\bash
>
On Sun, Dec 27, 2009 at 12:35 AM, Christopher Faylor
wrote:
> What happens if you just
>
> cd c:\cygwin\bin
> .\bash
>
> In a command shell?
After starting a cmd window I get:
C:\> cd cygwin\bin
C:\cygwin\bin> .\bash
C:\cygwin\bin>
So after trying to start bash I just get back to the cmd comman
On Sat, Dec 26, 2009 at 02:44:40PM +0100, Bernd Bartmann wrote:
>> That may be the symptom of two different versions of the DLL existing on
>> your system.
>>
>> See: http://cygwin.com/problems.html for more information on how to track
>> down Cygwin problems.
>
>Ok, one step closer but still no go
> That may be the symptom of two different versions of the DLL existing on
> your system.
>
> See: http://cygwin.com/problems.html for more information on how to track
> down Cygwin problems.
Ok, one step closer but still no go. There was indeed a second version
of the cygwin dll in the default se
On Fri, Dec 25, 2009 at 07:15:57PM +0100, Bernd Bartmann wrote:
>Hi,
>
>I just updated my old cygwin installation to the new version 1.7.1.
>I'm running it on a German WinXP SP3. The installation process went
>without any problem or error message, but now if I try to start cygwin
>using the desktop
Hi,
I just updated my old cygwin installation to the new version 1.7.1.
I'm running it on a German WinXP SP3. The installation process went
without any problem or error message, but now if I try to start cygwin
using the desktop icon a command window appears for a short time and
then goes away aga
21 matches
Mail list logo
