public inbox for cygwin-talk@cygwin.com
 help / color / mirror / Atom feed
From: mwoehlke <mwoehlke@tibco.com>
To: cygwin-talk@cygwin.com
Subject: Re: slow share = slow scripts?
Date: Thu, 25 May 2006 18:03:00 -0000	[thread overview]
Message-ID: <e54re3$l2p$1@sea.gmane.org> (raw)
In-Reply-To: <20060525172851.GA5946@trixie.casa.cgf.cx>

Christopher Faylor wrote:
> On Thu, May 25, 2006 at 12:20:59PM -0500, mwoehlke wrote:
>> Ooooooh... and here I always thought '-f' was how you told it to *not* 
>> mount 'noexec' (which apparently isn't documented?).
> 
> Yes, there are a whole lot of things which don't actually exist in cygwin
> or in mount which are not documented.  In fact, I would hazard a guess that
> there are an infinite number.

Naw, that would imply that there are an infinite number of instructions 
in Cygwin, in which case it wouldn't fit on my hard drive. ;-)

There may be a hippoplex of things, but not an infinite number. :-)

>> Ok, I'm all confused.  :-)
> 
> You're confused by the man page which clearly states what '-f' and
> '--force' do?

Nope, wasn't reading it... I already "knew" what '-f' does, so I didn't 
think about it.

>  Maybe you need to stop using the computer for the day.

Maybe :-)

-- 
Matthew
...Ruthlessly beating Windows with a hammer until it looks like POSIX.

       reply	other threads:[~2006-05-25 18:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <e52m82$rgm$1@sea.gmane.org>
     [not found] ` <4474FCB5.9070906@cygwin.com>
     [not found]   ` <e54elr$41p$1@sea.gmane.org>
     [not found]     ` <4475C82B.9060207@cygwin.com>
     [not found]       ` <e54ihh$hnf$2@sea.gmane.org>
     [not found]         ` <Pine.GSO.4.63.0605251138210.19906@access1.cims.nyu.edu>
     [not found]           ` <e54l2q$soh$1@sea.gmane.org>
     [not found]             ` <4475E5E3.8010608@cygwin.com>
     [not found]               ` <e54p1r$abp$1@sea.gmane.org>
     [not found]                 ` <20060525172851.GA5946@trixie.casa.cgf.cx>
2006-05-25 18:03                   ` mwoehlke [this message]
2006-05-26  2:49                     ` Gary R. Van Sickle
2006-05-26 16:07                       ` mwoehlke
     [not found]                 ` <004b01c68020$2ca7a190$a501a8c0@CAM.ARTIMI.COM>
     [not found]                   ` <e54pqi$ev6$1@sea.gmane.org>
     [not found]                     ` <20060525175702.GO13907@ns1.anodized.com>
     [not found]                       ` <20060525181108.GF5946@trixie.casa.cgf.cx>
     [not found]                         ` <20060525181935.GQ13907@ns1.anodized.com>
2006-05-25 18:55                           ` Christopher Faylor
2006-05-25 19:07                             ` mwoehlke
2006-05-26  2:06                             ` Gary R. Van Sickle
2006-05-26  3:40                               ` Christopher Faylor
     [not found]                           ` <20060525183058.GB7427@trixie.casa.cgf.cx>
2006-05-25 18:57                             ` Christopher Faylor
2006-05-25 19:37                               ` Igor Peshansky
2006-05-25 19:50                                 ` mwoehlke
2006-05-25 19:56                                   ` Igor Peshansky
2006-05-25 19:00                         ` mwoehlke
2006-05-25 19:10                           ` mwoehlke
2006-05-25 19:42                           ` Igor Peshansky
2006-05-25 20:06                             ` mwoehlke

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='e54re3$l2p$1@sea.gmane.org' \
    --to=mwoehlke@tibco.com \
    --cc=cygwin-talk@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).