devel October 2009

devel@lists.centos.org

35 participants
18 discussions

CentOS 5.4 Status
by IT2 Stuart Blake Tener, USNR 15 Oct '09

15 Oct '09

Mr. Herrold, Please understand that it is with no pleasure accorded to me that I must go and correct the some several assertions you have proffered within your commentary, as they are most certainly anomalous in nature. I think you might be well served to realize that most people have the expectation that no matter how slowly a project might progress, the status does change from time to time. And in the absence of a weekly or monthly status report on its progression, it is quite reasonable to proffer a request for pronouncement of the project's status. My queries were not specific to the S/390 apportionment of the 5.4 distribution from CentOS, but part of a greater overarching query regarding 5.4 more generally. Indeed, showing interest in the direction a particular distribution is heading, is actually contributing. It might not be writing code, but having the discussion about the needs of the community and the sorts of platforms that said community members might otherwise search for support on, is a contribution of intellectual value in terms distinctly not uncertain. Moreover, your presumption regarding my standing to represent the US Navy specifically concerning any interest in a S/390 distribution is entirely erroneous, but I appreciate you think highly enough of me that the Navy would leave that to me. However, I am sorry that you were so easily confused by the fact that my being a sailor in the Navy meant that I might be representing the Navy needing this distribution, as I do not represent the interests of the Navy regarding my comments. In fact, notwithstanding the fact that I never said the Navy had any desire for a S/390 variant of CentOS, what maybe far more likely is that I have a P/390 and am interested to see it come to fruition for the purposes of my personal mainframe hardware. Lastly, it instructive that many years ago I spent hours on the phones with folks from RedHat, back when they sold more books than Linux CDs, trying report bugs and explain where I thought the code could be improved. However, just to show you my heart is in the right place, once a 5.x variant is at least in beta for the S/390 platform (from CentOS), I shall certainly be happy to contribute by beta testing it and turning in bug reports. I await the project's advancement to said milestone, such that I can begin contributing sir. Now personally, I have my doubts as to a FOSS Fairy, but, just in case, I placed a CD with CentOS 3.9 for S/390 under my pillow! :) I appreciate your taking the time to review my reply comments, and look forward to discussing the needs of the greater CentOS community in more detail with you as the project moves forward. Have a wonderful and blessed day sir. Very Respectfully Submitted, Stuart B. Tener === 'IT2 Stuart Blake Tener, USNR': You have asked this how many times without contributing to advancing such an effort, now? If the Navy wants it, step and fund a run at it. If you do, put your shoulder to the wheel. I described my effort on an IBM provided build instance the last time this question was asked [with published build sources, and result packages], and the time before that as well, and I am sure it is in the archives Stuff is not just magically delivered by the FOSS fairy -- Russ herrold -- Very Respectfully, IT2 Stuart Blake Tener, USNR Las Vegas, NV / Beverly Hills, CA / Philadelphia, PA / Washington, DC Amateur Radio Call Sign: N3GWG (Extra) / Marine Radio Operator Permit (MROP) email: teners(a)bh90210.net (also carbon copies to my Blackberry) phone: +(1) 310.358.0202 (Beverly Hills, CA, forwards to mobile phone) phone: +(1) 215.338.6005 (Philadelphia, PA, voice mail only) E-Fax: +(1) 928.437.4505 (Telecopier, fax to email gateway) Military emails (checked monthly until remote NMCI access is secured) NIPRNET: stuart.tener(a)navy.mil NIPRNET: stuart.b.tener(a)us.army.mil NRO: teners(a)nro.mil TS/SCI: tenerstu(a)nro.ic.gov (GWAN) Confidentiality Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and/or privileged information, though strictly at the UNCLASSIFIED level. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the originate message.

2 1

QA Test Matrix submission: Rescue Mode
by Garry.Dale 15 Oct '09

15 Oct '09

Greetings: After looking over some of the QAWiki pages, I have attempted to create a test case for Rescue Mode [1]. Perhaps this could be included in the test matrix? Thanks. gd [1] http://wiki.centos.org/GarryDale

3 2

Re: [CentOS-devel] CentOS 5.4 Status
by IT2 Stuart Blake Tener, USNR 15 Oct '09

15 Oct '09

