public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Walter Franzini <walter.franzini@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: mounting windows shares with path exactly like on windows
Date: Fri, 29 Aug 2008 11:49:52 +0200	[thread overview]
Message-ID: <86vdxk881r.fsf@acer.nord-com.it> (raw)
In-Reply-To: 20080828095925.AB0ED313C53@f48.poczta.interia.pl

[-- Attachment #1: Type: text/plain, Size: 1719 bytes --]

kovlensky@interia.pl writes:

> I'm sorry to be slightly off topic, when it comes to this list, but
> I have no clue where to look for that and I think it can be doe on
> kernel level only.
>
> In short - I've got bunch of applications running both on windows
> and linux and these applications exchange links to files mounted on
> both sides. The problem is that these paths are different, i.e. like
> D:/dir/file on windows and /mountpoint/dir/file on Linux. What I
> need is unifying them. So my idea is to have path translator on
> anything on kernel level, which will make Linux open call to
> D:/dir/file on Linux work and open /mountpoint/dir/file. Was
> anything close to that ever incorporated in kernel?
>
> Applications are, as usual, closed source, and support for them,
> also as usual, answers "won't be fixed, switch to Windows,
> please". Very helpful.
>
> Any other ideas of solving this problem are also warmly
> welcomed. Also on windows side.

You may want to look at plasticfs (http://plasticfs.sourceforge.net/)

It does not do what you need, but should not be to difficult to
change.

From the Home Page:
------------------------------------------------------------------------
The Plastic File System is an LD_PRELOAD module for manipulating what
the file system looks like for programs. This allows virtual file
systems to exist in user space, without kernel hacks or modules.
------------------------------------------------------------------------

HTH
-- 
Walter Franzini
http://aegis.stepbuild.org/

PGP Public key ID: 1024D/CB3FEB43
Key fingerprint  : FA26 C33B CAFF 7848 EFEB  7327 96AA 2D57 CB3F EB43
Key server       : http://www.keyserver.net

[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]

  parent reply	other threads:[~2008-08-29  9:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-28  9:59 mounting windows shares with path exactly like on windows kovlensky
2008-08-29  9:36 ` el es
2008-08-29  9:49 ` Walter Franzini [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-08-29  8:03 Alan Jenkins
2008-08-29  8:18 Tomasz Chmielewski
2008-08-29  8:40 ` Alan Jenkins
2008-08-29  8:50 Tomasz Chmielewski
2008-08-29  9:13 ` Thorsten Kranzkowski
2008-08-29 10:54 kovlensky
2008-08-29 11:11 ` Al Viro

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=86vdxk881r.fsf@acer.nord-com.it \
    --to=walter.franzini@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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