Displaying 4 results from an estimated 4 matches for "_syscall".
Did you mean:
vsyscall
2004 Jun 06
2
HUGE change soon coming to a klibc near you
Hold on to your hats, because the world is about to break...
I have been trying to figure out for a while now how to migrate klibc to
a 64-bit off_t, and to handle other things like getuid32(). The final
decision is that the _syscall*() macros just got to go; they aren't
flexible enough, and the hope that they would make it easier to port
between platforms hasn't worked out - they're far too often simply broken.
Thus, I have worked on a new infrastructure which uses Perl to generate
assembly stubs for the system...
2004 Aug 28
4
iSCSI root
As promised, here''s what I did to get iSCSI root running under XenU under Debian 3.1 (Sarge):
Be running linux 2.6 under XenU.
Build XenU with SCSI disk support (I did them as modules)
Get linux-iscsi 4.0.1.8 from http://sourceforge.net/projects/linux-iscsi/
Build it according to the instructions there (i found it a bit tricky) and install under your XenU
Get iscsi-init 4.0.1 from
2007 Apr 02
3
Problem with gettid() on CentOS 5/gcc 4.1.1
...It compiles
(and runs) just fine on CentOS 4.4, and I'm using gettid() as described in the
man page. I wonder if this is a problem with RHEL 5 as well, but I don't have a
system to test on. I also wonder if this is a gcc 4.1.1 issue or something
missing in CentOS 5.
The issue is that the _syscall0 macro is not defined anywhere. If I copy and
paste the following definition for _syscall0 from a CentOS 4.4 system into the
test program, it works just fine:
#define _syscall0(type,name) \
type name(void) \
{\
return syscall(__NR_##name);\
}
Has anyone else run into this problem?...
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;