devel

devel@lists.centos.org

1 participants
4619 discussions

Debuginfo packages not signed
by Phil Schaffner 15 Jun '10

15 Jun '10

Just noticed that (at least some - e.g. CentOS-5 kernel-debuginfo, kernel-debuginfo-common, aspell-debuginfo) debuginfo packages are not signed. Started to file a bug entry, but don't know if it is merited. Is the intent to have these packages signed? The Debuginfo Wiki page shows "gpgcheck=1". http://wiki.centos.org/AdditionalResources/Repositories/DebugInfo Phil

3 3

LiveCD suggestion
by Phil Schaffner 07 Jun '10

07 Jun '10

For the next iteration of the LiveCD I would suggest omitting the netinstall option. This has caused a rather large support load on the fora (or forums if you prefer) from people who can't get it to work. As netinstall is really most useful with a "perfect" network connection or local archive, and can be tricky to get right, it is just confusing a lot of the LiveCD "market segment". More sophisticated users will just grab the netinstall CD or use images/boot.iso. Removing it would also leave more room for useful apps. Phil

9 18

Forum overhaul
by Monte Milanuk 01 Jun '10

01 Jun '10

Hello all, As an end user, I would like to know if there is any forward progress on doing something about the CentOS forums? This apparently has came up time and again, with various examples being given of the deficiencies of the existing setup (depending on your point of view). As near as I can tell the general consensus seems to be 'yes, something needs to be done'... and thats about as far as it gets. I realize everybody has lots on their plate, but this has been languishing for a year or more, with no apparent changes being made. For a self-proclaimed 'enterprise' OS, the associated support forum doesn't make much of a first impression. http://www.centos.org/modules/newbb/viewtopic.php?topic_id=14921&forum=18 http://lists.centos.org/pipermail/centos-devel/2008-September/003366.html https://www.centos.org/modules/newbb/viewtopic.php?topic_id=23201&start=0#f… http://lists.centos.org/pipermail/centos-devel/2009-December/005252.html What needs done? What needs decided? Whose backside needs a fire lit under it? What can *I* do? Monte

4 7

Awaiting C-5 Updates.
by Alan Bartlett 29 May '10

29 May '10

Hi KB, Some users are getting restless [1]. Would you like / do you have the time to post to that thread, please? If negative, may I have a comment from you that I can post on your behalf. Thanks, Alan. [1] http://www.centos.org/modules/newbb/viewtopic.php?topic_id=26452&forum=37

9 15

disk i/o stalls with mptsas since upgrade to centos 5.4
by Lennert Buytenhek 27 May '10

27 May '10

Hi! On two different machines, I've been experiencing disk I/O stalls after upgrading to the CentOS 5.4 kernel. Both machines have an LSI 1068E MPT SAS (mptsas) controller connected to a Chenbro CK13601 36-port SAS expander, with one machine having 16 1T WD disks hooked up to it, and the other having a mix of about 20 WD/Seagate/Samsung/Hitachi 1T and 2T disks. When there's a disk I/O stall, all reads and writes to any disk behind the SAS controller/expander just hang for a while (typically for almost exactly eight seconds), so not just the I/O to one particular disk or a subset of the disks. The disks on other (on-board SATA) controllers still pass I/O requests when the SAS I/O stalls. I hacked up the attached (dirty) perl script to demonstrate this effect -- it will read /proc/diskstats in a tight loop, and keep track of which request entered the request queue when, and when it completed, and it will WTF if a request took more than a second. (The same thing can probably be done with blktrace, but I was lazy.) New requests get submitted, but the pending ones fail to complete for a while, and then they all complete at once. This happens on kernel-2.6.18-164.11.1.el5, while reverting to the latest CentOS 5.3 kernel (kernel-2.6.18-128.7.1.el5) makes the issue go away again, i.e. no more stalls. It doesn't seem to matter whether the I/O load is high or not -- the stalls happen even under almost no load at all. Before I dig into this further, has anyone experienced anything similar? A quick google search didn't come up with much. thanks, Lennert #!/usr/bin/perl -w use Time::HiRes qw(clock_gettime CLOCK_MONOTONIC); sub read_stats { local *STATS; my %stats; %stats = (); open STATS, "< /proc/diskstats"; while (<STATS>) { my @fields; chomp; @fields = split; if ($fields[2] =~ /^sd[a-z]$/) { my $head = $fields[3] + $fields[7]; my $tail = $head + $fields[11]; $stats{$fields[2]} = [ $head, $tail ]; } } close STATS; return \%stats; } my %heads; my %queues; %heads = (); %queues = (); while (1) { my $now; my %stats; my $disk; $now = clock_gettime(CLOCK_MONOTONIC); %stats = %{read_stats()}; foreach $disk (sort keys %stats) { my $head; my $tail; next if ($disk eq "sda"); $head = $stats{$disk}->[0]; $tail = $stats{$disk}->[1]; if (not defined $heads{$disk}) { print "new disk $disk\n"; $heads{$disk} = $head; $queues{$disk} = []; } while ($heads{$disk} + scalar(@{$queues{$disk}}) < $tail) { push @{$queues{$disk}}, $now; print "$now: $disk add -> " . scalar(@{$queues{$disk}}) . "\n"; } while ($heads{$disk} < $head) { my $s; $heads{$disk}++; $s = int(1000 * ($now - (shift @{$queues{$disk}}))); if ($s > 1000) { print "WTF on " . localtime(time()) . " for $s ms\n"; } print "$now: $disk remove after $s ms -> " . scalar(@{$queues{$disk}}) . "\n"; } } }

