03-20-2011
The most obvious difference is the architecture change. Is your application available for Solaris on x86 ?
5 More Discussions You Might Find Interesting
1. Solaris
hi, i am trying to install solaris 10 (on 4 cd's downloaded from the sun website) on my dell poweredge 2800 server. 2 xeon processors, 2GB of RAM and 2 NICS, 73 GB SCSI (maxtor ultra320, 3.5 series), i can give more details on request...
the installation crashes when trying to detect the NICS... (0 Replies)
Discussion started by: xinugeek
0 Replies
2. Filesystems, Disks and Memory
Does anybody no how to get around the fact that the Red Hat installation does not see the SCSI hard drives. It lets you manually pick the proper device, but still fails saying no drive detected (or something to that effect). I was going to install windows 2003 Server and use VMware...but again,... (1 Reply)
Discussion started by: Fatflea
1 Replies
3. UNIX for Dummies Questions & Answers
Hi
I have experienced some problems with the new monitor on my Solaris WS (Solaris5.4). Old monitor (Sony ES200) died an we installed a new one (Dell Ultrascan P780)
The system booted but the monitor statrted blinking at the rate about once in 5-7 seconds. This is espetially strange that the... (0 Replies)
Discussion started by: Andrey Malishev
0 Replies
4. Solaris
Hello,
i am trying to get following configuration up running, but get no access to the library roboter.
Server: SunOS 5.10 Generic_138889-03 i86pc i386 i86pc
DELL TL-2000: 1 Tape: IBM ULT3580-HH4 and Robot: 3573-TL,
connected via ISCSI Bridge (build into the TL)
... (1 Reply)
Discussion started by: austin73
1 Replies
5. Solaris
Hi,
I am about to try Solaris 10 on a dell power edge 1950 server. I have googled and found some articles(2007) saying its not supported. Anybody tried this recently?
Thanks in advance (2 Replies)
Discussion started by: ./hari.sh
2 Replies
LEARN ABOUT CENTOS
scmp_sys_resolver
scmp_sys_resolver(1) libseccomp Documentation scmp_sys_resolver(1)
NAME
scmp_sys_resolver - Resolve system calls
SYNOPSIS
scmp_sys_resolver [-h] [-a ARCH ] [-t] SYSCALL_NAME | SYSCALL_NUMBER
DESCRIPTION
This command resolves both system call names and numbers with respect to the given architecture supplied in the optional ARCH argument. If
the architecture is not supplied on the command line then the native architecture is used. If the "-t" argument is specified along with a
system call name, then the system call will be translated as necessary for the given architecture. The "-t" argument has no effect if a
system call number is specified.
In some combinations of architecture and system call, a negative system call number will be displayed. A negative system call number indi-
cates that the system call is not defined for the given architecture and is treated in a special manner by libseccomp depending on the
operation.
-a ARCH
The architecture to use for resolving the system call. Valid ARCH values are "x86", "x86_64", "x32", and "arm".
-t If neccessary, translate the system call name to the proper system call number, even if the system call name is different, e.g.
socket(2) on x86.
-h A simple one-line usage display.
EXIT STATUS
Returns zero on success, errno values on failure.
NOTES
The libseccomp project site, with more information and the source code repository, can be found at http://libseccomp.sf.net. This tool, as
well as the libseccomp library, is currently under development, please report any bugs at the project site or directly to the author.
AUTHOR
Paul Moore <paul@paul-moore.com>
paul@paul-moore.com 23 May 2013 scmp_sys_resolver(1)