All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: "H. Peter Anvin" <hpa@zytor.com>, viro@math.psu.edu
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] klibc requirements
Date: Thu, 10 Jan 2002 17:30:29 +1100	[thread overview]
Message-ID: <20020110173029.7616f752.rusty@rustcorp.com.au> (raw)
In-Reply-To: <a1grbm$n6o$1@cesium.transmeta.com>
In-Reply-To: <20020108192450.GA14734@kroah.com> <20020109045109.GA17776@kroah.com> <a1giqs$93d$1@cesium.transmeta.com> <20020109060951.GA18024@kroah.com> <a1grbm$n6o$1@cesium.transmeta.com>

On 8 Jan 2002 23:26:46 -0800
"H. Peter Anvin" <hpa@zytor.com> wrote:
> *** Handling of hard links
> 
> When a nondirectory with c_nlink > 1 is seen, the (c_maj,c_min,c_ino)
> tuple is looked up in a tuple buffer.  If not found, it is entered in
> the tuple buffer and the entry is created as usual; if found, a hard
> link rather than a second copy of the file is created.  It is not

HPA,
	gnu cpio (v 2.4.2) actually puts the contents in the *last*
entry, for hardlinks in "newc" format.  This probably means you should
specify that if it's a found tuple, and c_filesize is non-zero,
overwrite the contents of the file.

Cheers!
Rusty.
-- 
  Anyone who quotes me in their sig is an idiot. -- Rusty Russell.

  reply	other threads:[~2002-01-10  8:32 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-08 19:24 [RFC] klibc requirements Greg KH
2002-01-08 20:37 ` Erik Andersen
2002-01-09  4:23 ` Felix von Leitner
2002-01-09  4:34   ` initramfs programs (was [RFC] klibc requirements) Greg KH
2002-01-09  6:10     ` Greg KH
2002-01-09  7:23       ` H. Peter Anvin
2002-01-09  9:33     ` Kai Germaschewski
2002-01-09 10:00     ` Erik Andersen
2002-01-09  4:51   ` [RFC] klibc requirements Greg KH
2002-01-09  5:01     ` H. Peter Anvin
2002-01-09  6:09       ` Greg KH
2002-01-09  7:26         ` H. Peter Anvin
2002-01-10  6:30           ` Rusty Russell [this message]
2002-01-10 18:41             ` H. Peter Anvin
2002-01-10 15:24           ` Matthias Kilian
2002-01-10 17:13             ` H. Peter Anvin
2002-01-09 14:15     ` Felix von Leitner
2002-01-09 14:30       ` Lars Brinkhoff
2002-01-09 14:51       ` Erik Andersen
2002-01-09 10:38   ` initramfs programs (was [RFC] klibc requirements) Anton Altaparmakov
2002-01-09 15:56     ` Pavel Machek
2002-01-09 16:04       ` Patrick Mochel
2002-01-09 16:26         ` Greg KH
2002-01-09 16:29         ` Pavel Machek
2002-01-09 16:48           ` Andreas Ferber
2002-01-09 21:15     ` Alex Bligh - linux-kernel
2002-01-09 21:34     ` Anton Altaparmakov
2002-01-09 21:40       ` Greg KH
2002-01-09 21:55       ` Anton Altaparmakov
2002-01-09 22:15         ` Andreas Ferber
2002-01-10  0:25           ` Tom Rini
2002-01-10  0:38             ` Andreas Ferber
2002-01-10  2:42               ` Tom Rini
2002-01-10 14:09                 ` Rob Landley
2002-01-10 22:24                   ` Tom Rini
2002-01-11  0:15                   ` H. Peter Anvin
2002-01-09 22:12       ` Alex Bligh - linux-kernel
2002-01-09 13:23   ` [RFC] klibc requirements Juan Quintela
2002-01-09 14:57     ` Erik Andersen
2002-01-15  3:08   ` Albert D. Cahalan
2002-01-15 11:55     ` Felix von Leitner
2002-01-15 14:54       ` David Lang
2002-01-15 16:15         ` Doug McNaught
2002-01-15 18:06           ` David Lang
2002-01-15 18:36             ` Doug McNaught
2002-01-16 18:36         ` Erik Andersen
2002-01-16  7:50       ` Albert D. Cahalan

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=20020110173029.7616f752.rusty@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@math.psu.edu \
    /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.