devel December 2010

devel@lists.centos.org

54 participants
25 discussions

Interested in IA64 build.
by James A. Peltier 22 Jan '13

22 Jan '13

I noticed on the SIG that people interested in other ports of interest. I'd like to express interest in the IA64 port. What is the best way to get started? I have two SGI Itanium 2 based machines. One 64 processor x 64GB SGI Altix and a 32 processor x 32GB RAM SGI Prism. They are currently running CentOS 4.8 and I would love to be able to run CentOS 5.5 on them to get them into compliance with the rest of the cluster. -- 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

9 53

are there any chances to see finished CentOS6 in 2011?
by Michał Piotrowski 10 Jan '11

10 Jan '11

Hi, I checked the website http://wiki.centos.org/QaWiki/6/AuditStatus so far only one package was centosified. So I wonder what are the chances of seeing CentOS6 in 2011. Or perhaps a more realistic date is 2012? (Maybe you are waiting for the release of DNF?) -- Best regards, Michal Sent from my fscking awesome Black Hole Generator

36 94

tracking packages in a Release, through the life of the release
by Karanbir Singh 06 Jan '11

06 Jan '11

hi, one thing that I'd like to do with 5.6 and 6.0 is to have centos-release carry repo info for the debuginfo and the vault repo's for the same Release. For 6.0 it would be fairly slim to start with but for 5.6 it could look like this : Enabled by default: [base] [updates] Available, but not enabled: [5.5] [5.5-updates] [5.4] [5.4-updates] .. [5.0] [5.0-updates] Allowing people to get specific packages from anywhere in the Release's past. the baseurl for these will point at vault.centos.org/ Similarly would be the debuginfo .repo's. For /5/ we have a single debuginfo repo, for /6/ we can, and i think we should, split these up into repo's that match the release's. so 6.0's debugs end up in debuginfo.c.o/6.0/ and 6.1 goto d.c.o/6.1/ etc. Just as with the older release's .repo files - these would be present but disabled. Also, I'm trying to plumb in debuginfo signing. But it might end up being a different key to the main distro signing key[1], cross signed by the distro key and master keys. lets see how that pans out. thoughts ? - KB

2 2

CentOS-6 repositories: *-devel, *-debuginfo, contrib-{unstable, testing, stable}
by Brian Schueler 05 Jan '11

05 Jan '11

Hi, As I have seen there is only a subset of development libraries included on the upstream's el6 DVD. While packaging my additional software with mock I needed to put some distro SRPMs into my local SRPMs directory to get the *-devel pkgs. (But it would make no sense when the distro packages are updated.) Will be there all *-devel packages included in the CentOS-6 [base]/[update] repositories and will be there a *-debuginfo repo, too? What about contributer repositories? My idea is to have 3 stages of user contrib repositories (two of them controlled by the CentOS dev team): [contrib-unstable] where everyone may upload software packages via web (requiring only a simple registration), that are not well tested and not targeted to a production system. [contrib-testing] packages that have been selected by the developer team that needs to be tested. [contib] packages that are fully tested and confirmed to be stable and which does not have any side-effects to the CentOS base installation. All these points would make C6 fantastic for everyone (for engineers, developers, administrators, end-users and even artists). Cheers, Brian.

3 2

rhel-6 rebuild summary
by Farkas Levente 04 Jan '11

04 Jan '11

