January 2011 - devel - lists.centos.org

anaconda dependency calculation?
by Nicholas Byrne 04 Aug '25

04 Aug '25

Hi all, I'm trying to find a tool that calculates all dependencies for a specific package or group of packages for use with CentOS 5 (beta) with the intention of putting together a custom single CD build of CentOS 5. With CentOS 4 i used a python script that used the hdrlist module to find all dependencies which borrowed code from a number of sources. I've looked at yumdownloader and how it checks dependencies (using the --resolve option) but if i pass it the list of packages defined in say the Base and the Core yum groups which generally form an absolute minimal install i end up with about 200 packages. If i do a custom install (using beta 1 disks) and deselect everything i end up with over 300 packages. So i'm guessing anaconda calculates dependencies in a slightly different way, can anyone point me to files/code where i should be looking to find out? Thanks very much in advance for help Nick 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.

6 11

forums + portal for {lang}.centos.org sites
by Karanbir Singh 16 Aug '24

16 Aug '24

Hi, Earlier in the evening today Ralph, Fabian and I had a chat about the present state of the language subsites. This email sort of summarises the main issue ( s/w ). We seem to have run into a slight technical hitch with punbb/fluxbb. They dont support LDAP as a backend. And we had decided a few months back that all new rollouts must have ldap backend so we can rollin CentOS-DS / openldap based backend. So we need to look at alternatives, and since the primary focus of these international sites is going be forums : Here is a shortlist ( if there is anything else that people are aware of, please add to this list ) - phpBB - SMF - Fudforum - phorum - fluxbb Requirements: - Must be able to scale ( couple of hundred thousand msgs ) - Must be able to handle ldap auth ( if it cant, whats involved in writing the ldap-auth portion ) - Must address the specific requirements raised by the present www.centos.org forum users ( Can you please fill this section in ? ) - Must support all languages we need ( pure utf8 support would be good ) - Secure - Skin'able Nice to have: - Capable of running multiple instances from a single deployment - responsive community :D Things we will need to do: - Decide on what s/w to use. - Give the ArtWork people enough time to get the look & feel sorted. - Migrate newbb forums from www.centos.org to $system ( hey, english is a language too :D ). - Migrate fr.centos.org into the final s/w - setup {de/es/ja/it/pt_br}.centos.org Actions: Ralph and Fabian are going to work on setting up a test ldap server, once that is online we will then start by installing into our test-vm-farm the various s/w to eval them. If anyone would like to help, please feel free to jump right in. I'll setup a wiki page for this issue, which might be a good place to track progress. -- Karanbir Singh : http://www.karan.org/ : 2522219@icq

22 81

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

php53 / bind97
by Karanbir Singh 03 Feb '11

03 Feb '11

hi, php53 and bind97 from the 5.6/ tree are available in the c5-testing repo, so test away. Consider the pkgs as mostly production ready, but features that rely on other new pkgs or updates in 5.6 may not work. If you run into one, let us know either on the list here, or in #centos-devel on irc.freenode.net - KB

4 9

Re: [CentOS-devel] A new look for CentOS (was Re: Italian Translation Team)
by Ralph Angenendt 01 Feb '11

01 Feb '11

On Wed, Jan 26, 2011 at 9:43 PM, Andrea Veri <av(a)gnome.org> wrote: > The point now is: which kind of software should the main website use if > the decision would be to give it a new look. Well, IMHO the best solution > at the moment would be to use drupal, it's easy to use and it has anything > needed to make a website rocking. (I've also been using it for a while and I > can tell drupal is a great CMS software) Not wanting to chase you away, this is probably best discussed on centos-devel. There have been discussions and also a test machine for getting the forums out of the main website (php-bb seemed the way to go for that at the moment), because that has to be done before website redesign. There hasn't been a real discussion or decision on which software the main website should run on. Preferrably something which can be "updated" easily, even more preferrably if it can be done so via package management. > The second point would be to setup a test istance with a CMS software on it > to start working on the new website. (unfortunately i don't have any machine > or host handy to run it) That is where we can step in. At least a vm is possible. But as said, this discussion should happen on the centos-devel mailing list, I'll crosspost this mail there. Regards, Ralph

11 41

A new look for CentOS: Main discussion
by Andrea Veri 30 Jan '11

30 Jan '11

