On Thu, Oct 29, 2020 at 08:13:44AM +0100, Alexander Dahl wrote: > Am Mittwoch, 28. Oktober 2020, 18:40:58 CET schrieb Michael Olbrich: > > On Wed, Oct 28, 2020 at 09:27:35AM -0400, Jon Ringle wrote: > > > On Wed, Oct 28, 2020 at 3:59 AM Michael Olbrich > > > <m.olbr...@pengutronix.de> wrote: > > > > On Wed, Oct 28, 2020 at 08:28:11AM +0100, Michael Olbrich wrote: > > > > > On Wed, Oct 21, 2020 at 09:27:54AM +0200, Ladislav Michl wrote: > > > > > > On Tue, Oct 20, 2020 at 08:57:27AM -0400, Jon Ringle wrote: > > > > > > > On Tue, Oct 20, 2020 at 2:06 AM Ladislav Michl <ladis@linux- > mips.org> wrote: > > > > > > > > On Mon, Oct 19, 2020 at 02:32:49PM -0400, Jon Ringle wrote: > > > > > > > > > I recently updated to ptxdist-2020.10.0 for running on our > > > > > > > > > device that > > > > > > > > > has 64MB or physical ram. > > > > > > > > > With systemd-246.6 that is installed,I'm finding that systemd > > > > > > > > > daemon-reload now fails: > > > > > > > > > > > > > > > > > > $ sudo systemctl daemon-reload > > > > > > > > > Failed to reload daemon: Refusing to reload, not enough space > > > > > > > > > available on /run/systemd. Currently, 10.6M are free, but a > > > > > > > > > safety > > > > > > > > > buffer of 16.0M is enforced. > > > > > > > > Out of curiosity: What is filling up /run for you? I've always had > > > > plenty > > > > of space in /run. > > > > > > On my target, it only has 64M of DRAM. After the kernel has reserved > > > its memory, only 55.5M is available for user space. It seems that /run > > > > Huh, I haven't used a system with less than 256M of SDRAM in a long time. > > I'm living in a different filter bubble... :-) > > For the record: we still work with boards designed ten years ago with 32 MiB > RAM and run almost recent ptxdist and LTS kernel.
Good to hear that. > I assume systemd + > additional dependencies (udev, dbus, …) would make those completly unusable. So I played a bit with the qemu in DistroKit. I didn't even get any kernel output with 32M RAM.... But it boots with 64M. And with just systemd, udev and journald running, about half the memory is still free, so that would be available for applications. And maybe 5-6M is used by those three processes, if I read the number correctly. The kernel is not trimmed for such low memory usage, so I think booting with 32M RAM with systemd might be possible, but the overhead is probably too much for real use-cases. But with 64M it should be fine. > Our new boards have 128 MiB though. Nothing with graphics i guess? I usually argue, that 512M is not enough... to run chromium :-). Michael -- Pengutronix e.K. | | Steuerwalder Str. 21 | http://www.pengutronix.de/ | 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ ptxdist mailing list ptxdist@pengutronix.de To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-requ...@pengutronix.de
