You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The reason will be displayed to describe this comment to others. Learn more.
An inode alone is not a unique identifier for the resource at a given path, because multiple devices can be mounted. Each device has its own inode numbers.
Do you plan to make a unique identifier by adding the device number, or add a separate device lookup? Maybe a method called any qw(.v .dev device)?
The reason will be displayed to describe this comment to others. Learn more.
On 24 Jan 2015, at 00:24, Brent Laabs ***@***.*** wrote:
An inode alone is not a unique identifier for the resource at a given path, because multiple devices can be mounted. Each device has its own inode numbers.
Do you plan to make a unique identifier by adding the device number, or add a separate device lookup? Maybe a method called any qw(.v .dev device)?
Ah, good point. I will take that into account as well.
Liz=
47aab48
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
An inode alone is not a unique identifier for the resource at a given path, because multiple devices can be mounted. Each device has its own inode numbers.
Do you plan to make a unique identifier by adding the device number, or add a separate device lookup? Maybe a method called any qw(.v .dev device)?
47aab48
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.