[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [RFR] templates://microcode.ctl/{templates}



Christian Perrier wrote:
> Your review should be sent as an answer to this mail.

> Template: microcode.ctl/check-new
...
>  These microcodes are non-free software and cannot distributed
                                                    ^be
>  within the package. They can be downloaded from the Internet (the
>  expected download size is about 300-400Kb).

> Package: microcode.ctl
...
> Description: Intel IA32/IA64 CPU Microcode Utility
>  The microcode_ctl utility is a companion to the IA32 microcode
>  driver. The utility has two uses:

This doesn't quite set things up for dropping the subject "it" on
the bullet-points.

...
>  The microcode update is volatile and needs to be uploaded on each
>  system boot, i.e. it doesn't re-flash the CPU permanently, reboot and
>  it reverts back to the old microcode. Ideally, the microcode should be
>  updated by the computer's BIOS, but most vendors do not implement that
>  behavior.

[transplanted:]
> I'm not sure that this is easy to understand, indeed. I even wonder
> whether this paragraph adds value.

The first sentence at least is useful.  Personally I'd been
wondering whether it should even incorporate a line or two from 
"http://kerneltrap.org/node/2678"; about why you might want to
perform these obscure activities! 
         
I won't anglicise the "i.e.", but "heavier" punctuation would help:

   The microcode update is volatile and needs to be uploaded on each
   system boot - i.e., it doesn't re-flash the CPU permanently; reboot,
   and it reverts back to the old microcode. [...]
-- 
JBR
Ankh kak! (Ancient Egyptian blessing)
--- ../microcode.ctl.old/debian/templates	2007-05-26 14:43:35.000000000 +0100
+++ debian/templates	2007-06-03 16:30:34.000000000 +0100
@@ -1,14 +1,14 @@
 Template: microcode.ctl/check-new
 Type: boolean
 Default: true
-_Description: Do you want to check online for new Intel CPU microcodes?
- microcode.ctl package needs the Intel microcodes to be usefull.
+_Description: Download Intel CPU microcodes now?
+ The microcode.ctl package needs the Intel microcodes for its operation.
  .
- Debian considers  these microcode non-free (microcodes are program, but
- without sources), so they cannot distributed within this package.
+ These microcodes are non-free software and cannot be distributed
+ within the package. They can be downloaded from the Internet (the
+ expected download size is about 300-400Kb).
  .
- The expected internet traffic is about 300-400Kb.
- Alternatively, you can check /usr/share/doc/microcode.ctl/README.Debian
- and download manually the microcodes or you can also run manually
- /usr/sbin/update-intel-microcode .
-
+ If you do not choose to download the microcodes now, please read
+ /usr/share/doc/microcode.ctl/README.Debian and download the needed
+ files manually or by running the '/usr/sbin/update-intel-microcode'
+ command.
--- ../microcode.ctl.old/debian/control	2007-05-26 14:43:35.000000000 +0100
+++ debian/control	2007-06-03 16:30:03.000000000 +0100
@@ -11,18 +11,16 @@
 Suggests: wget, bzip2
 Replaces: microcode-ctl
 Description: Intel IA32/IA64 CPU Microcode Utility
- The microcode_ctl utility is a companion to the IA32 microcode driver
- written by Tigran Aivazian <tigran@veritas.com>. The utility has two
- uses:
+ The microcode_ctl utility is a companion to the IA32 microcode
+ driver. The utility has two uses:
  .
- a) it decodes and sends new microcode to the kernel driver to be
-    uploaded to Intel IA32 family processors. (Pentium Pro, PII,
-    Celeron, PIII, Xeon, Pentium 4, etc.) and the Intel x86_64
-    family processors
- b) it signals the kernel driver to release any buffers it may hold
+  - it decodes and sends new microcode to the kernel driver for Intel IA32
+    family (Pentium Pro, PII, Celeron, PIII, Xeon, Pentium 4, etc.) and
+    Intel x86_64 family processors;
+  - it signals the kernel driver to release any buffers it may hold.
  .
  The microcode update is volatile and needs to be uploaded on each
- system boot i.e. it doesn't re-flash your CPU permanently, reboot and
- it reverts back to the old microcode. The ideal place to load
- microcode is in BIOS, but most vendors never update it!
-
+ system boot - i.e., it doesn't re-flash the CPU permanently; reboot,
+ and it reverts back to the old microcode. Ideally, the microcode should
+ be updated by the computer's BIOS, but most vendors do not implement
+ that behavior.
Template: microcode.ctl/check-new
Type: boolean
Default: true
_Description: Download Intel CPU microcodes now?
 The microcode.ctl package needs the Intel microcodes for its operation.
 .
 These microcodes are non-free software and cannot be distributed
 within the package. They can be downloaded from the Internet (the
 expected download size is about 300-400Kb).
 .
 If you do not choose to download the microcodes now, please read
 /usr/share/doc/microcode.ctl/README.Debian and download the needed
 files manually or by running the '/usr/sbin/update-intel-microcode'
 command.
Source: microcode.ctl
Section: contrib/utils
Priority: optional
Maintainer: Giacomo Catenazzi <cate@debian.org>
Build-Depends: debhelper (>= 5), po-debconf
Standards-Version: 3.7.2.2

Package: microcode.ctl
Architecture: i386 amd64
Depends: module-init-tools | modutils, udev | makedev (>> 2.3.1-52), po-debconf, ${shlibs:Depends}, ${misc:Depends}
Suggests: wget, bzip2
Replaces: microcode-ctl
Description: Intel IA32/IA64 CPU Microcode Utility
 The microcode_ctl utility is a companion to the IA32 microcode
 driver. The utility has two uses:
 .
  - it decodes and sends new microcode to the kernel driver for Intel IA32
    family (Pentium Pro, PII, Celeron, PIII, Xeon, Pentium 4, etc.) and
    Intel x86_64 family processors;
  - it signals the kernel driver to release any buffers it may hold.
 .
 The microcode update is volatile and needs to be uploaded on each
 system boot - i.e., it doesn't re-flash the CPU permanently; reboot,
 and it reverts back to the old microcode. Ideally, the microcode should
 be updated by the computer's BIOS, but most vendors do not implement
 that behavior.

Reply to: