Date: Sat, 6 Feb 2021 17:03:12 -0600 From: Valeri Galtsev <galtsev@kicp.uchicago.edu> To: Frank Leonhardt <freebsd-doc@fjl.co.uk> Cc: Scott Bennett via freebsd-questions <freebsd-questions@freebsd.org> Subject: Re: Is there an easy way to update your own kernel? Message-ID: <ABE6D766-CCC6-4CE3-A428-ADCEF3FD745B@kicp.uchicago.edu> In-Reply-To: <2c5bec8a-aeeb-d9d2-6001-f63b97b8e90b@fjl.co.uk> References: <2c5bec8a-aeeb-d9d2-6001-f63b97b8e90b@fjl.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Feb 6, 2021, at 4:57 PM, Frank Leonhardt <freebsd-doc@fjl.co.uk> wrote: > > I suspect there's no answer to this, but I'll ask it anyway. > > I have some tweaked drivers on my server cluster. I'd like to update FreeBSD, but obviously keep my driver tweaks. I've found two ways of doing this: > > 1) Upgrade from source, copying my own driver source over the "standard" versions. > > 2) To save building everything on every machine, do a source upgrade and then copy my custom kernel into /boot (using sftp) after a binary upgrade. > The third way (which I would use) is composition of the two: build all the way you need on one machine; distribute result of build to all, and on each of machines do “make install[kernel]”. Just a thought. Valeri > I *could* split the drivers in question out of the kernel and load them dynamically, but, AFAIK, there's no way to replace an in-built kernel driver by loading an external module - you have to recompile the kernel without it or it's ignored. I'm certain this used to be the case anyway. > > Has anyone got a better way than either of the above? > > Thanks, Frank. > > > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ABE6D766-CCC6-4CE3-A428-ADCEF3FD745B>