I honestly think it'd be smart to pull up the Kernel Configuration section in the Index and verify that every package that has special kernel configuration hasn't had it's options moved.

We need a volunteer for that.  The current editors' plates are pretty full.

  -- Bruce


I realize you're probably looking for something more sophisticated, but I compared the documentation against the kernel menu.  I believe I found the following:


                     documentation                 kernel menu


autofs

                     Kernel automounter version 4 support (also supports v3)                        Kernel automounter support (supports v3, v4 and v5)

                     CIFS support (advanced network filesystem, SMBFS successor)              non-existent?


bluez          Should RFCOMM TTV support, Multicast Filter support, and Protocol filter support be indented for consistency?


sane - The documentation mentions Kernel Configuration but none seems to exist.  Should that be stricken from the documentation?

The kernel menu does list several modules as (NEW), which the documentation does not.  I ignored that and the modules in brackets in the documentation, which I consider a nice touch.

That's helpful.  Did you find any discrepancies in the CONFIG_* listings?  Those cna be useful in menuconfig if you are searching for an item or want to find out more info about an option.

  -- Bruce


I hope I understand your question.  Using the 4.19.6 kernel and 12/03/18 development documentation I checked all occurences of [CONFIG_*]'s not listed in the .config file generated by 'make menuconfig' and found only the following:

CONFIG_INCOMP_PAR_MOD - introduction/conventions.html
CONFIG_OPT_PAR - introduction/conventions.html
CONFIG_REQU_PAR_MOD - introduction/conventions.html
CONFIG_REQU_PAR_NMOD - introduction/conventions.html

But as those are illustrative only they're probably not a big deal.

--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to