hi, after a talk on #centos-devel with Ralph and Karanbir, we've decided to send out a mail with all the details we might want to discuss on the list. Here are a few points: 1. Who will take the responsibility to coordinate the work and the ipothetic team we could set up to make this possible. I offered to cover that role and I will do my best to have everything working. 2. Karanbir suggested that around 3-4 people should be involved in the project, mostly: 2a. developer / coder on the platform 2b. a sysadmin type person ( James Hogarth (james.hogarth(a)gmail.com) offered to help out with this role) 3c. atleast 1 UI person 4d atleast one design person in the website SIG if you are willing to help out, please state your intentions on this mail! 3. cms software to use, many proposals have been made to the list about which software the new website should use. This is actually up to the official CentOS developers but looks like drupal is the platform that took more +1 to the list since now. (it also has LDAP integration which seemed to be the bottleneck for Ralph in the previous try to renew the website) 4. What the website should contain that it is not on the wiki? We will have to set up a wiki page with all ideas and opinions about this to avoid adding useless content. 5. Having the infrastructure up and running. This is an important point since we can spend words and words on the mailing list or irc but we need to make our ideas effective, otherwise we will get back to the old situation. (i.e stuck after 3 years) 6. I / we think that it is not time to change, I know it will take time, much time and even months but we need to start making this happen. well, that's all. Please contribute to the discussion, any idea or proposal is welcome but please avoid to send out a post commenting which software should be used or not. (this call will be made by official centos developers like Ralph or Karanbir) We need to know if anyone is willing to help and give some time to the project and also we want to hear your ideas about the website content, what do you think it will be useful to have on the website, what's not,what should go to the wiki etc. We need a website that does something and provide useful informations for newcomers and for experienced users, a website which is nice and handy at the same time. Let's make this happen altogether. Andrea

6 9

PATCH Missing ISO 9660 Image
by Vijay N. Majagaonkar 30 Jan '11

30 Jan '11

