public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Daniel Colascione <dancol@dancol.org>
To: cygwin@cygwin.com
Subject: Re: clisp crashes on startup
Date: Sat, 07 Jul 2012 19:04:00 -0000	[thread overview]
Message-ID: <4FF887F1.6010807@dancol.org> (raw)
In-Reply-To: <1758360489.20120707205120@mtu-net.ru>

[-- Attachment #1: Type: text/plain, Size: 1602 bytes --]

On 7/7/2012 9:51 AM, Andrey Repin wrote:
>>> your mount table looks strange
>>>
>>> C:                /               system  binary,auto
>>> c:\bin            /bin            system  text,cygexec
>>> c:/bin            /usr/bin        system  text,cygexec
>>> C:\lib            /usr/lib        system  binary,auto
>>> c:\usr\local\bin  /usr/local/bin  system  text,cygexec
>>> cygdrive prefix   /drv            system  binary,auto
>>>
>>> Why half are mounted as text instead of binary ?
> 
>> I think that's a cygcheck bug.
> 
>> $ cat /proc/mounts
>> C:/users/dancol/appdata/local/temp /tmp ntfs binary,posix=0,user 1 1
>> C:/usr/local/bin /usr/local/bin ntfs binary,cygexec 1 1
>> C:/bin /usr/bin ntfs binary,cygexec 1 1
>> C:/bin /bin ntfs binary,cygexec 1 1
>> C:/lib /usr/lib ntfs binary,auto 1 1
>> C: / ntfs binary,auto 1 1
> 
> What about `mount` output and contents of your /etc/fstab ?

$ cat /etc/fstab
none              /drv            cygdrive  binary         0 0
c:/bin            /usr/bin        ntfs      cygexec        0 0
c:/bin            /bin            ntfs      cygexec        0 0
c:/usr/local/bin  /usr/local/bin  ntfs      cygexec        0 0

$ cat /etc/fstab.d/dancol
c:/users/dancol/appdata/local/temp /tmp ntfs posix=0 0 0

$ mount
C:/users/dancol/appdata/local/temp on /tmp type ntfs (binary,posix=0,user)
C:/usr/local/bin on /usr/local/bin type ntfs (binary,cygexec)
C:/bin on /usr/bin type ntfs (binary,cygexec)
C:/bin on /bin type ntfs (binary,cygexec)
C:/lib on /usr/lib type ntfs (binary,auto)
C: on / type ntfs (binary,auto)


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]

  reply	other threads:[~2012-07-07 19:04 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-06 22:47 Daniel Colascione
2012-07-07 13:04 ` marco atzeri
2012-07-07 13:41   ` Daniel Colascione
2012-07-07 16:19     ` Reini Urban
2012-07-07 17:45       ` marco atzeri
2012-07-07 19:08         ` Daniel Colascione
2012-07-09 21:01           ` Reini Urban
2012-07-09 21:27             ` Daniel Colascione
2012-07-10  4:59               ` Daniel Colascione
2012-07-10  8:14                 ` Corinna Vinschen
2012-07-10 15:42                   ` Daniel Colascione
2012-07-13  3:48                     ` Daniel Colascione
2012-07-13  7:41                       ` Corinna Vinschen
2012-07-13 12:53                         ` Reini Urban
2012-07-13 14:27                           ` Corinna Vinschen
2012-07-13 16:30                             ` Reini Urban
2012-07-13 17:46                               ` Daniel Colascione
2012-07-07 17:05     ` Andrey Repin
2012-07-07 19:04       ` Daniel Colascione [this message]
2012-07-08 23:20         ` Andrey Repin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4FF887F1.6010807@dancol.org \
    --to=dancol@dancol.org \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).