On Wed, 2015-10-21 at 08:09 +0000, Eggert, Lars wrote: > Hi, > > I'm trying to include some loader tunables in the kernel, via the > "env" functionality described in config(5). > > When I look at the compiled kernel binary with strings(1), I see that > the tunables are compiled in. > > However, they don't seem to take any effect when booting the kernel, > and they also don't show up when running kenv(1) after boot. > > Any ideas? > > Thanks, > Lars
It took a while to get to, but now as of r293045 this should be fixed and the 'env' directive will be honored on all architectures. Be aware that the static environment completely replaces anything provided by the boot loader. That means that vfs.root.mount_from won't be set so you'll need to provide that value in your static env, or set ROOTDEVICE= in your kernel config. module_path is another one that loader(8) normally provides, and it needs to be set for kldload and things that auto-load modules (devd, mount) to work. I think this should be safe to MFC, but I tend to be lazy and do MFCing in long-delayed batches; let me know if you need it MFC'd sooner. -- Ian _______________________________________________ firstname.lastname@example.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"