cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chiradeep Vittal (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (CLOUDSTACK-158) Establish legal use of patches/systemvm/debian/config/etc/sysctl.conf
Date Fri, 21 Sep 2012 22:10:11 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Chiradeep Vittal closed CLOUDSTACK-158.
---------------------------------------

    Resolution: Fixed
      Assignee: Chiradeep Vittal

The content of this file was developed specifically for CloudStack. The first incarnation
was developed by me while consulting the Linux manuals. Subsequent modifications were made
by me (to customize behavior of ipsec), by Edison (to bump up memory for connection tracking)
and Hugo (to disable ipv6).

commit 55f74e5f7c896a0956779f4168d4c5eb2f8fd1cb
Author: Chiradeep Vittal <chiradeep@apache.org>
Date:   Fri Sep 21 15:07:43 2012 -0700

    CLOUDSTACK-158 sysctl.conf was developed for CloudStack

                
> Establish legal use of patches/systemvm/debian/config/etc/sysctl.conf
> ---------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-158
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-158
>             Project: CloudStack
>          Issue Type: Bug
>    Affects Versions: pre-4.0.0
>            Reporter: Chip Childers
>            Assignee: Chiradeep Vittal
>            Priority: Blocker
>              Labels: licensing
>             Fix For: 4.0.0
>
>
> We need to establish if the following file is one of the following:
> 1) Written specifically for CloudStack
> 2) Taken (and perhaps modified) from a source that has an ASLv2 compatible license
> 3) Taken (and perhaps modified) from a source that does not have a compatible license,
and then figure out what to do about it.
> patches/systemvm/debian/config/etc/sysctl.conf

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message