Date: Wed, 22 Feb 1995 18:12:51 +1100 From: Bruce Evans <bde@zeta.org.au> To: luigi@labinfo.iet.unipi.it, martin@innovus.com Cc: hackers@freefall.cdrom.com Subject: Re: cvs commit: src/sys/i386/boot/dosboot ansi.h boot.c boot.h bootinfo.h cdefs.h dinode.h dir.h dirent.h disk.c disklabe.h dkbad.h Message-ID: <199502220712.SAA00424@godzilla.zeta.org.au>
next in thread | raw e-mail | index | archive | help
>> [merging netboot with fbsdboot] >If someone goes off and does this, keep in mind that the EPROM version >has to stay less than 16K (I think it is over 15K right now). There is >"BOOTROM" define that could be used to keep the memory manager code from >being compiled for EPROM versions. How will the various boots work/be maintained when the standard bootstrap becomes multi-staged? I think I want to have a common big second stage that handles all the interfacing between the BIOS and the kernel. I think the network boot will not need to change much - it can load a second stage over the network. I don't see how the DOS boot could use this scheme. Supporting masses of DOS stuff in the second stage or doing the second stage in the DOS boot is too hard. (Doing a standard first stage is also too hard. I think the DOS boot should only support loading kernels from DOS file systems. Then it wouldn't have to duplicate so many FreeBSD headers.) Bruce
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199502220712.SAA00424>