From: Greywolf <greywolf@starwolf.com>
To: cygwin@cygwin.com
Subject: Re: find / without traversing /proc
Date: Sun, 30 Apr 2017 23:19:00 -0000 [thread overview]
Message-ID: <e87fb1c6-2a9d-959c-ffed-bd0b3aa27137@starwolf.com> (raw)
In-Reply-To: <a03e4bd6-721c-f449-27d4-66c6ed706042@starwolf.com>
[oops; hit send when meant to hit cancel (while confirming what I was
talking about before sending it...)]
On 2017-04-29 00:16, Greywolf wrote:
> -xdev was never a GNU extension; it was in Posix 1 (1990).
>
> On 2017-04-28 17:32, Andrey Repin wrote:
>> Greetings, Eric Blake!
>>
>>> On 04/27/2017 08:11 PM, Andrey Repin wrote:
>>
>>>>
>>>>> Doesn't the -xdev switch help with this?
>>>>
>>>> Just keep in mind that -xdev is an extension and different platform
>>>> may use a
>>>> different way to indicate that find should stick to the current device.
>>
>>> Huh? find -xdev is specified by POSIX, so it's portable:
>>
>>> http://pubs.opengroup.org/onlinepubs/9699919799/utilities/find.html
>>
>> 2016 edition. It's new. But pleasant.
>> Last time I checked it was labeled as GNU extension.
>>
>>
>
> --
> Problem reports: http://cygwin.com/problems.html
> FAQ: http://cygwin.com/faq/
> Documentation: http://cygwin.com/docs.html
> Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2017-04-29 7:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-27 16:31 bonhard
2017-04-27 17:16 ` Václav Haisman
2017-04-27 19:15 ` Andrew Schulman
2017-04-28 17:19 ` Andrey Repin
2017-04-28 18:38 ` Eliot Moss
2017-04-29 0:35 ` Eric Blake
2017-04-29 15:11 ` Andrey Repin
2017-04-30 21:37 ` Greywolf
2017-04-30 23:19 ` Greywolf [this message]
2017-04-28 10:05 ` Gary Johnson
2017-04-28 14:07 ` Brian Inglis
2017-04-28 13:09 Ugly Leper
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=e87fb1c6-2a9d-959c-ffed-bd0b3aa27137@starwolf.com \
--to=greywolf@starwolf.com \
--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).