From: Wolfgang Denk <wd@denx.de>
To: Dan Kegel <dank@kegel.com>
Cc: Brian Padalino <bpadalino@perigee.com>,
zjzhou@newrocktech.com, linuxppc-embedded@lists.linuxppc.org
Subject: Re: how to use busybox to make a ramdisk?
Date: Fri, 29 Aug 2003 20:55:43 +0200 [thread overview]
Message-ID: <20030829185548.38032C59E4@atlas.denx.de> (raw)
In-Reply-To: Your message of "Fri, 29 Aug 2003 08:27:33 PDT." <3F4F70E5.7070202@kegel.com>
In message <3F4F70E5.7070202@kegel.com> you wrote:
>
> Handy. I imagine the patches are in the ELDK SRPM for busybox.
> Where can I find that? I poked around on the eldk site but
There is very little interest in SRPMs (actually you're the first to
ask :-) The easiest way to access the patches is from our CVS server
(modules eldk_build and eldk_tarballs):
build/cross_rpms/genext2fs/SOURCES/genext2fs-1.3-eldk.patch
build/cross_rpms/genext2fs/SOURCES/genext2fs_perms.patch
build/cross_rpms/genext2fs/SOURCES/genext2fs_symlink.patch
build/cross_rpms/genext2fs/SOURCES/genext2fs_1.3-4.patch
build/cross_rpms/genext2fs/SOURCES/genext2fs_1.3-4_fifo.patch
build/cross_rpms/genext2fs/SPECS/genext2fs.spec
tarballs/genext2fs_1.3-2.diff
tarballs/genext2fs_1.3.orig.tar.gz
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
It is not best to swap horses while crossing the river.
- Abraham Lincoln
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2003-08-29 18:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3F4F70E5.7070202@kegel.com>
2003-08-29 18:55 ` Wolfgang Denk [this message]
2002-02-13 6:32 This question may be simple for you, but it doesn't let me sleeping John Zhou
2003-08-28 9:53 ` how to use busybox to make a ramdisk? John Zhou
2003-08-29 16:42 ` Brian Padalino
2003-08-29 14:50 ` Dan Kegel
2003-08-29 14:52 ` Wolfgang Denk
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=20030829185548.38032C59E4@atlas.denx.de \
--to=wd@denx.de \
--cc=bpadalino@perigee.com \
--cc=dank@kegel.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=zjzhou@newrocktech.com \
/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).