On Thu, 3 Jul 2003, M. Warner Losh wrote: > In message: <20030701164231.M88547_at_root.org> > Nate Lawson <nate_at_root.org> writes: > : On Wed, 2 Jul 2003, Florian Smeets wrote: > : > I set hw.acpi.ec.burst_mode=0 in loader.conf but when i was trying to > : > chek if it was set to 0 with sysctl hw.acpi.ec.burst_mode i got : > : > > : > flo_at_lappi [~] 15 #sysctl hw.acpi.ec.burst_mode > : > sysctl: unknown oid 'hw.acpi.ec.burst_mode' > : > : It's a tunable, not a sysctl. So you can only set it in loader.conf. Are > : there any messages when you boot with that in your loader.conf? Would you > : please post a separate dmesg for that case? > > I personally think that all tunable should be read-only (or rw if > possible) sysctls... I'm still not sure why we have both mechanisms. Perhaps a useful approach would be to sweep the tree for tunables and change them to sysctls with appropriate permissions (read-only if in doubt). Then remove the tunable mechanism. Care to put together a patch? -NateReceived on Thu Jul 03 2003 - 08:28:03 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:13 UTC