Just wanted to say a thank you for everyone’s comments. I’ve combined all my
replies into one mostly to sum everything up.
> On Oct 2, 2019, at 02:16, Stefan Sperling <s...@stsp.name> wrote:
> Try adding swap space.
> I have added 2GB of swap space on my alix and it has been running fine ever
> since.
My “disk” is 2GB. I don’t even have any X sets loaded as they won’t fit.
> On Oct 2, 2019, at 09:03, Olivier Cherrier <o...@symacx.com> wrote:
> On mine (only 32 MB of swap), I had to disable kernel relinking.
> Otherwise, the system more or less collapses at boot time.
Yeah, I believe I only have 32MB of swap (I chose the default disk layout oh so
long ago).
> On Oct 2, 2019, at 08:34, Joe Barnett <joe.barn...@mr72.com> wrote:
> I cannot comment on the upgrade process, but I have had zero fatal issues
> running 6.5 on my alix2d13 boards. That said, memory has been getting
> tighter with more recent OpenBSD versions, and swap (as someone else
> suggested) should help. I love these reliable boards, but they are starting
> to show their age (at least relative to how I use them with OpenBSD).
Yeah, so I’m wondering if I want to get a larger CompactFlash card and
reinstall, try and be clever and go off the reservation, or just pack in the 9
of these things I have and get an APU.
> On Oct 2, 2019, at 09:15, Stuart Henderson <s...@spacehopper.org> wrote:
> After boot, the kernel is relinked in a random order in the background
> ("/usr/libexec/reorder_kernel &" in /etc/rc).
Yes, I’m familiar with why it’s done. I was mostly wondering if I broke
something because I’ve not had this problem since I got these things (I don’t
even know how long ago), and 6.5 just killed it.
> Unfortunately the Alix doesn't have much RAM and if you have pretty
> much anything other than a minimal set of daemons running it won't
> cope well.
I’m running nsd and unbound. I can turn off smtpd. . . What I would be nice to
do is delay starting daemons until relinking is done. Regardless, I think I
have my answer about why it’s falling over.
> You can disable the reordering by removing /var/db/kernel.SHA256
> but be aware that syspatch relies on the reorder_kernel mechanism in
> order to apply kernel patches.
Good to know. I’m going to do everything I can to avoid turning off relinking,
because I want to go on the big boy rides! :-)
Sean