Mr. Singh, Well, if I were going to add details as to what I could do to help the build effort, how would I do that intelligently when no one is willing to give a status as to where the build effort is in terms of the project milestones or what resources are currently under demand by the project? I am going to tell you straight away, having read Russ' comments, I am in no way interested to work with him, and it appears he must be one of the development team leaders. During my work day I get paid to deal with unhappy people all day long, I am loath to volunteer to do it for free in my spare time after hours. If you and the development team want to attract more assistance from people, take note that pissing people off when they ask the status of a project is not the manner by which to ascend along that path. In the mean time, I shall await Russ' apology in precedence to making a decision as to what resources (monetary, computer related, or personal time) I have available in pursuance of furthering the effort at hand. If in fact Russ is not really one of the project leaders, and is just a "rouge member", do let me know that too. One last note, I might be the sort of person to go and say these things point blank, as I am a more direct person, but I imagine that there are people perhaps on this list who read Russ' comments and are thinking to themselves, "WOW...pffft...I am just going to stick to reading this list, who would want to work with this guy?...." Have a most wonderful and blessed day. V/R, Stuart Message: 7 Date: Wed, 14 Oct 2009 11:43:14 +0100 From: Karanbir Singh <mail-lists(a)karan.org> Subject: Re: [CentOS-devel] CentOS 5.4 Status To: "The CentOS developers mailing list." <centos-devel(a)centos.org> Message-ID: <4AD5AB42.7080608(a)karan.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed On 10/14/2009 07:10 AM, IT2 Stuart Blake Tener, USNR wrote: > Thank you for your reply, it was the sort of response I was curious to > hear. Just want to point out that I dont entirely disagree with Russ's post, its usually a 'nice' thing to also add details on what you might be able to offer to the build effort :) - KB ------------------------------ -- Very Respectfully, IT2 Stuart Blake Tener, USNR Las Vegas, NV / Beverly Hills, CA / Philadelphia, PA / Washington, DC Amateur Radio Call Sign: N3GWG (Extra) / Marine Radio Operator Permit (MROP) email: teners(a)bh90210.net (also carbon copies to my Blackberry) phone: +(1) 310.358.0202 (Beverly Hills, CA, forwards to mobile phone) phone: +(1) 215.338.6005 (Philadelphia, PA, voice mail only) E-Fax: +(1) 928.437.4505 (Telecopier, fax to email gateway) Military emails (checked monthly until remote NMCI access is secured) NIPRNET: stuart.tener(a)navy.mil NIPRNET: stuart.b.tener(a)us.army.mil NRO: teners(a)nro.mil TS/SCI: tenerstu(a)nro.ic.gov (GWAN) Confidentiality Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and/or privileged information, though strictly at the UNCLASSIFIED level. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the originate message.

3 2

CentOS 5.4 Status
by IT2 Stuart Blake Tener, USNR 14 Oct '09

14 Oct '09

Mr. Singh, Thank you for your reply, it was the sort of response I was curious to hear. Have a wonderful and blessed day. -- Very Respectfully, IT2 Stuart Blake Tener, USNR Las Vegas, NV / Beverly Hills, CA / Philadelphia, PA / Washington, DC Amateur Radio Call Sign: N3GWG (Extra) / Marine Radio Operator Permit (MROP) email: teners(a)bh90210.net (also carbon copies to my Blackberry) phone: +(1) 310.358.0202 (Beverly Hills, CA, forwards to mobile phone) phone: +(1) 215.338.6005 (Philadelphia, PA, voice mail only) E-Fax: +(1) 928.437.4505 (Telecopier, fax to email gateway) Military emails (checked monthly until remote NMCI access is secured) NIPRNET: stuart.tener(a)navy.mil NIPRNET: stuart.b.tener(a)us.army.mil NRO: teners(a)nro.mil TS/SCI: tenerstu(a)nro.ic.gov (GWAN) Confidentiality Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and/or privileged information, though strictly at the UNCLASSIFIED level. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the originate message.

2 1

CentOS 5.4 Status
by IT2 Stuart Blake Tener, USNR 13 Oct '09

13 Oct '09

Dear Sir or Ma'am, Can anyone estimate where in the process we are concerning the eventual distribution of CentOS 5.4? I am also curious if or what the status would be of an S390/S390(x) release of CentOS 5.4 or 5.x would be? Thanks in advance and have a most wonderful and blessed day! -- IT2 Stuart Blake Tener, USNR, N3GWG (Extra), MROP Beverly Hills, CA / Las Vegas, NV / Philadelphia, PA / Washington, DC mobile: (310) 358-0202 Nextel: 124*233172*14 (direct connect) e-mail: teners(a)bh90210.net

3 2

kernel panic in sg_cmd_done
by Erez Zilber 12 Oct '09

12 Oct '09

