On Wed, 11 Oct 2006 Jakko Pastuchio wrote :
>hi !
>
>On 11 Oct 2006 09:17:11 -0000, rohit hooda <rohit13hooda@xxxxxxxxxxxxxx> wrote:
>> >In that case, how do you make sure that there are no inode-number collisions
>> >between different filesystems mounted ? if every filesystem is responsible to
>> >allocate and remember its inodes, can't you reach a situation where
>> >two filesystems you mount gave the same inode number to different
>> >files ?
>>Well, as you said there are two different file systems, hence, same inode >number on two different file systems will represent two altogether different entities.
>> >given the inode number in this case, how you can reach the right file ?
>>the device numbers will be different. So, the (device no + inode number) >combination will take you to the right file.
>
>do you know of any example of code that access files by their inode
>numbers ?
files are always accessed by the file descriptors at the highest level
in code the flow will be as follows
process(file_descriptor) -> file_object -> dentry object -> inode object ...
>thanks a lot
>jakko
>>
>> >
>> >thanks !!!
>> >jakko
>>Thanks,
>>-Rohit
>> >
>> >--
>> >Kernelnewbies: Help each other learn about the Linux kernel.
>> >Archive: http://mail.nl.linux.org/kernelnewbies/
>> >FAQ: http://kernelnewbies.org/faq/
>> >
>>
>>
>>
>>
>>
