Brian J. Murrell wrote:
> On Sun, 2009-12-06 at 07:52 -0800, Tom Eastep wrote:
>> Well, since kernel versions ARE of the form xx.yy.zz, I guess the proper
>> workaround is to strip this non-standard 4-part form down to 3.
>
> This seems to work:
>
> # kernel=$(printf "%2d%02d%02d\n" $(uname -r 2
On Sun, 2009-12-06 at 07:52 -0800, Tom Eastep wrote:
> Well, since kernel versions ARE of the form xx.yy.zz, I guess the proper
> workaround is to strip this non-standard 4-part form down to 3.
This seems to work:
# kernel=$(printf "%2d%02d%02d\n" $(uname -r 2> /dev/null | sed -e 's/-.*//' -e
'
Brian J. Murrell wrote:
> On Sat, 2009-12-05 at 22:14 -0800, Tom Eastep wrote:
>> I'll fix these in the next 4.4 release; think I'll wait on 4.2.
>
> OK. I will patch OpenWRT's package then.
>
> Any thoughts on any (in-)compatibilities that might arise trying to load
> a 4.4 shorewall[6]-lite f
Brian J. Murrell wrote:
> On Sat, 2009-12-05 at 22:12 -0800, Tom Eastep wrote:
>> What does 'uname -r' return on this box?
>
> As you probably suspect (but I don't blame ya for asking:
>
> # uname -r
> 2.6.30.9
Well, since kernel versions ARE of the form xx.yy.zz, I guess the proper
workaround
On Sat, 2009-12-05 at 22:14 -0800, Tom Eastep wrote:
>
> I'll fix these in the next 4.4 release; think I'll wait on 4.2.
OK. I will patch OpenWRT's package then.
Any thoughts on any (in-)compatibilities that might arise trying to load
a 4.4 shorewall[6]-lite from a 4.2 shorewall[6] machine?
b
On Sat, 2009-12-05 at 22:12 -0800, Tom Eastep wrote:
>
> What does 'uname -r' return on this box?
As you probably suspect (but I don't blame ya for asking:
# uname -r
2.6.30.9
Cheers,
b.
signature.asc
Description: This is a digitally signed message part
-
