Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 12 Mar 2016 17:34:29 -0800 (PST)
From:      "Jeffrey Bouquet" <jbtakk@iherebuywisely.com>
To:        "current" <current@freebsd.org>
Subject:   Fwd: Re: UPDATING revision and seperate edge-case question(s)
Message-ID:  <E1aeuvN-0000W9-Bi@rmm6prod02.runbox.com>

next in thread | raw e-mail | index | archive | help
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@iherebuywisely.com>
To: "jbtakk" <jbtakk@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...=20

On Sat, 12 Mar 2016 08:10:22 -0800 (PST), "Jeffrey Bouquet" <jbtakk@iherebu=
ywisely.com> wrote:

> Having unexpectedly built world and kernel GENERIC on 3-8 Current, that i=
s not
> the principal system [1] ... browsing its UPDATING at the bottom the meth=
od(s) are
> not so precise and/or informative [follows...]
>=20
> [make world]
> make kernel
> installworld
> .... where is installkernel
>=20=20
> make buildworld
> make kernel
> mm...
> make installworld
> mm...
> .... where is installkernel
>=20
> but in motd where I save howtos
>=20
> backups
> check nosuid gone
> make buildworld
> make buildkernel
> single user
> mm...  [take good notes]
> installworld
>=20
> ... and for a lack of time, have to put it all on paper (several draft re=
visions
> within motd )
>=20
> and in another /usr/src-old
>=20
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                                       # revi=
sed
> install newly needed compatNif necc.
> yes | make delete-old                                                    =
  # revised
  yes | make delete-old-libs                                            # r=
evised
> restore nosuid
> restore make.conf
> rebuild nvidia-driver etc if necc.
>=20
> AND steps I often take that I've not listed...                      # som=
e in revision
>=20
> So, the latter example is more complete than the ones before it
> However, I think other things may be missing                   # see revi=
sions for example
> what if it should include a 2a.... make distribution  2b... make release =
etc which I have no=20
>   experience with...
>=20
> / end of requested another section in UPDATING with commented more-comple=
te steps from
> someone with more knowledge than I...
> .............................
> [1]
>=20
> Edge case...
> buildworld/kernel on another machine that is/was backup except that it ra=
n out of space
> on a few filesystems, so is NOT backup...
> wishing for a foolproof method to script its expected installkernel/insta=
llworld 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-d=
irectory fixes
> using cp, gcp, rsync until the hosed installworld is usable again (I've d=
one it before, that
> is why I am asking for a feature that will preclude the installworld fail=
ure, something like
> /work/ /stage/ in ports, where the /stage-installworld/ has been tested e=
very which way
> so that if the stage-installworld completes, the regular installworld is =
guaranteed to=20
> complete.=20=20
> 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 som=
ething
> similar as a feature, and/or explain an equivalent methodology, to increa=
se the
> reliability of updating a system, say upon a critical security advisory h=
appening to
> every os on the web all at once...
>=20
> ...................................
> ASKING NO RESPONSE to this email to here, do not wish to waste anyone's t=
ime, just
> to put forth a few ideas...
> ..........................
> Thanks for reading.
>=20
> J. Bouquet
>=20
>=20=20
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"




----- End Forwarded Message -----




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1aeuvN-0000W9-Bi>