4 6

CentOS 5 PowerPC port?
by Greg Snyder 26 May '10

26 May '10

Hi all, I'm trying to get a CentOS 5 port started for PowerPC. I saw there was some email back in February about this, but did not know what progress had been made. Does anyone have any news? I'm most interested in 32-bit, with the hope of eventually running it on some Apple (G4 and G5) desktops, as well as on some embedded PowerPC boards (mostly amcc 460ex based). So I'd be hoping to build with some pretty generic target options so the RPMs would be useful in the most places. Are there tools, scripts or techniques used to do the x86 RPMs build that could be leveraged? I looked around on the CentOS website and wiki, but could not find docs or sources for this. Any pointers on this, or just generally how the x86 build/build server is bootstrapped, and the x86 RPMs are produced, would be greatly appreciated. Given my previous somewhat painful experience with autoconf-related cross-build issues, my first thought was to build the bulk of the RPMs natively on PowerPC, rather than x86 to PowerPC cross-build. I have a few PowerPC boxes (currently running Fedora 12), including a quad core 2.5GHz G5, that I'd be happy to share with others interested in getting a CentOS PowerPC port done. I'd be grateful for any tips, help or direction. Thanks, Greg

6 11

builder running notification code fragment
by R P Herrold 26 May '10

26 May '10

Let me surface a conversation happening elsewhere here, for people interested in building a distibution I've mentioned my toy s390x builder privately to a few people, and have some external private testers; additionally I think I mentioned it on the Marist Linux/IBM list and perhaps here publicly. Someone noticed because I picked up a 'follower' on my twitter progress tool On Wed, 26 May 2010, R P Herrold wrote: > On Wed, 26 May 2010, xxx wrote: > >> On 05/26/2010 03:53 PM, R P Herrold wrote: >>> As to other builders, indeed, I got an email that an >>> unknown person's west coast build bot just started >>> following my toy build builder [for s390x] bot >>> http://twitter.com/buildmonbot >>> http://twitter.com/mrgbuildstatus >> damn, now I *gota* get me one of those! >> >> Sounds like a project for the evening! > more like 5 minutes to get started ... > > I've been tinkering with the 'self-hosting' convergence > progress indicator -- just added a feature for the next > restart of it > > [herrold@ibm bin]$ grep tty *sh > remote-build-try.sh: [ "x${NOTWEET}" != "xy" ] && > echo "disk use at ${DISK} ... bailing" | ttytter -script > remote-build-try.sh: ttytter -script > remote-build-try.sh:[ "x${NOTWEET}" != "xy" ] && echo "new > pass: $LNS candidates " | ttytter -script > remote-build-try.sh: [ "x${NOTWEET}" != "xy" ] && > echo "built $BASN (${COUNTER} of ${LNS}) " | ttytter -script > > ==================== > > [herrold@ibm bin]$ head /usr/local/bin/ttytter > #!/usr/bin/perl -s > ######################################################################### > # > # TTYtter v1.0 (c)2007-2010 cameron kaiser (and contributors). > # all rights reserved. > # http://www.floodgap.com/software/ttytter/ > # > # distributed under the floodgap free software license > # http://www.floodgap.com/software/ffsl/ > # -- Russ herrold

1 0

Re: [CentOS-devel] Interested in IA64 build
by James A. Peltier 22 May '10

22 May '10

----- "Karanbir Singh" <mail-lists(a)karan.org> wrote: <snip> | yes, I dont think we will have nearly as much traffic on these arch's | to | merit putting them on the main mirror system. I'd be willing to host the side arches as a mirror. I'm already hosting Ubuntu, a soon to be full CentOS mirror and a soon to be Fedora Enchilada mirror | > Probably the CentOS infrastructure team need to discuss this | > as to where reference 'side architecture' CentOS builds will | > 'live', outside the general mirroring | | good point, I've added it to the list of things. | | > Once I have a bootstrap into CentOS 5, and then 6 as time | > indicates, it may well be possible to 'wire' a ground up | > rebuild on the current CentOS builder and testing process, and | > any future builds into that current process | | Sounds good! There is some work that Ray has been doing as well, and I | | think we should have install media for centos-5 out from there in the | | next few days. Let me collect packages and put them on dev.c.o. But | you | raise an interesting point w.r.t 5 and 6 - at this stage, is it worth | | considering 6 to be a more productive target than 5 for arch's that | will | be supported through to 6 ( ie, not ia64 ) ? You are correct. IMHO perhaps we should target the upcoming 6 packages. When 6 is released we plan to go to it ASAP. I'm already certifying the RHEL 6 platform for our environment using the RHEL 6 Beta software. | > The unit also 'tweets' its progress at | > http://twitter.com/buildmonbot | | nice! Very cool indeed. :) -- James A. Peltier Systems Analyst (FASNet), VIVARIUM Technical Director Simon Fraser University - Burnaby Campus Phone : 778-782-6573 Fax : 778-782-3045 E-Mail : jpeltier(a)sfu.ca Website : http://www.fas.sfu.ca | http://vivarium.cs.sfu.ca MSN : subatomic_spam(a)hotmail.com Does your OS has a man 8 lart? http://www.xinu.nl/unix/humour/asr-manpages/lart.html

