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 <[email protected]> wrote: > > 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 that means you can easily import your own .config file as >>> described >>> at https://nixos.org/wiki/How_to_tweak_Linux_kernel_config_options, but >>> would an >>> attribute set not allow things like "if the kernel has this feature enabled, >>> install this package" or "if you enable this module the kernel must have >>> foo set >>> to one of these values"? >> >> pkgs/os-specific/linux/kernel/manual-config.nix allows passing a "config" >> attribute set containing kernel config option, e.g. >> >> config = { CONFIG_MODULES = "y"; CONFIG_FW_LOADER = "m"; }; > > Uh, nice to know! Maybe there should be an option to tell the builder > to include all "m" as "y" (Don't use modules but include the stuff > directly in the kernel). > > Would be nice for own kernels, I guess. > > --- > > Besides: Is there a documentation around how to build my own kernel > (and install it, of course) as system package? Maybe even from a local > clone of the kernel tree? > > -- > Mit freundlichen Grüßen, > Kind regards, > Matthias Beyer > > Proudly sent with mutt. > Happily signed with gnupg. > _______________________________________________ > nix-dev mailing list > [email protected] > http://lists.science.uu.nl/mailman/listinfo/nix-dev _______________________________________________ nix-dev mailing list [email protected] http://lists.science.uu.nl/mailman/listinfo/nix-dev
