From: "Larry Hall \(Cygwin\)" <reply-to-list-only-lh@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: ash start-up issue
Date: Fri, 30 Jul 2010 18:55:00 -0000 [thread overview]
Message-ID: <4C5319A0.4080600@cygwin.com> (raw)
In-Reply-To: <AANLkTikDN+tPWU82MJ6qK98=yoGDQBwhqUubze74sN6v@mail.gmail.com>
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.
--
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
next prev parent reply other threads:[~2010-07-30 18:27 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) [this message]
2010-07-30 18:59 ` Steven Collins
2010-08-02 12:11 ` Steven Collins
2010-08-03 4:24 ` Larry Hall (Cygwin)
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=4C5319A0.4080600@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).