Build failures for Atari ramdisk images

Martin Husemann <[email protected]> Fri, 19 Sep 2025 08:59:08 +0200
Newsgroups gmane.os.netbsd.ports.m68k
Message-ID <[email protected]>
Hey folks,

something changed in the last week (or so) in -current that killed
the Atari builds (the disk image overflows).

Anyone aware of what could have done this, or who could investigate
and fix it?

See https://releng.netbsd.org/cgi-bin/builds.cgi
and e.g. from
https://releng.netbsd.org/builds/HEAD/20250918222504Z/atari.build.failed:

Calculated size of `sysinst.fs.tmp': 1474560 bytes, 319 inodes
Extent size set to 4096
sysinst.fs.tmp: 1.4MB (2880 sectors) block size 4096, fragment size 512
	using 1 cylinder groups of 1.41MB, 360 blks, 384 inodes.
super-block backups (for fsck -b #) at:
 32,nbmakefs: Writing inode 315 (work/./usr/share/keymaps/atari/uk.map), bytes 0 + 1279: No space left on device

and this is a floppy image (I guess), so we can't make it bigger.


Martin