Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: "Hannu E K Nevalainen" <_garbage_collector_ AT telia DOT com> To: Subject: RE: Can't create Bash here document. (FIXED) Date: Thu, 18 Nov 2004 20:06:44 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit In-Reply-To: <4A9D05D8.7902F6E2.355BA21E@aol.com> X-IsSubscribed: yes you (YorkshireSkier BLOB aol.com) wrote : I wrote: >> What does this display: >> $ mount -m >> >> I suspect that you need: >> $ mount -fsb "$TEMP" "/tmp" > > Well I won't pretend to understand what's going on here. I forgot to > mention in my original email that the directory '/tmp' exists and is > writeable: 'touch /tmp/fred' works perfectly. Did you have a "/tmp" entry in the "mount -m" output? I guess that you didn't; that might have been the cause to your problem. > Moreover, if I use > 'mount -m' the output is the same as on my machines where I have no > problems. Any /tmp there? > However, I tried your suggested mount command and "Bingo!" the problem > is solved (or at least it appears to be!). So, I thank you for taking > the trouble to reply and for your suggestion. To me this indicates that I was right above. There is a subtle difference between a /tmp *directory* and a /tmp *mount entry*. Because I'm lazy and just "know", I'll leave to others to explain. (Resarch on the matter; begin with finding out what the mount table and mount command does on Linux/BSD) /Hannu E K Nevalainen, B.Sc. EE Microcomputer systems --72--> ** mailing list preference; please keep replies on list ** -- printf("LocalTime: UTC+%02d\n",(DST)? 2:1); -- --END OF MESSAGE-- -- 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/