Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

We are moving from Microsoft platform(ASP.NET/SQLServer/) to a LAMP Stack. What are some of the things that can be helpful.

share|improve this question

closed as too broad by RobM, Ward, kasperd, mdpc, HBruijn Aug 26 at 15:48

There are either too many possible answers, or good answers would be too long for this format. Please add details to narrow the answer set or to isolate an issue that can be answered in a few paragraphs.If this question can be reworded to fit the rules in the help center, please edit the question.

3 Answers 3

up vote 0 down vote accepted

Probably one of the biggest is case-sensitivity. In Windows, 'notepad foo.html' and 'notepad Foo.html' would open the same file, while in Linux 'vim foo.html' and 'vim Foo.html' would create two different files. The same applies to URLs on Linux servers.

Also, permissions are very important. I recommend not running the webserver, CGI scripts, etc. as 'root', the administrative account. Instead, use reduced privileges and run Apache, MySQL/PostgreSQL etc. with their own dedicated users.

Finally, I'd recommend reading the manual pages (accessible via the 'man' command) for the various tools you'll be using. These `man pages' are extremely useful and frequently very well-written documentation.

Some software uses an alternate manual system. Perl uses 'perldoc', while Ruby uses 'ri'.

One thing to look up about any language you write CGI programs in is its taint-checking features. Perl, for instance, has the -T switch and the taint module, which catch many types of insecure data handling.

share|improve this answer

You usually don't have a gui on a linux server. You'll need to get really comfy on the command line.

share|improve this answer
That's not true. There is nothing stopping you from installing a GUI, you just, unlike Windows, don't have to. –  SCdF May 1 '09 at 4:07
This is true. Most servers don't have one and some configuration can't be done without the command line. (From my experience) –  epochwolf May 1 '09 at 5:02
I second this. Using a GUI on a Linux server is too much overhead, you don't need all the GUI libs when running a server. –  Gert M May 1 '09 at 7:00
Another way to look at this is linux servers are almost exclusive command line managed. Tutorials, documentation, and support personnel are going to assume you are using the command line. –  epochwolf May 1 '09 at 7:05
  • mod_php in not thread safe, so you'll have to use forked server;
  • filenames are case sensitive;
  • symbolic links do work;
  • configuration is done by editing configuration files. Some distros provide GUIs, but they're limited only to very simple configuration.
share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.