All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Alexander Viro <viro@math.psu.edu>
Cc: Christian Koenig <ChristianK.@t-online.de>,
	linux-kernel@vger.kernel.org, hpa@transmeta.com
Subject: Re: [PATCH] initramfs
Date: Sun, 5 May 2002 23:34:16 -0700	[thread overview]
Message-ID: <20020506063416.GE1199@kroah.com> (raw)
In-Reply-To: <1744hw-0EYlYuC@fwd01.sul.t-online.com> <Pine.GSO.4.21.0205041509300.23892-100000@weyl.math.psu.edu>

On Sat, May 04, 2002 at 03:14:51PM -0400, Alexander Viro wrote:
>  
> Anyway, the real problem with iniramfs is on the build side.  I.e. what
> do we want in makefiles for early userland/what do we want to use as
> libc?

I have the start of a libc, based on your original "libc" in your
original initramfs patches, merged with some of my initial klibc 0.1
work <kernel.org/pub/linux/kernel/people/gregkh/klibc/> which was based
off of dietLibc.

It's available at http://linuxusb.bkbits.net:8080/klibc if people want
to poke around with it.  I'll dust it off this week, and post a clean
tarball, as it's been on hold.

Actually, in looking at that archive, it doesn't seem to have the latest
stuff checked in...I'll go find it in the morning...

I too am interested in how the makefiles and build process will work :)

thanks,

greg k-h

  parent reply	other threads:[~2002-05-06  7:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-04 19:57 [PATCH] initramfs Christian Koenig
2002-05-04 19:14 ` Alexander Viro
2002-05-04 22:05   ` H. Peter Anvin
2002-05-04 22:18     ` Alexander Viro
2002-05-06  6:34   ` Greg KH [this message]
2002-05-04 22:04 ` 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=20020506063416.GE1199@kroah.com \
    --to=greg@kroah.com \
    --cc="ChristianK."@t-online.de \
    --cc=hpa@transmeta.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.