Randy McMurchy wrote: > Andrew Beverley wrote these words on 02/07/07 11:58 CST: > >> Personally I think that's fine. Of course, it should call them >> extensions not modules to save confusion. > > Thanks for your help today. My last remark is that I call them > modules as .so files are built (these are ones just built using > the raw headers): > > -rwxr-xr-x 1 rml install 7320 Feb 7 11:21 libipt_string.so > -rwxr-xr-x 1 rml install 7806 Feb 7 11:21 libipt_recent.so > -rwxr-xr-x 1 rml install 7676 Feb 7 11:21 libipt_dccp.so > -rwxr-xr-x 1 rml install 6553 Feb 7 11:21 libipt_CLUSTERIP.so > -rwxr-xr-x 1 rml install 8064 Feb 7 11:21 libip6t_rt.so > -rwxr-xr-x 1 rml install 6685 Feb 7 11:21 libip6t_ipv6header.so > -rwxr-xr-x 1 rml install 6421 Feb 7 11:21 libip6t_hbh.so > -rwxr-xr-x 1 rml install 6536 Feb 7 11:21 libip6t_frag.so > -rwxr-xr-x 1 rml install 4728 Feb 7 11:21 libip6t_esp.so > -rwxr-xr-x 1 rml install 5941 Feb 7 11:21 libip6t_dst.so > -rwxr-xr-x 1 rml install 5557 Feb 7 11:21 libip6t_ah.so > -rwxr-xr-x 1 rml install 4802 Feb 7 11:21 libip6t_REJECT.so > > and the book over and over sort of references these files as > modules (sometimes plugins). Force of habit for me using the > term modules.
I'd call these specialized libraries. It looks like a note to the effect of "There are some additional specialized libraries that can be built if using the raw kernel headers. If you don't know what they are, you probably don't need them." -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
