(Contributed by Steven Mc Farling, edited)
"I have found it is the "security level" that made mod_php
not work. If I install (all other things the same) with a security level
of "high" the following is required to get php to work.[...]
-
Type the following at the command prompt to ensure
the mod_php3 rpm is installed on the machine:
rpm -qa | grep php3
If mod_php3-3.0.13-6mdk is listed, go to step 2.
If NOT, then install the mod_php3 rpm by doing the following:
- put Mandrake 7.0 CD in CDROM
- type:
mount /mnt/cdrom
- type:
cd /mnt/cdrom/Mandrake/RPMS
-
type: rpm -i mod_php3-3.0.13-6mdk
-
Add the lines with the ** in front of them to the
'/etc/httpd/conf/httpd.conf' file. I will put the line before the change
to help insure you put the lines in the correct place:
LoadModule setenvif_module modules/mod_setenvif.so
**LoadModule php3_module /usr/lib/apache/libphp3.so
AddModule mod_setenvif.c
**AddModule mod_php3.c
Include conf/vhosts/vhost0.conf
**Include conf/addon-modules/mod_php3.conf
-
Restart the web server by typing:
/etc/rc.d/init.d/httpd restart
-
You should see
Shutting down http: [ OK ]
Starting httpd: [ OK ] "
Yves Lucet adds:
"To use php on apache I had to add the following lines
to '/etc/httpd/conf/httpd.conf' (I am using Linux Mandrake 7.1):
#see http://www.mandrakeuser.org/troubles/tquick4.html
Include conf/addon-modules/mod_perl.conf
LoadModule php3_module modules/libphp3.so
AddModule mod_php3.c
Include conf/addon-modules/mod_php3.conf
So the quick tip should be completed by checking that
mod_perl is available, if it is not add the first Include line before loading
php3."
section index top
(Contributed by Al Chou, edited)
"I ran /etc/security/msec/init.sh custom
and answeredyes to allow root logins at the console. A typographic
bug at the beginning of line 53 of '/etc/security/msec/init-sh/custom.sh'
[msec-0.9] then caused '/etc/inittab' to be zeroed out, which upon reboot
caused the system to ask what runlevel I wanted to use and then proceed to
say, No more processes at this runlevel .
[...] Over the weekend I remedied this by reinstalling
from scratch (I didn't know any better), but at an early point I did discover
that /etc/inittab had zero bytes in it.[...]
I finally gleaned enough from Deja and the Linux System Administrator's
Guide to piece together what to do. Here it is:
- Upon booting, tell LiLo to use
linux init=/bin/sh .
- The file system will be mounted read-only, so remount
it in read-write mode:
mount -o remount,rw /dev/hda6 /
- Now restore your '/etc/inittab' from the backup copy
(assuming here you have one called '/etc/inittab.bak'):
cd /etc
cp inittab.bak inittab
- CTRL-ALT-DEL to reboot the system, which should come
up normally.
P.S. The bug in '/etc/security/msec/init-sh/custom.sh'
is fixed in the current version of msec that can be found in the Mandrake
cooker directory."
section index top
If you've got MS-Windows installed, check if it detects
the correct amount of system memory. If not, there is something wrong with
your memory modules.
Current GNU/Linux kernels have some difficulties with certain BIOS'es, read
this message from the linux-kernel mailing list for an explanation.
The only switch that might help you is supplying the correct amount of RAM
either on the boot prompt or via '/etc/lilo.conf'. At the boot prompt, type
linux mem=[size in MB]M
(e.g. linux mem=96M , if you have 96 MB RAM).
If this works, add it to your '/etc/lilo.conf', by changing
the stringappend="" to something like this:append="mem=96M"
In GRUB, use something like
title linux
kernel (hd0,0)/boot/vmlinuz root=/dev/hda1 mem=128M
section index top
Make sure you have version 4.05. But even that version
crashes when used at a color depth of 24bpp. Either use 'xpdf' for displaying
PDF files or change the color depth of
your display.
section index top
Due to a packaging error, the 'isdn4k-utils' package
in LM 7.1 does not install correctly. Either use the package from 7.0 or
get the updated package (isdn4k-utils-3.1b7-6mdk), e.g. via
the RPM Repository.
section index top
Next page of Quick Hacks
|