On 2022-03-12, Sven F. <sven.falem...@gmail.com> wrote: >> > Out of room? What does that even mean? Are you still using floppy disks!?
Some of the install images *are* still using these, of course. The install images are there to run the installer. If you need a more complete system for repair purposes, boot from media which has a more complete system installed onto it. For example you could install to a USB drive and boot from that. > On Sat, Mar 12, 2022 at 2:25 PM Sebastien Marie <sema...@online.fr> wrote: >> you should look at bsd.rd size instead. it is the install media, and >> it is far smaller (4.4M here). so 359K is about 8% in size. Plus libcurses, some kind of termcap file, quite likely more of libc than is already compiled into the crunchgen'd binary. As the filesystem for this is included in the install kernel, systems need to be able to boot that larger kernel. That is likely to cause problems with some machines/archs. >> if you need vi to repair your system (depending the exact problem), >> you could mount your partitions from the bsd.rd image, using something >> like (untested): >> >> # cd /dev && sh ./MAKEDEV sd0 # create sd0 nodes >> # mount -r /dev/sd0a /mnt # mount root partition (readonly) >> # chroot /mnt # chroot to /mnt >> (chroot)# mount -a # mount all partition >> > vt220 or maybe xterm if lucky or better > (chroot)# TERM=something vi or pccon
