RE: BAD Error Installing new Apache2 & PHP?
A,
I'm slowly catching up on the learning curve. My sources list is:
#deb file:///cdrom/ sarge main
deb ftp://ftp.us.debian.org/debian/ stable main
deb-src ftp://ftp.us.debian.org/debian/ stable main
deb http://security.debian.org/ stable/updates main
My general idea of a plan (remember, all this got started because
"vulnerabilities" were reported assoc with Apache & PHP) so far:
1. Change the sources.list to look for "sarge" instead of "stable" &
update/install apache2 & PHP pkgs. I guess it would be good to do
'apt-get clean' before this to "start over" with a new pkg cache...?
2. Check to see what versions of Apache & PHP this has given me. If this
solves the problem w/vulnerabilities, the rest is optional for now. From
what I've read, to really fix web server vulnerabilities you need to
step up to Etch.
3. Upgrade to the 2.6 kernel. I think the Etch installation guide
recommends this before going straight to 4.0.
4. Upgrade to Etch.
Sound reasonable?
I back up data files daily & several directories which probably contain
config files. Is there a list of the most common directories for config
data I could check against?
-Ron
-----Original Message-----
From: Andrew Sackville-West [mailto:andrew@farwestbilliards.com]
Sent: Tuesday, June 19, 2007 3:53 PM
To: debian-user@lists.debian.org
Subject: Re: BAD Error Installing new Apache2 & PHP?
On Tue, Jun 19, 2007 at 03:24:38PM -0700, Aikins, Ronald (Ron) (CIV)
wrote:
> I'm running Debian kernel version 2.4.27-2-386. I needed to upgrade
> Apache (from 2.0.54) & PHP (from 4.3.10-16) on our system. After doing
> "apt-get update" I executed the command:
are you still running sarge? did you fix up your sources.list so you'd
stay with sarge? you are treading in "upgrade to etch" waters
here... be careful.
>
> when it asked whether I wanted to remove the kernel =:0
>
did it install a new kernel first?
[...]
>
>
> Remove the running kernel image (not recommended) [No]? No
>
>
>
> dpkg: error processing kernel-image-2.4.27-2-386
> (--remove):
>
> subprocess pre-removal script returned error exit
status
> 1
>
> dpkg: initrd-tools: dependency problems, but removing
> anyway as you request:
>
> kernel-image-2.4.27-2-386 depends on initrd-tools (>=
> 0.1.48).
>
> Removing initrd-tools ...
------------------^^^^^^^^^^^^^^^^^^^^^^^^
so you've already begun the transition. you need to figure out what
you want to do, fix up your sources.list and attempt to fix-up
whatever you have broken... I can't be more specific without more
information
A
Reply to: