ble at:
http://anduin.linuxfromscratch.org/~bdubbs/mdadm-logs/
-- Bruce Dubbs
linuxfromscratch.org
ble at:
http://anduin.linuxfromscratch.org/~bdubbs/mdadm-logs/
-- Bruce Dubbs
linuxfromscratch.org
Karel Zak wrote:
The util-linux release v2.25 is available at
ftp://ftp.kernel.org/pub/linux/utils/util-linux/v2.25
Feedback and bug reports, as always, are welcomed.
In an LFS build environment, the configure, make, and make check are all
clean. It is especially nice the way you tell
Karel Zak wrote:
The util-linux release v2.25 is available at
ftp://ftp.kernel.org/pub/linux/utils/util-linux/v2.25
Feedback and bug reports, as always, are welcomed.
In an LFS build environment, the configure, make, and make check are all
clean. It is especially nice the way you tell
Jan Engelhardt wrote:
On Thursday 2012-09-06 21:37, Lucas De Marchi wrote:
kmod 10 is out:
ftp://ftp.kernel.org/pub/linux/utils/kernel/kmod/kmod-10.tar.xz
ftp://ftp.kernel.org/pub/linux/utils/kernel/kmod/kmod-10.tar.sign
make check fails here with glibc-2.15, gcc-4.7, x86_64,
due to what
Jan Engelhardt wrote:
On Thursday 2012-09-06 21:37, Lucas De Marchi wrote:
kmod 10 is out:
ftp://ftp.kernel.org/pub/linux/utils/kernel/kmod/kmod-10.tar.xz
ftp://ftp.kernel.org/pub/linux/utils/kernel/kmod/kmod-10.tar.sign
make check fails here with glibc-2.15, gcc-4.7, x86_64,
due to what
I some circumstances, mincore can succeed when it shouldn't.
Example:
Two files are mmapped to a process and they are adjacent in memory.
If mincore is run with a requested length that is too large, the
function does not differentiate between the different file pointers
within the different vma
I some circumstances, mincore can succeed when it shouldn't.
Example:
Two files are mmapped to a process and they are adjacent in memory.
If mincore is run with a requested length that is too large, the
function does not differentiate between the different file pointers
within the different vma
Nick Piggin wrote:
> Bruce Dubbs wrote:
>> When testing an installation with tests from the Linux Test Project, my
>> kernels fail one instance of the mincore01 tests:
>>
>> mincoremincore011 PASS : expected failure: errno = 22 (Invalid
>> argument)
>
When testing an installation with tests from the Linux Test Project, my
kernels fail one instance of the mincore01 tests:
mincoremincore011 PASS : expected failure: errno = 22 (Invalid
argument)
mincore012 PASS : expected failure: errno = 14 (Bad address)
mincore013 FAIL :
When testing an installation with tests from the Linux Test Project, my
kernels fail one instance of the mincore01 tests:
mincoremincore011 PASS : expected failure: errno = 22 (Invalid
argument)
mincore012 PASS : expected failure: errno = 14 (Bad address)
mincore013 FAIL :
Nick Piggin wrote:
Bruce Dubbs wrote:
When testing an installation with tests from the Linux Test Project, my
kernels fail one instance of the mincore01 tests:
mincoremincore011 PASS : expected failure: errno = 22 (Invalid
argument)
mincore012 PASS : expected failure: errno
12 matches
Mail list logo
