Samuel Thibault <samuel.thiba...@gnu.org> writes: > Joshua Branson, le ven. 25 oct. 2024 22:28:30 -0400, a ecrit: >> - When I choose to upgrade the Hurd after starting i3, I patiently >> wait for the upgrade to finish. I do not use any other programs >> or switch workspaces. When I have done so in the past, many times >> the Hurd slowed to a crawl and eventually X locked up on me. > >> I am using a T43 with 1.5 Gb of RAM, so maybe the hardware with >> limited resources is to blame? > > Possibly. Personally my VMs always have at least 2GiB and I don't run > Xorg, so it can be just lack of memory. Do you have swap enabled?
I have 1 GB of swap. I just checked fstab. > The out-of-memory situation is one of the most difficult things in > computer science, and that hasn't really been that much tackled in the > Hurd, so it's not really surprising. > > Maybe passing --sync=5 to your ext2fs could help > > fsysopts / --sync=5 > > to make it flush to disk more often. I just did. The update seemed to go smoother. I'll keep you posted. > That being said, we definitely need to fix this, it's also making > buildds crawl to a halt while building some large packages. > > Samuel How do go about fixing this? I'm assuming the problem you are trying to fix is what's described in this email: https://lists.gnu.org/archive/html/bug-hurd/2009-07/msg00084.html Or maybe something else? -- Joshua Branson Sent from the Hurd
