On Nov 2 12:20, Brian Dessent wrote:
> I'm not sure if the "SYSTEM user
> has mounts" issue would come up enough to warrant checking for it,
> because I can't really think of how that would come to happen.
I don't think this is really still an issue. AFAIR, the mounts in the
HKU/S-1-5-18 area
On Wed, Nov 02, 2005 at 01:23:39PM -0500, Christopher Faylor wrote:
> Here's a scary one: How about a "cygcheck --report" option which queries
> for a "from" email address and sends the report (as an attachment) to
> the cygwin mailing list?
Sounds like a separate program to me. As flea is to mut
On Wed, Nov 02, 2005 at 12:20:22PM -0800, Brian Dessent wrote:
>Christopher Faylor wrote:
>
>> What other kind of common things could cygcheck be testing for?
>
>I was thinking that instead of just reporting the current value of
>$PATH, it would be handy to also report on the Windows/Registry value
Dave Korn wrote:
if lots of
packages register check-callbacks with cygcheck, we're going to end up
(implicitly) making it dependent on a whole lot of other stuff being there and
working.
You could create a new directory, say /etc/cygcheck[.d]. Any package
that wants cygcheck to run a test fo
Christopher Faylor wrote:
> What other kind of common things could cygcheck be testing for?
I was thinking that instead of just reporting the current value of
$PATH, it would be handy to also report on the Windows/Registry value of
$PATH. That way, you can tell if Cygwin is being added to the pa
) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D.
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
If there's any real truth it's that the entire multidimensional infinity
of the Universe is almost certainly being run by a bunch of maniac
On Wed, Nov 02, 2005 at 06:31:46PM -, Dave Korn wrote:
>Igor Pechtchanski wrote:
>
>> Fair enough. I guess what I was saying is that the addition of the two
>> things I mentioned would make that part of cygcheck output all the more
>> valuable. :-)
>
> Oh yes, totally agree! But that's a sl
Igor Pechtchanski wrote:
> Fair enough. I guess what I was saying is that the addition of the two
> things I mentioned would make that part of cygcheck output all the more
> valuable. :-)
Oh yes, totally agree! But that's a slightly longer-term project :)
> BTW, one thing that's been sugges
On Wed, Nov 02, 2005 at 05:50:28PM -, Dave Korn wrote:
>Christopher Faylor wrote:
>> On Wed, Nov 02, 2005 at 05:37:25PM -, Dave Korn wrote:
>>> Christopher Faylor wrote:
Seeing Igor's analysis of corrupt /etc/services symlinks reminded me
that I wanted to start a discussion on cyg
Igor Pechtchanski wrote:
> On Wed, 2 Nov 2005, Dave Korn wrote:
>
>> Christopher Faylor wrote:
>>> On Wed, Nov 02, 2005 at 05:37:25PM -, Dave Korn wrote:
Christopher Faylor wrote:
> What other kind of common things could cygcheck be testing for?
>>
>> Hey, I had another idea. It s
On Wed, 2 Nov 2005, Dave Korn wrote:
> Christopher Faylor wrote:
> > On Wed, Nov 02, 2005 at 05:37:25PM -, Dave Korn wrote:
> >> Christopher Faylor wrote:
> >>> What other kind of common things could cygcheck be testing for?
>
> Hey, I had another idea. It should definitely scan /etc/postin
Christopher Faylor wrote:
> What other kind of common things could cygcheck be testing for?
>
> cgf
It should search the browser's webcache/history log, and if it doesn't find
that the user's been to view the FAQ lately, it forces it open in a
full-screen window!
cheers,
DaveK
--
Christopher Faylor wrote:
> On Wed, Nov 02, 2005 at 05:37:25PM -, Dave Korn wrote:
>> Christopher Faylor wrote:
>>> Seeing Igor's analysis of corrupt /etc/services symlinks reminded me
>>> that I wanted to start a discussion on cygcheck improvements.
>>>
>>> Ideally, cygcheck should report on
On Wed, Nov 02, 2005 at 12:45:13PM -0500, Christopher Faylor wrote:
>On Wed, Nov 02, 2005 at 05:37:25PM -, Dave Korn wrote:
>>Christopher Faylor wrote:
>>> Seeing Igor's analysis of corrupt /etc/services symlinks reminded me
>>> that I wanted to start a discussion on cygcheck improvements.
>>>
On Wed, Nov 02, 2005 at 05:37:25PM -, Dave Korn wrote:
>Christopher Faylor wrote:
>> Seeing Igor's analysis of corrupt /etc/services symlinks reminded me
>> that I wanted to start a discussion on cygcheck improvements.
>>
>> Ideally, cygcheck should report on things like /etc/services being
>>
Christopher Faylor wrote:
> Seeing Igor's analysis of corrupt /etc/services symlinks reminded me
> that I wanted to start a discussion on cygcheck improvements.
>
> Ideally, cygcheck should report on things like /etc/services being
> wrong.
>
> What other kind of common things could cygcheck be t
16 matches
Mail list logo
