I have been given the choice of chosing Linux distribution to ship our software on, and normally I would chose SuSE right away, but not this time... We are going to ship our software on high scale servers and ordinary workstation releases are out of the questions. The machine needs to be boundle with support and not this email list :-) I need a way of producing a custom made installation CD, the same way I have done with ALICE/SuSE7.3 for another product. But now I need the Enterprise version and currently Fabian has not added support for creating custom made CD's into SLE8/UL. I guess I have to play around with AutoYast a while before making any decisions there. I could also use Redhat's kickstart feature, but then I have to create the custom made installation CD manually. Further more I need to wait for their new Server release, since the current Redhat Enterprise kernel(2.4.9 heavily modified) just don't work... Anyway, all my promblems are really maintainence/patching and simplicity. We cannot allow a user to patch their system without us making sure those patches works with our software. Personally I believe it would work for 99.999% of the time, but that is not good enough. With SuSE(!SLE8) you can redirect the user to a different patching site, I don't know about SLE8. With redhat I assume you have to write your own patching scheme, since they require you to register with RHN and we would no longer have control over patching. I rather not care about having to verify patches, but we have third party software/kernel modules that requires a certain kernel etc. Currently I believe the workload are the same on both dists, unless I find some good shortcuts. E.g. for RH create a kickstart and a extra CD with our software, but that requires too much user interaction. I really like my SuSE7.3/ALICE installation CD, totally automated and 5 minutes installation gives you a fully running system... Great :-) After all this BS; do anyone have some suggestions? Or some plain tips, experience to share?! /Magnus