Hi Joe and CGL workgroup, We already put our registration documents on our public website. The website is http://www.asianux.com/CGL/Asianux4.0_cgl4.0_registration.php. Please check it. Any further requirement, please let us know. Thank you. Best Regards, Lily Software Engineer Test Team Server Development Department Tel: 010-62160610 Fax: 010-62160580 Asianux Corporation Ltd. www.asianux.com ? 2011/3/30 2:18, Joe MacDonald ??: > Hi Lily, > > [Re: CGL V4.0 Registration from Asianux Corp.] On 11.03.29 (Tue 17:27) lily wrote: > >> Hi Joe and CGL workgroup, >> >> Thank you for reviewing our documentation. >> >> We agree to put our registration under the category of "Does Not >> Implement All Mandatory Requirements". And the current company >> graphic is ok for us. >> >> For the disclosure type in our registration documentation, we think >> it is suitable for us. Thank you for your good suggestion. >> >> For the registration page, we will start to prepare it soon, maybe >> it will be finished in the middle of April, we will inform to you >> when finish. > Excellent! Thanks for your participation. Let us know when you've got > your registration documents up on some public website and we'll link to > them for you. > > -Joe MacDonald (on behalf of the CGL Workgroup). > >> Thank you very much! >> >> >> Best Regards, >> Lily >> Software Engineer >> Test Team >> Server Development Department >> Tel: 010-62160610 >> Fax: 010-62160580 >> Asianux Corporation Ltd. >> www.asianux.com >> >> >> ? 2011/3/28 21:20, Joe MacDonald ??: >>> Hi Lily, >>> >>> [CGL V4.0 Registration from Asianux Corp.] On 11.02.22 (Tue 15:44) lily wrote: >>> >>>> Hi CGL workgroup, >>>> >>>> This is lily from Asianux Corporation Ltd. We want to apply for CGL >>>> V4.0 Registration. Attachment are all required information as >>>> defined in the CGL V4.0 Registration Template. Please check them. >>>> Any further requirement, please let us know. >>>> Thank you. >>> Please accept our apologies for the delay in responding to your >>> registration. We have reviewed your documentation and are able to >>> approve your registration under the category of "Does Not Implement All >>> Mandatory Requirements", that is section 1.2 on the Registered >>> Distributions page. If you are satisfied with this, you are responsible >>> for making a copy of your registration forms. Once you have it up and >>> accessible, please provide us a URL where we can access it and we will >>> link to your documentation from the CGL Registered Distributions web >>> page at: >>> >>> http://www.linuxfoundation.org/collaborate/workgroups/cgl/registered-distributions#CGL_version_4.0_registered >>> >>> Currently the graphic we have for your distribution is here: >>> >>> http://www.linuxfoundation.org/images/6/68/Asianux.jpeg >>> >>> If you would like us to use a different graphic for your registration >>> information on the distributions page, please let us know. >>> >>> If you would like to amend your registration in order to be listed in >>> section 1.1, the category of "Implements All Mandatory Requirements", >>> you will need to amend the following sections in your registration >>> documents: >>> >>> AVL.3.2 Forced Un-mount >>> - Most vendors implement this via one of the forced unmount / badfs >>> patches available on the web or in some project pages on kernel.org >>> >>> PRF.1.7 Handling Interrupts As Threads >>> - You indicate you include the RT patches in your kernel, typically >>> this includes Soft IRQ threading, so you may already have this >>> requirement implemented. >>> >>> SFA.2.1 Live Kernel Remote Debugger >>> - This is typically implemented via kgdb. >>> >>> STD.11.1 Diameter Protocol CGL Major Features >>> - The common implementations of this come from either OpenDiameter or >>> FreeDiameter packages, easily found on the web. >>> >>> We have the following suggestions for items you may wish to amend in >>> your registration document prior to posting it, however these changes >>> are purely recommendations and will not influence your registration: >>> >>> You indicate you implement SPM.7.0 with a package called >>> 'axtsn-client-tools' which is categorized as an "open source community >>> package". Is this really an OS community package or a package developed >>> by Asianux? If you have developed it yourself, even if it is open >>> source, you are encouraged to categorize it as "value-added package". >>> >>> The same question and comment applies to SFA.6.0, System Snapshot, >>> implemented via system-config-kdump. >>> >>> -Joe MacDonald (on behalf of the CGL workgroup). >>>