Date: Mon, 20 May 2019 13:11:09 -0500 From: Tim Daneliuk <tundra@tundraware.com> To: RW <rwmaillists@googlemail.com>, freebsd-questions@freebsd.org Subject: Re: Unclear On The New MDS Patch Message-ID: <ab6a8ca9-9c5a-251d-85df-74e8a5bb7410@tundraware.com> In-Reply-To: <20190519230343.4340af09@gumby.homeunix.com> References: <db4ca28f-feed-5c71-b178-d3a750f1ed28@tundraware.com> <20190519230343.4340af09@gumby.homeunix.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 5/19/19 5:03 PM, RW via freebsd-questions wrote: > On Sun, 19 May 2019 16:10:09 -0500 > Tim Daneliuk wrote: > >> OK, so I have a confusion (nothing new there ...). I am running >> 11.3-PRE. Some questions: >> >> 1) If I put this in rc.conf: >> >> microcode_update_enable="YES" > > You need to install the package devcpu-data or the port > sysutils/devcpu-data. > > The microcode is then loaded from the rc.d script (as above) or > alternately from loader.conf. OK, that makes more sense now, thanks. What about cloud based servers like Digital Ocean FreeBSD droplets? Does microcode updating even make sense in that context since the underlying system is actually what touches the hardware? -- ---------------------------------------------------------------------------- Tim Daneliuk tundra@tundraware.com PGP Key: http://www.tundraware.com/PGP/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ab6a8ca9-9c5a-251d-85df-74e8a5bb7410>