Discuss August 2009

discuss@lists.centos.org

282 participants
265 discussions

CentOS-announce Digest, Vol 54, Issue 11
by centos-announce-request＠centos.org 25 Aug '09

25 Aug '09

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CESA-2009:1222 Important CentOS 5 i386 kernel Update (Karanbir Singh) 2. CESA-2009:1222 Important CentOS 5 x86_64 kernel Update (Karanbir Singh) ---------------------------------------------------------------------- Message: 1 Date: Mon, 24 Aug 2009 19:35:59 +0000 From: Karanbir Singh <kbsingh(a)centos.org> Subject: [CentOS-announce] CESA-2009:1222 Important CentOS 5 i386 kernel Update To: centos-announce(a)centos.org Message-ID: <20090824193559.GA1073(a)tantra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2009:1222 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2009-1222.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) i386: 229ffdd6e1c4ef228b519298d9aef095 kernel-2.6.18-128.7.1.el5.i686.rpm dec5d22af821cd3223677c07a6c46e20 kernel-debug-2.6.18-128.7.1.el5.i686.rpm 9d6596fb291c21ec81a50616c153b5ae kernel-debug-devel-2.6.18-128.7.1.el5.i686.rpm 8d206b5c5d9d6f544b1fc082c79f698c kernel-devel-2.6.18-128.7.1.el5.i686.rpm 07bd3312874c7110530bab61b01baf06 kernel-doc-2.6.18-128.7.1.el5.noarch.rpm dd3e3430535e7c6905adcf54cd982c72 kernel-headers-2.6.18-128.7.1.el5.i386.rpm ff19b5a51fcc2f4a7e514807d79e7c97 kernel-PAE-2.6.18-128.7.1.el5.i686.rpm d65893ebb79361fda3e3b78d4e2fdaf3 kernel-PAE-devel-2.6.18-128.7.1.el5.i686.rpm a7e59c15d2e94d2c304fd554dcbda582 kernel-xen-2.6.18-128.7.1.el5.i686.rpm 933e14b5610edf4a83d85dfaf13aaba7 kernel-xen-devel-2.6.18-128.7.1.el5.i686.rpm Source: 6f2a1a5d7d602684880454cd3bbe00e6 kernel-2.6.18-128.7.1.el5.src.rpm -- Karanbir Singh CentOS Project { http://www.centos.org/ } irc: z00dax, #centos(a)irc.freenode.net ------------------------------ Message: 2 Date: Mon, 24 Aug 2009 19:36:02 +0000 From: Karanbir Singh <kbsingh(a)centos.org> Subject: [CentOS-announce] CESA-2009:1222 Important CentOS 5 x86_64 kernel Update To: centos-announce(a)centos.org Message-ID: <20090824193602.GA1088(a)tantra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2009:1222 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2009-1222.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) x86_64: 90c9aa3034be5545a946ce13259a1590 kernel-2.6.18-128.7.1.el5.x86_64.rpm 98fe46baaef4f807ad3719f5bd3d0ccd kernel-debug-2.6.18-128.7.1.el5.x86_64.rpm 0d9e47b8cdcfe760e9a32807353caafe kernel-debug-devel-2.6.18-128.7.1.el5.x86_64.rpm 3ff5c6b8f8aa9a5bb392457d3f74ad53 kernel-devel-2.6.18-128.7.1.el5.x86_64.rpm 75cf07d4d6bd79f1d55c0499e74fb165 kernel-doc-2.6.18-128.7.1.el5.noarch.rpm ebaa6c16aec77563cccabff44829e802 kernel-headers-2.6.18-128.7.1.el5.x86_64.rpm 516e1ce8ad2146d43cc6b10d9c8c54b7 kernel-xen-2.6.18-128.7.1.el5.x86_64.rpm 3619c010401c79bc1222e23dd6388993 kernel-xen-devel-2.6.18-128.7.1.el5.x86_64.rpm Source: 6f2a1a5d7d602684880454cd3bbe00e6 kernel-2.6.18-128.7.1.el5.src.rpm -- Karanbir Singh CentOS Project { http://www.centos.org/ } irc: z00dax, #centos(a)irc.freenode.net ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org http://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 54, Issue 11 ***********************************************

1 0

anaconda and x86_64
by lhecking＠users.sourceforge.net 25 Aug '09

25 Aug '09

I'm trying to build a bugfixed anaconda package for 5.3 x84_64, but there are some fairly basic failures, like pkg-config .pc files not being found. When I modify the spec file accordingly, linking fails because installed libraries are not found. $ rpmbuild -ba anaconda.spec Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.25019 + umask 022 + cd /usr/src/redhat/BUILD + LANG=C + export LANG + unset DISPLAY + cd /usr/src/redhat/BUILD + rm -rf anaconda-11.1.2.168 + /usr/bin/bzip2 -dc /usr/src/redhat/SOURCES/anaconda-11.1.2.168.tar.bz2 + tar -xf - ... for d in isys wlite stubs loader2 po textw utils scripts bootdisk installclasses iw pixmaps isomd5sum command-stubs ui fonts; do make -C $d depend; done make[1]: Entering directory `/usr/src/redhat/BUILD/anaconda-11.1.2.168/isys' grep NFS_MOUNT_VERSION /usr/include/linux/nfs_mount.h | sed -e 's/NFS/KERNEL_NFS/' > nfs_mountversion.h Package libdhcp6client was not found in the pkg-config search path. Perhaps you should add the directory containing `libdhcp6client.pc' to the PKG_CONFIG_PATH environment variable Package 'libdhcp6client', required by 'libdhcp', not found cc -E -M -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -Wall -Werror -D_GNU_SOURCE =1 -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE=1 -D_LARGEFILE64_SOURCE=1 -DUSESELINUX=1 -I/usr/include/python2.4 -I.. -DHAVE_NFS nfsmount.c nfsmount_clnt.c nfsmount_xdr.c imount.c smp.c devnodes.c cpio.c uncpio.c dasd.c lang.c isofs.c dns.c linkdetect.c vio.c ethtool.c wireless.c eddsupport.c nl.c str.c auditd. c isys.c > .depend In file included from isys.c:55: /usr/include/libdhcp/pump.h:78:22: error: dhcp_nic.h: No such file or directory make[1]: *** [depend] Error 1 make[1]: Leaving directory `/usr/src/redhat/BUILD/anaconda-11.1.2.168/isys' make[1]: Entering directory `/usr/src/redhat/BUILD/anaconda-11.1.2.168/wlite' make[1]: *** No rule to make target `depend'. Stop. make[1]: Leaving directory `/usr/src/redhat/BUILD/anaconda-11.1.2.168/wlite' make[1]: Entering directory `/usr/src/redhat/BUILD/anaconda-11.1.2.168/stubs' make[1]: Nothing to be done for `depend'. make[1]: Leaving directory `/usr/src/redhat/BUILD/anaconda-11.1.2.168/stubs' Package libdhcp6client was not found in the pkg-config search path. Perhaps you should add the directory containing `libdhcp6client.pc' to the PKG_CONFIG_PATH environment variable Package 'libdhcp6client', required by 'libdhcp', not found ... etc. Any ideas how to fix this? The same package builds find under i386. --------------------------------------------------------------- This message and any attachments may contain Cypress (or its subsidiaries) confidential information. If it has been received in error, please advise the sender and immediately delete this message. ---------------------------------------------------------------

3 10

self signing certificates
by James B. Byrne 25 Aug '09

25 Aug '09

> From: Jerry Geis <geisj(a)pagestation.com> > To: CentOS ML <centos(a)centos.org> > Sent: Monday, 24 August, 2009 14:32:00 > Subject: [CentOS] self signing certificates > > hi all, > > I have gone through the process of self signing certificates. > Aside from the pop-ups about not trusted etc... everything > appears to work. > > For "internal" applications what do people/places do? > It would be nice to be seamless and have the "your not trusted" > window pop-up. > As someone else previously detailed, you really need to have a root signing CA that only signs certs for your issuing CAs and then use the issuing CAs to sign end use certificates of whatever types you deem appropriate. It is considered required practice that root CA and issuing CAs must be physically isolated from all network connections and that floppy or sneaker net must be used to handle incoming CSR and outgoing CERTS. If you are simply using certs for encryption and not for authentication then this practice probably can be safely dispensed with. If you ARE using certs for authentication then this provision is absolutely required. The arrangement of self-signed root CA <--CSR--- Issuing CA <--CSR--- end-user is now critical for Firefox users. Releases in the 3.x series will no longer trust any self-signed CA certificate. So, to avoid the warning box in Firefox you must have the end use certificates signed by an intermediate CA whose own certificate may however be signed by a self-signed root. > Yet this is not a public web site either. Just internal use. > The server might be on the internet but people from the internet > are not using it. > Well, the available software has no way of figuring that out for itself, so it makes no difference. And, to be precise, "people from the internet should not be using it", which is rather a different thing. > I presume there is no way to by-pass the certificate signing > process - even for internal apps. > Is there? > Not unless you can live with the warning boxes. -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

3 2

System freezes completely under kernel 2.6.18-128.7.1.el5
by Olaf Mueller 25 Aug '09

25 Aug '09

Hello, is there a known problem with the new kernel for CentOS 5.3? Till today, my server works without any problems. But after updating to the new kernel 2.6.18-128.7.1.el5 the system freezes completely with no more access by keyboard or over network. The last message in /var/log/messages is 'Aug 25 14:07:41 weidenwinde kernel: hdg: dma_timer_expiry: dma status == 0x21'. I have not change my hardware, have not change configuration and till this new kernel the system was running without any problems. The harddisks are younger than a year. Is someone else this seeing? regards Olaf

2 4

self signing certificates
by Jerry Geis 25 Aug '09

25 Aug '09

hi all, I have gone through the process of self signing certificates. Aside from the pop-ups about not trusted etc... everything appears to work. For "internal" applications what do people/places do? It would be nice to be seamless and have the "your not trusted" window pop-up. Yet this is not a public web site either. Just internal use. The server might be on the internet but people from the internet are not using it. I presume there is no way to by-pass the certificate signing process - even for internal apps. Is there? Thanks, Jerry

7 9

Re: [CentOS] Samba "use sendfile" configuration option set do disabled as default - why?
by Per Qvindesland 25 Aug '09

25 Aug '09

Hi I am not saying that this is the solution but I am saying that it might be worth a short, even if it works for you I would still fine tune it depending on your configs, a lot of the time fine tuning samba is a pain and most of the time it actually comes down to crappy network performance I.E the nic seems to be working but it actually has a fault. Regards Per Qvindesland --- Original message follows --- SUBJECT: Re: [CentOS] Samba "use sendfile" configuration option set do disabled as default - why? FROM: Christoph Maser TO: "CentOS mailing list" DATE: 24-08-2009 13:27 Am Montag, den 24.08.2009, 13:24 +0200 schrieb Per Qvindesland: > socket options = TCP_NODELAY IPTOS_LOWDELAY SO_RCVBUF=65536 > SO_SNDBUF=65536 These options are often found if you search for samba tuning. Did someone actaully benchmark the results? Shouldn't tuning buffers manuall be oboslete nowadays? I somewhat doubt this is THE solution for slow sambas. Chris financial.com AG Munich head office/Hauptsitz München: Maria-Probst-Str. 19 | 80939 München | Germany Frankfurt branch office/Niederlassung Frankfurt: Messeturm | Friedrich-Ebert-Anlage 49 | 60327 Frankfurt | Germany Management board/Vorstand: Dr. Steffen Boehnert (CEO/Vorsitzender) | Dr. Alexis Eisenhofer | Dr. Yann Samson | Matthias Wiederwach Supervisory board/Aufsichtsrat: Dr. Dr. Ernst zur Linden (chairman/Vorsitzender) Register court/Handelsregister: Munich – HRB 128 972 | Sales tax ID number/St.Nr.: DE205 370 553 _______________________________________________ CentOS mailing list CentOS(a)centos.org http://lists.centos.org/mailman/listinfo/centos

6 8

Access to xorg-x11-server-1.1.1-48.53.el5 (or later) SRPM ?
by James Pearson 25 Aug '09

25 Aug '09

Does anyone have access to the xorg-x11-server-1.1.1-48.53.el5 (or later) SRPM - which may be part of 5.4 beta? It's mentioned as having a fix for Bugzilla #448586 <https://bugzilla.redhat.com/show_bug.cgi?id=448586> I what to see if it fixes a X11 crash we're having. Thanks James Pearson

2 5

Re: [CentOS] self signing certificates
by Les Bell 25 Aug '09

25 Aug '09

Keith Keller <kkeller(a)speakeasy.net> wrote: >> If you're going to go through that much trouble << Although I didn't quote the entire process here (copyright, time, etc.) it's only one command, the adding of one line to the Apache httpd.conf, (probably) scp'ing the files onto the server and providing a link on a page somewhere. Oh, and reloading Apache. 5 mins, tops. If you're a slow typist. But I must admit, I've not bothered to do it myself. One of these days. . . Best, --- Les Bell [http://www.lesbell.com.au] Tel: +61 2 9451 1144

1 0

Re: [CentOS] self signing certificates
by Les Bell 25 Aug '09

25 Aug '09

Jerry Geis <geisj(a)pagestation.com> wrote: >> Was just trying to find a way so that users that "dont know" what this box is that is poping up wont even see the box. << Can't you install your own root certificate into the internal client browsers? The book "Network Security Hacks" (Andrew Lockhart, O'Reilly) gives a procedure for doing this (p. 112). You generate a .der file from the cacert.pem file, add a new mime type in the Apache config and then make the pem and der files available on your server. The users can now install the new root cert by just clicking on a link. (Sorry if this has already been covered - I wasn't paying attention to the earlier discussion). Best, --- Les Bell [http://www.lesbell.com.au] Tel: +61 2 9451 1144

2 1

logwatch not mailing
by Ray Leventhal 25 Aug '09

25 Aug '09

Hi, # uname -a Linux obfuscated.example.com 2.6.18-128.4.1.el5 #1 SMP Tue Aug 4 20:23:34 EDT 2009 i686 i686 i386 GNU/Linux I noticed a few days ago that I'm not getting my logwatch emails to the root account any longer, and while I've definitely been applying updates from base, no other changes have happened on this box. I ran logwatch at the command line: logwatch --detail medium --mailto root(a)fqdn.example.com but still no email. As expected, /etc/cron.daily has the following entry: lrwxrwxrwx 1 root root 39 Jul 30 2008 0logwatch -> /usr/share/logwatch/scripts/logwatch.pl Where should I start looking to figure out why logwatch seems not to be doing its thing? Thanks in advance, -Ray

7 10

← Newer
1
...
6
7
8
9
10
11
12
...
27
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss August 2009