> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf
> Of Randall R Schulz
> At 13:59 2003-07-23, Chris January wrote:
> > > Randall R Schulz wrote:
> > > > At 18:15 2003-07-22, David A. Cobb wrote:
> > > >>I would wish to tell find not to get involved with the
> /proc filesystem
> > > >>at a
At 13:59 2003-07-23, Chris January wrote:
> Randall R Schulz wrote:
> > At 18:15 2003-07-22, David A. Cobb wrote:
> >>I would wish to tell find not to get involved with the /proc filesystem
> >>at all. Can that easily be done?
> >
> > Very easily:
> > % find / -path '/proc' -prune -o -print
>
> Wou
> Randall R Schulz wrote:
> > At 18:15 2003-07-22, David A. Cobb wrote:
> >>I would wish to tell find not to get involved with the /proc filesystem
> >>at all. Can that easily be done?
> >
> > Very easily:
> > % find / -path '/proc' -prune -o -print
>
> Would it make sense to identify the inodes un
Randall R Schulz wrote:
> At 18:15 2003-07-22, David A. Cobb wrote:
>>I would wish to tell find not to get involved with the /proc filesystem
>>at all. Can that easily be done?
>
> Very easily:
> % find / -path '/proc' -prune -o -print
Would it make sense to identify the inodes under /proc/regis
David,
At 18:15 2003-07-22, David A. Cobb wrote:
Maybe this is something any native *nix speaker knows, but I'm stull
trudging up the learning curve.
It is entirely non-Cygwin-specific, yes.
If I do a (cygwin) find for some fragment of a filename, I get a whole
pile of hits in the /proc/regist
Maybe this is something any native *nix speaker knows, but I'm stull
trudging up the learning curve.
If I do a (cygwin) find for some fragment of a filename, I get a whole
pile of hits in the /proc/registry area -
none of which is relevant. I would wish to tell find not to get
involved with th
6 matches
Mail list logo
