From nobody Thu Aug 1 11:55:23 2024 X-Original-To: freebsd-virtualization@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4WZS8x2kRhz5SdfM for ; Thu, 01 Aug 2024 11:56:01 +0000 (UTC) (envelope-from odhiambo@gmail.com) Received: from mail-oa1-x2d.google.com (mail-oa1-x2d.google.com [IPv6:2001:4860:4864:20::2d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4WZS8w0X45z3wfQ for ; Thu, 1 Aug 2024 11:56:00 +0000 (UTC) (envelope-from odhiambo@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=e+7Kz+Yr; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of odhiambo@gmail.com designates 2001:4860:4864:20::2d as permitted sender) smtp.mailfrom=odhiambo@gmail.com Received: by mail-oa1-x2d.google.com with SMTP id 586e51a60fabf-26808290f43so979265fac.0 for ; Thu, 01 Aug 2024 04:56:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1722513358; x=1723118158; darn=freebsd.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=Y30Rp+l/prWDo52MfKqDVJNyJIzuKF29/bwObbJqxMs=; b=e+7Kz+Yrh4GLVKtl5U4CqCnOg0lIG10ztuE4dEdWiIR6xWqMCrKJVgtGoDr1quCf+K IsBz9S95J1APyFIY3VRIc2GnW/ifb+k6/r6ClEzn1QcRtlTe/PDnepmYc07hvr5X8F2y 0VEcr1sUsCu/8fdzHoo25rxaVOdqcRlrgE3UWIAk+g05H7N4CcQhO7U2fhhUy3+sVsmo AdsldsT+wsOb8zacoPJnzfGoeV39c0dToR1CBuPoA6TVii/h1clvam0lhzxQ6dL0Ff09 VH+KrZkiLK+kVMg/5H/4tP1iEGFutNNmp/Dn5MoQ+cmiSWRQCb+qVnUpjWiHK3KGe7vI bhmA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1722513358; x=1723118158; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=Y30Rp+l/prWDo52MfKqDVJNyJIzuKF29/bwObbJqxMs=; b=jT3UHfzxKZ2ExUg34Mh85ruENAxlatCd1ilc3M21ztQDNDT3Tg7YtEUntlbY3eUv0v QbZ7H78ON0OtNLrwjkH6v8L6Q3/mPj+LQRdx4utn/BUrPsOmDuywgMJGJ06Q8sEV2BSL AEXdzfy1NCrTDIqLTjVEY8clkQgPZTRMoIOCgob/CI6kQzlLPEn92bst5/OaSNfUQWcX WMCsIrlw+lhljbm9VX51lxqnDA6aPm0bqbgAUmrVYxIZ+eqDwW8qL3CvClhtRpIfl/mI iGMFi/c/Nd8BNecBvZ4js1QxvBe/UCVB9BF1PZYByvHkwqI7XljOkcxnKdbzbMPSh6FG 0rUQ== X-Gm-Message-State: AOJu0Yw9kKIWJ6UeAlB8S6Lrp1sYli+USn8R1CUpr2oZLiid/8xt0mZn NyVEs/y/A24m+0A/g9lys6XDbGNpwEInje1ooYDemJu4rNM7ts3842jLymdR9c5OBIOTwoYbfTB WOqOcE8dIqpW+CrEKSgv0CC+Bep49LLEy7so= X-Google-Smtp-Source: AGHT+IF5JyGp1lGceF70+WAud1KbJKdFztKcaCPtezao+zUEkze7ld2rPSzrdNoYw9XaYFGdiWKun8rlYCtM9F0dPEg= X-Received: by 2002:a05:6870:d6a3:b0:25d:fe73:28af with SMTP id 586e51a60fabf-2688797137bmr413675fac.24.1722513358357; Thu, 01 Aug 2024 04:55:58 -0700 (PDT) List-Id: Discussion List-Archive: https://lists.freebsd.org/archives/freebsd-virtualization List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-virtualization@freebsd.org Sender: owner-freebsd-virtualization@FreeBSD.org MIME-Version: 1.0 References: In-Reply-To: From: Odhiambo Washington Date: Thu, 1 Aug 2024 14:55:23 +0300 Message-ID: Subject: Re: upgrading 13.2-p11 to 13.3-p4 on azure via freebsd-update To: freebsd-virtualization@freebsd.org Content-Type: multipart/alternative; boundary="000000000000d89244061e9de4f4" X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.40 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-0.40)[-0.401]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; R_SPF_ALLOW(-0.20)[+ip6:2001:4860:4000::/36]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCPT_COUNT_ONE(0.00)[1]; FREEMAIL_ENVFROM(0.00)[gmail.com]; FREEMAIL_FROM(0.00)[gmail.com]; DKIM_TRACE(0.00)[gmail.com:+]; FROM_HAS_DN(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; PREVIOUSLY_DELIVERED(0.00)[freebsd-virtualization@freebsd.org]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MISSING_XM_UA(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; ASN(0.00)[asn:15169, ipnet:2001:4860:4864::/48, country:US]; MLMMJ_DEST(0.00)[freebsd-virtualization@freebsd.org]; RCVD_COUNT_ONE(0.00)[1]; RCVD_IN_DNSWL_NONE(0.00)[2001:4860:4864:20::2d:from] X-Rspamd-Queue-Id: 4WZS8w0X45z3wfQ --000000000000d89244061e9de4f4 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Aug 1, 2024 at 2:50=E2=80=AFPM void wrote: > On Thu, Aug 01, 2024 at 11:42:57AM +0300, Odhiambo Washington wrote: > >On Tue, Jul 30, 2024 at 2:57=E2=80=AFPM void wrote: > > > >> Hi, > >> > >> Are there any known issues upgrading 13.2-p11 to 13.3-p3 via > freebsd-update > >> on Azure? > >> > > > >How else would it be updated? You want to 'make buildworld buildkernel &= & > >install'?? > > No - it uses freebsd-update. I'm just asking if there are any known issue= s > upgrading 13.2-p11 to 13.3-p3 on the Azure platform. > If there were any known issues, I am sure the RELEASE Engineering Team would have flagged it at https://www.freebsd.org/releases/13.3R/announce/. In any case, it is always advisable to have backups that you can fall back to. For FreeBSD, that is config files and data. Go ahead and upgrade. --=20 Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' =C2=AF\_(=E3=83=84)_/=C2=AF :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html] --000000000000d89244061e9de4f4 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Thu, Aug 1, 2024 at 2:50=E2=80=AFP= M void <void@f-m.fm> wrote:
On Thu, Aug 01, 2024 a= t 11:42:57AM +0300, Odhiambo Washington wrote:
>On Tue, Jul 30, 2024 at 2:57=E2=80=AFPM void <void@f-m.fm> wrote:
>
>> Hi,
>>
>> Are there any known issues upgrading 13.2-p11 to 13.3-p3 via freeb= sd-update
>> on Azure?
>>
>
>How else would it be updated? You want to 'make buildworld buildker= nel &&
>install'??

No - it uses freebsd-update. I'm just asking if there are any known iss= ues
upgrading 13.2-p11 to 13.3-p3 on the Azure platform.
<= /div>

If there were any known issues, I am sure the REL= EASE Engineering Team would have flagged it at
In any case, it is always advisable to have backu= ps that you can fall back to. For FreeBSD, that is config files and data.

Go ahead and upgrade.

--
Best regards= ,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 322= 3
=C2=A0In=C2=A0an Internet failure case, the #1 suspect is a= constant: DNS.
"Oh, the cr= uft.",=C2=A0egrep -v '^$|^.*#'=C2=A0=C2=AF\_(=E3=83=84)_/=C2=AF=C2= =A0:-)
[How to ask smart = questions:=C2=A0http://www.ca= tb.org/~esr/faqs/smart-questions.html]
--000000000000d89244061e9de4f4--