Re: build kernel for server farm

[dee jay]

Actually if they are exactly the same, why dont you just copy the
relevant files over? ie. /lib/modules/`uname -r`/*, and as mentioned
your bzImage, System.map, and lilo.conf (and of course remember to run
lilo)?

Any particular reasons why you would want to go through the process of
compiling again on each machine?

-dj

 --- Matt Simonsen <[e-mail]> wrote: > I am pretty
familiar with the build process and kernel install for a
> single Linux box, but I wanted to confirm I'm doing things in a sane
> way
> for a large deployment. All the machines are the same hardware and
> running standard setups.
> 
> First, I plan on compiling the kernel on a development box. From
> there
> my plan is basically tar /usr/src/linux, copy to each box, untar,
> copy
> bzImage and System.map to /boot, run make modules_install, edit
> lilo.conf, run lilo.
> 
> Tips? Comments?
> 
> Thanks 
> Matt
> 
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-kernel" in
> the body of a message to [e-mail]
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/ 

http://careers.yahoo.com.au - Yahoo! Careers
- 1,000's of jobs waiting online for you!