Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
From: Tony Richardson <richardson AT evansville DOT edu>
Date: Fri, 02 Mar 2001 17:24:23 GMT
Message-ID: <20010302.17242373@ar63pc.cecs.evansville.edu>
Subject: RE: NT Problems
To: harry DOT erwin AT sunderland DOT ac DOT uk, cygwin AT cygwin DOT com
X-Mailer: Mozilla/3.0 (compatible; StarOffice/5.2;Win32)
X-Priority: 3 (Normal)
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id MAA23428

I wonder if it might not be related to bash
trying to write to it's history file in their
home directory (which I'm assuming is still on
the C: drive). Modify /etc/profile to change the
value of HOME to be on the network drive before
the user gets a prompt (or try setting HOME
immediately)

I use a network drive for my HOME, without any
problems, so I know it can be done.

Tony Richardson

> -----Original Message-----
> From: Harry Erwin [mailto:harry DOT erwin AT sunderland DOT ac DOT uk]
> Sent: Friday, March 02, 2001 10:46 AM
> To: cygwin AT cygwin DOT com
> Subject: NT Problems
> 
> 
> >On Mon, 26 Feb 2001 12:14:17 -0500, Christopher Faylor 
> wrote:
> >>
> >> On Mon, Feb 26, 2001 at 09:47:09AM +0000, Harry Erwin wrote:
> >> >We're trying to install cygwin on an NT-based network. The
> >> >installation is to the C: drive, while the students have 
> write-access
> >> >only to the H: drive, which contains their home 
> directories. When we
> > ++++++++++++++++++++
> >> >kick off bash and cd to H:/, we get an indication that we're in
> >> >/cygdrive/h/, but when we try a dir or ls on that, we crash hard.
> >
> >I guess that they try to access /tmp which is on C: drive (check
> >your mount table). /tmp must be writable for many programs.
> >
> >Ehud.
> 
> Apparently not the problem. It has to do with the networked drive, 
> H:. Anyone know of issues involving networked drives?
> 
> -- 
> ---
> Harry Erwin, PhD, Senior Lecturer of Computing, University of 
> Sunderland. Computational neuroscientist modeling bat bioacoustics 
> and behavior. <http://world.std.com/~herwin> 
> 
> --
> Want to unsubscribe from this list?
> Check out: http://cygwin.com/ml/#unsubscribe-simple
> 







--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple