Fwd: Re: UPDATING revision and seperate edge-case question(s)

From: Jeffrey Bouquet <jbtakk_at_iherebuywisely.com>
Date: Sat, 12 Mar 2016 17:34:29 -0800 (PST)
Sorry, sent it to this same email originally, on to the list...

----- Start Forwarded Message -----
Sent: Sat, 12 Mar 2016 17:33:31 -0800 (PST)
From: "Jeffrey Bouquet" <jbtakk_at_iherebuywisely.com>
To: "jbtakk" <jbtakk_at_iherebuywisely.com>
Subject: Re: UPDATING revision and seperate edge-case question(s)

Just for completeness, the buildworld draft section
I wrote below..., three were missing at least... though still
a rough draft... Approximately seven lines added/revised... 

On Sat, 12 Mar 2016 08:10:22 -0800 (PST), "Jeffrey Bouquet" <jbtakk_at_iherebuywisely.com> wrote:

> 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
>  
> 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 revisions
> within motd )
> 
> and in another /usr/src-old
> 
READ UPDATING
> svn sources
> move make.conf
> check nosuid
> buildworld
COMPARE NEWEST GENERIC WITH PRIOR GENERIC IF CUSTOM AND/OR NOT KERNEL
> buildkernel [ compare GENERICS assumed], add compatN etc
> installkernel
sh /usr/src/usr.sbin/mergemaster/mergemaster -vipPc (-F?)    # revised
> reboot single-user (yet)
mount -t ufs -u -o rw /dev/gpt/label   /    (or whatever)     # new
mount -va                                                                    #new
df                                                                        # new
> installworld
> another mergemaster  if necc                                       # revised
> install newly needed compatNif necc.
> yes | make delete-old                                                      # revised
  yes | make delete-old-libs                                            # revised
> restore nosuid
> restore make.conf
> rebuild nvidia-driver etc if necc.
> 
> AND steps I often take that I've not listed...                      # some in revision
> 
> So, the latter example is more complete than the ones before it
> However, I think other things may be missing                   # see revisions for example
> what if it should include a 2a.... make distribution  2b... make release etc which I have no 
>   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/installworld onto an
> attached main-os disk,  something with rsync... to expedite recovery from the main-os
> disk installworld that fails at some point midway, meaning directory-by-directory fixes
> using cp, gcp, rsync until the hosed installworld is usable again (I've done it before, that
> is why I am asking for a feature that will preclude the installworld failure, something like
> /work/ /stage/ in ports, where the /stage-installworld/ has been tested every which way
> so that if the stage-installworld completes, the regular installworld is guaranteed to 
> complete.  
> Seeming about a half-years work on someone's part, just adding this edge case in
> case someone has perchance crafted something similar, would jumpstart something
> similar as a feature, and/or explain an equivalent methodology, to increase the
> reliability of updating a system, say upon a critical security advisory happening to
> every os on the web all at once...
> 
> ...................................
> ASKING NO RESPONSE to this email to here, do not wish to waste anyone's time, just
> to put forth a few ideas...
> ..........................
> Thanks for reading.
> 
> J. Bouquet
> 
>  
> _______________________________________________
> freebsd-current_at_freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"




----- End Forwarded Message -----
Received on Sun Mar 13 2016 - 00:34:33 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:03 UTC