netdev - ttcp (maintenance) future?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Tue, 18 Mar 2008 21:13:11 +0200 (EET)
From:	Pekka Savola <pekkas@...core.fi>
To:	netdev@...r.kernel.org
Subject: ttcp (maintenance) future?

Hi,

I've maintaned somewhat updated version of ttcp [1] since 2001 but have not 
bothered to increment a version number or properly distribute it, CVS version 
the changes, etc.

Having one place with versioning, at least annual releases, etc. would likely 
be beneficial so all the distributions (both Linux and e.g. BSDs) that ship it 
could pick up and benefit from the changes collected in one place.

Some questions to the community as a whole:

- Has this already been done (in some other, modified ttcp version)?

- Is this worth doing given that there are other ttcp forks such as
   nuttcp and nttcp (these add major new features which I believe is
   not in scope for the original ttcp)?

- Are there major ttcp modifications that a future maintainer should
   be aware of?

- Would someone be willing to step up and take the maintenance to the
   next step?  (If not, I'll have to consider whether I can do it
   myself.)

[1]
http://netcore.fi/pekkas/linux/ipv6/ttcp.c

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html