From: Nigel Kukard <nkukard@lbsd.net>
To: buildroot@busybox.net
Subject: [Buildroot] adding packages to buildroot
Date: Sat, 29 Mar 2008 15:12:02 +0000 [thread overview]
Message-ID: <1206803522.3224.186.camel@nigel-x60> (raw)
Anybody got anything against me adding and maintaining the following
packages...
rpm5 - 4.4.9 & 5.0.x (+- 9 patches to support uclibc)
depends: libneon
depends: libbeecrypt
busybox's rpm is great, but lacks functionality which one can use for
emergency recovery.
bootutils - implements a switchroot alternative which supports automatic
discovery of root device/filesystem and emergency shell execution if
root device cannot be found or mounted. initramfs+bootutils+busybox
+dropbear <= perfect rescue initramfs/initrd.
-N
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://busybox.net/lists/buildroot/attachments/20080329/6ae85ee0/attachment.pgp
next reply other threads:[~2008-03-29 15:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-29 15:12 Nigel Kukard [this message]
2008-03-29 15:25 ` [Buildroot] adding packages to buildroot Peter Korsgaard
2008-03-31 9:25 ` Will Newton
2008-03-31 9:32 ` Nigel Kukard
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=1206803522.3224.186.camel@nigel-x60 \
--to=nkukard@lbsd.net \
--cc=buildroot@busybox.net \
/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