Igor Peshansky wrote:
> Well, that's easy enough to test as well: just create a
> "c:\cygwin\bwinrcb.txt" and "c:\q\qwinrcq.txt", make sure that when you do
> a 'find /cygdrive/c -name "*winrc"', you get them in the following order:
> ["c:\bwinrcb.txt", "c:\cygwin\bwinrcb.txt", "c:\q\qwinrcq.txt
On Thu, 19 Jan 2006, Brian Keener wrote:
> Igor Peshansky wrote:
> > The real directory is causing find to recurse into the /cygdrive/*
> > hierarchy, and that, in turn, causes the internal loop error. Note that
> > if you had a c:\bwinrcb file, it would be found with the real /cygdrive
> > direc
Igor Peshansky wrote:
> The real directory is causing find to recurse into the /cygdrive/*
> hierarchy, and that, in turn, causes the internal loop error. Note that
> if you had a c:\bwinrcb file, it would be found with the real /cygdrive
> directory, and not found without it (using your comman
On Thu, Jan 19, 2006 at 01:46:07PM -0500, Igor Peshansky wrote:
>BTW, you ought to get the same warning on Linux if you have weird mount
>structure, e.g.,
>
>/local/users/test on /u/test type none (rw,bind)
>/local/users on /u/test/users type none (rw,bind)
>
>(I don't know if the Linux "mount" wil
Ugh, top-posting... Reformatted.
On Thu, 19 Jan 2006, Linda. A. Walsh wrote:
> Igor Peshansky wrote:
>
> > On Thu, 19 Jan 2006, Corinna Vinschen wrote:
> >
> > > On Jan 18 16:49, Linda A. Walsh wrote:
> > >
> > > > Oh, sorry Brian -- flash update. Have you upgraded in the past
> > > > 45 hours?
Ok...sounds logical.
The warning message about the duplicate inode may be
confusing for those not used to seeing it. I haven't
figured out a way around it (I've had the message for
a long time as I have my 'cygdrive' prefix mapped to "/").
-l
Igor Peshansky wrote:
On Thu, 19 Jan 2006, Corin
On Thu, 19 Jan 2006, Brian Keener wrote:
> [snip]
> It appears the real directory is what causes the internal loop error.
The real directory is causing find to recurse into the /cygdrive/*
hierarchy, and that, in turn, causes the internal loop error. Note that
if you had a c:\bwinrcb file, it wo
Eric Blake wrote:
> find / -xdev -depth -name "*winrc*"
This works - no loop message
> Furthermore, you can try seeing if the error message goes away if find
> never changes device number during the traversal (this is achieved by
> having a real /cygdrive rather than a virtual one):
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Brian Keener on 1/18/2006 11:20 AM:
>
> When I attempt to do a find as in:
>
> [EMAIL PROTECTED] ~
> $ find / -name "*winrc*" -print
>
> I get the following:
>
> find: Filesystem loop detected; `/cygdrive/c/cygwin' has the same device
On Thu, 19 Jan 2006, Corinna Vinschen wrote:
> On Jan 18 16:49, Linda A. Walsh wrote:
> > Oh, sorry Brian -- flash update. Have you upgraded in the past
> > 45 hours? Then you might have the newest feature implemented
> > by Christopher.
> >
> > Is there any logic to doing this for /proc and /cy
On Jan 18 16:49, Linda A. Walsh wrote:
> Oh, sorry Brian -- flash update. Have you upgraded in the past
> 45 hours? Then you might have the newest feature implemented
> by Christopher.
>
> Is there any logic to doing this for /proc and /cygdrive and not
> /dev?
The logic is that /dev should be
On 01/18/2006, Brian Keener wrote:
When I attempt to do a find as in: [EMAIL PROTECTED] ~ $ find / -name
"*winrc*" -print I get the following: find: Filesystem loop detected;
`/cygdrive/c/cygwin' has the same device number and inode as a directory
which is 3 levels higher in the filesystem hier
Oh, sorry Brian -- flash update. Have you upgraded in the past
45 hours? Then you might have the newest feature implemented
by Christopher.
Is there any logic to doing this for /proc and /cygdrive and not
/dev?
At least now everyone can get the drive loop detected message
I've been getting for
On Wed, Jan 18, 2006 at 04:21:42PM -0800, L. A. Walsh wrote:
>Do you have a directory named "cygdrive" in your root? Normally, you
>shouldn't.
Not so: http://cygwin.com/ml/cygwin-announce/2006-01/msg00016.html
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem repor
Do you have a directory named "cygdrive" in your root?
Normally, you shouldn't. For example, if I type
"ls /proc*", I get:
ls: /proc*: No such file or directory
But if I type:
"ls /proc", I see:
1024 cpuinfo meminfo registry statversion
608 loadavg partitions self uptime
---
15 matches
Mail list logo
