X-Spam-Check-By: sourceware.org Message-ID: <45800D44.8010204@byu.net> Date: Wed, 13 Dec 2006 07:25:08 -0700 From: Eric Blake User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.8) Gecko/20061025 Thunderbird/1.5.0.8 Mnenhy/0.7.4.666 MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: bash.exe: warning: could not find /tmp, please create! References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to João Gonçalves on 12/12/2006 11:22 AM: > I am trying to start cygwin and I get this error message. > I understand, from what I read, that this error is because I am using > a different user. Yes, it is annoying that when /tmp is not mounted, and / does not contain a physical subdirectory named tmp, that bash refuses to start. I'll consider ripping that out of bash, since it was an upstream chunk of code protected by __CYGWIN__ (ie. someone in the distant past, before I was maintainer, thought that such a cygwin-specific patch would be useful), and replacing it with mkdir("/tmp") instead. Then the failure would only be if /tmp cannot be created, rather than that it did not exist. - -- Life is short - so eat dessert first! Eric Blake ebb9@byu.net volunteer cygwin bash maintainer -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFgA1E84KuGfSFAYARAgPjAJ44Ul3xdhNtaIgYMKTUyy91zRCHxQCfWMS5 wcz9GovVxsx+f5sOxO+V85w= =bTcT -----END PGP SIGNATURE----- -- 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/