Re: Hosting the Debian/kCygwin port?

Jakob Eriksson <[email protected]> Wed, 4 Jan 2012 21:02:52 +0100 (CET)
Newsgroups gmane.linux.debian.ports.windows
Message-ID <204955180.255.1325707372933.JavaMail.open-xchange@sys>
------=_Part_254_1952339299.1325707372871
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

This could be solved for instance with http://dokan-dev.net/en/ , which is
basically FUSE for Windows.
It could work by intercepting new "open()" calls and redirect it to the act=
ual
new file, while keeping the old one until all references are closed and the=
n
delete it. A lot of work, but not impossible.
=C2=A0
One could argue that it is cheating, since Dokan has a driver component.
=C2=A0
The other way would be to patch Cygwin itself, enhancing its file layer to =
do
the magic described above. Also cheating perhaps, but cleaner since it woul=
d
be a 100% user space solution. Might pay to talk to the Cygwin maintainer, =
he
may have ideas about it. Last I emailed him (a LONG time ago) he didn't see
the point, when he had a perfectly working package manager as it is.
=C2=A0
=C2=A0
best regards,
Jakob=C2=A0
=C2=A0
=C2=A0


On January 4, 2012 at 8:48 PM Sjors Gielen <[email protected]> wrote:

> Op 04-01-12 19:06, Carson Chittom schreef:
>
> > Just out of curiousity, has anything happened since this was posted in
> > 2009?
>
> Hi Carson,
>
> Shortly after that e-mail, I concluded that running Debian within Cygwin
> is not possible, as it was impossible to update the system while it was
> running. This is because on Windows, removing an in-memory shared
> library file then writing a new one with new contents, would somehow
> have an effect on running applications, causing crashes because of
> addressing problems. (In other operating systems, the old file stays
> around on the disk while it is in use, and is only removed when the last
> user closes it.)
>
> Sjors
>
------=_Part_254_1952339299.1325707372871
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml">
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"/>
    <title></title>
  </head>

  <body>
    <p style="margin: 0px;">This could be solved for instance with http://dokan-dev.net/en/ , which is basically FUSE for Windows.</p>

    <p style="margin: 0px;">It could work by intercepting new &quot;open()&quot; calls and redirect it to the actual new file, while keeping the old one until all references are closed and then delete it. A lot of work, but not impossible.</p>

    <p style="margin: 0px;">&#160;</p>

    <p style="margin: 0px;">One could argue that it is cheating, since Dokan has a driver component.</p>

    <p style="margin: 0px;">&#160;</p>

    <p style="margin: 0px;">The other way would be to patch Cygwin itself, enhancing its file layer to do the magic described above. Also cheating perhaps, but cleaner since it would be a 100% user space solution. Might pay to talk to the Cygwin maintainer, he may have ideas about it. Last I emailed him (a LONG time ago) he didn&#39;t see the point, when he had a perfectly working package manager as it is.</p>

    <p style="margin: 0px;">&#160;</p>

    <p style="margin: 0px;">&#160;</p>

    <p style="margin: 0px;">best regards,</p>

    <p style="margin: 0px;">Jakob&#160;</p>

    <p style="margin: 0px;">&#160;</p>

    <p style="margin: 0px;">&#160;</p>

    <p style="margin: 0px;"></p>

    <div style="margin: 5px 0px 5px 0px;">
      On January 4, 2012 at 8:48 PM Sjors Gielen &lt;[email protected]&gt; wrote:<br/>
      <br/>
      &gt; Op 04-01-12 19:06, Carson Chittom schreef:<br/>
      &gt;<br/>
      &gt; &gt; Just out of curiousity, has anything happened since this was posted in 2009?<br/>
      &gt;<br/>
      &gt; Hi Carson,<br/>
      &gt;<br/>
      &gt; Shortly after that e-mail, I concluded that running Debian within Cygwin<br/>
      &gt; is not possible, as it was impossible to update the system while it was<br/>
      &gt; running. This is because on Windows, removing an in-memory shared<br/>
      &gt; library file then writing a new one with new contents, would somehow<br/>
      &gt; have an effect on running applications, causing crashes because of<br/>
      &gt; addressing problems. (In other operating systems, the old file stays<br/>
      &gt; around on the disk while it is in use, and is only removed when the last<br/>
      &gt; user closes it.)<br/>
      &gt;<br/>
      &gt; Sjors<br/>
      &gt;
    </div>
  </body>
</html>
------=_Part_254_1952339299.1325707372871--