[lug] LUG Digest, Vol 202, Issue 5

[D. Stimits]

>     On 08/18/2020 10:14 AM Evelyn Mitchell <efm at tummy.com> wrote:
> 
> 
>     In looking at the docs ( https://en.wikipedia.org/wiki/Menuconfig) it appears that {} just indicates that the item can be compiled either as a module, or in kernel.
> 
Unfortunately, setting it as a module does not build. The CONFIG_ item never shows up in the ".config" despite having met all requirements. I can actually edit ".config" and enable this (fully knowing prerequisites are built) and build a working module, but I am thinking there is a bug that it does not compile (and does not show up in ".config").


>     Cool project I discovered on the way to that, is the Civil Infrastructure Platform, which is supporting 4.4 and 4.19 kernels till 2027 and 2029. They appear to be targeting small devices, likely to be found in IoT.
>     https://wiki.linuxfoundation.org/civilinfrastructureplatform/start
> 
Yes, I was asked about this by someone working on a graduate project for a small embedded device. In this case it is a 4.9 kernel, and updating to a newer release is not an option, but I suspect back porting from 4.19 may help.

>     Evelyn Mitchellhttp://tummy.com
>     , ltd.
> 
> 
> 
>     On Sat, Aug 15, 2020 at 12:00 PM < lug-request at lug.boulder.co.us mailto:lug-request at lug.boulder.co.us > wrote:
> 
>         > > Send LUG mailing list submissions to
> >                 lug at lug.boulder.co.us mailto:lug at lug.boulder.co.us
> > 
> >         To subscribe or unsubscribe via the World Wide Web, visit
> >                 http://lists.lug.boulder.co.us/mailman/listinfo/lug
> >         or, via email, send a message with subject or body 'help' to
> >                 lug-request at lug.boulder.co.us mailto:lug-request at lug.boulder.co.us
> > 
> >         You can reach the person managing the list at
> >                 lug-owner at lug.boulder.co.us mailto:lug-owner at lug.boulder.co.us
> > 
> >         When replying, please edit your Subject line so it is more specific
> >         than "Re: Contents of LUG digest..."
> > 
> > 
> >         Today's Topics:
> > 
> >            1. Kernel Options Syntax Question (D. Stimits)
> > 
> > 
> >         ----------------------------------------------------------------------
> > 
> >         Message: 1
> >         Date: Fri, 14 Aug 2020 15:47:00 -0600 (MDT)
> >         From: "D. Stimits" < stimits at comcast.net mailto:stimits at comcast.net >
> >         To: BLUG < lug at lug.boulder.co.us mailto:lug at lug.boulder.co.us >
> >         Subject: [lug] Kernel Options Syntax Question
> >         Message-ID: < 1873099316.103252.1597441620843 at connect.xfinity.com mailto:1873099316.103252.1597441620843 at connect.xfinity.com >
> >         Content-Type: text/plain; charset="utf-8"
> > 
> >         Hi,
> > 
> >         I am looking at some kernel build options for a 4.9.x series kernel on Ubuntu 18.04. In most cases the options are something one can set to module or integrated format, but in some cases the selection seems to be entirely automated. Specifically:
> >         CONFIG_NETFILTER_XT_MATCH_SCTP
> > 
> >         In the editor, instead of being able to pick "y" or "n" or "m", surrounded by either square or angle brackets ("[]" or "<>"), this is surrounded by curly brackets ("{}"). Accordingly if certain prerequisites are chosen, then this would be built as a module. As a result of having the prerequisites met, I see:
> >         {M} Netfilter Xtables support (required for ip_tables)
> > 
> >         When building this, the module is not built. It seems incorrect to edit the .config and force it to "=m", but I did this as a test. The module gets built, but is unable to insmod.
> > 
> >         Can someone tell me if I should automatically see the module built when it shows up as "{M}"? If such a module fails to build, is this a bug, or is this expected?
> > 
> >         Thanks!
> >         -------------- next part --------------
> >         An HTML attachment was scrubbed...
> >         URL: < http://lists.lug.boulder.co.us/pipermail/lug/attachments/20200814/b1e9055d/attachment-0001.html>
> > 
> >         ------------------------------
> > 
> >         Subject: Digest Footer
> > 
> >         _______________________________________________
> >         LUG mailing list
> >         LUG at lug.boulder.co.us mailto:LUG at lug.boulder.co.us
> >         http://lists.lug.boulder.co.us/mailman/listinfo/lug
> > 
> > 
> >         ------------------------------
> > 
> >         End of LUG Digest, Vol 202, Issue 5
> >         ***********************************
> > 
> >     >     _______________________________________________
>     Web Page: http://lug.boulder.co.us
>     Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
>     Join us on IRC: irc.hackingsociety.org port=6667 channel=#hackingsociety
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lug.boulder.co.us/pipermail/lug/attachments/20200818/1174328f/attachment.html>