From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: NTFS inode ouput from ls -i
Date: Fri, 23 Nov 2012 12:21:00 -0000 [thread overview]
Message-ID: <20121123122126.GQ17347@calimero.vinschen.de> (raw)
In-Reply-To: <50AF21C9.9090706@lysator.liu.se>
On Nov 23 08:12, Peter Rosin wrote:
> On 2012-11-22 22:08, Michael Lester wrote:
> > mike@computer ~/test3
> > $ ls
> > file1
> >
> > mike@computer ~/test3
> > $ cat file1
> > Hello!
> > 123
> >
> > mike@computer ~/test3
> > $ ifind -n /cygwin/home/mike/test3/file1 '\\.\c:'
> > 195962
> >
> > mike@computer ~/test3
> > $ icat '\\.\c:' 195962
> > Hello!
> > 123
> >
> > mike@computer ~/test3
> > $ ls -i file1
> > 281474976906618 file1
> >
> > mike@computer ~/test3
> > $
>
> I'm obviously not Corinna, but I did make a quick observation:
>
> 195962 == 0x2FD7A
> 281474976906618 = 0x100000002FD7A
>
> I don't know if that always holds, but it certainly looks promising.
It is. Cygwin uses the FileID value. Note that the FileID type is
ULONGLONG == 64 bit. Stripping off the upper 32 bit, as apparently the
ifind and icat tools do, seems wrong to me.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
--
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:[~2012-11-23 12:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-22 21:08 Michael Lester
2012-11-23 7:11 ` Peter Rosin
2012-11-23 12:21 ` Corinna Vinschen [this message]
2017-07-18 3:34 Harry G McGavran Jr
2017-07-18 15:49 ` Corinna Vinschen
2017-07-18 22:57 Harry G McGavran Jr
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=20121123122126.GQ17347@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.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).