1 0

anybody seen ggc compat issues after yum upgrade to 5.5? M_widen_init()?
by Shlomi Hazan 20 May '10

20 May '10

Hi, Sorry is not the place for the question, but I thought you guys should know: I have a 2 new link error after upgrading compiling an application that was not changed: undefined reference to `std::basic_ostream<char, std::char_traits<char> >& std::__ostream_insert<char, std::char_traits<char> >(std::basic_ostream<char, std::char_traits<char> >&, char const*, int)(a)GLIBCXX_3.4.9' undefined reference to `std::ctype<char>::_M_widen_init() const(a)GLIBCXX_3.4.11' <const(a)GLIBCXX_3.4.11%27> collect2: ld returned 1 exit status bummer anyone?

1 0

Why are Spacewalk packages removed from CentOS?
by Luc de Louw 18 May '10

18 May '10

Dear all, After filing a bug (http://bugs.centos.org/view.php?id=4315) Karan made me aware of a discussion held in January 2010. There was no conclusion, no decision. The origin was from Miroslav he was requesting to include rhnlib and friends as I made is on the bug report, and I totally agree with him. Let me pick up the pros and cons discussed in January: Quoting Miroslav @ http://lists.centos.org/pipermail/centos-devel/2010-January/005319.html <quote> Partialy true. Recent upstream version will not hit accidentaly rhn.redhat.com That version included in RHEL will do that by default. But these change: https://fedorahosted.org/spacewalk/changeset/cd925d940357d145c7106c1c3ed6ed… is only one which are required to prevent from accidental check of rhn.redhat.com So my recomendation is: take this patch and apply it on current rhel5 package and include all of them in CentOS. </quote> As I stated, I agree with Miroslav, the only thing we need to care is not to bother people with "click-trough-installations" with "install-numbers" and stuff (This is in anaconda, right?) Lets have a look at http://lists.centos.org/pipermail/centos-devel/2010-January/005321.html Quoting Marcus: <quote> Spacewalk development is much faster which may lead into missing features as they are not yet implemented in the version that is meant to be used with rhn. </quote> From my point of view this does not matter that much.I was able to register a RHEL 5.4 to a spacewalk server (0.8? Dont remember, it was just for the sake, not for production). Since spacewalk is the upstream of the RHN satellite, Red Hat will be careful to break API compatibility between rhn-client and RHN Satellite/Spacewalk. Recently I replaced a RHN Sat 5.0 with 5.3. (AFAIR the base of 5.3 was spacewalk 0.5). The only thing that changed from the client side was the activation key. There also have been a change for RHEL5.5 and sat 5.3 (too lazy to search for the errata). The yum errata was published weeks before RHEL5.5 hits the street. @Miroslav and the other RHN Sat/Spacewalk developers: Can you promise to announce incompatible changes early enough? If yes, CentOS can include the stuff immediately. Quoting Karan @ http://lists.centos.org/pipermail/centos-devel/2010-January/005361.html <quote> A very large number of pople who use centos, do so with little or no previous understand of linux or even the basics of systems management - we need to keep those people in mind as well. The problem that we have had, in the past, is that installing yum-rhn-plugin brought in loads of rhn\* packages as well, which in turn would cause traffic to rhn.r.c. Also, given that rhn itself is a rhel connected service, the view we took was that there is no need for that functionality in the distro at all. </quote> This is partially true. Another fact about CentOS is IMHO, that a lot of people and companies are using CentOS as a testbed for RHEL. I guess that even more users of spacewalk are using it a a replacement for a RHN sat, since RH does only provide 30 days test licences for RHN sat. Companies have (more or less) large test-environments with CentOS. For those companies it would be a great benefit to have those packages in stock CentOS. Benefits for my self: My daily work is with RHEL and RHN Satellite. In meanwhile I have quite a good to excellent knowledge of RHN sat and its future (I'm a git reader). This is mainly due to the existence of spacewalk. At the moment implementing a complete testbed consisting of CentOS AND spacewalk means quite a lot of work, due to to missing rhnlibs and friends in CentOS. Conclusion: With a very small patch as Miroslav suggested to avoid bothering rhn.redhat.com we can have a OS with is attracting to more people. If I can help maintaining the stuff, let me know, I'll do my best.... Thanks, Luc

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