X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Wed, 4 Apr 2012 16:03:36 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Cygwin 1.7.12-1: exit code 1 during post-install regarding dirs in /dev
Message-ID: <20120404140336.GE8014@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <4F7C215E DOT 60702 AT andreloker DOT de> <20120404121241 DOT GB8014 AT calimero DOT vinschen DOT de> <20120404130409 DOT GC28256 AT calimero DOT vinschen DOT de> <4F7C4DAB DOT 4020003 AT redhat DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <4F7C4DAB.4020003@redhat.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On Apr  4 07:33, Eric Blake wrote:
> On 04/04/2012 07:04 AM, Corinna Vinschen wrote:
> > On Apr  4 14:12, Corinna Vinschen wrote:
> >> On Apr  4 12:24, Andre Loker wrote:
> >>> I *suppose*  the issue is related to this change in 1.7.12:
> >>> "- Cygwin now automatically populates the /dev directory with all
> >>> existing POSIX devices."
> >>>
> >>> Do I have to take any actions regarding those issues? If so, which?
> >>
> >> Thanks for the report.  That's a blatant bug in the /dev handling.
> >> I hope I fixed it sufficiently in CVS.  I'm just generating a new
> >> snapshot which should be available in about half an hour on
> >> http://cygwin.com/snapshots/
> >>
> >> Please give it a try.  For instance, call the /etc/postinstall/bash.sh
> 
> A question from the bash maintainer - do I need to do anything special
> in the bash postinstall script to live with the new /dev handling?  I
> can push out a new bash package ASAP if that is the case.

No, you shouldn't have to do anything.  The general idea of the new /dev
handling is to handle /dev as virtual read-only filesystem, if it doesn't
exist on disk.  In that case, an ls /dev only lists the devices handled
by Cygwin internally, and you won't be able to create files, dirs, or
symlinks under /dev.

However, if /dev exists as directory on disk, an ls /dev lists the
internal devices *and* all files within /dev on disk.  So /dev mutates
to a bastard between real and virtual directory.  The idea is exactly
to have both, a listing of all exsiting internal devices, as well as
the ability to create /dev/shm and /dev/mqueue subdirs, as well as the
stdin/stdout, stderr, and fd symlinks.  And more, just as required.
If that doesn't work, it's just a bug in Cygwin.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

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