Re: Updated ec-burst.diff patch

From: John Baldwin <jhb_at_FreeBSD.org>
Date: Thu, 03 Jul 2003 13:32:57 -0400 (EDT)
On 03-Jul-2003 Nate Lawson wrote:
> 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?
 
Cause you can't set sysctl's from the loader, only tunables?  Are you
going to duplicate the entire kernel environment from 'kenv' in
sysctl?

-- 

John Baldwin <jhb_at_FreeBSD.org>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/
Received on Thu Jul 03 2003 - 08:32:52 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:13 UTC