From owner-freebsd-current@freebsd.org Sat Mar 12 16:10:32 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 18040ACD217 for ; Sat, 12 Mar 2016 16:10:32 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id F0F4B10B7 for ; Sat, 12 Mar 2016 16:10:31 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: by mailman.ysv.freebsd.org (Postfix) id F01DBACD215; Sat, 12 Mar 2016 16:10:31 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D5C91ACD214 for ; Sat, 12 Mar 2016 16:10:31 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: from aibo.runbox.com (aibo.runbox.com [91.220.196.211]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9C0D110B6 for ; Sat, 12 Mar 2016 16:10:31 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: from [10.9.9.241] (helo=rmm6prod02.runbox.com) by bars.runbox.com with esmtp (Exim 4.71) (envelope-from ) id 1aem7S-0005MQ-2J for current@freebsd.org; Sat, 12 Mar 2016 17:10:22 +0100 Received: from mail by rmm6prod02.runbox.com with local (Exim 4.76) (envelope-from ) id 1aem7S-0006Jc-1q for current@freebsd.org; Sat, 12 Mar 2016 17:10:22 +0100 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Received: from [Authenticated user (846156)] by runbox.com with http (RMM6); for ; Sat, 12 Mar 2016 16:10:22 GMT From: "Jeffrey Bouquet" Reply-To: jbtakk@iherebuywisely.com To: "current" Subject: UPDATING revision and seperate edge-case question(s) Date: Sat, 12 Mar 2016 08:10:22 -0800 (PST) X-Mailer: RMM6 Message-Id: X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Mar 2016 16:10:32 -0000 Having unexpectedly built world and kernel GENERIC on 3-8 Current, that is = not the principal system [1] ... browsing its UPDATING at the bottom the method= (s) are not so precise and/or informative [follows...] [make world] make kernel installworld .... where is installkernel =20 make buildworld make kernel mm... make installworld mm... .... where is installkernel but in motd where I save howtos backups check nosuid gone make buildworld make buildkernel single user mm... [take good notes] installworld ... and for a lack of time, have to put it all on paper (several draft revi= sions within motd ) and in another /usr/src-old svn sources move make.conf check nosuid buildworld buildkernel [ compare GENERICS assumed], add compatN etc installkernel mergemaster first type, using /usr/src/.../mergemaster.sh single-user (yet) installworld mergemaster (complete ) install newly needed compatNif necc. make delete-old ( and sometimes a pipe y | make... or something) restore nosuid restore make.conf rebuild nvidia-driver etc if necc. AND steps I often take that I've not listed... So, the latter example is more complete than the ones before it However, I think other things may be missing what if it should include a 2a.... make distribution 2b... make release et= c which I have no=20 experience with... / end of requested another section in UPDATING with commented more-complete= steps from someone with more knowledge than I... ............................. [1] Edge case... buildworld/kernel on another machine that is/was backup except that it ran = out of space on a few filesystems, so is NOT backup... wishing for a foolproof method to script its expected installkernel/install= world onto an attached main-os disk, something with rsync... to expedite recovery from t= he main-os disk installworld that fails at some point midway, meaning directory-by-dir= ectory fixes using cp, gcp, rsync until the hosed installworld is usable again (I've don= e it before, that is why I am asking for a feature that will preclude the installworld failur= e, something like /work/ /stage/ in ports, where the /stage-installworld/ has been tested eve= ry which way so that if the stage-installworld completes, the regular installworld is gu= aranteed to=20 complete.=20=20 Seeming about a half-years work on someone's part, just adding this edge ca= se in case someone has perchance crafted something similar, would jumpstart somet= hing similar as a feature, and/or explain an equivalent methodology, to increase= the reliability of updating a system, say upon a critical security advisory hap= pening to every os on the web all at once... ................................... ASKING NO RESPONSE to this email to here, do not wish to waste anyone's tim= e, just to put forth a few ideas... .......................... Thanks for reading. J. Bouquet =20=