public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chee Ong Loh <onnyloh@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] strange /init kernel-2.6.12-gentoo-r5 boot problems
Date: Fri, 15 Jul 2005 16:53:14 +0000	[thread overview]
Message-ID: <6fdd4b4c050715095360668bbc@mail.gmail.com> (raw)
In-Reply-To: <42D711F2.7030801@gmail.com>

solution are simple.
there is a new version of genkernel in portage.

try:
emerge --sync and emerge genkernel
and finally rebuild the entire kernel and that should solve.
At least I've solve mine.

good luckzzzzzz

On 7/15/05, Zac Medico <zmedico@gmail.com> wrote:
> Iain Buchanan wrote:
> > On Thu, 2005-07-14 at 08:36 +0200, Richard Fish wrote:
> >
> >>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.
> >
> >
> > What busybox config? `equery files busybox` doesn't show any config
> > files for busybox.  I found the previous thread here
> > http://marc.theaimsgroup.com/?l=gentoo-user&m=112127857419654&w=2 and
> > Zac suggested some different options:
> >
> >
> >>root (hd0,0)
> >>kernel /kernel-genkernel-x86-2.6.12-gentoo-r4n
> >>root=/dev/hda11 video=vesafb:1024x768-32@72
> >>splash=verbose gentoo=nodevfs udev devfs=nomount
> >>initrd /initramfs-genkernel-x86-2.6.12-gentoo-r4n
> >
> >
> > but that didn't help either.
> 
> So it still uses the initramfs even though you didn't specify root=/dev/ram0?  Richard said something about that (I wasn't aware of this behavior).  Apparently you need to remove the initrd parameter in order to disable it.
> 
> Genkernel builds busybox with the config file in /usr/share/genkernel/$arch/busy-config.  Of course, it will only build busybox if it doesn't find a suitable binary in your bincache (specified in /etc/genkernel.conf).
> 
> >
> > And why do I need to do a `busybox --install` ?? shouldn't this come up
> > in some emerge warning or be done by genkernel or something? I monitor
> > all the output from emerge with enotice, but I didn't see anything about
> > busybox...
> >
> > TIA,
> 
> You don't do busybox --install, that happens automatically in the init script.  It seems that the genkernel devs may have overlooked this minor detail.  It's easy to forget about it after you have a working busybox in your bincache.
> 
> Zac
> 
> --
> gentoo-user@gentoo.org mailing list
> 
> 


-- 
Regards,
Chee Ong

-- 
gentoo-user@gentoo.org mailing list



      reply	other threads:[~2005-07-15 17:02 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
2005-07-15  1:01   ` Iain Buchanan
2005-07-15  1:31     ` Zac Medico
2005-07-15 16:53       ` Chee Ong Loh [this message]

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=6fdd4b4c050715095360668bbc@mail.gmail.com \
    --to=onnyloh@gmail.com \
    --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