X-Recipient: archive-cygwin@delorie.com
X-SWARE-Spam-Status: No, hits=-1.6 required=5.0 	tests=AWL,BAYES_00,J_CHICKENPOX_66,SARE_MSGID_LONG40,SPF_PASS
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <4A673A27.1090700@dronecode.org.uk>
References: <4A673A27.1090700@dronecode.org.uk>
Date: Wed, 22 Jul 2009 19:57:20 +0100
Message-ID: <416096c60907221157r6d2a0f02j6b6ca1f15c15e3b6@mail.gmail.com>
Subject: Re: [1.7] mount -m output can contain flag 'noexec', which isn't  	understood in /etc/fstab
From: Andy Koppe <andy.koppe@gmail.com>
To: cygwin@cygwin.com
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-IsSubscribed: yes
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@cygwin.com>
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

2009/7/22 Jon TURNEY:
> Jon@byron ~
> $ mount -m
> //necker/jon /home/jon smbfs binary,noexec,noacl,user 0 0
> none /cygdrive cygdrive binary,posix=3D0,user 0 0
>
> I want this to be permanent, so I edit /etc/fstab to add a copy of the li=
ne:
> //necker/jon /home/jon smbfs binary,noexec,noacl,user 0 0
> close the window, and open another shell, which then says
>
> =C2=A0 =C2=A0 =C2=A03 [main] bash 3460 read_flags: invalid fstab option -=
 'noexec'
>
> (Curiously only a cmd.exe shell seems capable of showing this, MinTTY
> doesn't which caused me some confusion initially)

The message is printed while intialising the Cygwin DLL during
mintty's startup. Since mintty is a GUI subsystem program, stdout
points to digital Nirvana at that point.

I don't think there's anything I can do about it short of turning
mintty into a CUI program that hides its console unless there's output
on it already, like rxvt does. That, however, has the unfortunate side
effect of the console popping up briefly, so I'm really not keen on
that.

Perhaps the DLL could allocate a console if one isn't available before
printing diagnostic messages? Or use MessageBox()?

Andy

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

