linux-kernel - Re: util-linux: orphan

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4553AF8E.60605@zytor.com>
Date:	Thu, 09 Nov 2006 14:45:34 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Karel Zak <kzak@...hat.com>
CC:	linux-kernel@...r.kernel.org, Henne Vogelsang <hvogel@...e.de>,
	Olaf Hering <olh@...e.de>
Subject: Re: util-linux: orphan

Karel Zak wrote:
> 
>  I've originally thought about util-linux upstream fork, but as
>  usually an fork is bad step. So.. I'd like to start some discussion
>  before this step. Maybe Adrian will be realistic and he will leave
>  the project and invest all his time to kernel only.
> 

Actually, forking is not really that bad of an idea.  When I took over 
tftp, for example, I just did it and called it tftp-hpa.  It didn't take 
very long before I got a message from the netkit maintainer asking if I 
was planning to continue, and if so if he could drop tftp from netkit.

A similar thing happened when Jeremy (and now Ian) took over autofs from me.

Forking gets your new maintainership proven *before* you end up taking 
over.  On the other hand, magicfilter effectively died when I handed it 
over to someone who didn't do a good job with it.

	-hpa
-
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/