lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Fri, 29 Aug 2008 09:13:46 +0000
From:	Thorsten Kranzkowski <dl8bcu@...bcu.de>
To:	Tomasz Chmielewski <mangoo@...g.org>
Cc:	LKML <linux-kernel@...r.kernel.org>, alan-jenkins@...fmail.co.uk,
	kovlensky@...eria.pl
Subject: Re: mounting windows shares with path exactly like on windows

On Fri, Aug 29, 2008 at 10:50:51AM +0200, Tomasz Chmielewski wrote:
> 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.

current working directory, actually. Which means you don't necessarily have
to use the filesystem root but only a proper start directory for these
mounts/links. But yeah, we don't know if said proprietary application 
does/doesn't cwd() to it. 

I suggest extending this mess a bit:

# mkdir -p /server/share
# mount.cifs ... 

and use UNC paths. '//server/share/dir/file.txt' will work out nicely :-)

Thorsten.

> 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

-- 
| Thorsten Kranzkowski        Internet: dl8bcu@...bcu.de                      |
| Mobile: ++49 170 1876134       Snail: Kiebitzstr. 14, 49324 Melle, Germany  |
| Ampr: dl8bcu@...lj.#rpl.deu.eu, dl8bcu@...vin.dl8bcu.ampr.org [44.130.8.19] |
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