| 1 |
On Mon, Jun 19, 2006 at 05:00:41PM -0700, infowolfe wrote: |
| 2 |
> >Kernel headers being the virtual/linux-headers dependency that Georgi |
| 3 |
> >mentioned. `uname -r` works, but is annoying because you can't build |
| 4 |
> >for a kernel other than the one you're running. |
| 5 |
> Which only applies to kernel modules, not things like gnupg that don't |
| 6 |
> REALLY need kernel sources in order to function. |
| 7 |
Gnupg builds it's secure memory functionality differently based on what |
| 8 |
is available from the kernel. All of the possible APIs are available in |
| 9 |
the headers, but depending on what the kernel is configured as, affects |
| 10 |
which of the APIs provide secure memory blocks. |
| 11 |
|
| 12 |
With GnuPG, it happens that on older LiveCDs, the kernel that is running |
| 13 |
from the LiveCD doesn't offer what it wants, but the one that you would |
| 14 |
be rebooting to does. |
| 15 |
|
| 16 |
Could upstream have handled it better? Yes, most definitely. Did they? |
| 17 |
No, not yet. We're stuck picking up the pieces. |
| 18 |
|
| 19 |
-- |
| 20 |
Robin Hugh Johnson |
| 21 |
E-Mail : robbat2@g.o |
| 22 |
GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85 |
Archives