I am not set up to do so, but I have examined the sources
in 1.24 (current?) and the -xdev handling code is unchanged
from what I am testing.
-- Jim
-Original Message-
From: Bastian Bittorf [mailto:bitt...@bluebottle.com]
Sent: Tuesday, December 01, 2015 11:45 AM
To: Cathey, Jim
Cc:
the busybox.net software has been languishing for quite a long time,
so i gave it a strong kick today. just about every piece of software
has been upgraded on the box including bugzilla. my various testing
looks like it still works, but if you guys notice anything weird, feel
free to let me
* Cathey, Jim [01.12.2015 20:13]:
> (in BB V1.19.4 tested on a MIPS), in that it is doing the
this version is nearly 4 years old. please test if
this still is the case with current git or stable.
bye, bastian
___
busybox mailing
On 12/01/2015 01:30 PM, Bastian Bittorf wrote:
* Anshul [01.12.2015 08:50]:
I am trying to use busybox with linux kernel.
which version of busybox exactly?
busybox-1.24.1
Thanks
Anshul Maheshwari
___
busybox
* Anshul [01.12.2015 08:50]:
> I am trying to use busybox with linux kernel.
which version of busybox exactly?
bye, bastian
___
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
The non-fancy version of the from_cpuset uses CPU_SETSIZE as if it
represents the number of bytes in the cpuset, while it is actually
the number of bits. This leads to out-of-bounds accesses on the
cpu_set_t in the big-endian case. Basically all uses of CPU_SETSIZE
have to be divided by 8. This is
Am 01.12.2015 13:41, schrieb Ari Sundholm:
> On Mon, 2015-11-30 at 18:32 +, Ari Sundholm wrote:
>> On Mon, 2015-11-30 at 15:14 +, walter harms wrote:
>>>
>>> Am 30.11.2015 15:52, schrieb Ari Sundholm:
> ...
+ range[0] = offset;
+ range[1] = length;
>>>
>>> Can you discard