On Wed, 2006-05-24 at 17:13 -0500, Johnny Hughes wrote:
> CentOS Errata and Security Advisory 2006:0493
>
> https://rhn.redhat.com/errata/RHSA-2006-0493.html
>
> The following updated files have been uploaded and are currently
> syncing to the mirrors:
>
> i386:
> kernel-2.6.9-34.0.1.EL.i586.rpm
> kernel-2.6.9-34.0.1.EL.i686.rpm
> kernel-devel-2.6.9-34.0.1.EL.i586.rpm
> kernel-devel-2.6.9-34.0.1.EL.i686.rpm
> kernel-doc-2.6.9-34.0.1.EL.noarch.rpm
> …
[View More]kernel-hugemem-2.6.9-34.0.1.EL.i686.rpm
> kernel-hugemem-devel-2.6.9-34.0.1.EL.i686.rpm
> kernel-smp-2.6.9-34.0.1.EL.i586.rpm
> kernel-smp-2.6.9-34.0.1.EL.i686.rpm
> kernel-smp-devel-2.6.9-34.0.1.EL.i586.rpm
> kernel-smp-devel-2.6.9-34.0.1.EL.i686.rpm
>
> src:
> kernel-2.6.9-34.0.1.EL.src.rpm
I wonder if a change in the naming convention for centosplus kernels
might be in order? Had to think a bit to understand why yum was not
showing me the new errata kernel until I realized that
2.6.9-34.106.unsupported > 2.6.9-34.0.1.EL
in the sorting order. I downloaded from a mirror and forced the
install:
[root@tabb1 RPMS]# rpm -ivh kernel-2.6.9-34.0.1.EL.i686.rpm
Preparing... ########################################### [100%]
package kernel-2.6.9-34.106.unsupported (which is newer than kernel-2.6.9-34.0.1.EL) is already installed
[root@tabb1 RPMS]# rpm -ivh --force kernel-2.6.9-34.0.1.EL.i686.rpm
Preparing... ########################################### [100%]
1:kernel ########################################### [100%]
[root@tabb1 RPMS]#
Similar problems for kernel-devel and kernel-doc RPMS.
If the name for the last centosplus/unsupported version had been
kernel-2.6.9-34.unsupported.106 (or similar) the new version[s] would
have been offered for installation, and since (I believe)
unsupported.106 > EL
for rpm/yum, the new centosplus kernels would still be installable if
that repo is configured.
Phil
[View Less]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Is anyone having any printing problems in CentOS 4.3?
Here's what I'm seeing (problem)
1. Can't import ppd file
2. After manually adding the ppd file it doesn't show up in the gui
print tool
3. Haven't been able to share a printer using the gui tool
I'm wondering if this is just my problem (user error on my part) or if
this is a CentOS/Redhat problem.
- --
You can get my public PGP key at https://keyserver.pgp.com
Digital Overload
http://www.…
[View More]digitaloverload.net
Keep your data safe by doing regular backups. At Digital Overload we use
a combination of DVD and hard drive backups. For off site storage we use
a safe-deposit box at the bank. All backups are encrypted.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFEehKh+rNhalK/8UURAogIAJkBtRyca04LgyV5Bqp70lYwuX6CPQCZAZ88
q8iIdbEP4O0fddIFnHpP8pc=
=RJRw
-----END PGP SIGNATURE-----
[View Less]
Hi,
i added second nic to my server
I have these two uplinks:
My main uplink is 195.XXX.XXX.XXX
My secondary is 83.XXX.XXX.XXX
When I add the secondary NIC, CentOS automatically sets default gw to
83.XXX.XXX.1 and deletes the gateway from 195.XXX.XXX.1
How can I set it that CentOs uses the gateway 195.XXX.XXX.1 as default
gateway. When I set this manually with route, CentOS changes my sentings
after a reboot.
And I need also to accept incoming traffic on 83.XXX.XXX.1.
Thanks for your …
[View More]help and best regards
Niels
[View Less]
I generally 3Ware controllers get recommended but the servers we are
looking at getting use LSI Megaraid SATA 150-4 controllers.
I was wonder what experiences there are under CentOS 4 with these
positive & negative?
Regards,
Paul Berger
Greetings,
I am not able to find the 4.3 single server cd torrent or iso
Would someone please tell me where it currently resides? :-)
Thanks in advance!
- rh
--
Robert Hanson - Abba Communications
Computer & Internet Services
(509) 624-7159 - www.abbacomm.net
Barry L. Kline <mailto:blkline@attglobal.net> tapped at Friday, May 26, 2006
4:50 PM:
> Les Mikesell wrote:
>> On Fri, 2006-05-26 at 16:56, Barry L. Kline wrote:
>
>>
>> Note that unless it has changed recently, SATA drives don't pass
>> errors up to the software raid layer correctly. If a drive
>> dies it doesn't get kicked out as it should.
>
> Good point. The systems on which I use it are either IDE-based or
> SCSI-based. The SATA …
[View More]machines I have are all 3ware RAID controller
> equipped.
>
> Barry
This is what I go with, 3Ware and SATA drives. My company just needs
the raw storage space, and not so much speed. So, I can live with SATA
drives on 3Ware cards, and things just work.
Mark
[View Less]
Barry L. Kline <mailto:blkline@attglobal.net> tapped at Friday, May 26, 2006
4:48 PM:
> Mark Schoonover wrote:
>> Barry L. Kline <mailto:blkline@attglobal.net> tapped at Friday, May
>> 26, 2006 2:56 PM:
>>
>
>>
>> I'd like to know how things went with software raid when you've lost
>> a drive in a mirror or RAID5. The times that's happened to me, I
>> could never recover the partition - had to always restore from tape.
>> …
[View More]After that point, it was hardware only. Software RAID works fine, as
>> long as there's no problems.
>>
>
> I have lost a drive in a mirror and had no trouble recovering it. The
> steps are basically the same for a RAID 5 system as they are for the
> mirror.
>
> What I figured out early on was that I didn't want to be discovering
> how RAID recovery works while under the gun to get a failed drive
> replaced. I tried that once and found it extremely stressful.
>
> What you might want to do (assuming that you have an old PC and a
> couple
> of old drives around) is build a test system that you can experiment
> with.
Today, you don't need the spare hardware laying around. You can
download VMware Server for free, and create what you need virtually. You'll
accomplish the same thing, without the added expense and space of using
actual hardware.
I did that and now have a good working knowledge of the
> recovery
> steps. ('tho I took good notes because the frequence of this occuring
> has been, for me, rather low). Failed drive in another machine?
> BRING
> IT ON! (okay, okay... I don't want to tempt the gods and *really*
> have
> that failure, but I'm not as concerned about it as I once was).
>
> Barry
I'd rather not bring it on, but there are times it's going to
happen!
Mark
[View Less]
Hello list,
Anybody saw this: http://www.instalinux.com/ ?
Interesting idea.
Regards
--
_________________________________________________________________
D o m i n i k S k ł a d a n o w s k i
hey friends,
I am trying to make postfix run with tls in chroot mode, but I am not
able to send the messages with tls on. I am using postfix 2.2.10 on
centos 4.0 and I had compiled the postfix from sources with tls &
cyrus-sasl support. I copied the certificates from /usr/share/ssl to
/etc/postfix.
Below are the errors I am getting:
May 25 13:27:51 test1 postfix/smtpd[4095]: warning: TLS library problem:
4095
:error:0906406D:PEM routines:DEF_CALLBACK:problems getting
password:pem_lib.c:…
[View More]10
5:cyrus-sasl support. I copied the certificates from /usr/share/ssl to
/etc/postfix.
Below are the errors I am getting:
May 25 13:27:51 test1 postfix/smtpd[4095]: warning: TLS library problem:
4095
:error:0906406D:PEM routines:DEF_CALLBACK:problems getting
password:pem_lib.c:10
5:
May 25 13:27:51 test1 postfix/smtpd[4095]: warning: TLS library problem:
4095
:error:0906A068:PEM routines:PEM_do_header:bad password read:pem_lib.c:399:
May 25 13:27:51 test1 postfix/smtpd[4095]: warning: TLS library problem:
4095
:error:140B0009:SSL routines:SSL_CTX_use_PrivateKey_file:PEM
lib:ssl_rsa.c:707:
May 25 13:27:51 test1 postfix/smtpd[4095]: cannot load RSA certificate and
ke
y data
May 25 13:27:51 test1 postfix/smtpd[4095]: connect from
test1.sun.net[192.168.1.125]
May 25 13:27:51 test1 postfix/smtpd[4095]: disconnect from
test1.sun.net[192.168.1.125]
May 25 13:29:37 test1 postfix/smtpd[4257]: warning: cannot get private key
fr
om file /etc/postfix/newreq.pem
May 25 13:29:37 test1 postfix/smtpd[4257]: warning: TLS library problem:
4257
:error:0906406D:PEM routines:DEF_CALLBACK:problems getting
password:pem_lib.c:10
5:
May 25 13:29:37 test1 postfix/smtpd[4257]: warning: TLS library problem:
4257
:error:0906A068:PEM routines:PEM_do_header:bad password read:pem_lib.c:399:
May 25 13:29:37 test1 postfix/smtpd[4257]: warning: TLS library problem:
4257
I telnet into the port 25 on localhost and tried to start tls but it
says "454 TLS not available due to local problem"
telnet localhost 25
Trying 127.0.0.1...
Connected to localhost.localdomain (127.0.0.1).
Escape character is '^]'.
220 test1.sun.net ESMTP Postfix
EHLO test1.sun.net250-test1.sun.net
250-PIPELINING
250-SIZE 51200000
250-VRFY
250-ETRN
250-STARTTLS
250 8BITMIME
starttls
454 TLS not available due to local problem
quit
I have also attached the result of postconf command with this mail in
"postfix.txt" file.Both SELinux and firewall are off on this system.
Please let me know if you need any further inputs.
Thanks & Regards
Ankush Grover
May 25 13:27:51 test1 postfix/smtpd[4095]: warning: TLS library problem:
4095
:error:0906A068:PEM routines:PEM_do_header:bad password read:pem_lib.c:399:
May 25 13:27:51 test1 postfix/smtpd[4095]: warning: TLS library problem:
4095
:error:140B0009:SSL routines:SSL_CTX_use_PrivateKey_file:PEM
lib:ssl_rsa.c:707:
May 25 13:27:51 test1 postfix/smtpd[4095]: cannot load RSA certificate and
ke
y data
May 25 13:27:51 test1 postfix/smtpd[4095]: connect from
test1.sun.net[192.168.1.125]
May 25 13:27:51 test1 postfix/smtpd[4095]: disconnect from
test1.sun.net[192.168.1.125]
May 25 13:29:37 test1 postfix/smtpd[4257]: warning: cannot get private key
fr
om file /etc/postfix/newreq.pem
May 25 13:29:37 test1 postfix/smtpd[4257]: warning: TLS library problem:
4257
:error:0906406D:PEM routines:DEF_CALLBACK:problems getting
password:pem_lib.c:10
5:
May 25 13:29:37 test1 postfix/smtpd[4257]: warning: TLS library problem:
4257
:error:0906A068:PEM routines:PEM_do_header:bad password read:pem_lib.c:399:
May 25 13:29:37 test1 postfix/smtpd[4257]: warning: TLS library problem:
4257
I telnet into the port 25 on localhost and tried to start tls but it
says "454 TLS not available due to local problem"
telnet localhost 25
Trying 127.0.0.1...
Connected to localhost.localdomain (127.0.0.1).
Escape character is '^]'.
220 test1.sun.net ESMTP Postfix
EHLO test1.sun.net250-test1.sun.net
250-PIPELINING
250-SIZE 51200000
250-VRFY
250-ETRN
250-STARTTLS
250 8BITMIME
starttls
454 TLS not available due to local problem
quit
I have also attached the result of postconf command with this mail in
"postfix.txt" file.Both SELinux and firewall are off on this system.
Please let me know if you need any further inputs.
Thanks & Regards
Ankush Grover
[View Less]
Hi, where are the kernel sources for x86_64.
They are not on the DVD for 4.3
Thanks,
--
-------------------------------------------
Erick Perez
Linux User 376588
http://counter.li.org/ (Get counted!!!)
Panama, Republic of Panama