Re: apparent loss of continuity in kernel .config?

[rh_]

On Thu, 1 Jan 2015 18:43:03 -0500
Gene Heskett <gheskett@xxxxxxxx> wrote:

> 
> IMO that is NOT how its supposed to work.  So I guess I'll waste a

I agree.

> tree and print a working  3.16.0 & use that to build a new one. I do
> not believe it even makes an attempt to read the old one, but simply
> goes wandering in the vineyard, making frequent stops to recycle the
> barrel sampling.

I used to try to make it work but I usually give up and stick with
the config that works. Maybe I'm doing it all wrong. My laptop works
fine though. But it wasn't easy building a static kernel for it.

> 
> Indeed, but it no doubt will take quite a few boxes.  The funny thing

Probably true.

> lots of people find hard to believe is that Ed wrote that in about
> 1940.  His long view obviously started before mine as mine didn't
> start will late in '34.  It took me till the middle 60's to decide
> its broken.  And every libtard fix breaks it worse...

Smedley Butler and lots of others knew a long time ago too.
G.E. Griffin and friends have lots to say.

The long-con is always hard to see.

> 
> 
> Thanks & lets hope 2015 is a better year.

Can do.

> 
> Cheers, Gene Heskett
> -- 
> "There are four boxes to be used in defense of liberty:
>  soap, ballot, jury, and ammo. Please use in that order."
> -Ed Howdershelt (Author)
> Genes Web page <http://geneslinuxbox.net:6309/gene>
> US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/