Displaying 20 results from an estimated 200 matches similar to: "Malicious Linux modules"
2014 Sep 24
1
Error Reading from Connection
Hello,
I am running Rx64 3.03 under Windows 8 environment. I have been getting the following error.
when running some of my old R applications. Below is a mock-up example.
Could someone please help me resolve the issue?
Thanks,
Pradip Muhuri
setwd ("D:/")
>
>
> #load Rdata file
>
> load("heroin.rdata")
Error: error reading from connection
2012 Apr 11
0
mosaic 0.4 on CRAN
One of the products of Project MOSAIC (funded by an NSF CCLI grant)
has been the development of an R package with the goal of making it
easier to use R, especially in teaching situations. We're not quite
ready to declare that we've reached version 1.0, but version 0.4 does
represent a fairly large step in that direction. You can find out
more about the package on CRAN or by installing
2012 Apr 11
0
mosaic 0.4 on CRAN
One of the products of Project MOSAIC (funded by an NSF CCLI grant)
has been the development of an R package with the goal of making it
easier to use R, especially in teaching situations. We're not quite
ready to declare that we've reached version 1.0, but version 0.4 does
represent a fairly large step in that direction. You can find out
more about the package on CRAN or by installing
2006 May 30
1
max / pmax
Hello R users,
I am relatively new to R and cannot seem to crack a coding problem. I
am working with substance abuse data, and I have a variable called
"primary.drug" which is considered the drug of choice for each
subject. I have just a few missing values on that variable. Instead
of using a multiple imputation method like chained equations, I would
prefer to derive these
2002 Dec 23
1
klibc insmod for recent kernels
--9jxsPFA5p3P2qPhR
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
I stripped down the insmod command from modules-init-tools for use with
klibc.
Rusty agreed to have this contributed to klibc.
The second patch removes old style modules support.
--
ciao,
Marco
--9jxsPFA5p3P2qPhR
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment;
2017 Oct 11
1
[PATCH v1 06/27] x86/entry/64: Adapt assembly for PIE support
Change the assembly code to use only relative references of symbols for the
kernel to be PIE compatible.
Position Independent Executable (PIE) support will allow to extended the
KASLR randomization range below the -2G memory limit.
Signed-off-by: Thomas Garnier <thgarnie at google.com>
---
arch/x86/entry/entry_64.S | 22 +++++++++++++++-------
1 file changed, 15 insertions(+), 7
2017 Oct 20
0
[PATCH v1 06/27] x86/entry/64: Adapt assembly for PIE support
* Thomas Garnier <thgarnie at google.com> wrote:
> Change the assembly code to use only relative references of symbols for the
> kernel to be PIE compatible.
>
> Position Independent Executable (PIE) support will allow to extended the
> KASLR randomization range below the -2G memory limit.
>
> Signed-off-by: Thomas Garnier <thgarnie at google.com>
> ---
>
2010 Apr 04
1
Need sys_call_table exported
Hi,
As part of over writing some system calls, I need to export the
sys_call_table. Please let me know how to do this in centos 5.4 .
Thanks,
Jai
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.centos.org/pipermail/centos/attachments/20100404/c479c411/attachment-0003.html>
2003 Nov 26
1
[PATCH] use 2.6 module syscalls in klibc
I had a klibc build failure (on s390) because of include/sys/module.h
and noticed that it still has the old system call interface for 2.4
style modutils. Is there any reason to keep that in klibc?
This patch fixes the build problem by removing the old file and also
makes it possible to build module-init-tools (after some tweaking
there) against klibc.
Arnd <><
=====
2017 Oct 20
3
[PATCH v1 06/27] x86/entry/64: Adapt assembly for PIE support
On Fri, Oct 20, 2017 at 1:26 AM, Ingo Molnar <mingo at kernel.org> wrote:
>
> * Thomas Garnier <thgarnie at google.com> wrote:
>
>> Change the assembly code to use only relative references of symbols for the
>> kernel to be PIE compatible.
>>
>> Position Independent Executable (PIE) support will allow to extended the
>> KASLR randomization range
2017 Oct 20
3
[PATCH v1 06/27] x86/entry/64: Adapt assembly for PIE support
On Fri, Oct 20, 2017 at 1:26 AM, Ingo Molnar <mingo at kernel.org> wrote:
>
> * Thomas Garnier <thgarnie at google.com> wrote:
>
>> Change the assembly code to use only relative references of symbols for the
>> kernel to be PIE compatible.
>>
>> Position Independent Executable (PIE) support will allow to extended the
>> KASLR randomization range
2007 Apr 18
1
[PATCH 1/2] Transparent entry.S IRQ holdoff handling
i386 Transparent paravirtualization patch #1.
Add support for interrupt holdoff to the entry.S fault and syscall paths. This
is a straightforward macro-ization for the default sub-architecture. Note that
CLI, STI and IRET may be called with non-flat segments because guest %ds and
%es segments are live at the time. Any alternative implementation (such as a
virtual interrupt mask) is required to
2007 Apr 18
1
[PATCH 1/2] Transparent entry.S IRQ holdoff handling
i386 Transparent paravirtualization patch #1.
Add support for interrupt holdoff to the entry.S fault and syscall paths. This
is a straightforward macro-ization for the default sub-architecture. Note that
CLI, STI and IRET may be called with non-flat segments because guest %ds and
%es segments are live at the time. Any alternative implementation (such as a
virtual interrupt mask) is required to
2008 Sep 28
0
[LLVMdev] compile linux kernel
On Sep 27, 2008, at 4:34 PM, Ashish Bijlani wrote:
> Thanks for the help. I've a couple of questions though:
>
> How does LLVM deal with inline assembly?
It's been implemented piece by piece on an as-needed basis. At this
point most of the things people actually use should work. llvm-gcc
has seen the Linux kernel, so most usages in there ought to work.
The symptoms here
2008 Sep 27
2
[LLVMdev] compile linux kernel
Thanks for the help. I've a couple of questions though:
How does LLVM deal with inline assembly?
I'm trying to compile kernel and I get this error probably because
LLVM is not able to handle inline assembly. I'm using LLVM-2.3
code snippet from "arch/x86_64/kernel/asm-offsets.c"
....
#define DEFINE(sym, val) \
asm volatile("\n->" #sym " %0 "
2008 Oct 14
0
Guildwars Wifi Problem
I recently installed Guildwars and everything works fine, apart from after a short while of playing the game it seems to cause my Wireless Adapter to constantly reconnect to my wireless network until the game is closed.
Im running wine version; 0.9.60, I know that this is an old version but when i use the latest release, the game is will constantly hang and will not load at all.
I am running
2008 Sep 28
3
[LLVMdev] compile linux kernel
Thanks. I actually checked the IR code generated, it seems inline
assembly is being handled correctly. The preprocessing is also being
done correctly. Here is the asm-offsets.i file snippet..
...
builtin_offsetof(struct crypto_tfm,__crt_ctx)));
asm volatile("\n->" : : );
asm volatile("\n->" "__NR_syscall_max" " %0 " "sizeof(syscalls) - 1"
2007 Apr 18
1
[RFC, PATCH 8/24] i386 Vmi syscall assembly
Illustration of how VMI inlines are used to greatly limit the impact of code
change in low level assembler code. Spinlocks, system calls, and the fault
handling paths are affected by adding some padding bytes to convert the native
instructions into a hook point for the hypervisor to insert shim code.
These changes are sufficient to glue the Linux low level entry points to
hypervisor event
2007 Apr 18
1
[RFC, PATCH 8/24] i386 Vmi syscall assembly
Illustration of how VMI inlines are used to greatly limit the impact of code
change in low level assembler code. Spinlocks, system calls, and the fault
handling paths are affected by adding some padding bytes to convert the native
instructions into a hook point for the hypervisor to insert shim code.
These changes are sufficient to glue the Linux low level entry points to
hypervisor event
2006 Feb 18
0
Does your rkhunter do an md5 check?
I rebuilt rkhunter-1.2.8-1.noarch.rpm by using the spec and tgz from
the rkhunter site (www.rootkit.nl). (I rebuilt it using his
instructions.) However rkhunter does not do an md5 check. The box
used to have fedora and each time there were updates it would
complain that the some of the md5's don't match. I contacted the
author using his contact feature on Wednesday but he hasn't