From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: klibc update
Date: 5 Feb 2003 14:57:37 -0800 [thread overview]
Message-ID: <b1s4t1$ck9$1@cesium.transmeta.com> (raw)
In-Reply-To: 20030205052354.GL15544@kroah.com
Followup to: <20030205052354.GL15544@kroah.com>
By author: Greg KH <greg@kroah.com>
In newsgroup: linux.dev.kernel
>
> For those wondering what's happening with klibc, here's an update...
>
> I have it building relatively well within the kernel, and have modified
> the usr/gen_init_cpio.c file to add files to the cpio "blob". That all
> seems to work, but I don't seem to be able to extract the files properly
> (or at least that's what I'm guessing is happening).
>
> If anyone wants to see the current progress, there's a big patch against
> 2.5.59 at:
> kernel.org/pub/linux/kernel/people/gregkh/klibc/klibc-2.5.59.patch.gz
> and a bk tree with the different changes broken down into "logical"
> chunks at:
> bk://kernel.bkbits.net/gregkh/linux/klibc-2.5
>
> Any help with trying to debug init/initramfs.c to figure out what is
> going wrong would be greatly appreciated.
>
Very cool :)
I will look at your stuff some time next week when I'm in .se for
NordU2003. Until then I'm afraid I'll have my hands full with
non-Linux work :(
-hpa
P.S. klibc-0.76 removes the much-complained-about Digest::MD5
dependence.
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
Architectures needed: cris ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64
next prev parent reply other threads:[~2003-02-05 22:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-05 5:23 klibc update Greg KH
2003-02-05 22:57 ` H. Peter Anvin [this message]
[not found] <20030205053013$7d61@gated-at.bofh.it>
2003-02-06 1:45 ` Arnd Bergmann
-- strict thread matches above, loose matches on Subject: below --
2003-02-06 12:07 Arnd Bergmann
2003-02-07 5:00 ` Greg KH
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='b1s4t1$ck9$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