From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: restoring hard linked files from zisofs/iso9660 w. RR
Date: 25 Jan 2002 09:55:57 -0800 [thread overview]
Message-ID: <a2s67d$8s0$1@cesium.transmeta.com> (raw)
In-Reply-To: <20020125135545.A28897@espoo.tasking.nl>
Followup to: <20020125135545.A28897@espoo.tasking.nl>
By author: Frank van Maarseveen <fvm@altium.nl>
In newsgroup: linux.dev.kernel
>
> 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?
>
WHAT doesn't work?
> or by a more advanced inode number synthesis in fs/isofs?
There is, I belive, an inode number RR attribute. Last I checked I
was happily using hard links with RockRidge...
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com>
next prev parent reply other threads:[~2002-01-25 17:56 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
2002-01-25 17:55 ` H. Peter Anvin [this message]
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='a2s67d$8s0$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--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