Hi All, I posted PATCH for missing ISO 9660 image, But not got any response for this patch :( https://www.centos.org/modules/newbb/viewtopic.php?topic_id=29925&forum=37 It will be great help if i get some reply or feedback for this Patch, Thanks for the help V!jay.

2 3

irc meeting today re: 5.6/6.0
by Karanbir Singh 17 Jan '11

17 Jan '11

hi guys, Based on feedback, we seem to have general consensus that getting 5.6/ to mirrors first is the way to go. However, this does not mean that work on 6.0 will stop, we will try and get the isos ready - but we might need to give the mirrors a bit of a break before releasing those as well. I'll get a timeline in place with details after the weekend. thanks everyone for feedback on this issue - KB

15 24

wallpapers
by Kenneth Armstrong 15 Jan '11

15 Jan '11

Will CentOS 6 also have the same wallpaper packages that came with RHEL 6? The reason that I ask is that I love the new wallpapers in RHEL 6, but I'm not sure if they are copyrighted or anything to the point that CentOS can't import them in the build. Thanks, and keep up the good work. I use CentOS alongside RHEL at work, and it is a fantastic project. -Kenny

11 18

Re: [CentOS-devel] 5.6 Tweet
by Phil Schaffner 14 Jan '11

14 Jan '11

http://twitter.com/centos "So: QA 5.6 and 6.0 in parallel or prefer one release over the other. Imho, 5.6 impacts existing installs, should get higher pref. Thoughts ?" Agree. A public announcement of a decision on this, when made, would help head off a lot of user questions. Phil P.S. Apologies to the QA list for the cross-post. On refection I thought a more public forum would be appropriate for this discussion.

15 21

Status update re: 6.0
by Karanbir Singh 13 Jan '11

13 Jan '11

hi guys, I am sure lots of people want to know - so here is a quick status update about 6.0 build. Over the next 2 days, we are going to clear out all patches and ensure all patched packages build and link correctly. That would then complete the package 'tree'. As soon as that is done ( good place to check is look at the AuditStatus page in the wiki, but I am hopeful we can get this done for Monday the 17th close of play ). The only major time consuming process is getting the anaconda patches in, including the language and url remapping stuff; most of the rest should be fairly quick working through if its a few people working on it. The actual distro build process has already been tested, although with a smaller and incomplete tree. With the complete tree in place, we can then get the package policy in place ( as in what rpm makes it to which media disk etc ), and fire up a distro build. What happens at this point is that the QA team get access to the output from the distro-build process; and they need to go through the motions of making sure its-all-good. This is also the stage where the release notes get setup, and the translation teams goto work on their stuff. A thumbs up from the QA team means the content is then passed onto the infra team and we move to release. The 'seed' process takes between 48 hrs to 72 hrs; and we announce release right after that. About 24 hrs after we open the seeding process, we pass around the .torrent files to high capacity seeders ( 100mbps+ available for at-least a week from release date ). so if you can, do join. - KB

2 1

5.6
by Phil Schaffner 13 Jan '11

13 Jan '11

The upstream release is on the street. https://www.redhat.com/archives/rhelv5-announce/2011-January/msg00000.html Phil

1 0

bugs.centos.org mantisBT file upload issue
by Athmane Madjoudj 12 Jan '11

12 Jan '11

Hello all; While working on a bug that require file uploading, I've noticed that we can't upload a 1.1 MB png file nor 1.6 MB xcf.bz2 file but we can see "(Max. size: 5,000k)" in mantisBT upload form. Can anyone confirm this issue ? Thanks in advance; Best regards. -- Athmane Madjoudj

2 2

thanks for the offers to help test the installer
by Karanbir Singh 12 Jan '11

12 Jan '11

hi guys and girls, thanks for the many many offers to test the installer and installable tree's on the machines you already have and in roles that you would expect to use the distro in. However, rather than manual installs - we all gain by being able to automate these runs using kickstarts; so consider writing kickstarts for your tests. There are some examples here : https://nazar.karan.org/cgit/bluecain/tree/ ; clone the git repo with "git clone git://nazar.karan.org/testing/bluecain" Here is what needs doing : - Write a kickstart file that would either install an existing system[1] - Write a bash shell script that can be run on the machine, which would do some tests and exit with '0' if all goes well. - Please name the kickstart file in a way that it ends in .cfg - Please name the test script exactly the same as the kickstart file but ending in .sh Here is what happens: - When the distro tree is in place the kickstart would be used to run through an install. - Once the install is done, the machine or vm will reboot - post reboot, an ssh connection is made to the installed machine or vm, with the test script being ssh'd over. - test script is run, and hopefully exits with 0 Feel free to contribute against centos4 or 5 or 6 (or common ones ) for bare metal installs and Xen installs - we dont have kvm capability in there as yet ( but we should in the next few weeks ). And don't forget to add your name to the Authors file. git submit via git-email to this list would work. Thanks, - KB

3 6

Re: [CentOS-devel] Am I qualified to help?
by Karanbir Singh 10 Jan '11

10 Jan '11

On 01/05/2011 11:52 PM, Hubert Bahr wrote: > I assume you are referring to bugs.centos.org. I have created an > account there and set my preferences to centos 6 and I see 47 entries > with status entries of confirmed, feedback, acknowledge, new, assigned. I assume assigned are indeed that and don't need to be looked at. Thats mostly on target. However, plenty of pkgs which dont have a report against them might also need to be looked at for various reasons - so its worth keeping an eye out for those. What I usually recommend to people is : first consider the package set you are most interested in, either since thats the package set you are going to most use, or thats the target role you are most keen on deploying into ( in many case, both those are prolly the same thing anyway ). Once you have done those, move onto the rest. > guess the most of rest still need patches. I assume these are patches > against the redhat source rpms. How do you want them submitted? I patches should be named centos-<pkgname>-<functionality>.patch and attached as files on the tracker ( there are a few there you can look at already, or look in the c5 tree to see how they were done there ). > also assume severity "block" are first priority. Which end are you Dont mark anything as block - thats something the QA / Automated Testing will throw up ( eg. a missing package in the final tree or invalid binary or unsigned packages etc ). In most cases, you should just report and leave the issue marked as 'new'. If you look at the AuditStatus page, the various status' also have some comments on what they mean or how we use them. > starting from. I assume numerical bug ID# tracker order. In building > from Red Hat sources we also needed to patch several specs plus a couple of source files. This is an interesting conversation in itself - we dont patch spec files for buildtime issues. But if you bring up a few cases, we can talk about those. > Frakus submitted them upstream but they have not > migrated through their process. Do you want those submitted? I think > this is the area I prefer to work. I guess I will start at the high end and work backwards. When in doubt, submit a report :) we need to find more stuff for Fabian, Manuel and Jeff to do anyway! - KB note: moved to a new thread

9 19

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

RHEL and Centos differences
by derleader __ 09 Jan '11

09 Jan '11

Hi, Is there a guide where I can see the exact differences between RHEL and Centos? For example which logos do you change where I can find them. I'm sure that you have list of changes that you make every time in new RHEL version. Regards Peter

2 1

How to help out for Centos 6
by . 07 Jan '11

07 Jan '11

Hello Centos-devel. As an outsider looking in, I have found that it is .. Not simple to find out what needs doing. I _think_ I am on the right track, but would like to be corrected if not. Here is what I have come up with from reading forums/mailing lists/irc. I hope someone can throw the below on the wiki somewhere appropriate once corrected. If I am way off, please let me know I would like to get started. How to help with Centos 6: Currently Centos 6 needs help re-branding RHEL6 as Centos 6. This is relatively easy to do if you know how to build RPMS, and make patch files. Step 1: Go here: http://wiki.centos.org/QaWiki/6/AuditStatus This is a list of what issues still need to be fixed. Step 2: Pick something that looks fun (and perhaps easy), and click the bug id ('bid' column) This will take you to the mantis bug tracker page. Step 3: *Optional* If you are pretty sure you can fix this problem and don't want someone else re-inventing the wheel with you, Signup for a new account with bugs.centos.org , and let people know you are going to work on this. Don't worry about doing this if you are not sure you can do it. If you want to just try, skip this step. Step 4: Find the package name The "Category" of the bug you picked should have a package name in it, this is the package we are going to need to download and fix. If my example category was: '[CentOS-6] xulrunner' then I would be patching the xulrunner package. Step 5: Download the package http://ftp.redhat.com/redhat/linux/enterprise/6Server/en/os/SRPMS/(mypackag… ie: http://ftp.redhat.com/redhat/linux/enterprise/6Server/en/os/SRPMS/xulrunner… Step 6: Fix the package The issues should already be laid out for you in the description of the mantis bug tracker. Modify the files, and rebuild the RPM. Once you think you have fixed everything, create a patch file. Test your patch file on a fresh install. Need icons / images? Find them on a centos 5.x box. Do you have to do this from a RHEL6 beta installation? No you don't _have_ to. We are after the patch, not your RPMS. Step 7: If you haven't created an account at bugs.centos.org, now is the time. Create an account and attach your patch file. Step 8: Give the nearest person a high-five and then go to Step 1.

4 3

Is there a "mock" setup or downloadable list of tweaked packages for testing CentOS 6 builds?
by Nico Kadel-Garcia 07 Jan '11

07 Jan '11

I may be able to pry time free to test CentOS 6 builds. But I don't want to burn useful worktime with building mock files and manually rebuilding all the SRPM's. I've got access to licensed RHEL 6 to use as a build environment, and to do what gcc does: build a "staging" setup, then do a clean rebuild with that staging, then do a final rebuild to make sure material matches and look for discrepancies. Is this already done somewhere I can get a copy, so that I don't have to burn time re-inventing the wheel? I'd particularly like to make sure that a current "mock" is in the "extras" repository, to speed build times. (The current mock in epel-testing is much faster and more efficient than the older mock releases.)

4 6

Re: [CentOS-devel] are there any chances to see finished CentOS6 in 2011?
by William Boyle 06 Jan '11

06 Jan '11

I would be happy to help/test/whatever also. I have an 8 core Intel workstation currently running CentOS 5.5 (w/ Plus kernel). I also have a spare hot-swap system drive to install and test version 6 on, or I can run it in a virtual machine under 5.5. FWIW, Scientific Linux 6 is currently available in beta form. If I can't get CentOS 6 at least in a beta form pdq, then I may be switching to SL instead. Since my wife is a physicist on the computing division staff at FermiLab, at least I know who to gripe at when problems arise! Of course, that doesn't mean she'll listen/respond to them... :-) Bill Boyle Chairman, Chicago-Rockford IEEE Consultant's Network

2 1

Re: [CentOS-devel] are there any chances to see finished CentOS6 in 2011?
by Timo Schoeler 06 Jan '11

06 Jan '11

Hi Bill, thanks a lot for your interest. Unfortunately, I'm not in my office at the moment, answering from my cell phone, so please forgive me top posting. I'll come back to you in about 16 hrs, when I'm back in the office. Including you, we're six guys now. Seems very promising! Best regards, Timo -- Urspr. Mitt. -- Betreff: Re: [CentOS-devel] are there any chances to see finished CentOS6 in 2011? Von: William Boyle <woboyle(a)ieee.org> Datum: 06.01.2011 18:50 I would be happy to help/test/whatever also. I have an 8 core Intel workstation currently running CentOS 5.5 (w/ Plus kernel). I also have a spare hot-swap system drive to install and test version 6 on, or I can run it in a virtual machine under 5.5. FWIW, Scientific Linux 6 is currently available in beta form. If I can't get CentOS 6 at least in a beta form pdq, then I may be switching to SL instead. Since my wife is a physicist on the computing division staff at FermiLab, at least I know who to gripe at when problems arise! Of course, that doesn't mean she'll listen/respond to them... :-) Bill Boyle Chairman, Chicago-Rockford IEEE Consultant's Network _______________________________________________ CentOS-devel mailing list CentOS-devel(a)centos.org http://lists.centos.org/mailman/listinfo/centos-devel

1 0

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

Closing out CentOS 6 Bugs
by JohnS 06 Jan '11

06 Jan '11

Karanbir, Can you look into closing out the bugs that can be closed etc? Can also [1,2] be looked into to confirm package depends on abrt / report (hidden gotchas). Look at the example spec file at the changes that are required and the level of them that the Application Backend will have to support. Is there someone that can take on the App Server end? Also needed to know if you are symlinking from "redhat-release" to "centos-release" or not. That depends on how other packages need to be patched, ie "lsb_release". John [1] http://bugs.centos.org/view.php?id=4648 [2] http://bugs.centos.org/view.php?id=4647

4 6

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

Re: [CentOS-devel] Closing out CentOS 6 Bugs
by JohnS 05 Jan '11

05 Jan '11

On Wed, 2011-01-05 at 12:50 +0000, Karanbir Singh wrote: No problem it was the "CC:" is why. It deleted my dev list copy. Here's again to dev list for KB. If needed I'll do the BR. John > > On 01/05/2011 12:36 PM, JohnS wrote: > > > > On Wed, 2011-01-05 at 11:42 +0000, Karanbir Singh wrote: > >> Hi John, > >> > >> On 01/05/2011 11:40 AM, JohnS wrote: > >>> Karanbir, > >>> > >>> Can you look into closing out the bugs that can be closed etc? > >> > >> Yes, I will try and get to that either today or early in the day tomorrow. > > > > Thanks > > > >>> Can also [1,2] be looked into to confirm package depends on abrt / > >>> report (hidden gotchas). Look at the example spec file at the changes > >>> that are required and the level of them that the Application Backend > >>> will have to support. Is there someone that can take on the App Server > >>> end? > >>> > >>> Also needed to know if you are symlinking from "redhat-release" to > >>> "centos-release" or not. That depends on how other packages need to be > >>> patched, ie "lsb_release". > >> > >> I am keen on looking at using a centos-release with a link over from > >> redhat-release, but lets consider / look at the implications and > >> fallouts before deciding on something for sure. There should not be any > >> reason to patch redhat-lsb; > > > > This here in the spec file needs to be done so it does not imply to the > > user that it is RHEL: > > > > redhat-lsb.spec.orig 2010-01-15 01:57:55.000000000 -0500 > > +++ redhat-lsb.spec 2010-12-02 06:15:17.000000000 -0500 > > @@ -46,7 +46,7 @@ > > %define lsbrelver 4.0 > > %define srcrelease 1 > > > > -Summary: LSB base libraries support for Red Hat Enterprise Linux > > +Summary: LSB base libraries support for CentOS > > > >> whatever we do should not, ideally, have any > >> impact on code and expectations from other apps ( specially since there > >> might be implications to third party apps that we cant / dont want to > >> have a feedback loop into ) > >> > >> What do you see as needing patched into redhat_lsb, that would fallout > > > > Well doing it by using a sym link in /etc nothing needs changing. > > CHECKFIRST="/etc/redhat-release" as so that will catch the link sym > > link so nothing will be changed in it. > > > > If you do the reverse of the above CHECKFIRST="/etc/centos-release" then > > it needs a fix me up. So I say go with the symlink > > > > John > > > > >

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel January 2011