From: redhowlingwolves@nc.rr.com (scott)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Kernel compilation
Date: Wed, 05 Jan 2011 02:10:16 -0500 [thread overview]
Message-ID: <4D241958.1000105@nc.rr.com> (raw)
In-Reply-To: <AANLkTi=89KUh4jkbb-fh1KigaRGPAyf-WfNnPJPVSQU8@mail.gmail.com>
On 01/05/2011 01:46 AM, Mulyadi Santosa wrote:
> Hi Scott :)
>
> On Wed, Jan 5, 2011 at 12:34, scott<redhowlingwolves@nc.rr.com> wrote:
>> I'm new to the list and would like to say hello to everyone. Now on to
>> the meat.
>>
>> I have tried to compile a kernel with a grsec patch 5 times now using a
>> couple of different methods and I keep getting a "No init found" and
>> "Couldn't support optional features" errors every time at bootup.
>> I'm trying to use a vanilla 2.6.32.27 kernel on 10.04 Ubuntu and it
>> compiles fine,
>> just will not boot.
> My first question is: did the patching go successfully? were you
> applying the correct grsec version against a matching vanilla kernel
> version?
>
> And last, maybe you can attach your kernel .config content...and one
> of fine people here will try to decipher what's wrong with it :)
>
The patch was matched and was successful. It compiled with no errors.
Just the 'no init' at boot.
I'll post my .config later today as it's late here and have to work. I'm
beginning to think it may have something to do with the limits on file
size as I got a few warnings about out-of-range sizes. I have it set to
1024.
Thanks for your reply,
Scott
Thanks for your reply.
next prev parent reply other threads:[~2011-01-05 7:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-05 5:34 Kernel compilation scott
2011-01-05 6:46 ` Mulyadi Santosa
2011-01-05 7:10 ` scott [this message]
2011-01-05 7:37 ` Robert P. J. Day
-- strict thread matches above, loose matches on Subject: below --
2011-05-02 18:32 Sleep and Wake up Abu Rasheda
2011-05-02 19:40 ` Kernel compilation Ezequiel García
2011-05-05 14:15 ` Pico Geyer
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=4D241958.1000105@nc.rr.com \
--to=redhowlingwolves@nc.rr.com \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).