--- Eric Dickner <[EMAIL PROTECTED]> wrote:
> Date: Fri, 17 Sep 2004 15:20:33 -0700 (PDT)
> From: Eric Dickner <[EMAIL PROTECTED]>
> Subject: Re: Differences between binary images and
> compiled kernels - 5 min
> To: Alvin Oga <[EMAIL PROTECTED]>
>
>
&g
--- Silvan <[EMAIL PROTECTED]> wrote:
>
> Configging a kernel is an arduous process of booting
> and then figuring out
> what you got wrong.
Yes, it is. You guessed correctly when you said that
I might have gotten a "bad config" file from the
vendor of the binaries. "Bad" in that it while
hi ya
On Fri, 17 Sep 2004, Silvan wrote:
> Configging a kernel is an arduous process of booting and then figuring out
> what you got wrong. It's a pain in the ass.
the pain can be minized by:
- always start from a kernel from kernel.org unless you know
what they did to it fr
On Thursday 16 September 2004 08:41 am, Eric Dickner wrote:
> --- Silvan <[EMAIL PROTECTED]> wrote:
> > Not enough information.
>
> Thanks for you time! I didn't want to get too
> specific in case there was a general and simple answer
> to this situation (getting an old configuration from a
> bina
Eric Dickner <[EMAIL PROTECTED]> writes:
>> What basic procedure was that?
>
> make mrproper
> make oldconfig
> make dep
> make bzImage
> make modules
> make modules_install
> "user fools with links and lilo"
>
> I've seen is outlined for all the distros.
I don't think you should run make mrprope
--- Silvan <[EMAIL PROTECTED]> wrote:
>
> Not enough information.
Thanks for you time! I didn't want to get too
specific in case there was a general and simple answer
to this situation (getting an old configuration from a
binary install to work).
> What lead you up to running
> make oldconf
On Wednesday 15 September 2004 10:23 pm, Eric Dickner wrote:
> kernels handle hardware. My questions are these:
> 1) How did the seller of my original binary kernel
> compile it to be specific to certain hardware?
> RE question 1, if the answer is just in standard
> configuring why did the "ma
7 matches
Mail list logo
