linux-kernel - A fork starts with a single branch.

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]

Message-ID: <trinity-94209088-72cf-43a0-bf76-d2dd2668e36e-1415948250579@3capp-mailcom-lxa14>
Date:	Fri, 14 Nov 2014 07:57:31 +0100
From:	"George Malone" <georgemaloneiii@...l.com>
To:	linux-kernel@...r.kernel.org
Subject: A fork starts with a single branch.

A fork starts with a single branch.
As a precaution, I (for one (of many)) have all the debian source packages allready,
and the full binary set for some architectures.

(I'm sure many others have taken this precaution aswell, some
as a matter of course)

This is how all forks start.
I've done it more than once.
The key is a stable base, no shifting sands.
Then you can build and build, gradually, till you die.
(and it's fun all the time)

I think the Best path is 3 and then 4.
Once people stop work on Wheezy (they still release point releases)
then it is truly time to continue on from there.
There must be preperations made to be ready
by that time, however. Some have allready been done.

Perhaps the mempo and other debian-based projects
who work best in a unix-like linux can set sail
down the same river when that time comes?

As for the coup. I believe that the coupists should
be continually confronted and harranged. They should
not be allowed to get away with this without so much
as a word. They need to be exposed, pointed at, shown
to be what they are. In one's free time between working,
on projects, as a way of not burning one-self out
continually doing one and only one thing.

(One feature that would be good for such a fork would
be to provide old versions of things like python 
installable alongside current versions, this is because
python (and others) break compatability between versions.
I have "old" programs that require the old versions.
Had to find and build the old version. Might aswell
package it up at some time.
Also things like earier versions of KDE would be nice.
To some degree things like this allready exist in debian
(*box wms))

A full fork of Debian is not impossible, infact debian
makes it easy to do. One change is how it always, always
starts.

Best of linux, before systemd. http://youtu.be/Bml5bjoMYjQ
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/