taskSavannah Administration - Tasks: task #10458, Submission of Katana

 
 

task #10458: Submission of Katana

Submitter:  James M.H. Oakley <electron>
Submitted:  Wed 16 Jun 2010 05:35:52 AM UTC
   
 
Should Start On:  Wed 16 Jun 2010 12:00:00 AM UTC Should be Finished on:  Sat 26 Jun 2010 12:00:00 AM UTC
Category:  Project Approval Priority:  * 5 - Normal
Status:  Done Privacy:  Public
Assigned to:  marioxcc Open/Closed:  Closed
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Wed 23 Jun 2010 03:39:08 AM UTC, comment #14: 

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

June 22th 2010 in GNU Savannah task #10467: "Submission of Katana"

Deprecated by task #10467.

Item status changes:

Status -> Done
Open/Cloesd -> Closed
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEAREIAAYFAkwhghgACgkQZ4DA0TLic4gFDwCeOx86n4BTByvely1Qzj0AR1B6
w6QAn3Giy5AJrbEd7f2+/Jb8GZqPKljm
=iJke
-----END PGP SIGNATURE-----

Mario Castelán Castro <marioxcc>
Mon 21 Jun 2010 04:55:17 PM UTC, comment #13: 

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

June 21th 2010 in GNU Savannah #task #10458: "Submission of Katana".

>When preparing the project for submission in the first place, I
>attempted to do this. Are you stating this merely as a general notice
>or because you observed files which needed these lines and did not
>have them?


They have a notice like:

  Copyright (C): 2010 Dartmouth College
  License: GNU General Public License

But this statement is very weak.  It don't ever state which GNU GPL
version the project is using, lacks the no warranty statement, the
URL of the license, and so.  Also some files lack a copying notice at
all (For example, those in code_tests).  The suggested way is
https://savannah.gnu.org/task/?10458#comment8.  Please change your
files according to that advice and resubmit the project (You can leave
the description text fied void if you wish).

Regards.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEAREIAAYFAkwfmcUACgkQZ4DA0TLic4gWKACgjQ7qCr04QRtWLq5sh1ZoATcY
hC4AniJOVWfW7lKvZnuV8EHGndXDWUHH
=Ig6j
-----END PGP SIGNATURE-----

Mario Castelán Castro <marioxcc>
Mon 21 Jun 2010 05:13:59 AM UTC, comment #12: 

I will fix the noted areas and resubmit

>> In order to release Katana project properly and unambiguously
>> under the GNU GPL, please place copyright notices and
>> permission-to-copy statements at the beginning of every
>> copyrightable file, usually any file more than 10 lines long.


When preparing the project for submission in the first place, I attempted to do this. Are you stating this merely as a general notice or because you observed files which needed these lines and did not have them?

>> Would you mind changing references to Linux as an OS to GNU/Linux?


Certainly, I'll do that

>> Please include the appropiate licensing & copyright
>> information in the katana documentation. You may use any
>> FDL-compatible license for manuals.


Right, sorry about that, I will add a notice licensing them under FDL

James M.H. Oakley <electron>
Sun 20 Jun 2010 04:46:22 PM UTC, comment #11: 

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

June 20th 2010 in GNU Savannah task #10458: "Submission of Katana".

I don't see the need to keep the task open.  When the need changes are
done James can resubmit the project, opening a new one.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEAREIAAYFAkweRicACgkQZ4DA0TLic4hewwCfTrde6Ei1UIVR1dBL7KBEZJhV
HmoAnjnKzzamDrPUWIqCGVnQBpDN+oYc
=BT9+
-----END PGP SIGNATURE-----

Mario Castelán Castro <marioxcc>
Sun 20 Jun 2010 04:32:12 PM UTC, comment #10: 

With your permission, I reopened the task so that we don't forget about it.

Alex Fernandez <alexfernandez>
Sun 20 Jun 2010 03:51:35 PM UTC, comment #9: 

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

June 20th 2010 in GNU Savannah task #10458: "Submission of Katana".

I forget to say: Please include the appropiate licensing & copyright
information in the katana documentation.  You may use any
FDL-compatible license for manuals.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEAREIAAYFAkweOWQACgkQZ4DA0TLic4jJIwCePXXgq2Nby4cYXnKBCGMoIHfe
GngAn2A2rS+HOpfNdUvW9PZ+GtQZWWHI
=1Hm4
-----END PGP SIGNATURE-----

