All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Collins <bcollins@debian.org>
To: sparclinux@vger.kernel.org
Subject: Re: initrd problems??
Date: Fri, 02 Jul 2004 12:44:29 +0000	[thread overview]
Message-ID: <20040702124429.GC3320@phunnypharm.org> (raw)
In-Reply-To: <20040701194809.3e060eb0.tvaroqua@ie2.u-psud.fr>

On Fri, Jul 02, 2004 at 02:58:50PM +0200, till varoquaux wrote:
> Thanks.
> I didn't knew how to pass parameters to the kernel. interesting...
> It does seem however like there is a weird bug:
> I recompiled busybox with init support
> (>init utilities
> 	>init
> 	>Support reading an initab file
> 	>Support running init from within an initrd
> 	>Should init be _extra_ quiet ion boot) 
> and moved my /linurxc to /etc/init.d/rcS
> and everything works fine now.....
> I'm using kernel 2.4.26. Should I fill a bug report?
> Regards,
> Till
> P.S.:I've build initrd on x86 before and definitly did not encounter
> this behavior.

I'm not quite sure why, but there is some weird difference in how
sparc64 boots up with initrd. I went down this road a long time ago with
the Debian boot images. I don't consider it a bug with the kernel, just
that x86 seems to be less critical of the initrd environment than other
architectures do. Hell, I can't even remember what it was that caused
this.

-- 
Debian     - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
WatchGuard - http://www.watchguard.com/

  parent reply	other threads:[~2004-07-02 12:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-01 17:48 initrd problems?? till varoquaux
2004-07-02 12:21 ` Ben Collins
2004-07-02 12:44 ` Ben Collins [this message]
2004-07-02 12:58 ` till varoquaux
2004-07-07 14:06 ` till varoquaux

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=20040702124429.GC3320@phunnypharm.org \
    --to=bcollins@debian.org \
    --cc=sparclinux@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.