From: "H. Peter Anvin" <hpa@zytor.com>
To: Milton Miller <miltonm@bga.com>
Cc: klibc@zytor.com, linux-kernel@vger.kernel.org,
viro@parcelfarce.linux.theplanet.co.uk, akpm@osdl.org
Subject: Re: INITRAMFS: allow no trailer
Date: Fri, 03 Dec 2004 18:11:55 -0800 [thread overview]
Message-ID: <41B11CEB.30103@zytor.com> (raw)
In-Reply-To: <200412040147.iB41lIlK031974@sullivan.realtime.net>
Milton Miller wrote:
>
> hpa points out that you should be careful with the headers, use unique
> inode numbers and/or add a cpio header with just TRAILER!!! to reset
> the inode hash table to avoid unwanted hard links. I just put this
> sequence as the last files loaded.
>
Correction. I just remembered we wrote the spec so that a file with a
link count of 1 is not entered in the hash table and therefore is never
hardlinked. This should do what you need. (This was obviously done for
exactly this reason.)
-hpa
prev parent reply other threads:[~2004-12-04 2:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-04 1:47 INITRAMFS: allow no trailer Milton Miller
2004-12-04 2:10 ` [klibc] " H. Peter Anvin
2004-12-04 2:11 ` H. Peter Anvin [this message]
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=41B11CEB.30103@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@osdl.org \
--cc=klibc@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miltonm@bga.com \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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