This is the mail archive of the
mailing list for the Cygwin project.
Re: Mounting ISOs with Cygwin?
- From: Warren Young <warren at etr-usa dot com>
- To: Cygwin-L <cygwin at cygwin dot com>
- Date: Tue, 04 Jun 2013 15:21:14 -0600
- Subject: Re: Mounting ISOs with Cygwin?
- References: <20130603222026 dot GA11213 at ns2 dot sdsitehosting dot net> <51AD1CFA dot 5050908 at cygwin dot com> <CAPF-yOaOFgHrw_1on74E3E0-gcvjtd_ajRnx_S2PuDfH7Ue94g at mail dot gmail dot com> <51AD2A47 dot 3070808 at etr-usa dot com> <CAPF-yOa+e3X7-vyuvYou9gd3f-sOV5NRyusZrH2gEAqVAq43sw at mail dot gmail dot com>
On 6/3/2013 17:52, Dan Kegel wrote:
On Mon, Jun 3, 2013 at 4:44 PM, Warren Young wrote:
Cygwin != Linux
/proc/cpuinfo begs to differ :-)
$ grep -i linux /proc/cpuinfo | wc -l
Wrong test. I think you were looking for
$ test -f /proc/cpuinfo && echo "looks like linux"
See also http://www.sourceware.org/ml/cygwin-patches/2003-q2/msg00054.html
$ test -f /etc/termcap && echo "looks like BSD"
Any single test is likely to confuse software that needs to be portable.
This is why, 2 decades ago, the creators of Autoconf popularized the
practice of testing for individual needed features, not whole platforms.
(You see this in the long output from a "configure" script. It doesn't
just say "looks like Linux".)
Cygwin does conform most closely to Linux, but if you write softwares
that blindly assumes Cygwin *is* Linux, you're likely to get surprised
at some point.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple