devel February 2011

devel@lists.centos.org

65 participants
20 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

Website Version 2, next steps
by Ralph Angenendt 21 Mar '11

21 Mar '11

First thing: I am sorry that this mail comes this late, it should have been there a week earlier. Second: At Fosdem we sat together with a round of people, trying to identify which parts CentOS has that are facing to the community, which parts need renewing and which contents should go / has to go where. We identified 5 parts, some of which can and will stay as they are (mostly), some which need to change. And we discussed some architectural things. What we did not discuss was which software should be used where, although for many pieces this already has been chosen. At the end of the mail I will talk about some pros and cons to this approach. - Bug reporting against the CentOS components We will continue to use mantis as our bug tracker, so there will be no change in software there, maybe an update to the newest version, if that can be done without too many issues. - Wiki The wiki will find it's role as being about the distribution side of things (read on for an explanation). All documentation about the project which is generated by the project and community members will go on the wiki. This means FAQs, all help material for users, Howtos and Tipps, but also QA content (see the QaTeam section) and the main Release Notes and translations. MoinMoin will be used there for the time coming. Planning of events where CentOS will be shown will still happen on the wiki. - Website The website will be about the project side of things. Firstly it should be a starting point for all users - a role which it does not really play at the moment. Where to download the distribution, what is current, where to get help if you need it, pointers to things people can help with - all that should be easily found on the website. Also on the website will be generated content for CentOS. This means the hosting of upstream documentation, automated content via RSS (so planet.centos.org shouldn't be it's own page anymore, those Feeds should be on the website), Twitter feeds and so on. No decision on whose feeds should be found on there have been made yet. If you are looking for events, where you can talk to people who are around CentOS should also be found on the website. Mirrors, mirror status and general infrastructure content will also be on the website. Downloads for projects within CentOS should also be found here (like Artwork, special CD isos, or whatever you can think of a project within the CentOS eco system) Aim is to have something which can be automatically filled in parts, and be easy to access and update in the other parts. The website is for finished things. - Forums Forums at the moment are an integral part of the website. They will need to move, as we sure are moving away from the current content management system. We already know how to migrate those forums into php-bb, so we will go with that. - Projects People wanting to run projects or Special Interest Groups (SIGs) within CentOS need a place to develop. We have projects.centos.org for that, which has it's own wiki, bug tracker and version control system for those projects. Once things are in a releasable state, those releases should go to a part of the main web site. projects.centos.org is for developing things. - Glue At the moment we have different user databases for everything except website and forums. This has to change. As far as we've found out, every piece of software we use at the moment can be coaxed to authenticate against an LDAP database. We want to order those accounts by email (make that the primary key, as it has to be unique) and try to merge them into one large database. Logging in will still be done on username / password or on the wiki with WikiName / password, where your WikiName will be one of the attributes your account has in the LDAP backend. This has some issues: We will invariably have lots of doubled accounts, as people might have subscribed to the website with a different mail address than to the wiki. We will need to weed out spammer acocunts, something which probably will not be easy. This is something which will still need discussion on how to do it, and especially on how to do the transition correctly, so that it does not have a large impact on users. - Mailing lists Last issue, as there won't be any changes there. Pros and Cons: - Pros Clear division of which content will go where. This also means that a clearer presentation of content can be done on all parts, not the muddle we have there at the moment. One user database allows all users to access parts of the CentOS infrastructure with only one account, although representations of those accounts may differ among applications, like the wiki, where the FirstnameLastname account naming still is wanted. This doesn't mean that you can automatically write on the wiki once you have an account, the procedure will mostly stay as it is at the moment. With one user database, only one place is needed to distinguish users from bots: The place where you register your account. Another plus: the schema is extendable, should the need arise. - Cons Some software might need to be convinced to play well with LDAP authentication. Links between forum posts might go away, I am not sure if there is a possibility to find out the new target of a link. As already mentioned above: Merging the user accounts will probably be a rather largish task: Find out which accounts haven't been used for a certain time, weed out spammer's accounts out of those which have been actively used, find out which accounts belong together, retaining editing rights on the wiki, maybe moving the forum status (rookie, newbie, pro and whatever they are called) to the new forums. We don't have a central account management solution at the moment, this also needs to be written or snarfed from somewhere, and then adapted to our needs. Conclusion: With the content division in mind, there now is a clearer view of what needs to go where. With a central user database, we make many things easier for users and for the people maintaining the different parts of "the CentOS web". Now please discuss if you can live with what is written above, if you see things differently, if you have other ideas and so on. Please try to not extend what is above too much, as that already looks like a rather largish move. Ah yes, we'd like to stay with the layout we have on wiki.centos.org throughout the whole eco system if possible. No idea if it is needed on bugs.centos.org or lists.centos.org, though. For actual execution we will use Atrium for planning, more on how to set up your account there will come after this discussion. Thanks for reading this far (and please trim your mails when replying only to parts of this mail!). Ralph

15 44

CentOS-4.9 SRPMS
by Johnny Hughes 07 Mar '11

07 Mar '11

It seems Red Hat is not releasing media for the 4.9 release, so this seems to be just a bunch of updates that is going into the tree. Based on the SRPMS listed here: ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4AS/en/os/SRPMS/ And the current CentOS 4.8+updates SRPMS here: http://mirror.centos.org/centos-4/4.8/os/SRPMS/ http://mirror.centos.org/centos-4/4.8/updates/SRPMS/ This is the list of SRPMS I have started building: autofs-4.1.3-240.src.rpm autofs5-5.0.1-0.rc2.114.src.rpm bash-3.0-27.el4.src.rpm bind-9.2.4-37.el4.src.rpm centos-release-4-9.src.rpm comps-4AS-0.20110202.src.rpm coreutils-5.2.1-37.el4.src.rpm device-mapper-1.02.28-3.el4.src.rpm device-mapper-multipath-0.4.5-42.el4.src.rpm glibc-2.3.4-2.54.src.rpm gnome-volume-manager-1.1.0-9.src.rpm hal-0.4.2-9.el4_8.src.rpm httpd-2.0.52-47.ent.centos4.src.rpm hwdata-0.146.33.EL-19.src.rpm iscsi-initiator-utils-4.0.3.0-10.src.rpm kernel-2.6.9-100.EL.src.rpm kernel-utils-2.4-23.el4.src.rpm lvm2-2.02.42-9.el4.src.rpm net-snmp-5.1.2-20.el4.src.rpm nfs-utils-1.0.6-94.EL4.src.rpm nss_ldap-253-16.el4.src.rpm numactl-0.6.4-1.44.src.rpm procps-3.2.3-8.21.src.rpm python-2.3.4-14.9.el4.src.rpm quota-3.12-9.el4.src.rpm redhat-release-4AS-10.src.rpm rhnlib-2.1.4-17.el4_8.1.src.rpm rhpl-0.148.6-2.src.rpm rpmdb-redhat-4-0.20110202.src.rpm samba-3.0.33-0.29.el4.src.rpm sendmail-8.13.1-6.el4.src.rpm sysklogd-1.4.1-30.el4.src.rpm sysstat-5.0.5-27.el4.src.rpm system-config-lvm-1.1.4-4.el4.src.rpm system-config-network-1.3.22.0.EL.4.6-4.el4.src.rpm systemtap-1.3-5.el4.src.rpm tmpwatch-2.9.1-1.el4.2.src.rpm udev-039-10.30.el4.src.rpm up2date-4.9.1-29.el4.centos.src.rpm util-linux-2.12a-28.el4.src.rpm xorg-x11-6.8.2-1.EL.66.src.rpm If there is more than one SRPM of the same package, I only took the latest SRPM. Can I get a couple of you guys to verify my SRPM list? Note: The Red Hat FTP site is all updates since the release of RHEL 4.0. The CentOS 4.8 SRPMS are the ones on the 4.8 ISOs and the updates are those SRPMS updated since the release of 4.8. We are only interested in the newest SRPMS for each app. Thanks, Johnny Hughes

16 57

Re: [CentOS-devel] progress?
by William L. Sebok 25 Feb '11

25 Feb '11

Any updates on progress, either on 5.6 or 6.0? Bill Sebok Computer Software Manager, Univ. of Maryland, Astronomy Internet: wls(a)astro.umd.edu URL: http://furo.astro.umd.edu/

44 254

[jrd@gerdesas.com: Re: progress?]
by John R. Dennison 23 Feb '11

23 Feb '11

Mr. Stevens, I feel I owe you, and the list membership, a public retraction and apology for this message. It was uncalled for, and went far beyond even my normal abrasive self. Please accept my sincere apologies for my tone and insinuations; I assure you it will not happen again. John R. Dennison Principle Gerdesas Systems ----- Forwarded message from "John R. Dennison" <jrd(a)gerdesas.com> ----- > Date: Tue, 22 Feb 2011 20:17:29 -0600 > From: "John R. Dennison" <jrd(a)gerdesas.com> > To: "Morten P.D. Stevens" <mstevens(a)imt-systems.com> > Cc: "The CentOS developers mailing list." <centos-devel(a)centos.org> > Subject: Re: [CentOS-devel] progress? > > On Wed, Feb 23, 2011 at 02:56:12AM +0100, Morten P.D. Stevens wrote: > > > Just take the missing build dependencies from Fedora 12/13. Red Hat > > has probably done the same. > > "Just", "probably". Do these types of guessing games work out > well for you in your professional life? > > > What are you waiting for @ CentOS team??? Until Red Hat released the > > missing build dependencies? > > Do you wake up in the morning thinking of how you can be the > most selfish, arrogant and entitled jerk possible or is it > something that comes to you on the spur of the moment? > > > Then you can probably wait a long time. > > It's a shame that releases can't be done in a fully selective > manner; if so I would plead with and bribe, if necessary, the > CentOS developers to release to everyone *except* you. > > Here's a thought for you: > > How about you no longer comment in a project DEVELOPMENT channel > on those subjects you aren't technically proficient enough to > understand? Even better, how about you just go away? Go use > another distro or attempt to build your own or buy Redhat or > whatever you choose to do; it's quite apparent you aren't happy > here and you likely won't ever be so go try something else. ----- End forwarded message ----- -- "My other computer is your windows box." -- Ralf Hildebrandt

1 0

Motion to moderate this mailing list.
by Antaryami Khuda 23 Feb '11

23 Feb '11

To all, I would like to file a motion to get admins of this list to set the list to moderated until the centos prjoect releases something tangible to appease the trolls. What do you say karambir? Put ralph in change of post moderation? Jonnhy is obviously busy making packages. Have you others to help? I'm not aware. Your Welcome: Ant.

5 5

netlink_kernel_create() always returns NULL
by YANG 22 Feb '11

22 Feb '11

My code fragment is below: "*nl_sk = netlink_kernel_create(16, 0, nl_data_ready, THIS_MODULE);"* It can be "make" and "insmod" correctly. But error mesage is printed into log. It indicates the netlink_kernel_create() returns NULL. Once I change the firt parameter to another(<32 && >16), system crash when I execute insmod. Is the protocol ID occupied? Why can't use another and how to define a new ID? I have tried to update net_link.h but fail also.

2 1

Re: [CentOS-devel] Website Version 2, next steps
by Karanbir Singh 22 Feb '11

22 Feb '11

On 02/22/2011 09:03 AM, Didi wrote: >> I agree with this. the level of complexity introduced by trying to >> wrangle an existing solution into working for the various properties / >> resources we have might be a lot higher than just doing something simple >> from scratch. > > I started looking at the solutions. The two mentioned have a lot of > features and we have a relatively simple problem. Just to remove any ambiguity : are you saying that the mentioned solutions would work for our given definition of the 'problem'; or that they are too cumbersome and perhaps an overkill for our simple requirements. - KB

1 0

Re: [CentOS-devel] Watch One, Do One, Teach One (the simple teaching method used in medical schools)
by Antaryami Khuda 22 Feb '11

22 Feb '11

> While it is understood that it is not the responsibility of the CentOS > Team to teach the community, nevertheless, it would be helpful if the > CentOS Team (or others in the know) could list a handful of packages > that are among the 600 Johnny reports as requiring attention in C6, > preferably some that won't even compile, others that require > comparison with the upstream binaries to note the problem. Dearest Larry, I AM SO FUCKING SICK AND TIRED OF YOUR ENDLESS DRIVEL PASSING THROUGH MY INBOX, I may give up on this distro based on you and you ALONE. PS: Shouldn't you be busy running your business rather than running your fingers on a mailing list? PS #2: Looking at your business website, it appears your "store" is low on product. Perhaps you should concentrate on things that matter? Graciously: Ant.

3 2

Watch One, Do One, Teach One (the simple teaching method used in medical schools)
by Larry Vaden 21 Feb '11

21 Feb '11

While it is understood that it is not the responsibility of the CentOS Team to teach the community, nevertheless, it would be helpful if the CentOS Team (or others in the know) could list a handful of packages that are among the 600 Johnny reports as requiring attention in C6, preferably some that won't even compile, others that require comparison with the upstream binaries to note the problem. N.B.: . for C 3, 4 and 5, to date, we've watched nearly 4,000 (albeit it was hard to see anything other than the outcome, which was GREAT) . many of us are ready and would like to do one, so please tell us which packages in the corpus will result in a failure in a stock/vanilla build environment. . perhaps somewhere between C6 and C7 some will pass muster. THANKS for your consideration of the use of this widely used method of teaching MDs, DVMs, DDSs, et al. kind regards/ldv/vaden(a)texoma.net

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel February 2011