Stuart Henderson wrote:
They are using code from 2008 or earlier.
My bad. Using three different OBSD machines at different levels, man gpioctl on
wrong one :(
Thanks, Stuart.
--
Jack Woehr # "I'm not lazy, I'm useless.
Box 51, Golden CO 80402 # There's a big difference."
http:/
On 2012-04-04, Jack Woehr wrote:
> Christopher Zimmermann wrote:
>> place them after the comment. "securelevel=1" is just a variable assignment,
>> which is used in /etc/rc, which sources
>> /etc/rc.securelevel.
> Thanks ... are there also undocumented flags? I have a user who is using the
> i
Christopher Zimmermann wrote:
place them after the comment. "securelevel=1" is just a variable assignment, which is used in /etc/rc, which sources
/etc/rc.securelevel.
Thanks ... are there also undocumented flags? I have a user who is using the
invocation
/usr/sbin/gpioctl -q -d /dev/gpio1 -c
On Wed, 04 Apr 2012 12:24:37 -0600
Jack Woehr wrote:
> gpioctl(8) man page says: "Only pins that have been configured at
> securelevel 0, typically during system startup, are accessible once
> the securelevel has been raised."
>
> However, /etc/rc.securelevel first says "securelevel=1" and only
gpioctl(8) man page says: "Only pins that have been configured at securelevel 0, typically during system startup, are
accessible once the securelevel has been raised."
However, /etc/rc.securelevel first says "securelevel=1" and only then "# Place local
actions here".
Should I put gpioctl stat
5 matches
Mail list logo
