The following errata for CentOS-2 have been built and uploaded the the
centos mirror:
RHSA-2005:031-01 Updated php packages fix security issues
Files available:
php-4.1.2-2.2.i386.rpm
php-devel-4.1.2-2.2.i386.rpm
php-imap-4.1.2-2.2.i386.rpm
php-ldap-4.1.2-2.2.i386.rpm
php-manual-4.1.2-2.2.i386.rpm
php-mysql-4.1.2-2.2.i386.rpm
php-odbc-4.1.2-2.2.i386.rpm
php-pgsql-4.1.2-2.2.i386.rpm
More details are available from the RedHat web site at
https://rhn.redhat.com/errata/rh21as-errata.html
The easy way to make sure you are up to date with all the latest patches
is to run:
# yum update
--
John Newbigin - Computer Systems Officer
School of Information Technology
Swinburne University of Technology
Melbourne, Australia
http://www.it.swin.edu.au/staff/jnewbigin
The following errata for CentOS-2 have been built and uploaded the the
centos mirror:
RHSA-2005:012-01 Updated krb5 packages fix security vulnerabilities
Files available:
krb5-devel-1.2.2-32.i386.rpm
krb5-libs-1.2.2-32.i386.rpm
krb5-server-1.2.2-32.i386.rpm
krb5-workstation-1.2.2-32.i386.rpm
More details are available from the RedHat web site at
https://rhn.redhat.com/errata/rh21as-errata.html
The easy way to make sure you are up to date with all the latest patches
is to run:
# yum update
--
John Newbigin - Computer Systems Officer
School of Information Technology
Swinburne University of Technology
Melbourne, Australia
http://www.it.swin.edu.au/staff/jnewbigin
> you've added them to your public key ring - not to your rpmdb.
> rpm --import thekey
> that will make it work.
> -sv
I've done that and I get the same error and the same list publick keys:
pub 1024D/025E513B 2004-03-15 CentOS-3 Key <centos-3key(a)caosity.org>
sub 2048g/EE899A92 2004-03-15 [expires: 2009-03-14]
Should I see something different ???
Can any one tell me step by step how to delete ALL keys from EVERYWHERE
(rpm, gpg.) and re-add them ?? Maybe I'm missing something.
Thanks!!
Alejandro.
I'm looking for some volunteers to make some CD's and DVD's of cAos
and CentOS for the upcoming LinuxWorld Expo to give out at our booth.
I would need to recieve them by Feb 10th.
Contact me directly if you can help.
--
Matt Shields
http://masnetworks.bizhttp://shieldsmedia.com (currently under construction)
http://shieldsproductions.com (currently under construction)
https://rhn.redhat.com/errata/RHSA-2005-043.html refers
updated files :-
updates/i386/RPMS/kernel-2.4.21-27.0.2.EL.athlon.rpm
updates/i386/RPMS/kernel-2.4.21-27.0.2.EL.i586.rpm
updates/i386/RPMS/kernel-2.4.21-27.0.2.EL.i686.rpm
updates/i386/RPMS/kernel-2.4.21-27.0.2.EL.src.rpm
updates/i386/RPMS/kernel-BOOT-2.4.21-27.0.2.EL.i386.rpm
updates/i386/RPMS/kernel-doc-2.4.21-27.0.2.EL.i386.rpm
updates/i386/RPMS/kernel-hugemem-2.4.21-27.0.2.EL.i686.rpm
updates/i386/RPMS/kernel-hugemem-unsupported-2.4.21-27.0.2.EL.i686.rpm
updates/i386/RPMS/kernel-smp-2.4.21-27.0.2.EL.athlon.rpm
updates/i386/RPMS/kernel-smp-2.4.21-27.0.2.EL.i686.rpm
updates/i386/RPMS/kernel-smp-unsupported-2.4.21-27.0.2.EL.athlon.rpm
updates/i386/RPMS/kernel-smp-unsupported-2.4.21-27.0.2.EL.i686.rpm
updates/i386/RPMS/kernel-source-2.4.21-27.0.2.EL.i386.rpm
updates/i386/RPMS/kernel-unsupported-2.4.21-27.0.2.EL.athlon.rpm
updates/i386/RPMS/kernel-unsupported-2.4.21-27.0.2.EL.i586.rpm
updates/i386/RPMS/kernel-unsupported-2.4.21-27.0.2.EL.i686.rpm
updates/i386/SRPMS/kernel-2.4.21-27.0.2.EL.src.rpm
These files are on mirror.caosity.org now and should be on all local
mirrors within a few hours.
To update run yum update kernel
You will need to reboot to use the new kernel after update.
Lance
Hi all,
I am having problems to get the SeaLevel IO card to work with CentOS distro.
Basically the card is being recognised and shown by lspci BUT /proc/devices
file is not updated with the new devices does anyone know why. ?
Could someone tell me what/where infos are needed to get /proc/devices to be
updated.
The reason I require the /proc/devices infos is because I want to run a mknod
command with those infos.
This is rather urgent so any help will be much appreciated.
=========
[root@machine]# ./seaio-load
Warning: kernel-module version mismatch
/opt/relay/lib/modules/seaio.o was compiled for kernel version
2.4.21-20.EL.c0smp
while this kernel is version 2.4.21-20.0.1.ELsmp
Warning: /opt/relay/lib/modules/seaio.o symbol for parameter break_on_load
not found
Warning: loading /opt/pmx-relay/lib/modules/seaio.o will taint the kernel: no
license
See http://www.tux.org/lkml/#export-tainted for information about tainted
modules
Warning: loading /opt/relay/lib/modules/seaio.o will taint the kernel:
forced load
Module seaio loaded, with warnings
mknod: wrong number of arguments
Try `mknod --help' for more information.
mknod: wrong number of arguments
Try `mknod --help' for more information.
mknod: wrong number of arguments
Try `mknod --help' for more information.
mknod: wrong number of arguments
Try `mknod --help' for more information.
chgrp: failed to get attributes of `/dev/dio[0-3]': No such file or directory
chmod: failed to get attributes of `/dev/dio[0-3]': No such file or directory
lsmod output
==========
Module Size Used by Tainted: PF
seaio 8784 0 (unused)
Kernel version :-
============
Linux pdc-svr3 2.4.21-20.0.1.ELsmp #1 SMP Thu Dec 2 23:06:40 GMT 2004 i686
i686 i386 GNU/Linux
lspci output
==========
03:06.0 Class ff00: Sealevel Systems Inc: Unknown device 8012 (rev 01)
/etc/sysconfig/hwconf output
=======================
class: OTHER
bus: PCI
detached: 0
driver: unknown
desc: "Sealevel Systems Inc|unknown device 135e:8012"
vendorId: 135e
deviceId: 8012
subVendorId: 135e
subDeviceId: 8012
pciType: 1
pcibus: 3
pcidev: 6
pcifn: 0
--
Regards
JC
Hi! Am new in trying CentOS, can you please help me how to install
xfce4. What do I need to add in my yum,.conf or in my source.list
for my apt-get.
Thanks you very much and more power to you guys!
Regards,
Julius
Hello!
I'm running clamav-milter, clamd, and sendmail on CentOS 3.3 (RHEL3). I'm
trying to verify that my milter works. I've sent test emails from
testvirus.org but they don't appear to be getting flagged. I don't see
anything in the logs to indicate they were. Is there a sure-fire way to know?
Also, how should the clamd work? Does it watch the filesystem? Or will it only
work on a scan?
--
<<JAV>>