On Mon, Apr 04, 2022 at 08:37:57PM +0100, Steve Fairhead said:
> To put it another way, what is the recommended way of upgrading a production
> system with patches applied (so -stable)?
Historically I used the manual method to upgrade releases but have been using
sysupgrade(8) since it became The
On 2022/04/04 20:37, Steve Fairhead wrote:
> On 04/04/2022 13:10, owner-m...@openbsd.org wrote:
> > sysupgrade only copes with what look like release versions (no version
> > suffix, upgrades to release+0.1 with no arguments, or snapshot with -s)
> > or snapshots (-current or -beta suffix, by defau
On 04/04/2022 13:10, owner-m...@openbsd.org wrote:
sysupgrade only copes with what look like release versions (no version
suffix, upgrades to release+0.1 with no arguments, or snapshot with -s)
or snapshots (-current or -beta suffix, by default -current upgrades
to release+0.1 or -beta upgrades t
OK, thanks, good to know.
Dave
On 4/3/22, Stuart Henderson wrote:
> On 2022/04/03 14:02, Raymond, David wrote:
>> So, to clarify, if I upgrade to a snapshot after upgrading to 7.0
>> stable, what happens when 7.1 stable comes along? Can I get to that
>> stable release from a previous snapshot?
On 2022/04/03 14:02, Raymond, David wrote:
> So, to clarify, if I upgrade to a snapshot after upgrading to 7.0
> stable, what happens when 7.1 stable comes along? Can I get to that
> stable release from a previous snapshot?
Official binaries do not have "-stable" (neither releases nor
syspatches)
So, to clarify, if I upgrade to a snapshot after upgrading to 7.0
stable, what happens when 7.1 stable comes along? Can I get to that
stable release from a previous snapshot?
Dave Raymond
On 4/3/22, Stuart Henderson wrote:
> On 2022-04-03, Steve Fairhead wrote:
>> On 07/11/2021 10:35, Steve Fa
On 2022-04-03, Steve Fairhead wrote:
> On 07/11/2021 10:35, Steve Fairhead wrote:
>>
>> That's what I'd expect, and I did indeed run sysupgrade without specific
>> options. Nonetheless I seem to have wound up with -current when I would
>> have expected -stable:
>>
>> # dmesg | grep OpenBSD
>>
On 07/11/2021 10:35, Steve Fairhead wrote:
That's what I'd expect, and I did indeed run sysupgrade without specific
options. Nonetheless I seem to have wound up with -current when I would
have expected -stable:
# dmesg | grep OpenBSD
OpenBSD 6.9-stable (GENERIC.MP) #0: Mon Aug 23 21:44:18 BS
On 07/11/2021 08:44, Sebastien Marie wrote:
You didn't need to remove the previous;
you could have just updated the source you had.
running cvs update (with -r OPENBSD_7_0) is a possibility, but
removing files and reinstall is another. Nothing wrong here.
Actually I did try a CVS update first,
On Sun, Nov 07, 2021 at 08:48:47AM +0100, Jan Stary wrote:
> On Nov 06 20:51:53, st...@fivetrees.com wrote:
> > Hi folks,
> >
> > I think I've probably done something stupid, but I'm not sure where. Not
> > used sysupgrade before; I usually reinstall. So this is new to me.
> >
> > I updated a sys
On Sat, Nov 06, 2021 at 08:51:53PM +, Steve Fairhead wrote:
> Hi folks,
>
> I think I've probably done something stupid, but I'm not sure where. Not
> used sysupgrade before; I usually reinstall. So this is new to me.
>
> I updated a system from 6.9 to 7.0 with sysupgrade; no problems at all.
On Nov 06 20:51:53, st...@fivetrees.com wrote:
> Hi folks,
>
> I think I've probably done something stupid, but I'm not sure where. Not
> used sysupgrade before; I usually reinstall. So this is new to me.
>
> I updated a system from 6.9 to 7.0 with sysupgrade; no problems at all. I
> then nuked t
Hi folks,
I think I've probably done something stupid, but I'm not sure where. Not
used sysupgrade before; I usually reinstall. So this is new to me.
I updated a system from 6.9 to 7.0 with sysupgrade; no problems at all.
I then nuked the contents of /usr/src, and decanted the 7.0 src.tar.gz
13 matches
Mail list logo
