mirror of
https://github.com/Zeckmathederg/glfs.git
synced 2025-01-24 15:12:11 +08:00
Package update and some rewording:
Update to fetchmail-6.4.27. Rewording about the examples in Intel microcode, they are old and that machine now runs version 0xec (although I guess they will soon stop providing newer updates for Skylake) and of course the kernel versions are way out of date.
This commit is contained in:
parent
43149b817d
commit
bfd2ba3cfc
@ -41,6 +41,16 @@
|
||||
</itemizedlist>
|
||||
</listitem>
|
||||
-->
|
||||
<listitem>
|
||||
<para>February 12th, 2022</para>
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>[ken] - Update to fetchmail-6.4.27. Fixes
|
||||
<ulink url="&blfs-ticket-root;16019">#16019</ulink>.</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>February 11th, 2022</para>
|
||||
<itemizedlist>
|
||||
|
@ -6,9 +6,9 @@
|
||||
|
||||
<!ENTITY fetchmail-download-http "&sourceforge-dl;/fetchmail/fetchmail-&fetchmail-version;.tar.xz">
|
||||
<!ENTITY fetchmail-download-ftp " ">
|
||||
<!ENTITY fetchmail-md5sum "2fc7463df373ad92420b62f9901c4527">
|
||||
<!ENTITY fetchmail-md5sum "fbeab300ed54b973066d651132e80592">
|
||||
<!ENTITY fetchmail-size "1.3 MB">
|
||||
<!ENTITY fetchmail-buildsize "16 MB including tests">
|
||||
<!ENTITY fetchmail-buildsize "17 MB including tests">
|
||||
<!ENTITY fetchmail-time "0.1 SBU including tests">
|
||||
]>
|
||||
|
||||
|
@ -661,7 +661,7 @@ to avoid building libxml2 twice, which is slow with all deps -->
|
||||
<!-- Chapter 19 -->
|
||||
<!ENTITY mailx-version "12.5">
|
||||
<!ENTITY procmail-version "3.22">
|
||||
<!ENTITY fetchmail-version "6.4.26">
|
||||
<!ENTITY fetchmail-version "6.4.27">
|
||||
<!ENTITY mutt-version "2.1.5">
|
||||
<!ENTITY alpine-version "2.21">
|
||||
|
||||
|
@ -206,7 +206,9 @@
|
||||
microcode. This must be done by navigating to <ulink url=
|
||||
'https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/releases/'/>
|
||||
and downloading the latest file there. As of this writing the most
|
||||
secure version of the microcode, for those machines which can boot it,
|
||||
<!-- at one time, some skylakes had problems with a certain revision
|
||||
secure version of the microcode, for those machines which can boot it, -->
|
||||
secure version of the microcode
|
||||
is microcode-20220207.<!-- If you have a Skylake machine, please read the
|
||||
Caution in the 'Early loading of microcode' section below.--> Extract this
|
||||
file in the normal way, the microcode is in the <filename>intel-ucode
|
||||
@ -289,10 +291,10 @@ Processor type and features --->
|
||||
<screen><userinput>dmesg | grep -e 'microcode' -e 'Linux version' -e 'Command line'</userinput></screen>
|
||||
|
||||
<para>
|
||||
This reformatted example for a machine with old microcode in its BIOS
|
||||
This old example showing the very old BIOS firmware version
|
||||
was created by temporarily booting without
|
||||
microcode, to show the current Firmware Bug messages, then the late load
|
||||
shows it being updated to revision 0xea.
|
||||
shows it being updated to revision 0xea which was current at that time.
|
||||
</para>
|
||||
|
||||
<screen><literal>[ 0.000000] Linux version 5.12.8 (lfs@leshp) (gcc (GCC) 11.1.0,
|
||||
@ -485,7 +487,7 @@ cd initrd</userinput></screen>
|
||||
|
||||
<para>
|
||||
The places and times where early loading happens are very different
|
||||
in AMD and Intel machines. First, an Intel (Skylake) example with early loading:
|
||||
in AMD and Intel machines. First, an old example of an Intel (Skylake) with early loading:
|
||||
</para>
|
||||
|
||||
<screen><literal>[ 0.000000] microcode: microcode updated early to revision 0xea, date = 2021-01-25
|
||||
|
Loading…
Reference in New Issue
Block a user