Mail Archives: cygwin/2004/11/14/08:21:08
In regards to adding code to support coLinux, I don't see why that
would be neccessary. coLinux doesn't need to talk to cygwin. Except
for older versions, coLinux is not built on cygwin.
If someone is really interested, as part of the coLinux tools I wrote
set of functions for querying cygwin paths from a non-cygwin
executable. It does so by calling a cygwin executable to convert
paths. If the executable fails, it assumes the cygwin.dll has not
been installed.
I would not recommend adding it to cygwin, because it would be
pointless. If you know someone has installed cygwin to install the
tool, then there is no reason not to link to the cygwin.dll directly.
However, the tool is open source, so people are free to use it for
their non-cygwin, but cygwin compatible open source projects.
Bill
On Sat, 13 Nov 2004 12:38:32 -0500, Christopher Faylor
<cgf-no-personal-reply-please AT cygwin DOT com> wrote:
> On Sat, Nov 13, 2004 at 01:07:03PM +0100, Reini Urban wrote:
>
>
> >Christopher Faylor schrieb:
> >>On Fri, Nov 12, 2004 at 05:58:00PM +0100, Gerrit P. Haase wrote:
> >>>Christopher Faylor wrote:
> >>>>>Hey cool, you have top?
> >>>>>
> >>>>>$ top
> >>>>>bash: top: command not found
> >>>>>
> >>>>>Where can I get it?
> >>>>
> >>>>http://cygwin.com/cgi-bin2/package-cat.cgi?file=procps%2Fprocps-010801-2&grep=top%5C.exe
> >>>
> >>>I really need to install this package, thanks.
> >>
> >>Just to fruitlessly stifle the next question from anyone else who
> >>has just found out about this package:
> >>
> >>No, there is no way to make top or procps display non-cygwin processes.
> >
> >For everything there's a way. The question is if it's worth the effort.
> >
> >For example I'm now seriously considering exporting a procfs to native
> >windows, just to play with installable filesystems.
>
> I didn't say it was impossible. It's not even hard. It just doesn't
> work now.
>
> >To improve mount and to get cygwin better talk to colinux.
>
> I don't think we want to add any colinux features to cygwin. Maybe
> Corinna will disagree but I don't see any reason to add one byte of
> extra code to cygwin to handle colinux.
>
> cgf
>
>
>
> --
> Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
> Problem reports: http://cygwin.com/problems.html
> Documentation: http://cygwin.com/docs.html
> FAQ: http://cygwin.com/faq/
>
>
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -