Hi I use Suse6.2 . My apache web server is installed when i install suse. It's working good. After then i installed MySQL. Now I want to install php3. I read some tutorials. They say I should install apache and php at the same time. Bu I already installed apache before. What should I do ? Sincerelly ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
I believe that the new boot process in 6.3 involves a ramdisk. I intend to compile my own kernel and so will not need to use a ramdisk. To remove the 'ramdisk part' from the boot process (ie to revert back to the 6.2 boot process), having installed a new kernel, do I simply remove the initrc = /sbin/initrc from my /etc/lilo.conf before reinstalling lilo? Is that all I need to do...no changes to the rc files or to init? (i don thtink there should be). Having done this, if I delete /sbin/initrc and the 'make initrc' file (forgot exact name, but its something liek mk.initrc), will the boot process be exactly like 6.2? I want to remove all traces a ramdisk ever being used. Thank you. -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
On Thu, 30 Dec 1999, A Nourai wrote:
I believe that the new boot process in 6.3 involves a ramdisk.
... a special one, called 'initial ramdisk'. Special, because the boot loader loads it and the kernel starts using the filesystem on it as initial '/'
I intend to compile my own kernel and so will not need to use a ramdisk.
To remove the 'ramdisk part' from the boot process (ie to revert back to the 6.2 boot process), having installed a new kernel, do I simply remove the initrc = /sbin/initrc from my /etc/lilo.conf before reinstalling lilo?
Is that all I need to do...no changes to the rc files or to init? (i don thtink there should be).
Yes.
Having done this, if I delete /sbin/initrc and the 'make initrc' file (forgot exact name, but its something liek mk.initrc), will the boot process be exactly like 6.2? I want to remove all traces a ramdisk ever being used.
Hey, I was waiting for us to use this modern method for supporting modules for your SCSI stuff for a long time and celebrated its arrival, and you want to drop it?! -- Michael Hasenstein http://www.suse.de/~mha/ Private Pilot (ASEL) since 1998 -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
On Thu, 30 Dec 1999, A Nourai wrote:
I believe that the new boot process in 6.3 involves a ramdisk.
... a special one, called 'initial ramdisk'. Special, because the boot loader loads it and the kernel starts using the filesystem on it as initial '/'
I intend to compile my own kernel and so will not need to use a ramdisk.
To remove the 'ramdisk part' from the boot process (ie to revert back to
6.2 boot process), having installed a new kernel, do I simply remove the initrc = /sbin/initrc from my /etc/lilo.conf before reinstalling lilo?
Is that all I need to do...no changes to the rc files or to init? (i don thtink there should be).
Yes.
Having done this, if I delete /sbin/initrc and the 'make initrc' file (forgot exact name, but its something liek mk.initrc), will the boot
Could you please explain to me the benefits of using the 'initial ramdisk' having compiled my own kernel. I use a scsii hard drive connected to a adaptec 2940U2 controller. I compiled the scsii support for the adapter into the kernel (as opposed to modularising it). If I were to keep on using the ramdisk, and want to compile my own kernel, then just need to run mk.initrc (or whatever the name is) and create a new initrc...correct? I'd of course leave the 'initrc = ...' parameter in my lilo.conf. Thanks. ----- Original Message ----- From: "Michael Hasenstein" <mha@suse.de> To: "A Nourai" <nagash@ozemail.com.au> Cc: <suse-linux-e@suse.com> Sent: Thursday, 30 December, 1999 9:12 PM Subject: Re: [SLE] New boot process in SuSE 6.3 the process
be exactly like 6.2? I want to remove all traces a ramdisk ever being used.
Hey, I was waiting for us to use this modern method for supporting modules for your SCSI stuff for a long time and celebrated its arrival, and you want to drop it?!
-- Michael Hasenstein http://www.suse.de/~mha/ Private Pilot (ASEL) since 1998
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Could this new boot process be the reason I can't boot to a recompiled kernel in 6.3? I didn't get any compile errors (that I noticed anyway). I used my old lilo.conf file and added the entry for the new kernel. I've always found yast to be cumbersome and confusing regarding lilo, so I edit it manually. Maybe I should create a new lilo.conf via yast and add my old kernel to it instead? Or, I've never tried bzlilo should I just do that then edit in my old kernel? Tim, NJ A Nourai wrote:
Could you please explain to me the benefits of using the 'initial ramdisk' having compiled my own kernel.
I use a scsii hard drive connected to a adaptec 2940U2 controller. I compiled the scsii support for the adapter into the kernel (as opposed to modularising it).
If I were to keep on using the ramdisk, and want to compile my own kernel, then just need to run mk.initrc (or whatever the name is) and create a new initrc...correct? I'd of course leave the 'initrc = ...' parameter in my lilo.conf.
Thanks. ----- Original Message ----- From: "Michael Hasenstein" <mha@suse.de> To: "A Nourai" <nagash@ozemail.com.au> Cc: <suse-linux-e@suse.com> Sent: Thursday, 30 December, 1999 9:12 PM Subject: Re: [SLE] New boot process in SuSE 6.3
On Thu, 30 Dec 1999, A Nourai wrote:
I believe that the new boot process in 6.3 involves a ramdisk.
... a special one, called 'initial ramdisk'. Special, because the boot loader loads it and the kernel starts using the filesystem on it as initial '/'
I intend to compile my own kernel and so will not need to use a ramdisk.
To remove the 'ramdisk part' from the boot process (ie to revert back to the 6.2 boot process), having installed a new kernel, do I simply remove the initrc = /sbin/initrc from my /etc/lilo.conf before reinstalling lilo?
Is that all I need to do...no changes to the rc files or to init? (i don thtink there should be).
Yes.
Having done this, if I delete /sbin/initrc and the 'make initrc' file (forgot exact name, but its something liek mk.initrc), will the boot process be exactly like 6.2? I want to remove all traces a ramdisk ever being used.
Hey, I was waiting for us to use this modern method for supporting modules for your SCSI stuff for a long time and celebrated its arrival, and you want to drop it?!
-- Michael Hasenstein http://www.suse.de/~mha/ Private Pilot (ASEL) since 1998
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
The Apache installed by SuSE-6.2 already has PHP3. You don't need to do anything. To confirm, point your browser at the server and click on the PHP3 test link. The URL is probably http://localhost/test.php3
I use Suse6.2 . My apache web server is installed when i install suse. It's working good. After then i installed MySQL. Now I want to install php3. I read some tutorials. They say I should install apache and php at the same time. Bu I already installed apache before. What should I do ?
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
On Thu, 30 Dec 1999, Kadir Imamoglu wrote:
Hi
I use Suse6.2 . My apache web server is installed when i install suse. It's working good. After then i installed MySQL. Now I want to install php3. I read some tutorials. They say I should install apache and php at the same time. Bu I already installed apache before. What should I do ?
If you did it the sensible way (apache.rpm from series [n]), simply install mod_perl and mod_php3 from series [n]. -- -=|JP|=- Jon Pennington | Atipa Linux Solutions -o) jpennington@atipa.com | http://www.atipa.com /\\ Kansas City, MO, USA | 816-241-2641 _\_V -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
participants (6)
-
fountai＠hursley.ibm.com -
jpennington＠atipa.com -
kimamoglu＠hotmail.com -
mha＠suse.de -
nagash＠ozemail.com.au -
tajc＠goes.com