public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Larry Hall \(Cygwin\)" <reply-to-list-only-lh@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: ash start-up issue
Date: Tue, 03 Aug 2010 04:24:00 -0000	[thread overview]
Message-ID: <4C5799DF.4030304@cygwin.com> (raw)
In-Reply-To: <AANLkTiknMdvbg7Zg0Pks_fXmGnWZF-f7JDVRHtC3o26_@mail.gmail.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.
>>
>> Thanks,
>> Steven
>>
>
> 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
> can.

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
out. ;-)

-- 
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
216 Dalton Rd.                          (508) 893-9889 - FAX
Holliston, MA 01746

_____________________________________________________________________

A: Yes.
> 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
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

      reply	other threads:[~2010-08-03  4:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-29 21:14 Steven Collins
2010-07-30 16:25 ` Steven Collins
2010-07-30 16:35   ` Larry Hall (Cygwin)
2010-07-30 16:37     ` Steven Collins
2010-07-30 17:03       ` Steven Collins
2010-07-30 16:47     ` Steven Collins
2010-07-30 17:06       ` Larry Hall (Cygwin)
2010-07-30 17:36         ` Steven Collins
2010-07-30 18:08           ` Eric Blake
2010-07-30 18:15             ` Steven Collins
2010-07-30 18:27               ` Larry Hall (Cygwin)
2010-07-30 18:34                 ` Steven Collins
2010-07-30 18:55                   ` Larry Hall (Cygwin)
2010-07-30 18:59                     ` Steven Collins
2010-08-02 12:11                       ` Steven Collins
2010-08-03  4:24                         ` Larry Hall (Cygwin) [this message]

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=4C5799DF.4030304@cygwin.com \
    --to=reply-to-list-only-lh@cygwin.com \
    --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).