[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openbsd-misc
Subject:    building STABLE
From:       Ken Walling <ken () cybercede ! net>
Date:       2003-02-23 20:01:07
[Download RAW message or body]

Ho.

I have pulled down the 3.2 stable patch branch
I have rebuilt my kernel  - backed up the old - and moved the new in
place and rebooted.

I have followed directions from several different resources to get to
where I am (different faq pages and other online oBSD resources)

I did this:

cd /usr/src
rm -r /usr/obj/*  (<- this I did several times because I was having
hardware problems and had to redo the 'make build' several times and
wanted to start fresh each time - because I wasn't comfortable trying to
issue the commands manually after doing a 'make -n build' -- though I
tried that at one point too - I just found the examples less than weenie
proof and wanted to be sure I didn't screw this up.)

I did finally (after swapping out bas hardware) get a successful exit
to:
make obj && make build

(it did take a while - left it going overnight and into the next day on
my Pentium 133)

now (sorry for the long intro) here is my question:

The "Patch Branches" document was very helpful (I found it on
openbsd.org via google - and didn't see a link to it from the FAQ side
of things, which would have been even more helpful).

However, that document ends with the lines: " # make obj && make
build           This will take awhile..."

BUT  in the "MINI-FAQ:  Upgrading OpenBSD"  section 1.5 I see more
things to do.
specifically:
<frag>

"...

   6.

      Update /etc and /dev by hand. These are not updated automatically.
Choose a directory with enough space to hold /, /dev, /var, and /etc.
Here I'll use /home/newroot

  # mkdir /home/newroot          
  # export DESTDIR=/home/newroot
  # cd /usr/src/etc && make distribution-etc-root-var

      Now compare the files in /home/newroot with their installed
counterparts. Replace or update the files as necessary.

  # rm -rf /home/newroot   (when done)

   7.

      Reboot to make sure the new /etc files are correct"
</frag>

??  I'm really not sure what I would be doing here ??
can someone please elaborate on:

1.  what the above steps (6 and 7) do - and what I actually have to do
in this regard when I'm building a stable patch branch build (i.e. is it
required or desired - or only needed when actually 'upgrading').
and
2. Please comment on this:  
at this point in my build process I believe I have
a. a new kernel in place
and 
b.  'patched' binaries in place since the code that I built had the
erratta changes ++ merged into place.

-- what I'm after is the perfection of the process - so I know what I'm
doing when a vuln I do care about gets merged into the stable branch -
and I need to do this all again.

at that point I assume that I 'update' my src via cvs - and execute
another 'make build' - and I'm all set.

Am I missing something?

   Thank you,

              Capt. Weenie

PS
after I get my stable build finished (if it isn't already)
I will be building a current build - anything terribly different there?
(I did see the extra steps associated with adding new groups and the
like - is that always a manual process?)

[prev in list] [next in list] [prev in thread] [next in thread]