hi, i write this mail after more people ask me in private. and since the centos core devel team not share any info about it's build system, status, there modifications, doesn't have any public revision system and not really accept any help or advice for outside. but i still believe these are useful info for many others so i try to summarize our rhel-6 rebuild experience. first question is the build host and base repo selection. it's advice to choose both the build system and the base repo as close as to rhel-6 as possible. unfortunately even with official rhel-6 isos you can't get the optional packages in binary. so imho the best base system and base repo is a union of rhel-6 rc2 and rhel-6 beta. both are available freely in binary but only the beta include the optional packages in binary from. after you finish you can rebuild packages on itself again. another important note that most update packages (there're a few dozens) have higher buildreq packages then in the base repo, but these buildreqs are not versioned in the specs. so you've to add the updates pacakges to the build system's base packages otherwise you'll get build errors. i recommend mock-1.1.7 for building. unfortunately at rh it's not required to be able to build src.rpm is mock, they use only rpmbuild (!) which of course cause a few dozen of packages won't build:-( imho it'd be useful something like this for rhel too: http://fedoraproject.org/wiki/FTBFS so let we see what's are the problematic packages (fortunately most of the packages build clean). all of these packages bellow has a bugzilla entry and most of them already contains the solutions. so just go and search for it (i'd not like to link all bz entry:-() - virt-top (missing ocaml-camomile-data) - spice-client (missing pixman-devel) these two packages can't be rebuild on rhel-6 since they has such buildreq which is not shipped in rhel-6 (simple rh forget about it:-) so you can either add to the base repo these packages from epel or from a rebuild from fedora or simple drop them. - bash - zsh can't be rebuild in mock-1.x since a mock tty bug. in this case imho the easiest solution: mock <params> --rebuild bash... ctrl-c during build, then mock <params> --shell rpmbuild --rebuild /builddir/build/originals/bash... - nss can't be rebuild in mock since during %check try to connect to the localhost to test ssl, but it's not working in mock. i suggest the above solution plus ctrl-c during the rpmbuild when the build hang at the ssl connection test and after the you'll got a successful build:-) - kernel unfortunately kernel spec is not updated to the new noarch subpackage style. which means you've to build the arch and noarch packages separately (as in rhel-5). but the new spec file even worst then the rhel-5 was so eg: a simple: mock <params> --target "noarch,i686" --rebuild kernel... no longer works, but mock <params> --target "noarch" --rebuild kernel... mock <params> --target "i686" --rebuild kernel... works:-) imho the best would be to update the kernel spec to the new noarch style subpackage, but afais rh so conservative about kernel spec it won't be happened in the rhel-6.x series:-( - opal has a wrong rh patch which cause ekiga not compile, so you've to fix opal first. - java-1.6.0-openjdk-1.6.0.0-1.21.b17.el6 can't be build, unfortunately bz with fixes for this package are not public, but there's an update which can be build (may be we'd have to leave this package out). and the remaining packages has different problems in the spec file, but all has (mostly a simple) solution in bz, but doesn't have update package: - guile - openmpi - foomatic - hivex - mod_auth_kerb - gnome-doc-utils - pilot-link - linuxdoc-tools - perl-Sys-Virt - perl-Test-MockObject - perl-Test-Memory-Cycle - perl-GSSAPI - perl-Makefile-Parser - perl-CGI-Session - perl-IPC-Run3 - python-lxml - python-sqlalchemy - rome - epydoc - kdepim-runtime i hope it can help for a few poeple. anyway happy xmas! -- Levente "Si vis pacem para bellum!"

7 14

Re: [CentOS-devel] Collecting data
by derleader __ 26 Dec '10

26 Dec '10

>I have a hard time trying to figure out why you would want to write a kernel module for all >of this. There are userland tools that can do just about everything you describe. I know that there are many tools. This C program is developed with special task. Can you help me? Regards Peter

3 2

Collecting data
by derleader __ 24 Dec '10

24 Dec '10

Hi, I'm developing C plugin for Centos which will be installed as kernel module. The problem is how to collect the data about: CPU Check – Utilization, Model, Number of Cores RAM Check – Total Memory, Free Memory, Memory Load HDD Check – Number of physical HDDs, Number of logical partitions, Total space, Free space Running processes – Total number of processes Logs – system logs such as error logs System uptime Users logged in and last login – total list of users Total network connections Check hardware parts model and number The kernel module will check the status of the OS every 5 minutes. What is the most efficient way to collect these data? Regards Peter

3 2

fyi, first el6 live .iso's available based on SL6alpha
by Douglas McClendon 18 Dec '10

18 Dec '10

FYI, today both I[1] and Urs Beyerle[2] announced some early releases of x86 Live .iso images based on the SL6 rolling alpha. Urs's is I think their equivalent of what Patrice will be releasing. Mine is an independent platform, primarily highlighting the rebootless installation method. And later, after I've submitted a spec here for your contrib repository, I hope my 'VirOS' toolset will prove to be a useful alternative in at least some use-cases to Fedora's livecd-tools. I'll aim not to spam this list again. If you are interested- http://cloudsession.com/dawg/downloads/xzyx http://cloudsession.com/dawg/projects/viros http://viros.sourceforge.net viros-devel(a)lists.sourceforge.net Happy Holidays, Cheers, -dmc Douglas McClendon [1] http://listserv.fnal.gov/scripts/wa.exe?A2=ind1012&L=scientific-linux-devel… [2] http://listserv.fnal.gov/scripts/wa.exe?A2=ind1012&L=scientific-linux-devel…

1 0

Re: [CentOS-devel] CentOS and rhn tools
by Marcus Moeller 17 Dec '10

17 Dec '10

Dear Baptiste. > I used cobbler to manage my CentOS 5.x repos and kickstarts, but Spacewalk > is now a more mature project and so I start to use it, but as you know it > works with rhn-* tools. > > Do rhn tools becomes available in future versions of CentOS (CentOS 5.6, > CentOS 6...) ? If you Kickstart your systems through Spacewalk (that's what it's meant for) you can associate a Channel containing the Tools to the Kickstart Profile. The packages in there will be available during installation phase (before system registration) as well. So there is not need for having them in CentOS. Kind Regards Marcus

2 1

CentOS and rhn tools
by Baptiste AGASSE 17 Dec '10

17 Dec '10

Hi all, I used cobbler to manage my CentOS 5.x repos and kickstarts, but Spacewalk is now a more mature project and so I start to use it, but as you know it works with rhn-* tools. Do rhn tools becomes available in future versions of CentOS (CentOS 5.6, CentOS 6...) ? Regards. Baptiste.

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel December 2010