devel

devel@lists.centos.org

17 participants
4602 discussions

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

Why does CentOS 5 claim to be i386 compatible when it's really not?
by Martin Jungowski 15 Dec '10

15 Dec '10

Hi everybody, I've tried to install CentOS 5.5 i386 on an AMD Geode LX 800 processor. That processor, being of the much more recent i586 family, is fully i386- compatible. However, my attempt was brutally shattered when I had to discover that CentOS takes a rather open and surprising attempt at defining x86 compatibility: while claiming to be i386-compatible CentOS 5 requires an i686 processor and does not support the fully i386 but not the least i686 compatible i586 architecture. This is more of a general issue. i386 does not generally refer to "whatever x86-compatible processor is the most recent" but a very well defined and standardized architecture. Specifically, i386 refers to Intels 80386 processor and its 32-bit x86 architecture (which is why x86 are i386 are often used interchangeably when x86 should instead be referring to the 8086 architecture). Code that claims to be i386 compatible has to run on any given microprocessor that claims to be i386 compatible. It's as simple as that: if it doesn't run on i386 processors then it's not i386 compatible. That's industry standard and thus universally valid. If one would claim i386 compatibility but require a x86_64 compatible processor, which of course would be capable of executing standard i386 code, it'd be the exact same issue. It'd be more radical but at its core not different from CentOS's unmet claim of i386 copmpatibility. I guess my question is thus quite simple: why does CentOS 5 claim to be i386 when it's not even remotely i386 compatible? And shouldn't the name reflect code and/or processor family compatibility and affiliation? And in a closely related question of more personal interest: what exactly is it that makes CentOS require an i686 processor? Thanks, Martin -- Rieke Computersysteme GmbH Hellerholz 5 D-82061 Neuried Email: martin[at]rhm[dot]de

9 13

please submit all work-in-progress status's
by Karanbir Singh 10 Dec '10

10 Dec '10

hi guys aiming to wrap the first tree build today, so if you have any work in progress, please get it into the issue tracker before midnight UTC Thur 9th Dec. This isnt the end of all efforts, its just a milestone, so if you are doing stuff please keep on doing the 'stuff'. - KB

6 8

MacBook Air 3.1
by Marcus Moeller 10 Dec '10

10 Dec '10

http://dentifrice.poivron.org/laptops/macbookair3,1/ -- Greets Marcus

1 1

build errors with some RHEL6 packages
by Sergio Rubio 10 Dec '10

10 Dec '10

Good morning everyone, I'm having some problems rebuilding some RHEL6 packages from: http://ftp.redhat.com/pub/redhat/linux/enterprise/6/en/source/SRPMS/ in particular, mock building python-2.6.5 results in: Checking for unpackaged file(s): /usr/lib/rpm/check-files /builddir/build/BUILDROOT/python-2.6.5-3.el6.x86_64 error: Installed (but unpackaged) file(s) found: /usr/lib/debug/usr/lib64/libpython2.6.so.1.0.debug-gdb.py /usr/lib/debug/usr/lib64/libpython2.6.so.1.0.debug-gdb.pyc /usr/lib/debug/usr/lib64/libpython2.6.so.1.0.debug-gdb.pyo RPM build errors: Installed (but unpackaged) file(s) found: /usr/lib/debug/usr/lib64/libpython2.6.so.1.0.debug-gdb.py /usr/lib/debug/usr/lib64/libpython2.6.so.1.0.debug-gdb.pyc /usr/lib/debug/usr/lib64/libpython2.6.so.1.0.debug-gdb.pyo Child returncode was: 1 My build-env is a RedHat Workstation 6, beta2 release, mock 1.1.5-1. I'm looking for suggestions here, as this is my first foray into building recently released upstream RHEL packages: 1. Looks like a bug in the source RPM, but I might be wrong. If so, is it Ok to report it to bugzilla.redhat.com? 2. Something weird in my env being it beta2? My mock profile config attached. Thanks.

12 23

CentOS 5 or 6
by Filip Bartmann 09 Dec '10

09 Dec '10

I need to start my server in Janurary 2011, so I need to know when it's planned to release CentOS 6 to make decisiion if I use current CentOS 5 or CentOS 6 on this server. Plan you release CentOS 6 to January 2011? Thank's for your response Filip Bartmann

4 3

Rebranding Help
by James Stull 09 Dec '10

09 Dec '10

Greetings, a couple weeks ago I sent an email to Ralph and he pointed me to the dev list. Long story short, I would like to help with the Centos 6 release any way I can and was told that you are currently working on rebranding. And that this is the process I needed to follow: http://wiki.centos.org/QaWiki/6/Round1 I've been reading through the wiki on how to get started but honestly I don't know where to start and I'm asking for some direction. Is their a dev repo where I can download the current version of "Centos 6" or do I simply download RHEL 6 and look through the bug list and try to find more packages/man pages/etc that need to be rebranded?? Some direction would be great. If I can help out in any way please let me know. If their are any documents/processes I need to review please let me know. I don't have any programming experience but I can do some minor scripting. I'm familiar with Red Hat/Fedora/Centos and currently Admin a handful of boxes. Thanks for the help and direction. --James

2 4

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