This is the mail archive of the
mailing list for the Cygwin project.
Re: Fresh Cygwin-64 instal reports post-install errors for bash
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Tue, 23 Apr 2013 10:44:41 +0200
- Subject: Re: Fresh Cygwin-64 instal reports post-install errors for bash
- References: <5F8AAC04F9616747BC4CC0E803D5907D0AF6C605 at MLBXv04 dot nih dot gov>
- Reply-to: cygwin at cygwin dot com
On Apr 23 01:52, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote:
> Just wanted to share that while installing Cygwin64 on a clean PC, setup threw me the following postinstall errors:
> 2013/04/22 21:38:33 running: C:\Cygwin64\bin\bash.exe --norc --noprofile "/etc/postinstall/bash.sh"
> ln: failed to create symbolic link `/dev/stdin': Read-only file system
> ln: failed to create symbolic link `/dev/stdout': Read-only file system
> ln: failed to create symbolic link `/dev/stderr': Read-only file system
> ln: failed to create symbolic link `/dev/fd': Read-only file system
> 2013/04/22 21:38:33 abnormal exit: exit code=1
/dev is a bastard directory. If it not exists on the filesystem, it is
faked within Cygwin, but then it is a read-only filesystem. If it exists
on the filesystem, the device entries are faked by Cygwin, but you can
also add your own entries in /dev.
The above happens when /dev doesn't exist on the filesystem. I didn't
get this error in my three test installations. Usually /dev is generated
by the 000-cygwin-post-install.sh postinstall script, since it also
has to create the /dev/smh and /dev/mqueue subdirs. I don't know why
it failed for you, though.
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple