From: rich turner <rich@storix.com>
To: linux-kernel@vger.kernel.org
Subject: Re: initrd and fc3
Date: Thu, 09 Dec 2004 11:59:06 -0800 [thread overview]
Message-ID: <1102622346.19320.12.camel@rich> (raw)
In-Reply-To: <41B8AAF9.6000807@gmail.com>
On Thu, 2004-12-09 at 11:43, Matan Peled wrote:
> rich turner wrote:
>
> >i am testing fc3 by using an old-school initrd. by old-school i mean not
> >the new initramfs/cpio type initrd. the process i use to create the
> >initrd works for all other distributions (suse, mandrake, debian, fc2,
> >2.2.x, 2.4.x, 2.6.x, etc) but fails with fc3 (2.6.9-1.667).
> >
> >upon system boot, the kernel executes, checks to see if the initrd is
> >initramfs (it isnt), finds the initrd (ext2), mounts it, and then
> >immediately exits without executing linuxrc.
> >
> >anyone have any ideas as to why linuxrc is not being executed?
> >
> >-
> >To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> >the body of a message to majordomo@vger.kernel.org
> >More majordomo info at http://vger.kernel.org/majordomo-info.html
> >Please read the FAQ at http://www.tux.org/lkml/
> >
> >
> >
> You pretty much deduced the bug is in FC3, and not the general kernel...
>
> So why exactly is this on topic on LKML?
i agree that this isnt the proper place for this topic if it is only
related to fc3.
>
>
> Is the bug reproducible on a vanilla kernel.org kernel?
i am doing this now. if this is reproducable in vanilla 2.6.9 then i
will let the list know.
>
> - Mif
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2004-12-09 19:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-09 19:28 initrd and fc3 rich turner
2004-12-09 19:43 ` Matan Peled
2004-12-09 19:59 ` rich turner [this message]
2004-12-09 20:48 ` Valdis.Kletnieks
2004-12-09 20:55 ` Valdis.Kletnieks
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=1102622346.19320.12.camel@rich \
--to=rich@storix.com \
--cc=linux-kernel@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.