new motherboard - reinstall ubuntu?

[Jonathan Saylor]

heck my 2 cents can be added on this. :)
do you need to reinstall ubuntu with a new motherboard.   the answer is: no
why?

because even if you HAVE compiled your own custom kernel and went out of
your way to remove the default kernel completely you still have the
install CD in which you can use its kernel to boot into the current
installed system to a) compile another custom kernel for that hardware
or b) re-install the default ubuntu kernel.

I recomend people who have never built a kernel to do so ONLY if you
want to learn more about linux, if you dont care about that kind of
thing you dont need to do a custom kernel build, the generic kernel sent
with *most* distros is usually all you need.

Jon


Alvin Thompson wrote:

> can't you just use a kernel module instead of recompiling the kernel?
> are you saying you need to patch the kernel? sounds like more trouble
> than it's worth. i'm an old linux hand, and i haven't recompiled my
> kernel in ages. not even on gentoo. :)
>
> -alvin
>
>
> mike wrote:
>
>> On 8/22/05, paul cooke <paul.cooke100 at blueyonder.co.uk> wrote:
>>
>>> On Monday 22 August 2005 04:40, Richard W. Knight wrote:
>>>
>>>> Before you do the upgrade, recompile the kernel with the appropriate
>>>> modules for your current system and the modules needed by the new MB.
>>>> The new kernel "should" boot on either new or old MB. After the
>>>> upgrade,
>>>> you can remove the un-needed modules and tweek for the new MB.
>>>>
>>>
>>> there's absolutely NO need to recompile your kernel with Ubuntu
>>> unless you've
>>> been mad enough to have created a custom one in the first place...
>>
>>
>>
>> uh, yeah, because people who compile custom kernels are crazy...  i
>> never use vendor kernels for personal machines.  my firewall, my car
>> computer, my file server, and my workstation all have tailored 2.6
>> kernels.  for the longest time, my firewall box was a node on the
>> 6bone running a custom 2.1.x kernel because it had ipv6 support in the
>>
>>> ~100 series.  for the ~40 servers i administer, i go with vendor
>>
>>
>> kernels because they are easier to administer.  however, since my
>> company is in a big antivirus push, i may end up going with custom
>> kernels on all servers in order to utilize etrust's realtime antivirus
>> monitor.  but even then, i will compile on one machine, then produce a
>> package which i will install on the other machines.
>>
>> learning to compile your own kernel is an exercise in further
>> understanding linux.  there are MANY reasons why you would want to
>> build your own kernel.  don't let this guy prevent you from learning
>> more about linux.
>>
>> -mike
>>
>
>