From: "Peter Wächtler" <pwaechtler@loewe-komp.de>
To: frank.van.maarseveen@altium.nl
Cc: linux-kernel@vger.kernel.org
Subject: Re: restoring hard linked files from zisofs/iso9660 w. RR
Date: Fri, 25 Jan 2002 14:28:31 +0100 [thread overview]
Message-ID: <3C515D7F.3145102E@loewe-komp.de> (raw)
In-Reply-To: <20020125135545.A28897@espoo.tasking.nl>
Frank van Maarseveen schrieb:
>
> This doesn't seem to work due to inode number differences. Is
> this a fundamental problem or can it be solved somehow, e.g.
> by an attribute which refers to a sort of "original" inode
> number?
>
> or by a more advanced inode number synthesis in fs/isofs?
>
Don't know about isofs, but hardlinks do not use an inode.
It's just another entry in a directory pointing to a "used"
inode (there is another entry refering to the same inode)
fast symlinks do occupy an inode, symlinks an inode + 1 diskblock.
next prev parent reply other threads:[~2002-01-25 13:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-25 12:55 restoring hard linked files from zisofs/iso9660 w. RR Frank van Maarseveen
2002-01-25 13:28 ` Peter Wächtler [this message]
2002-01-25 17:55 ` H. Peter Anvin
2002-01-28 16:07 ` Frank van Maarseveen
2002-01-28 18:46 ` H. Peter Anvin
2002-01-28 19:43 ` H. Peter Anvin
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=3C515D7F.3145102E@loewe-komp.de \
--to=pwaechtler@loewe-komp.de \
--cc=frank.van.maarseveen@altium.nl \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.