n-Reply-To: <657BD3A2-AED4-4598-A482-26A7B1021F6C@nreilly.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - cp1.inocweb.com
X-AntiAbuse: Original Domain - freebsd.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - inoc.net
X-Get-Message-Sender-Via: cp1.inocweb.com: authenticated_id: rblayzor@inoc.net
X-Authenticated-Sender: cp1.inocweb.com: rblayzor@inoc.net
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Spamd-Bar: -
X-Spamd-Result: default: False [-1.99 / 15.00];
	NEURAL_HAM_MEDIUM(-1.00)[-1.000];
	NEURAL_HAM_LONG(-1.00)[-0.999];
	NEURAL_SPAM_SHORT(0.81)[0.812];
	DMARC_POLICY_ALLOW(-0.50)[inoc.net,quarantine];
	R_DKIM_ALLOW(-0.20)[inoc.net:s=default];
	R_SPF_ALLOW(-0.20)[+mx];
	ONCE_RECEIVED(0.20)[];
	MIME_GOOD(-0.10)[text/plain];
	HAS_X_SOURCE(0.00)[];
	TO_MATCH_ENVRCPT_ALL(0.00)[];
	HAS_X_AS(0.00)[rblayzor@inoc.net];
	RCVD_TLS_ALL(0.00)[];
	RCPT_COUNT_ONE(0.00)[1];
	HAS_X_GMSV(0.00)[rblayzor@inoc.net];
	DKIM_TRACE(0.00)[inoc.net:+];
	FROM_HAS_DN(0.00)[];
	ARC_NA(0.00)[];
	MLMMJ_DEST(0.00)[stable@freebsd.org];
	TO_DN_NONE(0.00)[];
	FROM_EQ_ENVFROM(0.00)[];
	HAS_X_ANTIABUSE(0.00)[];
	MID_RHS_MATCH_FROM(0.00)[];
	RCVD_VIA_SMTP_AUTH(0.00)[];
	BLOCKLISTDE_FAIL(0.00)[64.22.37.1:server fail,2607:f058:11:a:509c:7a89:74e5:504d:server fail];
	RCVD_COUNT_ONE(0.00)[1];
	ASN(0.00)[asn:22302, ipnet:64.22.36.0/23, country:US];
	MIME_TRACE(0.00)[0:+]
X-Rspamd-Queue-Id: 4dQF2c53D4z42tM

On 12/5/25 15:55, Nathan Reilly-list wrote:
> Hello,
> 
> I updated from 13.5 to 15 on amd64 with freebsd-update fine.]


I've gone from 13.5 and 14.3 to 15.0 following the freebsd-update methods.

The only thing I got bit by is that afer the first "freebsd-update 
install" and subsequent reboot for the new kernel if you're using ipfw 
you're going to have issues until the new userland gets installed.

Best advice would be to disable ipfw before the first reboot, install 
the new userland, re-enable ipfw and reboot again.

To be safe you could just do it completely from the console. But for 
remote installs if you don't disable ipfw first and it's not set to 
default allow, it'll be an issue.


-- 
inoc.net!rblayzor
PGP:  https://pgp.inoc.net/rblayzor/