From owner-freebsd-doc@FreeBSD.ORG Fri Nov 20 16:52:30 2009 Return-Path: Delivered-To: doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C5D3E106566B; Fri, 20 Nov 2009 16:52:30 +0000 (UTC) (envelope-from manolis@FreeBSD.org) Received: from kane.otenet.gr (kane.otenet.gr [83.235.67.31]) by mx1.freebsd.org (Postfix) with ESMTP id 3F52B8FC0C; Fri, 20 Nov 2009 16:52:29 +0000 (UTC) Received: from pulstar.local (athedsl-4487278.home.otenet.gr [94.71.68.118]) by kane.otenet.gr (8.13.8/8.13.8/Debian-3) with ESMTP id nAKGqQbL008375; Fri, 20 Nov 2009 18:52:26 +0200 Message-ID: <4B06C94A.30600@FreeBSD.org> Date: Fri, 20 Nov 2009 18:52:26 +0200 From: Manolis Kiagias User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: Giorgos Keramidas References: <4B05BA06.3010303@FreeBSD.org> <87ws1luqmx.fsf@kobe.laptop> In-Reply-To: <87ws1luqmx.fsf@kobe.laptop> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-7 Content-Transfer-Encoding: 7bit Cc: Tom Rhodes , "doc@FreeBSD.org" , Gabor PALI , Gabor Kovesdan , Rene Ladan , Manolis Kiagias Subject: Re: [RFC] Article on freebsd-update-server X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Nov 2009 16:52:30 -0000 Giorgos Keramidas wrote: > - All changes look fine up to this point > : > : - Note down the generated KeyPrint; this value is entered into > : - /etc/freebsd-update.conf for binary > : - updates. > : + Keep a note of the generated key fingerpring. This value is > : + entered into /etc/freebsd-update.conf for > : + binary updates. > : > > There are various places that the article refers to "KeyPrint". I think it > means "key fingerpring", but I am not sure. If that's what the real meaning > should be, please use "key fingerprint". > > Probably, but we need some input from Jason here. I assume you are right. > : Mon Aug 24 17:54:07 PDT 2009 Extracting world+src for FreeBSD/amd64 7.2-RELEASE > : @@ -411,10 +428,7 @@ to sign the release. > : file named USAGE. Execute > : scripts/approve.sh, as directed. This will sign > : the release, and move components into a staging area suitable for > : - uploading. It is important to make sure that your key is mounted > : - during this process. A simple df will show if it > : - is mounted. If not mounted, mount the key with the passphrase supplied > : - when creating it earlier. > : + uploading. > > I don't know where the key mounting bits come from. It seems to refer to > those FreeBSD installations where PGP keys are stored in removable media, like > a USB flash disk. Why do we have to explicitly mention this here? After all, > we don't describe how gpg-agent(1) works, or how seahorse(1) integrates PGP > with Gnome, or any other case of the dozens of PGP setups possible... > > Same here, I am not really sure what the key mounting refers to. > : @@ -524,9 +547,11 @@ Wed Aug 26 12:50:07 PDT 2009 Cleaning st > : > : When running a patch level build, we are assuming that previous > : patches are in place. When a patch build is run, it will run all > : - patches less than or equal to the number specified. Beyond this, > : - you will have to take appropriate measures to verify authenticity > : - of the patch. > : + patches less than or equal to the number specified. > : + > : + It is up to the administrator of the freebsd-update > : + server to take appropriate measures to verify the authenticity of > : + every patch. > > I think we ought to emphasize a bit the part about patch authenticity, but I > am not sure if I chose the right way to do this. > > Or maybe use around it? > : - Follow the same process as noted before for appoving a build. > : + Follow the same process as noted before for approving a build: > > Typo. > > There are more changes, in the attached patch. Most of them are attempts to > improve the wording of various small parts of the article. Please see the > attached diff for all of them. > > The patch has been applied, the new version is available in mercurial and also uploaded again to freefall. > One more important detail. We are still discussing at doceng@ how we can > bring the final article into CVS. So, please hold from committing this, until > we have resolved all the remaining details. > > Yes, I am aware of this. Jason has thought of something like this (copied from email): Afterword This FreeBSD Update article was originally published at Experts-Exchange. and I thought we could turn this into something like "Acknowledgements / Further Reading" section (will probably need to be expanded a bit). Does this make any sense? > I'm sure that a lot of people will love reading an article that describes in > detail how to set up a local freebsd-update server. Thanks for all the work > done so far on what seems to be an excellent article! :-D > And we thank you for the thorough review :)