Cygwin 1.7.12-1: exit code 1 during post-install regarding dirs in /dev

Corinna Vinschen
Wed Apr 4 14:04:00 GMT 2012

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
> >>
> >>
> >> Please give it a try.  For instance, call the /etc/postinstall/
> 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 Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

Problem reports:
Unsubscribe info:

More information about the Cygwin mailing list