From: Richard Fish <bigfish@asmallpond.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] strange /init kernel-2.6.12-gentoo-r5 boot problems
Date: Thu, 14 Jul 2005 08:36:48 +0200 [thread overview]
Message-ID: <42D60800.3040904@asmallpond.org> (raw)
In-Reply-To: <1121306885.24388.23.camel@orpheus>
Iain Buchanan wrote:
>-install: applet not found
>/init: 41: In: not found
>/init: 45: cat: not found
>/init: 150: sed: not found
>
>
Apparently it is a problem with busybox configuration:
>From another thread on this list less than 12 hours old:
Zac Medico wrote:
>It's not as bad as it looks. I had the same problem. You simply need to enable CONFIG_FEATURE_INSTALLER in the busybox config. Then you can do "busybox --install" and it automatically creates hardlinks for all the enabled applets.
>
>Zac
>
HTH,
-Richard
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-07-14 6:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-14 2:08 [gentoo-user] strange /init kernel-2.6.12-gentoo-r5 boot problems Iain Buchanan
2005-07-14 6:36 ` Richard Fish [this message]
2005-07-15 1:01 ` Iain Buchanan
2005-07-15 1:31 ` Zac Medico
2005-07-15 16:53 ` Chee Ong Loh
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=42D60800.3040904@asmallpond.org \
--to=bigfish@asmallpond.org \
--cc=gentoo-user@lists.gentoo.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