public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: cygwin@cygwin.com
Subject: Re: find / without traversing /proc
Date: Sat, 29 Apr 2017 00:35:00 -0000	[thread overview]
Message-ID: <2d6ad098-c844-bf4b-0afd-7631cad2b2b7@redhat.com> (raw)
In-Reply-To: <1188853682.20170428041153@yandex.ru>


[-- Attachment #1.1: Type: text/plain, Size: 903 bytes --]

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

-xdev
    The primary shall always evaluate as true; it shall cause find not
to continue descending past directories that have a different device ID
(st_dev, see the stat() function defined in the System Interfaces volume
of POSIX.1-2008). If any -xdev primary is specified, it shall apply to
the entire expression even if the -xdev primary would not normally be
evaluated.

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3266
Virtualization:  qemu.org | libvirt.org


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

  parent reply	other threads:[~2017-04-28 14:07 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 [this message]
2017-04-29 15:11       ` Andrey Repin
2017-04-30 21:37         ` Greywolf
2017-04-30 23:19           ` Greywolf
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=2d6ad098-c844-bf4b-0afd-7631cad2b2b7@redhat.com \
    --to=eblake@redhat.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).