Mario Castelán Castro <marioxcc>
Sun 20 Jun 2010 03:48:16 PM UTC, comment #8: 

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

June 20th 2010 in GNU Savannah task #10458: "Submission of Katana".

Hi all.

Please excuse for the mistrake James.  Let's continue with the
registration process:

======================================================================

In order to release Katana project properly and unambiguously under
the GNU GPL, please place copyright notices and permission-to-copy
statements at the beginning of every copyrightable file, usually any
file more than 10 lines long.

In addition, if you haven't already, please include a copy of the
plain text version of the GPL, available from
http://www.gnu.org/licenses/gpl.txt, into a file named "COPYING".

For more information, see http://www.gnu.org/licenses/gpl-howto.html.

If some of your files cannot carry such notices (e.g. binary files),
then you can add a README file in the same directory containing the
copyright and license notices. Check
http://www.gnu.org/prep/maintain/html_node/Copyright-Notices.html for
further information.

The GPL FAQ explains why these procedures must be followed.  To learn
why a copy of the GPL must be included with every copy of the code,
for example, see
http://www.gnu.org/licenses/gpl-faq.html#WhyMustIInclude.

======================================================================

The katana documetnation says "Tested on any operating system besides
Linux". "Linux" is just a kernel of a more complex system that we like
to refer to as GNU/Linux, to emphasize the ideals of the Free Software
movement.

Would you mind changing references to Linux as an OS to GNU/Linux?

For more information, see http://www.gnu.org/gnu/linux-and-gnu.html.

======================================================================

Please fix these problems and resubmit the project with an updated
tarball.

Regards and thanks for your understanding.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEAREIAAYFAkweOJEACgkQZ4DA0TLic4jyWQCdExhSDmPnSX1Q8sMzPNSTBCNZ
kgcAnR3QkIxIzTb0fhgF0TmxuITRoeNy
=1OWv
-----END PGP SIGNATURE-----

Mario Castelán Castro <marioxcc>
Sun 20 Jun 2010 05:31:21 AM UTC, comment #7: 

If everyone is in agreement, then by all means let us move forward.

cheers

James M.H. Oakley <electron>
Sat 19 Jun 2010 09:23:25 PM UTC, comment #6: 


> I don't think this is an equivalent to the advertising clause


Yeah, you're right, I was wrong.  Brett just explained this to me.  (However, what the modified BSD license says is considerably more liberal ("and/or other ..."), so it's not the best analogy.)

Therefore, James ... if you still want to host the package there, we could proceed.  Sorry for our perplexity.


Karl Berry <karl>
Site Administrator
Sat 19 Jun 2010 09:35:12 AM UTC, comment #5: 

I don't think this is an equivalent to the advertising clause per-se: requirements to include text (notably the license itself) in related documentation can be found in various licenses including the modified BSD.
I wonder if doing just that (copying to the documentation the full license, which includes the mandatory "This product includes software developed by Dartmouth College" text) would just comply with the license.

Sylvain Beucler <Beuc>
Fri 18 Jun 2010 11:49:47 PM UTC, comment #4: 

Nicodemo, the problem is the text quoted below:

Any redistribution must include the
acknowledgment, “This product includes software developed by Dartmouth
College,” in any related documentation ...

