<feed xmlns='http://www.w3.org/2005/Atom'>
<title>src/sys/amd64/linux32/syscalls.conf, branch release/8.2.0</title>
<subtitle>FreeBSD source tree</subtitle>
<id>https://cgit-dev.freebsd.org/src/atom?h=release%2F8.2.0</id>
<link rel='self' href='https://cgit-dev.freebsd.org/src/atom?h=release%2F8.2.0'/>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/'/>
<updated>2006-08-15T17:25:55Z</updated>
<entry>
<title>- Remove unused sysvec variables from various syscalls.conf.</title>
<updated>2006-08-15T17:25:55Z</updated>
<author>
<name>John Baldwin</name>
<email>jhb@FreeBSD.org</email>
</author>
<published>2006-08-15T17:25:55Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=df78f6d313b6f6d3502ba351fa851fa132f513ff'/>
<id>urn:sha1:df78f6d313b6f6d3502ba351fa851fa132f513ff</id>
<content type='text'>
- Send the systrace_args files for all the compat ABIs to /dev/null for
  now.  Right now makesyscalls.sh generates a file with a hardcoded
  function name, so it wouldn't work for any of the ABIs anyway.  Probably
  the function name should be configurable via a 'systracename' variable
  and the functions should be stored in a function pointer in the sysvec
  structure.
</content>
</entry>
<entry>
<title>Add preliminary support for running 32-bit Linux binaries on amd64, enabled</title>
<updated>2004-08-16T07:55:06Z</updated>
<author>
<name>Tim J. Robbins</name>
<email>tjr@FreeBSD.org</email>
</author>
<published>2004-08-16T07:55:06Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=ea0fabbc4fcb15d10fbcaad14c405826d5eefea3'/>
<id>urn:sha1:ea0fabbc4fcb15d10fbcaad14c405826d5eefea3</id>
<content type='text'>
with the COMPAT_LINUX32 option. This is largely based on the i386 MD Linux
emulations bits, but also builds on the 32-bit FreeBSD and generic IA-32
binary emulation work.

Some of this is still a little rough around the edges, and will need to be
revisited before 32-bit and 64-bit Linux emulation support can coexist in
the same kernel.
</content>
</entry>
</feed>
