Qrux wrote: > On Mar 2, 2012, at 4:26 PM, James Robertson wrote: >> On Mar 1, 2012 2:49 PM, "Ken Moffat" <[email protected]> >> wrote: >>> Actually, we used to have a guy who did run production servers - >>> but he spent a lot of time keeping them up to date, and he built >>> on one machine and then rolled the binaries out to the others >>> after testing. >> LOL. I still do. I am much more efficient than in years past. LFS >> has provided me a very stable, modern and downright fast platform. >> FWIW I am currently running some test builds with Jeremy's proposed >> idea. I am pretty meticulous, so it will be a bit before I am >> ready to report back. >> >> James (yes I am still here!) > > *whew* I was starting to think I was the only one who'd ever > considered running LFS (or a very close derivative) in production.
I've been doing that since 2004. And the lfs servers are running lfs. I'd consider that 'production', wouldn't you? > James, if you automate your builds, I'd love to compare notes. You > can see my work here: https://github.com/qrux/xlapp. It's an > automated build for virtualization using Xen with LFS as the base > system. It provides a few server "types" (DNS, smtp/imap, and a LAPP > stack). The README is now pretty dated, but still paints the big > picture. jhalfs does a very nice job with LFS and I have my build scripts for BLFS packages, so a build goes pretty fast. For multiple virtualization builds, I have a generic build with few add ons that I can just copy and add additional BLFS packages. One thing to note is that you generally don't need to rebuild a system just because there are new package versions. Some systems run just fine for years without significant updates. The lfs main server is still running a 2.6.18 kernel. There has been no need to change, but we will update when we build the new server. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
