Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Last I heard (about 2 years ago), load balance wasn't supported on Solaris. Looks like it is now in 3.0D. Actually, I went through the release notes for B,C,D and I never saw it mentioned as new feature. Chris said he remembers seeing it in a doc somewhere.
I've been tasked with install JBOSS web to evaluate it as a possible replacement for IIS as our "presentation layer". JBoss web is distributed as a standalone webserver running on top of the JBoss 4 microkernel. JBOSS web is not pure java, it contains native code, compiled, and optimized for each OS. The install is simply to unzip it, set my JAVA_HOME, and run "run.sh" from the bin directory. Errors may appear in the server.log.