For my own use cases at least, I’ve found that when the generic config is not
good enough it’s better to just generate a config on my own the traditional way
(via make nconfig or similar) and pass it to manual-config.
> On Feb 10, 2015, at 1:56 PM, Matthias Beyer wrote:
>
> On 10-02-2015 14:56
On 10-02-2015 14:56:55, Eelco Dolstra wrote:
> Hi,
>
> On 10/02/15 14:48, Wout Mertens wrote:
>
> > Just wondering out loud with probably no actionable change:
> >
> > Why are the kernel options implemented as strings ("FOO y") instead of an
> > attribute set ({ foo = "y": })?
> >
> > Of course
Hi,
On 10/02/15 14:48, Wout Mertens wrote:
> Just wondering out loud with probably no actionable change:
>
> Why are the kernel options implemented as strings ("FOO y") instead of an
> attribute set ({ foo = "y": })?
>
> Of course that means you can easily import your own .config file as descri
Just wondering out loud with probably no actionable change:
Why are the kernel options implemented as strings ("FOO y") instead of an
attribute set ({ foo = "y": })?
Of course that means you can easily import your own .config file as
described at https://nixos.org/wiki/How_to_tweak_Linux_kernel_c
