Date: Thu, 18 Sep 1997 20:53:59 +0930 From: Mike Smith <mike@smith.net.au> To: nik@iii.co.uk Cc: hackers@FreeBSD.ORG Subject: Re: Different kernels for the bindist and boot.flp? Message-ID: <199709181124.UAA00465@word.smith.net.au> In-Reply-To: Your message of "Thu, 18 Sep 1997 12:12:46 %2B0100." <19970918121246.52480@strand.iii.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
> > Ah. Does this mean that boot.flp from a current snapshot will recognise > an IDE ZIP drive at boot time (modulo any user solvable constraints like > "There must be a disk in the drive"), and let the user use it as a UFS or > DOS disk? Yes, and specifically yes, you must have a disk in and leave it in. Removing it will make Bad Things happen. > But there is also the more general problem of integrating a custom built > kernel into the rest of the installation mechanism right from the start. > Including dropping the correct kernel into /kernel. Of course, this might > turn into a bit of a no-brainer as well. No, it's actually quite hard. Due to the way the boot floppy works, you have to build a custom image with your new kernel, and then hack sysinstall to splat a new kernel image down after it's extracted the bindist. You could alternatively specify a different kernel to go in the bindist, which is relatively straightforward but slow (you have to build a release to do it). > > OTOH, it _is_ a great learning experience, and if nothing else you may > > well come out of it with some suggestions that'll make it easier for > > the next novice, so don't take this as any sort of discouragement. > > Yep. I'll be doing the install (possibly several times) later today, and > plan to write up anything out of the ordinary I need to do. Of course, it's > entirely possible that it all just works. Oh, I meant hacking the release code 8) mike
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199709181124.UAA00465>