Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's 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.
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.
If I understood your first post correctly, you already have a working lamp (ok, some configuration issues still need to be solved).
Why did you start over again?
If I can recall correctly, the OP has Apache working but not PHP and not MySQL. But I prefer SQLite over MySQL anyway.
What Linux distro, OP, do you have? Ubuntu? Fedora? Mint? SuSE? Slackware? Arch? PCLinuxOS? If it's any of these, you *don't* have to build PHP from source. And especially if you don't have Slackware, you can just install it from the package manager and you're all set.
sudo apt-get install php5
su -c "yum install php5"
For Mint, follow the Ubuntu instructions. Also for Debian.
For SuSE, open YaST and search for "php".
For Slackware, it's a little bit trickier. You have to download the package (hopefully from the Slackware site) and then install it manually using Slackware's package manager, hoping there's no dependencies to deal with.
pacman -Sy php5
I don't know the command on PCLinuxOS, but it's just one Google away.
i have /etc/apache2/conf.d/
these are the three files in it. not sure which is to edit and insert AddType application
conf.d # ls
charset localized-error-pages security
linux conf.d # cat charset
# Read the documentation before enabling AddDefaultCharset.
# In general, it is only a good idea if you know that all your files
# have this encoding. It will override any encoding given in the files
# in meta http-equiv or xml encoding tags.
linux conf.d #
conf.d # cat localized-error-pages
# Customizable error responses come in three flavors:
# 1) plain text 2) local redirects 3) external redirects
# Some examples:
#ErrorDocument 500 "The server made a boo boo."
#ErrorDocument 404 /missing.html
#ErrorDocument 404 "/cgi-bin/missing_handler.pl"
#ErrorDocument 402 http://www.example.com/subscription_info.html
# Putting this all together, we can internationalize error responses.
# We use Alias to redirect any /error/HTTP_<error>.html.var response to
# our collection of by-error message multi-language collections. We use
# includes to substitute the appropriate text.
# You can modify the messages' appearance without changing any of the
# default HTTP_<error>.html.var files by adding the line:
# Alias /error/include/ "/your/include/path/"
# which allows you to create your own set of files by starting with the
# /usr/share/apache2/error/include/ files and copying them to /your/include/path/,
# even on a per-VirtualHost basis. If you include the Alias in the global server
# context, is has to come _before_ the 'Alias /error/ ...' line.
# The default include files will display your Apache version number and your
# ServerAdmin email address regardless of the setting of ServerSignature.
# WARNING: The configuration below will NOT work out of the box if you have a
# SetHandler directive in a <Location /> context somewhere. Adding
# the following three lines AFTER the <Location /> context should
# make it work in most cases:
# <Location /error/>
# SetHandler none
# The internationalized error documents require mod_alias, mod_include
# and mod_negotiation. To activate them, uncomment the following 37 lines.
conf.d # cat security
# Disable access to the entire file system except for the directories that
# are explicitly allowed later.
# This currently breaks the configurations that come with some web application
# Debian packages. It will be made the default for the release after lenny.
# AllowOverride None
# Order Deny,Allow
# Deny from all
# Changing the following options will not really affect the security of the
# server, but might make attacks slightly more difficult in some cases.
# This directive configures what you return as the Server HTTP response
# Header. The default is 'Full' which sends information about the OS-Type
# and compiled in modules.
# Set to one of: Full | OS | Minimal | Minor | Major | Prod
# where Full conveys the most information, and Prod the least.
# Optionally add a line containing the server version and virtual host
# name to server-generated pages (internal error documents, FTP directory
# listings, mod_status and mod_info output etc., but not CGI generated
# documents or custom error documents).
# Set to "EMail" to also include a mailto: link to the ServerAdmin.
# Set to one of: On | Off | EMail
# Allow TRACE method
# Set to "extended" to also reflect the request body (only for testing and
# diagnostic purposes).
# Set to one of: On | Off | extended
For Slackware, it's a little bit trickier. You have to download the package (hopefully from the Slackware site) and then install it manually using Slackware's package manager, hoping there's no dependencies to deal with...Hope this helps.
No, it doesn't. PHP is already included in Slackware.