Re: re Laptop Does Not See eth0

On Sun, Mar 18, 2012 at 06:12:10AM -0700, Rich Shepard wrote:
> On Sat, 17 Mar 2012, Bradley D. Thornton wrote:
> 
> >I don't understand why, actually, that you feel a need to
> >compile the kernel from a SlackBuild, when you can simply
> >install the generic 3.2.7 kernel and create an initrd.
> 
>   My understanding is that the stock 3.2.7 kernel was built on a 
> machine running -current and that it's always been best to build 
> kernels on the specific machines that will run them.

Excuse me, I am allergic to that logic ... I feel a sneeze coming 
on... ... ah... ahhhh... GENTOO!

<wipes nose> Sorry, please forgive me. ;)

No, there is no benefit to this. The kernel you get from Slackware is 
quite as good as any generic kernel you might compile for yourself. 
Few users need custom kernels at all, and locally-built kernels have 
no inherent benefit over distributor-provided ones.

I understand that you are in need of a newer kernel than Slackware 
13.37's kernel. If you are running -current already, and if the 
version in -current meets your needs, just use that, the binary 
kernel from slackware(64)?-current.

> >I mean, if you were hell bent on running 3.2.9 then of course I
> >could understand, but you already have 3.2.7 waiting for you,
> >and unless you want to build a monolithic kernel then.... why?

FWIW I have no sympathy for those who want non-modular kernels. :) 
There are sane and reasonable reasons to want a custom kernel, such 
as to trim it down to only what is needed, but I don't count 
"monolithic" among those reasons.

Those who want non-modular kernels are those for whom nanoseconds of 
CPU time are more important than hours of human time. (Even that can 
make sense if you are developing an embedded platform.)

>   I can try using the 3.2.7 kernel packages.

Again, if you're already running -current, and if 3.2.7 has the 
enhancements you need, do this.

> At worst, I re-install 13.37 then build a 3.2.11 kernel from
> souce (that's the most current stable kernel.)

I don't understand why you'd re-install 13.37 for this, but that 
might work too. You could take the slackware-current 3.2.7 build 
script and config as a basis, if you need 3.2.11.
-- 
  http://rob0.nodns4.us/ -- system administration and consulting
  Offlist GMX mail is seen only if "/dev/rob0" is in the Subject: