Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <415034C8.B597FF38@adnovum.ch>
Date: Tue, 21 Sep 2004 16:03:52 +0200
From: Andreas Petralia <Andreas DOT Petralia AT adnovum DOT ch>
Organization: AdNovum Informatik AG
MIME-Version: 1.0
To: Cygwin List <cygwin AT cygwin DOT com>
Subject: Re: multi-user environment: mounting a lot of shares via ssh
References: <41502E44 DOT 8CAE54F0 AT adnovum DOT ch> <6 DOT 1 DOT 0 DOT 6 DOT 0 DOT 20040921093736 DOT 03d5bae0 AT pop DOT prospeed DOT net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Larry Hall wrote:
> 
> At 09:36 AM 9/21/2004, you wrote:
> >hi
> >
> >while 'shares' can be mounted in a ssh session via 'net use' by a single
> >user, it seems that in a multi-user environment, the users have to make
> >sure, that they do not re-use already mapped drive letters.
> >
> >consider the following example:
> >
> >user A:
> >1. ssh <host>
> >2. net use h: \\\\computer\\A_home
> >3. ln -s /cygdrive/h /HOMES/A
> > --> ok
> >
> >user B:
> >1. ssh <host>
> >2. net use h: \\\\computer\\B_home
> > --> System error 85 has occurred.
> >     The local device name is already in use.
> >
> >question:
> >how can more than 26 users (user A, user B, ... user Z) mount their
> >HOME-directory?
> >is there a way to solve this problem?
> 
> Is that pubkey or password authentication?

password
 
> Why not use the UNC path directly instead?

because of the following reasons:

1.

i want to make the home-directories available in the directory /HOMES:
  /HOMES/A, /HOMES/B, /HOMES/C, ...
and i think it's not possible to link to a UNC path (eg. ln -s
<UNC_path> /HOMES/A) is it?

2. not every binary (tool) can handle UNC-paths

3. i would like to set up an environment, where *unix*-scripts+tools do
not have to know anything about UNC_paths.

regards,
andreas

--
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/