[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20170805061544.GA23869@nazgul.tnic>
Date: Sat, 5 Aug 2017 08:15:44 +0200
From: Borislav Petkov <bp@...e.de>
To: Paul Menzel <pmenzel@...gen.mpg.de>
Cc: hpa@...or.com, torvalds@...ux-foundation.org, tglx@...utronix.de,
linux-kernel@...r.kernel.org, mingo@...nel.org,
peterz@...radead.org
Subject: Re: [tip:x86/microcode] x86/microcode: Document the three loading
methods
On Fri, Aug 04, 2017 at 01:24:02PM +0200, Paul Menzel wrote:
> > Gitweb: http://git.kernel.org/tip/0e3258753f8183c63bf68bd274d2cc7e71e5f402
>
> Could you the script(?) please be updated to use HTTPS URLs?
tip guys?
> Maybe it could be added, that certain bootloaders like GRUB allow to specify
> several `initrd` images. So you wouldn’t need to concatenate the file [1].
So this is the simplest script possible just to show the basic steps
that are required. Any treatise of what some bootloaders do is out of
scope as then I'm going to have to maintain a full-fledged script (there
will be other people saying, but but, on my system... ) which is going to
be pointless - distros are free to create the initrd they way they see
best. This script is an example only and the bare minimum at that.
> The *legacy* confuses me a little. Is it because `/sys` is used?
They're legacy because they're the older methods and people should try
to avoid them and concentrate on the early, initrd loading.
Thanks.
--
Regards/Gruss,
Boris.
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
--
Powered by blists - more mailing lists