Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
There is less than 2 hours left to vote in the 2015 LinuxQuestions.org Members Choice Awards. Click here to go to the polls. Vote now and make sure your voice is heard!
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.
This is a bit of an oxymoron.
I'm trying to convert a lad at work here to linux, and I've got him partly on the way because XP home don't support IIS (what a great decision). So, he's got apache going which was easy and made him a bit relaxed, but he's an ASP/cold fusion developer, so needs that. Coldfusion was a breeze, which is again great, but we just can't seem to get ASP working. We've tried Apache::ASP - no luck there, (and if I'm not wrong, don't you have to write perl code rather than ASP), also tried Chillisoft, but it will only install on windows with apache <=1.3.2 which is a little old now and way different from 1.3.22.
So anyone got any ideas?
Chilisoft ASP 3.6 runs on Apache 1.3.20 (one point three point twenty). That might help you since Apache 1.3.20 is fairly close to your current running system of Apache 1.3.22.
Second, ASP is not -really- a language. You can use a number of different languages such as VBScript, JScript and PerlScript in ASP pages. So, you can write the ASP pages in Perl, you just don't have to (unless you meant in regards to Apache::ASP).
Why not put your friend on a linux box with apache and chilisoft? If you do, be careful, I tried running Chilisoft sometime back (a year or more ago when I wanted the 'quick' not 'right' thing to do ((the right thing being porting the code to a REAL programming language, instead of bastardized VB fodder))), the damn thing would run away with 99% of the CPU.
We tried ChilliSoft with xx.22, but it didn't work. The install wouldn't pick up apache. No matter I guess.
I'd like to get him on a linux box, but we don't have them at work (I am a contractor). I try and try to get him to use JSP ))
No luck there however, he'll probably try to stick with CF unfortunately.
Not that I like ColdFusion much either, but it is certainly better than MS ASP, right? Neither are real languages, so your co-worker will eventually run into situations where he will be limited in what he can do.
What about going back a bit and installing Apache 1.3.20, instead of 1.3.22? The Chilisoft installer may have some sort of version limiter or some(crap)thing like that. Keep your httpd.conf file backed up, remove the version you have now and downgrade to 1.3.20 -- that is the version Chilisoft says it supports. Then, just put your httpd.conf file back in its place (overwriting the default from the second installation) and the whole thing should run as before.