devel

devel@lists.centos.org

17 participants
4602 discussions

openssh security update
by Akemi Yagi 08 May '07

08 May '07

CentOS developers, Could someone take a look at this? It was posted on the CentOS Forum by bdaniels. Apparently this security update came out on May 1, but not all versions have been made available for CentOS. Akemi === Forum posting by bdaniels === Well, the announce list has been posting them: [CentOS-announce] CESA-2007:0257 Low CentOS 4 s390(x) openssh - security update 05/04/2007 06:44 PM CentOS Errata and Security Advisory 2007:0257 https://rhn.redhat.com/errata/RHSA-2007-0257.html But only for the s390 and ia64 architectures. The i386/ia32 ones are missing.

3 4

Re: [CentOS-devel] Re: Third repos CentOS 5 compatibility
by Durval Menezes 08 May '07

08 May '07

Folks, For what's worth, IMO there is at least one thing we at Centos-devel could learn from EPEL: they have very clear rules about how to get contributed packages into their repo: http://fedoraproject.org/wiki/EPEL/FAQ#head-24b4e4b98953a6d3de80019e85e8311… I for one have some packages (http://www.durval.com.br/RPMS/el4/) I've been trying to contribute to CentOS for many months now, without success: I've posted messages trying to submit the packages, talked to some developers, even started a page on the CentOS Wiki about it, but in the end it came to naught (I privately received information from one developer explaining why there are no clear rules, but I was asked to keep it confidential and so I can't post it here). This is very frustrating, and I think it keeps many people from contributing to CentOS. Best Regards, -- Durval Menezes (durval AT tmp DOT com DOT br, http://www.tmp.com.br/)

6 6

Third repos CentOS 5 compatibility
by Jordi Espasa Clofent 07 May '07

07 May '07

Hi all, I've always used kb, dries and dag's repos in CentOS 4.x. Now I'm testing CentOS 5.x (congratulation for your great work!) and I wonder if the three popular repos called above are available/compatible for CentOS 5. I've considered to approach this question to repos mantainers directly, but I know they read and contribute the present list in active way. -- Thanks, Jordi Espasa Clofent

7 11

anaconda dispatch.py
by Nicholas Byrne 05 May '07

05 May '07

re CentOS 5 release I'm doing a kickstart, in the post section i mount and access the CDROM. This works with most CDROM's with motorised drives however on drives that have an eject only type mechanism (i.e. laptop/1u server cdroms) i cannot do this as the eject is happening before the %post section. With the fully motorised drives the mount attempt retracts the CDROM draw so it works. I tracked this down to Anaconda's dispatch.py ordering, it has: ("methodcomplete", doMethodComplete, ), ("dopostaction", doPostAction, ), which in my opinion is wrong, (methodcomplete does the eject). It should be the other way around i.e. ("dopostaction", doPostAction, ), ("methodcomplete", doMethodComplete, ), Has this been done on purpose, i would think a lot of people access the CDROM in post scripts... or is this just a bug imported from the upstream vendors version? My colleague has opened a bug on this with rh - https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=239002 , should we open one on the CentOS tracker as well? Thanks and regards Nick PS as always apologies for the corporate footer that i cant get rid of. This e-mail is the property of Quadriga Worldwide Ltd, intended for the addressee only and confidential. Any dissemination, copying or distribution of this message or any attachments is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and deleting it from your computer. Messages sent to and from Quadriga may be monitored. Quadriga cannot guarantee any message delivery method is secure or error-free. Information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. We do not accept responsibility for any errors or omissions in this message and/or attachment that arise as a result of transmission. You should carry out your own virus checks before opening any attachment. Any views or opinions presented are solely those of the author and do not necessarily represent those of Quadriga.

2 1

reposync for CentOS 4
by Daniel de Kok 05 May '07

05 May '07

Hi all, I have attached a backport of reposync from yum-utils CVS to yum 2.4 in CentOS 4. There may still be a bug luring here or there, but it would be nice to hear if it works for others. Thanks, Daniel

9 27

Newbie Questions: Goal to make a customized minimal CentOS install CD
by EXT-Rodgers, Marianne 04 May '07

04 May '07

I have some basic questions, easy to most of you, I am sure. I have looked on the CentOS main site at the install manual, but am not finding my answers. Am I at the right place? I already know how to make install DVDs and CDs. I just need to know if there is things for the CentOS director, comps.xml updates, things like this for my customized DVD. I want to delete packages on my install DVD until I only have the rpms left that I want to use. Current questions: 1. Just how are the hdr (header) files used, and how do you update them? 2. How do I update the comps.xml file, and is this necessary ? 3. Why isn't /var/log/rpmpkgs on my prototype, which rpm or command makes it work? 4. Which files will update automatically when rpms are removed, and can I safely just remove RPMs from the CerntOS/RPM directory? I apologize in advance if this is not the right forum to ask these questions. I would be happy if directed to a proper site to find my answers. I have already googled, with little results. Marianne Rodgers PCS (Portable Computer System Group) Operating System Analyst United Space Alliance marianne.rodgers(a)boeing.com 281-244-4200 The comments & Opinions expressed are my own & do not represent the views of United Space Alliance

7 7

Need help testing new mysql pkgs on c4 x86_64 -- Centosplus
by Devin Henderson 04 May '07

04 May '07

Hey guys. Evolution built some new mysql packages for c4-centosplus because I was seeing a bug. He has verified that the new packages fix the bug on i386 but I'm still seeing the bug on x86_64. I need some people who can test these packages in a c4 x86_64 environment to verify that the bug still exists. Just install mysql and mysql-server from here: http://dev.centos.org/centos/4/testing/x86_64/RPMS/ And then run the command 'mysql -u root -p < create.mysql.sql' using the create.mysql.sql file attached to the bug: http://bugs.centos.org/view.php?id=1975 If you get " ERROR 2013 (HY000) at line 61: Lost connection to MySQL server during query " and 'mysqladmin -u root -p version' shows that mysql has crashed and been restarted then the bug still exists. Thanks! Let me know what you find out. Cheers, Devin

1 0

[PATCH] Fix xen bridge creation in multi-homed hosts
by Mike Fedyk 02 May '07

02 May '07

If a centos5 xen dom0 has one ip address, the default route line from "ip route list" has 5 fields. If the dom0 has more than one ip address, the default route line adds two more fields specifying the source ip address used for that route. This patch makes sure bridges are created properly in both cases. Mike Fedyk

3 4

Updated packages for kmod-gfs-xen
by carlopmart 02 May '07

02 May '07

Hi all, Where are kmod-gfs-xen updated package for kernel 2.6.18-8.1.1 and kernel 2.6.18-8.1.3?? ftp redhat site has published src packages ... Thanks. -- CL Martinez carlopmart {at} gmail {d0t} com

2 1

More XFS Filesystem Tips
by Joshua Kramer 01 May '07

01 May '07

Hello All, This was posted to the Postgres Admin list - it has some valuable tips wrt XFS usage. I haven't had time yet to see if the C5 kernel conforms to what Hannes is talking about, but it looks like XFS is *very* picky about having hardware working correctly (and raid arrays set up correctly). Cheers, -J ---------- Forwarded message ---------- Date: Tue, 01 May 2007 16:35:28 +0200 From: Hannes Dorbath <light(a)theendofthetunnel.de> To: Adam Witney <awitney(a)sgul.ac.uk>, pgsql-admin(a)postgresql.org Subject: Re: [ADMIN] File systems linux !!! Adam Witney wrote: > Could you give a couple of examples of things that could be done wrong? I > have XFS running for my data partition, but I didn't really do much when I > set it up... > > Thanks for any advice 1.) Don't run XFS on any hardware that's not proven to be 100% fsync/fua safe. It's extremely unforgiving in that regard. Double check your raid controller settings and then test with something like http://www.faemalia.net/mysqlUtils/diskTest.pl 2.) Don't run it with a 4K stacks kernel. Though most issues with 4k stacks have been fixed long ago, there is an 4k stack fix in 2.6.21 release notes yet again. I just wouldn't trust it 100% yet. Especially avoid to run with 4k stacks in production if you are used to stack block devices on top of each other (LVM, EVMS, DRBD, GNBD etc). 3.) Use the deadline I/O scheduler, anticipatory and XFS don't like each other. This is true for almost any FS != ext3. This makes a difference especially for OLTP. 4.) Don't use stripe alignment unless you are 100% sure on how to calculate that numbers for your raid setup. No stripe alignment is always better than a wrong alignment. Some controllers don't like it at all and degrade in performance. 5.) Make sure to use write barriers unless you run on a hardware controller with BBU. Actually this is XFS default these days, but it gets disabled if you have any block device in your stack that doesn't support it. An example is DRBD (though write barriers are on the road map) 6.) Flushing data is the sole responsibility of the application. XFS does nothing to help broken applications, like ext3 can do with data=ordered or data=journal. XFS uses writeback exclusively. Don't run anything that does not conform to ACID on XFS. This is fine for PostgreSQL, but might not be fine for all your applications. 7.) Check dmesg for XFS messages and be able to interpret them. Especially something about "CORRUPTED_GOTO". If you see such a line chances are high that 1.) is not true. This is a cry from XFS to run xfs_repair ASAP, the file system was only mounted to keep your box online and will shutdown immediately if any suspicious position is accessed. Take XFS messages serious and Google for them if your are not sure what they mean. 8.) Grab all those nice PDFs at http://oss.sgi.com/projects/xfs/training/index.html These are essential readings for any XFS admin. IMHO XFS is a mature and rock stable file system, however your really need to obey the things above. It's just not the general-purpose-mkfs-and-forget-FS like what ext3 is claimed to be. What I recommend for a PostgreSQL production box is to use ext3 data=journal for / and XFS for $PGDATA. This should give you a system which really behaves nice on power failures. ext3 data=journal for all non ACID applications, XFS for ACID applications. Personally I use XFS on / as well, but I have taken some steps to make it behave like I wish. -- Best regards, Hannes Dorbath ---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend

3 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel