Re: multi-user environment: mounting a lot of shares via ssh

2004-09-21 Thread Brian Ford
On Tue, 21 Sep 2004, Andreas Petralia wrote:

> > 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
>  /HOMES/A) is it?

It is possible.

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

Agreed :-(, but those tools are arguably broken.

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

Why would they?

And, as suggested in a later reply, use mount.

-- 
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
the best safety device in any aircraft is a well-trained pilot...

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



Re: multi-user environment: mounting a lot of shares via ssh

2004-09-21 Thread CyberZombie
Do you want a separate home directory from the one specified in 
/etc/passwd?  You could always 'mount -fsb //computer/A_home /A_home'...

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 
2. net use h: computer\\A_home
3. ln -s /cygdrive/h /HOMES/A
--> ok
user B:
1. ssh 
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?
Why not use the UNC path directly instead?
--
Larry Hall  http://www.rfk.com
RFK Partners, Inc.  (508) 893-9779 - RFK Office
838 Washington Street   (508) 893-9889 - FAX
Holliston, MA 01746 

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


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


Re: multi-user environment: mounting a lot of shares via ssh

2004-09-21 Thread Andreas Petralia
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 
> >2. net use h: computer\\A_home
> >3. ln -s /cygdrive/h /HOMES/A
> > --> ok
> >
> >user B:
> >1. ssh 
> >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
 /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/



Re: multi-user environment: mounting a lot of shares via ssh

2004-09-21 Thread Larry Hall
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 
>2. net use h: computer\\A_home
>3. ln -s /cygdrive/h /HOMES/A
> --> ok
>
>user B:
>1. ssh 
>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?

Why not use the UNC path directly instead?


--
Larry Hall  http://www.rfk.com
RFK Partners, Inc.  (508) 893-9779 - RFK Office
838 Washington Street   (508) 893-9889 - FAX
Holliston, MA 01746 


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



multi-user environment: mounting a lot of shares via ssh

2004-09-21 Thread Andreas Petralia
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 
2. net use h: computer\\A_home
3. ln -s /cygdrive/h /HOMES/A
 --> ok

user B:
1. ssh 
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?

regards,
andrew

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