public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tomasz Chmielewski <mangoo@wpkg.org>
To: LKML <linux-kernel@vger.kernel.org>
Cc: alan-jenkins@tuffmail.co.uk, kovlensky@interia.pl
Subject: Re: mounting windows shares with path exactly like on windows
Date: Fri, 29 Aug 2008 10:50:51 +0200	[thread overview]
Message-ID: <48B7B86B.8090104@wpkg.org> (raw)

Alan Jenkins wrote:

> Tomasz Chmielewski wrote:
>>> 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?
>>
>> What's wrong with just:
>>
>> # mkdir -p /D:/dir
>> # mount.cifs ...
>> # touch /D:/dir/file
>>
>> ?
>>
>> Or, use symlinks from /D:/dir to /mountpoint/dir/
> That only works from the root directory though.  In unix, "C:/" is a
> relative path.

Yeah, creating "C:" symlink in each and every directory accessed by the 
application doesn't sound like a neat solution.

BTW, it's the first time I hear about a unix application which has paths 
like D:/ or C:/ hardcoded.


-- 
Tomasz Chmielewski
http://wpkg.org

             reply	other threads:[~2008-08-29  8:51 UTC|newest]

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

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=48B7B86B.8090104@wpkg.org \
    --to=mangoo@wpkg.org \
    --cc=alan-jenkins@tuffmail.co.uk \
    --cc=kovlensky@interia.pl \
    --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