Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Reply-To: Cygwin List <cygwin@cygwin.com>
Message-Id: <6.2.0.14.0.20041210135251.04b633e0@pop.prospeed.net>
Date: Fri, 10 Dec 2004 13:56:34 -0500
To: cygwin@cygwin.com
From: Larry Hall <lh-no-personal-replies-please@cygwin.com>
Subject: Re: sshd in Windows 2003 server
In-Reply-To: <20041210181035.GB22133@trixie.casa.cgf.cx>
References: <41B86015.2050406@scytl.com> <41B8630B.5050706@scytl.com> <Pine.GSO.4.58.0412091218120.3354@orne> <41B9D414.0@scytl.com> <41B9D74C.9000203@scytl.com> <6.2.0.14.0.20041210120503.047e7b90@pop.prospeed.net> <41B9DBC5.AEF927BA@dessent.net> <Pine.GSO.4.61.0412101232040.26044@slinky.cs.nyu.edu> <6.2.0.14.0.20041210123502.04d28008@pop.prospeed.net> <20041210181035.GB22133@trixie.casa.cgf.cx>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 01:10 PM 12/10/2004, you wrote:
>On Fri, Dec 10, 2004 at 12:40:37PM -0500, Larry Hall wrote:
>>At 12:34 PM 12/10/2004, you wrote:
>>>On Fri, 10 Dec 2004, Brian Dessent wrote:
>>>
>>>> Larry Hall wrote:
>>>> >
>>>> > The shortcut for all of that process is to run the below:
>>>> >
>>>> > mount -f -s -b "<DOS path to Cygwin installation directory>/bin" "/usr/bin"
>>>> > mount -f -s -b "<DOS path to Cygwin installation directory>/lib" "/usr/lib"
>>>> > mount -f -s -b "<DOS path to Cygwin installation directory>" "/"
>>>> >
>>>> > FWIW, following the reporting guidelines at <http://cygwin.com/problems.html>
>>>> > would have given the list this information in your initial post.  In other
>>>> > words, there's good stuff at this page. :-)
>>>>
>>>> hmm... what if there was a simple shell script added to base-files, such
>>>> as "mksysmounts" (and corresponding "mkusermounts" too I suppose) that
>>>> would change any system mounts to user mounts, and vice versa.  (Or
>>>> perhaps a single script with several options.)  Then the response to "I
>>>> installed 'For me only'" would be "just run mksysmounts" instead of
>>>> "reinstall" or "modify these paths as appropriate and run these
>>>> commands".
>>>
>>>Good idea.  I'd call the scripts "remount_as_system" and "remount_as_user"
>>>or something...  And I would also use the
>>>
>>>eval "`mount -m | sed ...`"
>>>
>>>trick that I posted earlier, instead of hard-coding the paths into the
>>>scripts.
>>
>>
>>I have no problem with this but if we're offering suggestions on how to 
>>fix the actual problem, then I'd go to the source and change the install 
>>scripts or maybe even 'cygrunsrv' to provide a warning and/or 'fix'.  
>>That should reduce the number of people having problems running service
>>to only those that don't have permission to do so, in which case we can't 
>>help them anyway.
>
>Maybe we should just get rid of the "install as user" option and only
>use it when absolutely necessary.  Then issue a warning at that point.

Yeah, I'd agree that it's unclear to current users what the implication 
is for installing as "Just for Me" so I don't think it should be a user
selected option.  So I think your suggestion is a step in the right 
direction.


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