Hi, I got a kernel panic with CentOS 5.3 (kernel is 2.6.18-128.1.6.el5) in sg_cmd_done. I wasn't able to reproduce this behavior. Here's the output of /var/log/messages. Is this a known bug? Sep 16 14:36:48 172.16.9.60 general protection fault: 0000 [1] Sep 16 14:36:48 172.16.9.60 SMP Sep 16 14:36:48 172.16.9.60 Sep 16 14:36:48 172.16.9.60 last sysfs file: /block/dm-13/dev Sep 16 14:36:48 172.16.9.60 CPU 1 Sep 16 14:36:48 172.16.9.60 Sep 16 14:36:48 172.16.9.60 Modules linked in: Sep 16 14:36:48 172.16.9.60 iscsi_scst(U) Sep 16 14:36:49 172.16.9.60 iscsi_tcp(U) Sep 16 14:36:49 172.16.9.60 libiscsi_tcp(U) Sep 16 14:36:49 172.16.9.60 libiscsi(U) Sep 16 14:36:49 172.16.9.60 scsi_transport_iscsi(U) Sep 16 14:36:49 172.16.9.60 isp_mod(U) Sep 16 14:36:49 172.16.9.60 isp_scst(U) Sep 16 14:36:49 172.16.9.60 scst_user(U) Sep 16 14:36:49 172.16.9.60 scst(U) Sep 16 14:36:49 172.16.9.60 dm_round_robin Sep 16 14:36:49 172.16.9.60 nls_utf8 Sep 16 14:36:49 172.16.9.60 loop Sep 16 14:36:49 172.16.9.60 dm_multipath Sep 16 14:36:49 172.16.9.60 scsi_dh Sep 16 14:36:49 172.16.9.60 ipt_MASQUERADE Sep 16 14:36:50 172.16.9.60 iptable_nat Sep 16 14:36:50 172.16.9.60 ip_nat Sep 16 14:36:50 172.16.9.60 xt_state Sep 16 14:36:50 172.16.9.60 ip_conntrack Sep 16 14:36:53 172.16.9.60 nfnetlink Sep 16 14:36:53 172.16.9.60 ipt_REJECT Sep 16 14:36:53 172.16.9.60 xt_tcpudp Sep 16 14:36:53 172.16.9.60 iptable_filter Sep 16 14:36:53 172.16.9.60 ip_tables Sep 16 14:36:53 172.16.9.60 x_tables Sep 16 14:36:53 172.16.9.60 bridge Sep 16 14:36:53 172.16.9.60 netconsole Sep 16 14:36:53 172.16.9.60 autofs4 Sep 16 14:36:53 172.16.9.60 nfs Sep 16 14:36:53 172.16.9.60 lockd Sep 16 14:36:53 172.16.9.60 fscache Sep 16 14:36:53 172.16.9.60 nfs_acl Sep 16 14:36:53 172.16.9.60 sunrpc Sep 16 14:36:53 172.16.9.60 video Sep 16 14:36:53 172.16.9.60 sbs Sep 16 14:36:53 172.16.9.60 backlight Sep 16 14:36:53 172.16.9.60 i2c_ec Sep 16 14:36:53 172.16.9.60 i2c_core Sep 16 14:36:53 172.16.9.60 button Sep 16 14:36:53 172.16.9.60 battery Sep 16 14:36:53 172.16.9.60 asus_acpi Sep 16 14:36:53 172.16.9.60 acpi_memhotplug Sep 16 14:36:53 172.16.9.60 ac Sep 16 14:36:53 172.16.9.60 ipv6 Sep 16 14:36:53 172.16.9.60 xfrm_nalgo Sep 16 14:36:53 172.16.9.60 crypto_api Sep 16 14:36:53 172.16.9.60 parport_pc Sep 16 14:36:53 172.16.9.60 lp Sep 16 14:36:53 172.16.9.60 parport Sep 16 14:36:53 172.16.9.60 joydev Sep 16 14:36:53 172.16.9.60 bnx2(U) Sep 16 14:36:53 172.16.9.60 bnx2x(U) Sep 16 14:36:53 172.16.9.60 sg Sep 16 14:36:53 172.16.9.60 pcspkr Sep 16 14:36:53 172.16.9.60 dm_raid45 Sep 16 14:36:53 172.16.9.60 dm_message Sep 16 14:36:53 172.16.9.60 dm_region_hash Sep 16 14:36:53 172.16.9.60 dm_mem_cache Sep 16 14:36:53 172.16.9.60 dm_snapshot Sep 16 14:36:53 172.16.9.60 dm_zero Sep 16 14:36:53 172.16.9.60 dm_mirror Sep 16 14:36:53 172.16.9.60 dm_log Sep 16 14:36:53 172.16.9.60 dm_mod Sep 16 14:36:54 172.16.9.60 shpchp Sep 16 14:36:54 172.16.9.60 mptsas Sep 16 14:36:54 172.16.9.60 mptscsih Sep 16 14:36:54 172.16.9.60 mptbase Sep 16 14:36:54 172.16.9.60 scsi_transport_sas Sep 16 14:36:54 172.16.9.60 sd_mod Sep 16 14:36:54 172.16.9.60 scsi_mod Sep 16 14:36:54 172.16.9.60 ext3 Sep 16 14:36:54 172.16.9.60 jbd Sep 16 14:36:54 172.16.9.60 uhci_hcd Sep 16 14:36:54 172.16.9.60 ohci_hcd Sep 16 14:36:54 172.16.9.60 ehci_hcd Sep 16 14:36:54 172.16.9.60 Sep 16 14:36:54 172.16.9.60 Pid: 0, comm: swapper Tainted: G 2.6.18-128.1.6.el5.KM4 #1 Sep 16 14:36:54 172.16.9.60 RIP: 0010:[<ffffffff881b11f0>] Sep 16 14:36:54 172.16.9.60 [<ffffffff881b11f0>] :sg:sg_cmd_done+0x2e/0x24e Sep 16 14:36:54 172.16.9.60 RSP: 0018:ffff8106800a3e20 EFLAGS: 00010006 Sep 16 14:36:54 172.16.9.60 RAX: ffffffff881b11c2 RBX: 0000000000000000 RCX: 0000000000000000 Sep 16 14:36:54 172.16.9.60 RDX: 0000000000000000 RSI: ffff81065ca726e8 RDI: ffffffff881b483b Sep 16 14:36:54 172.16.9.60 RBP: ffff81064fc24070 R08: 00000000000003bf R09: 000000007e8ac500 Sep 16 14:36:54 172.16.9.60 R10: ffffc20010083240 R11: ffffffff8807aa47 R12: ffff810c20957340 Sep 16 14:36:54 172.16.9.60 R13: 2030207772207366 R14: ffff81065ca726e8 R15: 0000000000000000 Sep 16 14:36:54 172.16.9.60 FS: 0000000000000000(0000) GS:ffff81011a125a40(0000) knlGS:0000000000000000 Sep 16 14:36:54 172.16.9.60 CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b Sep 16 14:36:54 172.16.9.60 CR2: 00002b3e2f65f5a8 CR3: 0000000000201000 CR4: 00000000000006e0 Sep 16 14:36:54 172.16.9.60 Process swapper (pid: 0, threadinfo ffff81068009e000, task ffff81011a133080) Sep 16 14:36:54 172.16.9.60 Stack: Sep 16 14:36:54 172.16.9.60 ffff81065ddfe440 Sep 16 14:36:54 172.16.9.60 ffffffff8002c863 Sep 16 14:36:54 172.16.9.60 ffff810c7e8ac500 Sep 16 14:36:54 172.16.9.60 ffff81065ca726d8 Sep 16 14:36:54 172.16.9.60 Sep 16 14:36:54 172.16.9.60 ffff8106595cd708 Sep 16 14:36:54 172.16.9.60 ffff810c20957340 Sep 16 14:36:54 172.16.9.60 0000000000000001 Sep 16 14:36:54 172.16.9.60 0000000000000246 Sep 16 14:36:54 172.16.9.60 Sep 16 14:36:54 172.16.9.60 0000000000000000 Sep 16 14:36:54 172.16.9.60 ffffffff8807aa72 Sep 16 14:36:54 172.16.9.60 0000000000000001 Sep 16 14:36:54 172.16.9.60 ffff8106595cd708 Sep 16 14:36:54 172.16.9.60 Sep 16 14:36:54 172.16.9.60 Call Trace: Sep 16 14:36:54 172.16.9.60 <IRQ> Sep 16 14:36:54 172.16.9.60 [<ffffffff8002c863>] __end_that_request_first+0x265/0x5d1 Sep 16 14:36:54 172.16.9.60 [<ffffffff8807aa72>] :scsi_mod:scsi_end_async+0x2b/0x4c Sep 16 14:36:54 172.16.9.60 [<ffffffff8807a024>] :scsi_mod:scsi_end_request+0xa7/0xcd Sep 16 14:36:54 172.16.9.60 [<ffffffff8807a198>] :scsi_mod:scsi_io_completion+0x14e/0x324 Sep 16 14:36:54 172.16.9.60 [<ffffffff8807a42d>] :scsi_mod:scsi_device_unbusy+0x67/0x81 Sep 16 14:36:54 172.16.9.60 [<ffffffff8003747d>] blk_done_softirq+0x5f/0x6d Sep 16 14:36:54 172.16.9.60 [<ffffffff80011e94>] __do_softirq+0x89/0x133 Sep 16 14:36:54 172.16.9.60 [<ffffffff8005e2fc>] call_softirq+0x1c/0x28 Sep 16 14:36:54 172.16.9.60 [<ffffffff8006cad9>] do_softirq+0x2c/0x85 Sep 16 14:36:54 172.16.9.60 [<ffffffff8006c961>] do_IRQ+0xec/0xf5 Sep 16 14:36:54 172.16.9.60 [<ffffffff8018f862>] acpi_processor_idle+0x0/0x43a Sep 16 14:36:54 172.16.9.60 [<ffffffff8005d615>] ret_from_intr+0x0/0xa Sep 16 14:36:54 172.16.9.60 <EOI> Sep 16 14:36:54 172.16.9.60 [<ffffffff8018f7f3>] acpi_safe_halt+0x25/0x36 Sep 16 14:36:55 172.16.9.60 [<ffffffff8018f9e9>] acpi_processor_idle+0x187/0x43a Sep 16 14:36:55 172.16.9.60 [<ffffffff8018f862>] acpi_processor_idle+0x0/0x43a Sep 16 14:36:55 172.16.9.60 [<ffffffff8018f862>] acpi_processor_idle+0x0/0x43a Sep 16 14:36:55 172.16.9.60 [<ffffffff80048a6d>] cpu_idle+0x95/0xb8 Sep 16 14:36:55 172.16.9.60 [<ffffffff80076c1f>] start_secondary+0x45a/0x469 Sep 16 14:36:55 172.16.9.60 Sep 16 14:36:55 172.16.9.60 Sep 16 14:36:55 172.16.9.60 Code: Sep 16 14:36:55 172.16.9.60 4d Sep 16 14:36:55 172.16.9.60 8b Sep 16 14:36:55 172.16.9.60 65 Sep 16 14:36:55 172.16.9.60 08 Sep 16 14:36:55 172.16.9.60 4d Sep 16 14:36:55 172.16.9.60 85 Sep 16 14:36:55 172.16.9.60 e4 Sep 16 14:36:55 172.16.9.60 74 Sep 16 14:36:55 172.16.9.60 09 Sep 16 14:36:55 172.16.9.60 41 Sep 16 14:36:55 172.16.9.60 8a Sep 16 14:36:55 172.16.9.60 44 Sep 16 14:36:55 172.16.9.60 24 Sep 16 14:36:55 172.16.9.60 30 Sep 16 14:36:55 172.16.9.60 84 Sep 16 14:36:55 172.16.9.60 c0 Sep 16 14:36:55 172.16.9.60 74 Sep 16 14:36:55 172.16.9.60 13 Sep 16 14:36:55 172.16.9.60 48 Sep 16 14:36:55 172.16.9.60 c7 Sep 16 14:36:55 172.16.9.60 Sep 16 14:36:55 172.16.9.60 RIP Sep 16 14:36:55 172.16.9.60 [<ffffffff881b11f0>] :sg:sg_cmd_done+0x2e/0x24e Sep 16 14:36:55 172.16.9.60 RSP <ffff8106800a3e20> Sep 16 14:36:55 172.16.9.60 Sep 16 14:36:55 172.16.9.60 Kernel panic - not syncing: Fatal exception Sep 16 14:36:55 172.16.9.60

2 2

ipv6 in mirrorlist
by Karanbir Singh 04 Oct '09

04 Oct '09

hi, So, running a natively ipv6 machine on CentOS comes with the problem that there are no published ipv6 mirrors in our mirrorlist's - we know about a few ipv6 mirrors, and it should be possible to extend our testing stuff to cover them. Whats the best way to handle this situation ? Am I the only one running native ipv6 at the moment.... is there someway we can gauge what the use-case-density for AAAA mirrorlist.centos.org is at the moment ? should we do the dns record, vhost a static list if we must, of a few ipv6's and see what the hit-rate is ? - KB

4 3

Re: [CentOS-devel] Red Hat IPA
by Sean Brady 04 Oct '09

04 Oct '09

I know that this was discussed back in May, but I am unclear on the status of IPA on CentOS. Any word on this, or has this indeed been dropped due to lack of interest? "little interest to keep it going in its present form either upstream or downstream" Does this mean that Redhat is backing off of the product as well, or am I reading this wrong? Thanks, Sean

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel October 2009