Re: install/59759: Core dump on sysupgrade to 11.0 BETA

["Ramiro Aceves via gnats" <gnats-admin%NetBSD.org@localhost>]

The following reply was made to PR install/59759; it has been noted by GNATS.

From: Ramiro Aceves <ea1abz%gmail.com@localhost>
To: gnats-bugs%netbsd.org@localhost, install-manager%netbsd.org@localhost,
 gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost, jspath55%gmail.com@localhost
Cc: 
Subject: Re: install/59759: Core dump on sysupgrade to 11.0 BETA
Date: Tue, 18 Nov 2025 07:55:11 +0100

 El 17/11/25 a las 23:50, Jim Spath via gnats escribió:
 > The following reply was made to PR install/59759; it has been noted by GNATS.
 > 
 > From: Jim Spath <jspath55%gmail.com@localhost>
 > To: gnats-bugs%netbsd.org@localhost
 > Cc:
 > Subject: Re: install/59759: Core dump on sysupgrade to 11.0 BETA
 > Date: Mon, 17 Nov 2025 17:46:04 -0500
 > 
 >   On Mon, Nov 17, 2025 at 4:55=E2=80=AFPM Christos Zoulas via gnats
 >   <gnats-admin%netbsd.org@localhost> wrote:
 >   > This is already documented.
 >   
 >   > And also in tracking current: https://www.netbsd.org/docs/current/?utm_so=
 >   urce=3Dchatgpt.com#using-anoncvs
 >   > When upgrading to a more recent version of -current you should always ins=
 >   tall and boot a new kernel before installing any new libs (*). In general t=
 >   he best approach is to try the new kernel before anything else, and if you =
 >   hit any problems see the entry in the Kernel FAQ.
 >   
 >   I see the above online, such as:
 >   https://www.netbsd.org/docs/guide/en/chap-upgrading.html
 >   
 >   I believe I was misled by the sysupgrade man page, or I misread the
 >   order presented:
 >   
 >   Standalone upgrade steps:
 >   
 >   sysupgrade [common_flags] clean
 >   sysupgrade [common_flags] etcupdate
 >   sysupgrade [common_flags] fetch [releasedir]
 >   sysupgrade [common_flags] kernel [kernel_name]
 >   sysupgrade [common_flags] modules
 >   sysupgrade [common_flags] sets [set1 .. setN]
 >   sysupgrade [common_flags] postinstall [arg1 .. argN]
 >   
 >   I then reboot.
 >   
 >   The online documents differ as pointed out:
 >   
 >   # sysupgrade fetch https://cdn.NetBSD.org/pub/NetBSD/NetBSD-9.2/amd64
 >   # sysupgrade kernel
 >   # sysupgrade modules
 >   # reboot
 >   # sysupgrade sets
 >   # sysupgrade etcupdate
 >   # sysupgrade postinstall
 >   # sysupgrade clean
 >   # reboot
 >   
 >   As sysupgrade is in pkgsrc, should I suggest the doc change there?
 >   
 >   Jim
 >   
 
 Oh, luckily from my start in NetBSD I have read the sysupgrade WEB 
 instructions first instead of the man page "standalone upgrade steps". 
 Reading them after reading the WEB page they are not too confusing. But 
 yes, if you read them first are prone to cause confusion.
 
 Reading the sysupgrade man page at "auto" chapter I see that there is no 
 "reboot" after the kernel upgrade phase:
 
 ***
       The standard upgrade procedure performed by this command is as 
 follows:
 
       1.   â??fetchâ??: Retrieve distribution sets into the local cache 
 directory.
 
       2.   â??modulesâ??: Unpack new kernel modules.
 
       3.   â??kernelâ??: Upgrade kernel.
 
       4.   â??setsâ??: Upgrade system sets, except configuration files.
 
       5.   â??etcupdateâ??: Merge new changes to configuration files.  This 
 is the
            only interactive step in the process and can be disabled for this
            reason by setting ETCUPDATE to false.
 
       6.   â??postinstallâ??: Perform sanity checks and optionally apply
            unconditional fixes to the upgraded system.
 
       7.   â??cleanâ??: Remove contents of the cache directory.  This can be
            disabled by setting AUTOCLEAN to false in case you want to 
 keep the
            downloaded distribution files around.
 ***
 
 I am curious to know what would happen when I upgrade my RaspberryPi 
 Zero W and Raspberry Pi 4 using sysupgrade over SSH. Perhaps it would be 
 safer with an attached HDMI monitor.
 
 Regards.