Re: Making and using a release

[Josh Grosse]

On Sun, Jan 31, 2016 at 02:38:59PM +, Mark Carroll wrote:
> On 31 Jan 2016, Mark Carroll wrote:
> 
> > I thought that one option might be to update my sources to the latest
> > OPENBSD_5_8 revision, build and install the update on one, then make the
> > release on it and copy and unpack it to the other machines so that they
> > could then have the patches too.
> 
> I should have of course added the note that these machines are all
> already running an earlier version of 5.8 stable.

-stable is merely the published errata, and occasionally patches which 
do not rate receiving errata publication.  Since these do not change 
the system, you can indeed update simply by copying the kernel and
extracting the filesets. 

The folowing "update" script is what I use to update systems which
are already at an older -stable.  I don't use this when
transiting releases; for that I use the bsd.rd upgrade script.

I've replaced my local -stable build machine name with /path/to
in this example.

The servers that use this are uniprocessors, so I don't need to
worry about the bsd.sp kernel, the bsd kernel mentioned below
is GENERIC, not GENERIC.MP.

#!/bin/sh
rel=58
cd /
echo backing up kernels...
cp -p bsd bsd.rd bkupboot/
ftp http://path/to/stable/bsd
ftp http://path/to/stable/bsd.rd
ftp -mo - http://path/to/stable/base$rel.tgz | tar xzphf -
ftp -mo - http://path/to/stable/comp$rel.tgz | tar xzphf -
ftp -mo - http://path/to/stable/game$rel.tgz | tar xzphf -
ftp -mo - http://path/to/stable/man$rel.tgz | tar xzphf -

Re: Making and using a release

[trondd]

On Sun, January 31, 2016 7:04 am, Mark Carroll wrote:
> http://www.openbsd.org/faq/faq5.html#Release tells me at the end that,
>
>> ... if updating a machine to a new -stable, simply unpack the tar
>> files in the root directory of the target machine.
>
> Am I right to worry that this approach wouldn't include all the patches
> because it won't actually update the kernel itself?
>
> -- Mark
>

Yeah, you should follow the entire update process (unless you know exactly
what changed).  Replace your kernel, reboot, unpack the tarballs, run
sysmerge, etc.

Looks like someone already tweaked the FAQ.

Tim.

Re: Making and using a release

[Mark Carroll]

On 31 Jan 2016, tro...@kagu-tsuchi.com wrote:

> Yeah, you should follow the entire update process (unless you know exactly
> what changed).  Replace your kernel, reboot, unpack the tarballs, run
> sysmerge, etc.
>
> Looks like someone already tweaked the FAQ.

Thank you to everyone who helped me here. It's good when things seem to
be making sense. (-:

-- Mark

Re: Making and using a release

[Josh Grosse]

On Sun, Jan 31, 2016 at 12:24:03PM -0500, Josh Grosse wrote:
> The folowing "update" script is what I use to update systems which
> are already at an older -stable.  I don't use this when
> transiting releases; for that I use the bsd.rd upgrade script.

For clarity, the script is only used with a release(8) I've 
built myself, and where the -stable systems to be updated are 
at the same  version.  I would NEVER recommend using it in 
any other way.

In addition, the /bkupboot directories must be 
created in advance.  

Making and using a release

[Mark Carroll]

http://www.openbsd.org/faq/faq5.html#Release tells me at the end that,

> ... if updating a machine to a new -stable, simply unpack the tar
> files in the root directory of the target machine.

Am I right to worry that this approach wouldn't include all the patches
because it won't actually update the kernel itself?

-- Mark

Re: Making and using a release

[Mark Carroll]

On 31 Jan 2016, Mark Carroll wrote:

> I thought that one option might be to update my sources to the latest
> OPENBSD_5_8 revision, build and install the update on one, then make the
> release on it and copy and unpack it to the other machines so that they
> could then have the patches too.

I should have of course added the note that these machines are all
already running an earlier version of 5.8 stable.

-- Mark

Re: Making and using a release

[lists]

Sun, 31 Jan 2016 12:04:50 + Mark Carroll 
> http://www.openbsd.org/faq/faq5.html#Release tells me at the end that,
> 
> > ... if updating a machine to a new -stable, simply unpack the tar
> > files in the root directory of the target machine.  
> 
> Am I right to worry that this approach wouldn't include all the patches
> because it won't actually update the kernel itself?

You should not worry in the first place but pick what is closest to
appropriate for your intended operation cycle.

What is your goal, to keep a (group of) system(s) running -stable or
-current?  Here are details to help you decide this first:

http://www.openbsd.org/faq/faq5.html#Flavors
http://www.openbsd.org/faq/faq5.html#BldBinary

Note: it is often recommend following latest snapshots and updating
ports at regular intervals (weekly or up to about monthly at rarest)
and then considering further optional steps like following -current.

Building a -release is not the usual way to keep your systems up to
date unless they require installation like process with a different
binaries set than the biannual release cycle optical disks.

Re: Making and using a release

[Mark Carroll]

On 31 Jan 2016, li...@wrant.com wrote:

> Sun, 31 Jan 2016 12:04:50 + Mark Carroll 
>> http://www.openbsd.org/faq/faq5.html#Release tells me at the end that,
>> 
>> > ... if updating a machine to a new -stable, simply unpack the tar
>> > files in the root directory of the target machine.  
>> 
>> Am I right to worry that this approach wouldn't include all the patches
>> because it won't actually update the kernel itself?
>
> You should not worry in the first place but pick what is closest to
> appropriate for your intended operation cycle.
>
> What is your goal, to keep a (group of) system(s) running -stable or
> -current?

To keep a group of identical systems running -stable.

> Building a -release is not the usual way to keep your systems up to
> date unless they require installation like process with a different
> binaries set than the biannual release cycle optical disks.

I thought that one option might be to update my sources to the latest
OPENBSD_5_8 revision, build and install the update on one, then make the
release on it and copy and unpack it to the other machines so that they
could then have the patches too.

-- Mark