I was able to build the kernel, began building the system at 8:30pm. When I returned back to my office after 1am to discover the system build had not completed, I canceled the process and issued the command to pull the next snapshot and upgrade the system. Inevitably I would regret this decision.
Rebooted the system, ran package update, and then went to upgrade some Go programs I use. As soon as the command was issued to install, my system crashed without dropping into debug mode, straight to reboot, and another lengthy filesystem check. Now it's 2am, and I am assuming this is a different issue altogether. The Go programs are not system critical, so I have removed them from PATH. I will try again to get my system up and running. If successful, I will create a virtual machine to see if I can reproduce the issue. If not successful, I will assume the issue has been resolved in the source code, and restart the build again from scratch. The latter will push system availability to later than 7 am tomorrow morning. Here goes something, William On Mon, Oct 21, 2024, 1:33 PM William Thebrand <williamthebr...@gmail.com> wrote: > That was a stupid question. The next snapshot release will occur tonight > around 10pm EST. > > I will build from source, by booting from a release cd, mount my hard > drive, pull from anoncvs, and then build source. > > It seems like the "grown-up" thing to do. Been a while since I have had to > build from source, but relatively easy, and the FAQ is always their as a > guide. > > William > > On Mon, Oct 21, 2024, 12:55 PM William Thebrand <williamthebr...@gmail.com> > wrote: > >> Cool beans. When will the next snapshot be out? >> >> On Mon, Oct 21, 2024, 6:11 AM Martin Pieuchot <m...@grenadille.net> wrote: >> >>> On 21/10/24(Mon) 01:12, William Thebrand wrote: >>> > I pull the newest snapshot release every sunday, and run a full >>> upgrade on >>> > my system. Which means the OS, packages, and even git based projects I >>> use. >>> > Four times in a row, the system has crashed without warning, and is >>> > practically unusable. There is variance on what I was doing when the >>> system >>> > decided to crash, so the source of the crash assumedly deals with a >>> > background process. >>> > >>> > I have tried to "tread lightly", and poke around to see if I can find >>> the >>> > error, but it just crashes regardless, with little progress. As you >>> would >>> > be aware of, with each crash there is a 30min filesystem check, which >>> makes >>> > exploration rather time consuming. >>> > >>> > This is the most severe bug I have come across in my experience with >>> > OpenBSD. I can usually work around them, but not this time. It's at a >>> > rather bad time, because I need my system for work. >>> > >>> > There are more photos than Gmail allows me to upload. So I might have >>> to >>> > creat a gallery in google photos. >>> >>> This is due to a mistake that has been reverted. Please wait for the >>> next snapshot or build a kernel from sources. >>> >>> Cheers, >>> Martin >>> >>
