From: Alex Riesen <alexander.riesen@synopsys.COM>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, Jeff Garzik <jgarzik@pobox.com>,
hpa@zytor.com, Russell King <rmk@arm.linux.org.uk>
Subject: Re: [RFC] klibc for 2.5.59 bk
Date: Fri, 7 Feb 2003 16:00:38 +0100 [thread overview]
Message-ID: <20030207150038.GM5239@riesen-pc.gr05.synopsys.com> (raw)
In-Reply-To: <20030207045919.GA30526@kroah.com>
Greg KH, Fri, Feb 07, 2003 05:59:19 +0100:
> Hi all,
>
> Thanks to Arnd Bergmann, it looks like the klibc and initramfs code is
> now working. I've created a patch against Linus's latest bk tree and
> put it at:
> http://www.kroah.com/linux/klibc/klibc-2.5.59-2.patch.gz
was the following part of the patch intended? (hello_world?)
cpio_mknod("/dev/console", 0600, 0, 0, 'c', 5, 1);
cpio_mkdir("/root", 0700, 0, 0);
+ cpio_mkdir("/sbin", 0700, 0, 0);
+ cpio_mkfile("usr/hello_world/hello", "/sbin/hotplug", 0700, 0, 0);
cpio_trailer();
exit(0);
next prev parent reply other threads:[~2003-02-07 14:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-07 4:59 [RFC] klibc for 2.5.59 bk Greg KH
2003-02-07 5:06 ` H. Peter Anvin
2003-02-07 5:10 ` Greg KH
2003-02-07 15:00 ` Alex Riesen [this message]
2003-02-09 12:57 ` Greg KH
2003-02-17 3:06 ` Kai Germaschewski
2003-02-17 5:50 ` Jeff Garzik
2003-02-17 18:02 ` Sam Ravnborg
2003-02-17 18:07 ` H. Peter Anvin
2003-02-17 18:36 ` Jeff Garzik
2003-02-17 18:57 ` Sam Ravnborg
2003-02-17 19:24 ` Jeff Garzik
2003-02-18 8:58 ` H. Peter Anvin
2003-02-18 9:17 ` Jeff Garzik
2003-02-18 9:36 ` Stelian Pop
2003-02-18 9:37 ` Stelian Pop
2003-02-18 9:46 ` Jeff Garzik
2003-02-18 9:45 ` Jeff Garzik
2003-02-18 9:56 ` Stelian Pop
[not found] <20030217031008$3e63@gated-at.bofh.it>
[not found] ` <20030217031008$270a@gated-at.bofh.it>
2003-02-17 17:12 ` Arnd Bergmann
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=20030207150038.GM5239@riesen-pc.gr05.synopsys.com \
--to=alexander.riesen@synopsys.com \
--cc=greg@kroah.com \
--cc=hpa@zytor.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.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;
as well as URLs for NNTP newsgroup(s).