This is the mail archive of the
mailing list for the Cygwin project.
Re: ash start-up issue
- From: "Larry Hall \(Cygwin\)" <reply-to-list-only-lh at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Tue, 03 Aug 2010 00:23:59 -0400
- Subject: Re: ash start-up issue
- References: <AANLkTim884bxpLwFCWH4WJGWb3v0DTwk4Wj+qSPQoFQL@mail.gmail.com> <AANLkTimLs_cVs2n6tvVCVHmtmyvcmMR6dMAj1d1Sn2sH@mail.gmail.com> <4C52FCA3.email@example.com> <AANLkTinC=GNRohJbd04ZKR2UqQw5PCZt_3u2sgGmGUQL@mail.gmail.com> <4C53020D.firstname.lastname@example.org> <AANLkTi=DTcmvYj+tUQy-kL=L9KxBdzhvYwma-3Rz3z9h@mail.gmail.com> <4C530620.email@example.com> <AANLkTimxzkpZcpSXqkV0fmV0HC3t7qBb54JR8cAtbksn@mail.gmail.com> <4C531528.firstname.lastname@example.org> <AANLkTikDN+tPWU82MJ6qK98=yoGDQBwhqUubze74sN6v@mail.gmail.com> <4C5319A0.email@example.com> <AANLkTim7MQx2Ze9k3taoSuHb0_xqQpWqDnP9Xv17tCmm@mail.gmail.com> <AANLkTiknMdvbg7Zg0Pks_fXmGnWZF-f7JDVRHtC3o26_@mail.gmail.com>
- Reply-to: cygwin at cygwin dot com
On 8/2/2010 8:11 AM, Steven Collins wrote:
On Fri, Jul 30, 2010 at 12:34, Steven Collins<> wrote:
On Fri, Jul 30, 2010 at 12:27, Larry Hall (Cygwin)<> wrote:
On 7/30/2010 2:15 PM, Steven Collins wrote:
If this is BLODA I'm just plain screwed because it is corporate driven
and I have no control over it. This scenario is the biggest reason I
hate seeing the BLODA response. It seems to me that it would be good
to find ways to get Cygwin to work despite the presence of things that
are considered BLODA. Many users are in a similar situation to my own
where they are not the masters of what is on their computer. I take it
from the BLODA response that neither of you sees any issue with the
contents of the cygcheck file.
I didn't see anything that caught my attention beyond the services, which
we covered. That doesn't mean there isn't something else of course. ;-)
BLODA is indeed a pain. The fact that there is no transparent way to
deal with it makes it worse.
Since you have 2 identically configured machines with one seeing the
problem and one not suggests that there's a way to "fool" the BLODA
in question. Understanding that would be helpful.
Since I don't see any other options open to me I'm in the process of
doing a complete, clean, reinstall of Cygwin. I'll post the results of
that installation when it is complete. Most likely that won't be until
Monday or later.
The one thing I have thought of since my last post is that I did at
one point attempt to get cygports installed on this machine. That is
something I've not done with the other. I ran into some sort of
problem with that install and gave up on it. I already had cygwin
installed when I tried to do the cygports install. I didn't start over
from scratch for that, despite the process talking about downloading
locally first. I doubt this is the source of the issue, but it is a
difference between this computer and all the others I have set up with
cygwin at work.
Just got into the computer that I left re-installing Cygwin from
scratch. First thing I tried is starting ash.exe from a cmd prompt.
Works fine now. Anything more we can try at this point to figure out
the source of the problem? I still have the install that wasn't
working in C:\cygwin.old. It would be nice to end this conversation
with a conclusion and maybe even a better fix than re-installing for
the next person that sees this type of scenario.
If reinstalling worked, then that says to me that there was something
(and I suspect some service) that was keeping the old cygwin1.dll loaded
even after you killed all the other Cygwin apps. I don't know what that
would be since it wasn't obvious from your cygcheck output, unless you
have a <http://cygwin.com/acronyms/#3PP> installed and hiding somewhere.
I guess a compare of your old and new cygcheck output may shed light on
this or some other difference. You could also do a diff of the old and
new installations looking for clues. And then there's the old search
of your drives for 3PP cygwin1.dlls chestnut.
I had sshd configured under the original install. Can anyone tell me
what files I need to grab from my cygwiin.old in order to get the same
configuration I was using. I could re-run the configuration script,
but then I believe all the computers that I connect to this one would
warn me about a known hosts mismatch. I'd prefer to avoid that if I
Yep. Still I'd start by running the script, since that will set up the
service properly. Then stop sshd, copy over /etc/ssh* and ~/.ssh from
the old installation, and restart sshd. That should do it. That said,
I haven't tested this procedure to make sure nothing important got left
Larry Hall http://www.rfk.com
RFK Partners, Inc. (508) 893-9779 - RFK Office
216 Dalton Rd. (508) 893-9889 - FAX
Holliston, MA 01746
Q: Are you sure?
A: Because it reverses the logical flow of conversation.
Q: Why is top posting annoying in email?
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple