From: Rik van Riel <riel@redhat.com>
To: Jeff Shanab <jshanab@earthlink.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Starting a grad project that may change kernel VFS. Early research Re: Starting a grad project that may change kernel VFS. Early research
Date: Tue, 25 Aug 2009 13:28:54 -0400 [thread overview]
Message-ID: <4A941F56.8060502@redhat.com> (raw)
In-Reply-To: <4A93428A.4070903@earthlink.net>
Jeff Shanab wrote:
> Updates start at the file and only work upwards back to root. How does
> the hardlink get traversed?
A hard link is just a second directory entry linking to
the same inode. There are no back links from inodes to
the directory entries that point to them and they are
essentially indistinguishable from files that are not
hardlinked.
Hard links have been done like this in pretty much every
Unix filesystem since the 1970's.
--
All rights reversed.
next prev parent reply other threads:[~2009-08-25 17:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-25 1:46 Starting a grad project that may change kernel VFS. Early research Re: Starting a grad project that may change kernel VFS. Early research Jeff Shanab
2009-08-25 17:28 ` Rik van Riel [this message]
2009-08-25 18:04 ` Jeff Shanab
2009-08-26 1:30 ` Theodore Tso
[not found] ` <4A94BF9E.2010101@earthlink.net>
[not found] ` <20090826130513.GM32712@mit.edu>
2009-08-26 14:42 ` Jeff Shanab
2009-08-26 15:09 ` Bryan Donlan
2009-08-26 12:18 ` Stefan Richter
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=4A941F56.8060502@redhat.com \
--to=riel@redhat.com \
--cc=jshanab@earthlink.net \
--cc=linux-kernel@vger.kernel.org \
/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