Opened 19 years ago

Closed 19 years ago

#1569 closed defect (fixed)

Section 8.3.2 nitpick

Reported by: randy@… Owned by: manuel@…
Priority: lowest Milestone:
Component: Book Version: TESTING
Severity: trivial Keywords:
Cc:

Description

Perhaps a mention of the Linux-Libc-Headers package should now be mentioned in the short description of the 'kernel headers'. Now that the kernel headers from the Linux sources are not copied or even touched for that matter, it may be sensible to mention the Linux-Libc-Headers are installed in the system include directory as a reminder to folks who come back to Section 8.3.2 to update their kernel.

You guys know better than I if this is worth mentioning here.

Change History (8)

comment:1 by manuel@…, 19 years ago

This is the current text used in cross-lfs: "Defines the interface to the services that the kernel provides. The headers in the system's include directory should always be the ones against which Glibc was compiled, that is, the ones from the Linux-Libc-Headers package, and therefore, should not be replaced by the kernel headers." If that is good for trunk and testing I can merge it.

comment:2 by Matthew Burgess, 19 years ago

Sounds good to me, Manuel, thanks. And apologies for not getting around to getting that wording into trunk/testing before now. Randy, would you mind reviewing Manuel's suggested text please? If it's OK, feel free to commit it to trunk, Manuel. I'd like to see it in situ before it gets merged to testing though.

comment:3 by randy@…, 19 years ago

The more I think about it, the more I think that the whole description of the kernel headers should be removed. They are *not* installed, not any more so than the kernel documentation of other kernel source files.

Manuel's description is one line describing the kernel headers, the rest is a blurb about the Linux-Libc_Headers packages. More importantly though, is the fact that no headers are installed, so why is it even mentioned here any more?

Others may disagree, but I think it is improper to list something in the "Installed Files" section, when they hare not actually installed.

comment:4 by randy@…, 19 years ago

Oops, never did comment on the text. Is it just me or does anyone else see the singular "interface" to the services the kernel provides, perhaps should be "interfaces"?

Anyway, this is good text, however, I now firmly believe this text should be in a Note somewhere, not in the "Installed Files" section. It is important information that can help folks, however, as mentioned before it is out of place where it is now, and, a Note in a more prominent location on the page would serve to notify the readers of this important information.

comment:5 by manuel@…, 19 years ago

What about this?:

  • To remove "kernel headers" from the list of installed files.

  • To add "config-&linux-version;" to the list, plus renaming "kernel" to

"lfskernel-&kernel-version; and "System.map" to "System.map-&linux-version;".

  • To place in the same "warning" box where we are discussing about

the /usr/src/linux symlink the following text: "Also, the headers in the system's include directory should always be the ones against which Glibc was compiled, that is, the ones from the Linux-Libc-Headers package, and therefore, should not never be replaced by the kernel headers."

comment:6 by randy@…, 19 years ago

That sounds like a good plan, Manuel.

However, in the very last sentence of the note, please remove the word "not". "should never" is perfectly adequate.

Matt?

comment:7 by manuel@…, 19 years ago

Owner: changed from lfs-book@… to manuel@…

Doing the changes in unstable. About the "not", I see it after send the comment. I was adding "never" to try to match both the current kernel sources and future kernel updates.

comment:8 by manuel@…, 19 years ago

Resolution: fixed
Status: newclosed

Fixed on trunk (r6044 and r6045) and testing (r6060)

Note: See TracTickets for help on using tickets.