similar to: Initial 6.0 trees in QA

Jeff Sheltren has been providing timely and clear updates about the status of the 6.3 release: http://qaweb.dev.centos.org/ They're much appreciated! Thank you very, very much. -- Paul Heinlein heinlein at madboa.com 45?38' N, 122?6' W

Posted, in case you haven't seen it already: http://qaweb.dev.centos.org/qa/node/116 Good news.

The QA web site at http://qaweb.dev.centos.org/qa/blog was really helpful for those of us who were curious as to how CentOS 6.0 was coming along. However, there doesn't seem to be much information as to how CentOS 6.1 is going from either the QA web site, the forums (Announcements), or Kananbir's twitter feed -- but it may be I'm just not looking in the right place. Does the QA

Greetings- Is there any updated news on the CentOS6 front? As per qaweb [1], today should be the day of QA signoff and syncing to internal mirrors. Are things still on track? --Tim [1] http://qaweb.dev.centos.org/qa

I just want to say that I really, really, appreciate the information given on this site: http://qaweb.dev.centos.org/qa/calendar -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB at Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax:

For those who don't follow the QA RSS, see: http://qaweb.dev.centos.org/qa/node/120 to get the latest info on the status of 6.2. Looks good so far!

> From: Edward Ned Harvey [mailto:shill at nedharvey.com] > > I have a Dell R710 which has been flaky for some time.? It crashes about once > per week.? I have literally replaced every piece of hardware in it, and > reinstalled Sol 10u9 fresh and clean. It has been over 3 weeks now, with no crashes, and me doing everything I can to get it to crash again. So I''m going to

Hi gang - Just took a look at http://qaweb.dev.centos.org/qa/calendar/ I dont see anything on there for 6.1 Not trying to start flames and I know its ready when its ready and all that - but I was just surprised to see "nothing" on the calendar. jerry

Hi folks: At work, I have an R510, and R610 and an R710 - all with the H700 PERC controller. Based on experiments, it seems like there is no way to bypass the PERC controller - it seems like one can only access the individual disks if they are set up in RAID0 each. This brings me to ask some questions: a. Is it fine (in terms of an intelligent controller coming in the way of ZFS) to have the

The $vmdk value is a directory name in ESX.pm, although the later codes replace '/' with '_', the volume name isn't still friendly, for example, it looks like this: # virsh vol-list pool-dir Name Path ----------------------------------------- esx4.1-rhel6.2-x86_64_esx4.1-rhel6.2-x86_64

I have a Dell R710 which has been flaky for some time. It crashes about once per week. I have literally replaced every piece of hardware in it, and reinstalled Sol 10u9 fresh and clean. I am wondering if other people out there are using Dell hardware, with what degree of success, and in what configuration? The failure seems to be related to the perc 6i. For some period around the time

Does anybody know why this list is private and password protected? It would be nice to see progress, but it appears that part of the development is completely locked down and not open source. -- Steven Crothers steven.crothers at gmail.com

Hello guys, we have done some progress on the new web site project. We need your comments for the design of the front page. We have 3 proposals or the design of the frontpage. Please look at them, we need your help :) http://qaweb.dev.centos.org/websitever2/ Best regards, Marian -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type:

Hi devs, If/when someone has a few minutes, could someone post an update on 6.1 on http://qaweb.dev.centos.org/qa/blog ?. I suspect the devs have been busy with the just-released 5.7 version. :) -- Digimer E-Mail: digimer at alteeve.com Freenode handle: digimer Papers and Projects: http://alteeve.com Node Assassin: http://nodeassassin.org "At what point did we

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

Does anyone know if a PERC H200 is a real RAID controller? I'm about to build a box to CentOS 6.5 (it was Windows...) with RAID 6 on Monday, and this PE R610 has this.... I'm familiar with PERC 6 and 7s, but just dunno 'bout this one. mark

Hi folks, Here's the situation. I have a group of engineers who love to save things to disk. Now that the filer is getting full, they are interested in archiving some of those things to DVD. The tress containing the things they want to archive are specified like so: /path/path/path/A/04?? /path/path/path/B/04?? /path/path/path/A/05?? /path/path/path/B/05?? /path/path/path/A/06??

In IRC today, someone who was hitting that same IB performance ceiling that occasionally gets reported had this to say [11:50] <nissim> first, I ran fedora which is not supported by Mellanox OFED distro [11:50] <nissim> so I moved to CentOS 6.3 [11:51] <nissim> next I removed all distibution related infiniband rpms and build the latest OFED package [11:52] <nissim>

> when I print the tree I get something like this: > 1) root 1130 19580.00 535.6 > 2) V17: 2,3,4,5 853 4833.00 533.7 > 4)V9 < 541.5 185 1011.00 531.9 * > ................................etc > > When I use this tree for prediction : > > >predict.tree(t, data[1,]) > > I get something like this: > > >531.9205 //note the

Package: xen-hypervisor-4.4-amd64 Version: 4.4.1-9 Severity: critical Justification: breaks the whole system Dear Maintainer, After upgrading the R610 server from Debian 7 to Debian 8, the dom0 becomes unresponsive via ssh after an hour or so, although the domUs still remain accessible. Initially we thought it may be a disk space issue on / or /boot so action was taken to increase those