Date: Tue, 31 Oct 1995 13:15:23 +0100 (MET) From: "Georg-W. Koltermann" <gwk@racer.dkrz.de> To: freebsd-bugs@freebsd.org Cc: jkh@time.cdrom.com Subject: news from the 4MB front Message-ID: <199510311215.NAA23051@racer.dkrz.de>
next in thread | raw e-mail | index | archive | help
Last Sunday I tried to install the 951020-SNAP on the computer of my wife at home. [I had written the floppies on Friday before I knew that a new snap was being born...] The machine is a 386/25 with 4 MB, EGA, and 162 MB IDE disk. At first I got the well-known page fault in kernel mode right after the probes. I then checked the main board setup and found that remapping was disabled, leaving only 640 kB of base and 3 MB of extended RAM. I enabled remapping (that motherboard only remaps 256 kB) and tried again. Now the install menu came up just fine. I did my stuff and hit commit. The screen displayed making filesystem on wd0s2a, and that was it. On the Alt-F2 screen I found something like "vm_pageout unable to allocate swap space", scrolling on and on. When the newfs starts, a swap partition has already been designated. Why don't you enable swapping before you do the first fork? Another option might be to provide a stripped down bare-bones kernel for those desperados installing on 4 MB machines. I'll try to build such a kernel starting with BOOTMFS once I have the latest snap loaded on my other machine, which has 8 MB. After building a kernel I could then just replace /kernel on the boot.flp right? Should I also lower the size of the root MFS as much as I can? I assume I would then also have to remake the FS on the boot.flp, matching the new size? Regards, Georg-W. Koltermann, gwk@cray.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199510311215.NAA23051>