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.
[ 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
5 matches
Mail list logo