That is equivalent to the "advertising clause" in the original BSD license (http://www.xfree86.org/3.3.6/COPYRIGHT2.html#6) and hence is incompatible with the GPL.

If Dartmouth requires it, it precludes hosting on savannah.  Very unfortunate all round.  If it's really optional, then of course that's fine.



Karl Berry <karl>
Site Administrator
Fri 18 Jun 2010 11:38:31 PM UTC, comment #3: 

Mario, according to the link you passed there is nothing wrong with what James is using as his license. The article recommends that the 3rd clause of the original BSD license not be used. It is talking about the requirement that the authors name must be included in the advertising. This is definitely not the problem in Dartmouth's case.

-Deleted Account- <nicalvaro>
Fri 18 Jun 2010 01:25:16 AM UTC, comment #2: 

For my own part I would be just as happy to remove the attribution requirement, however unfortunately Dartmouth College requires it, so I'm afraid I must seek hosting elsewhere. Thank you for your time

James M.H. Oakley <electron>
Thu 17 Jun 2010 03:33:35 PM UTC, comment #1: 

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi James.

Please note we don't allow the original BSD attribution requirement,
because it turn the license into GPL-incompatible, and because it's
unpractical: http://www.gnu.org/philosophy/bsd.html.  GNU Savannah
only host free, GPL-compatible software
(https://savannah.gnu.org/register/requirements.php).

Free feel to resubmit the project if you want to follow a
GPL-compatible license without aditional restrictions.

Regards.

Item status changes:

Assigned to -> mariosxcc
Status -> Cancelled
Open/Cloesd -> Closed
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEAREIAAYFAkwaQKUACgkQZ4DA0TLic4ga8wCaAiTSzSpKz62UMkUAWfKf/xlh
Gk8An3mkiMRoNI24kep2zbqm8z+tzYE5
=F0r5
-----END PGP SIGNATURE-----

Mario Castelán Castro <marioxcc>
Wed 16 Jun 2010 05:35:52 AM UTC, original submission:  

A new project has been registered at Savannah
This project account will remain inactive until a site admin approves or discards the registration.


Registration Administration


While this item will be useful to track the registration process, approving or discarding the registration must be done using the specific Group Administration page, accessible only to site administrators, effectively logged as site administrators (superuser):



Registration Details


  • Name: Katana
  • System Name:  katana
  • Type: non-GNU software & documentation
  • License: GNU General Public License v2 or later (Any redistribution must include copyright notice attribution to

Dartmouth College as well as the Warranty Disclaimer below, as well as
this list of conditions in any related documentation and, if feasible,
on the redistributed software; Any redistribution must include the
acknowledgment, “This product includes software developed by Dartmouth
College,” in any related documentation and, if feasible, in the
redistributed software; and The names “Dartmouth” and “Dartmouth
College” may not be used to endorse or promote products derived from
this software. 

                         WARRANTY DISCLAIMER
PLEASE BE ADVISED THAT THERE IS NO WARRANTY PROVIDED WITH THIS SOFTWARE, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING, DARTMOUTH COLLEGE, ANY OTHER COPYRIGHT HOLDERS, AND/OR OTHER PARTIES PROVIDING OR DISTRIBUTING THE SOFTWARE, DO SO ON AN "AS IS" BASIS, WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE SOFTWARE FALLS UPON THE USER OF THE SOFTWARE. SHOULD THE SOFTWARE PROVE DEFECTIVE, YOU (AS THE USER OR REDISTRIBUTOR) ASSUME ALL COSTS OF ALL NECESSARY SERVICING, REPAIR OR CORRECTIONS.

IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL DARTMOUTH COLLEGE OR ANY OTHER COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE SOFTWARE AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE SOFTWARE (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. )




Description:

   Katana is a hot-patcher (a system for applying a patch to a process
   while it is running) with a general method similar to the
   successful KSplice project
   (http://www.ksplice.com/doc/ksplice.pdf). Unlike KSplice, Katana
   operates on userland processes rather than on the kernel. Katana,
   unlike any other known system, utilizes binary debugging
   information (DWARF) to allow patching of variables as well as
   functions with minimal user interaction. We attempt to provide a
   patching method that is as transparent as possible and paves the
   way for integrating hot-patching with the standard toolchain.

   More information on the details of Katana can be found in the paper
   at http://www.cs.dartmouth.edu/~sws/pubs/rbls10.pdf.

   Katana is not currently mature. It is in proof-of-concept stage and
   passes seven tests, but it is not yet ready to patch production
   software.



Other Software Required:

 Libelf     LGPL http://www.mr511.de/software/english.html
 Libdwarf   LGPL http://reality.sgiweb.org/davea/dwarf.html
 Libunwind  X11  http://www.nongnu.org/libunwind


Tarball URL:

http://quark.kiewit.dartmouth.edu/~james/katana-0.1.0b.tar.gz


James M.H. Oakley <electron>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by alexfernandez (Posted a comment)
  • -email is unavailable- added by Beuc (Posted a comment)
  • -email is unavailable- added by karl (Posted a comment)
  • -email is unavailable- added by nicalvaro (Posted a comment)
  • -email is unavailable- added by marioxcc (Posted a comment)
  • -email is unavailable- added by electron (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follow 7 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2010-06-23 marioxcc StatusIn Progress Done
        Open/ClosedOpen Closed
    2010-06-20 alexfernandez StatusCancelled In Progress
        Open/ClosedClosed Open
    2010-06-17 marioxcc StatusNone Cancelled
        Assigned toNone marioxcc
        Open/ClosedOpen Closed

    Back to the top

    Powered by Savane 3.13-758e.
    Corresponding source code