10 More Discussions You Might Find Interesting
1. UNIX Desktop Questions & Answers
I use XFCE 4.10 on OpenBSD 5.3; The use of Thunar produces a core dump, if I am logged in as a user, but if I log in as root, it works fine. Obviously it is a permissions issue, but what permission on what file? (4 Replies)
Discussion started by: RichardET
4 Replies
2. BSD
I used to use x86 Linux clients for this years ago, but ceased all activity until last night. I have resurrected an old Sun Blade 100, which used to run Solaris 9, when I first owned it, in the 2003 period, but now is very much alive with 2 gig of new ram, and and extra 10 gig of drive space... (0 Replies)
Discussion started by: RichardET
0 Replies
3. AIX
Hello people,
I'm facing some problems Installing AIX in my Power server 720
Well, to tell the truth my problem is in Virtual I/O (IVM) installation.
OBSERVE THAT I DON'T HAVE A HMC! By the way: I have the latest server Firmware!
I've done all the process in ASMI, then inserted and... (1 Reply)
Discussion started by: Xscaio
1 Replies
4. Red Hat
Hello,
can someone please assist me userguide to setup simple Redhat yum Repository server with out using redhat satellite server. So all client will be pointing to this repository server to install rpm's.
Thanks, (3 Replies)
Discussion started by: bobby320
3 Replies
5. UNIX for Dummies Questions & Answers
Hi, I have mounted the Ubuntu server edition 10.10 ISO on my server under a directory media/servercd. I would like to install some services from this. I edited the sources.list file to say:
deb file:/media/servercd maverick main restricted
and it's properly mounted but when I try... (1 Reply)
Discussion started by: shadowcat
1 Replies
6. Ubuntu
Hi all,
I'm new here. I already install ubuntu 9.10 and mail server (Dovecot + Postfix + SASL + Squirrel Mail). But after login on squirrelmail. an error message appeared "Error connecting to IMAP server: localhost. 111 : Connection refused". Any solutions?
Thanks (1 Reply)
Discussion started by: dnet
1 Replies
7. Solaris
Hi,
i am trying to install Oracle 10g Companion Products on a Solaris 5.9 server.
At the end of the installation the configuration assistant fails and it's unable to start the HTTP Server.
Below is the error
opmnctl: starting opmn and all managed processes...
Failed to get IP for ... (0 Replies)
Discussion started by: saharookiedba
0 Replies
8. Linux
Hello I am trying to install VMWARE in Ubuntu 8.10 and I have two issues.
VMWARE server wants to compile modules to work with my kernel one them gives an error. What do I do:
None of the pre-built vsock modules for VMware Server is suitable for your
running kernel. Do you want this program... (1 Reply)
Discussion started by: mojoman
1 Replies
9. Red Hat
A previous post, How to get OpenJDK 6 for Red Hat Enterprise Linux 5, covered how to install OpenJDK for Fedora Extra Packages for Enterprise Linux (EPEL) 5. Now these instructions are at an even easier URL to remember:
http://openjdk.java.net/install/#fedora
These instructions cover... (0 Replies)
Discussion started by: Linux Bot
0 Replies
10. HP-UX
Hello,
We would like to perform tests on a product that my company created lately.
We don't have the right hardware for HP-UX enviornment
I've read the thred "Unix environments for MS Windows", but didn't see there a possibility to install HP-UX OS on a special compatible hardware.
We've... (4 Replies)
Discussion started by: AshkA
4 Replies
COMPAT_SVR4(8) BSD System Manager's Manual COMPAT_SVR4(8)
NAME
compat_svr4 -- setup procedure for running SVR4/iBCS2 binaries compat_svr4_32 -- setup procedure for running 32-bit SVR4/iBCS2 binaries
DESCRIPTION
NetBSD supports running SVR4/iBCS2 binaries. This code has been tested on i386 (with binaries from SCO OpenServer and XENIX), m68k (with
binaries from AMIX) and sparc (with binaries from Solaris) systems. Most programs should work, but not ones that use or depend on:
kernel internal data structures
the /proc filesystem
the ticotsord loopback RPC mechanism (NIS uses this)
sound and video interfaces
threads (ttsession uses threads)
the streams administrative driver
The SVR4 compatibility feature is active for kernels compiled with the COMPAT_SVR4 option enabled. Since support for ELF executables is
included only if the kernel is compiled with the EXEC_ELF32 or EXEC_ELF64 options enabled, kernels which include COMPAT_SVR4 should also typ-
ically include EXEC_ELF32 (for 32-bit ELF support) and/or EXEC_ELF64 (for 64-bit ELF support).
Another compatibility feature is COMPAT_SVR4_32, which allows the execution of 32-bit SVR4 binaries on a machine with a 64-bit kernel. This
requires EXEC_ELF32 and COMPAT_NETBSD32 options as well as COMPAT_SVR4. It is configured the same way as COMPAT_SVR4 but uses the
/emul/svr4_32 directory instead of /emul/svr4. But typically, /emul/svr4_32 can be made to point to /emul/svr4 if the operating system
donating the libraries has support for both 32-bit and 64-bit binaries.
Execution of 32-bit SVR4 binaries on a machine with a 32-bit kernel uses COMPAT_SVR4, not COMPAT_SVR4_32.
Most SVR4 programs are dynamically linked. This means that you will also need the shared libraries that the program depends on and the run-
time linker. Also, you will need to create a ``shadow root'' directory for SVR4 binaries on your NetBSD system. This directory is named
/emul/svr4. Any file operations done by SVR4 programs run under NetBSD will look in this directory first. So, if a SVR4 program opens, for
example, /etc/passwd, NetBSD will first try to open /emul/svr4/etc/passwd, and if that does not exist open the 'real' /etc/passwd file. It
is recommended that you install SVR4 packages that include configuration files, etc under /emul/svr4, to avoid naming conflicts with possible
NetBSD counterparts. Shared libraries should also be installed in the shadow tree.
The simplest way to set up your system for SVR4 binaries is:
1. Make the necessary directories:
(me@netbsd) mkdir -p /emul/svr4/{dev,etc}
(me@netbsd) mkdir -p /emul/svr4/usr/{bin,lib,ucblib}
(me@netbsd) mkdir -p /emul/svr4/usr/openwin/{bin,lib}
(me@netbsd) mkdir -p /emul/svr4/usr/dt/{bin,lib}
2. Copy files from an svr4 system:
(me@svr4) cd /usr/lib
(me@svr4) tar -cf - . |
rsh netbsd 'cd /emul/svr4/usr/lib && tar -xpf -'
(me@svr4) cd /usr/ucblib
(me@svr4) tar -cf - . |
rsh netbsd 'cd /emul/svr4/usr/ucblib && tar -xpf -'
If you are running openwindows:
(me@svr4) cd /usr/openwin/lib
(me@svr4) tar -cf - . |
rsh netbsd 'cd /emul/svr4/usr/openwin/lib && tar -xpf -'
(me@svr4) cd /usr/dt/lib
(me@svr4) tar -cf - . |
rsh netbsd 'cd /emul/svr4/usr/dt/lib && tar -xpf -'
3. You will also probably need the timezone files from your Solaris system, otherwise emulated binaries will run on UTC time.
(me@netbsd) mkdir -p /emul/svr4/usr/share/lib/zoneinfo
(me@netbsd) mkdir -p /emul/svr4/etc/default
(me@svr4) cd /usr/share/lib/zoneinfo
(me@solaris) tar -cf -. |
rsh netbsd 'cd /emul/svr4/usr/share/lib/zoneinfo &&
tar -xpf -'
(me@netbsd) echo TZ=US/Pacific > /emul/svr4/etc/default/init
4. Set up the configuration files and devices:
(me@netbsd) cd /usr/share/examples/emul/svr4/etc
(me@netbsd) cp netconfig nsswitch.conf /emul/svr4/etc
(me@netbsd) cp SVR4_MAKEDEV /emul/svr4/dev
(me@netbsd) cd /emul/svr4/dev && sh SVR4_MAKEDEV all
As the major number allocated for emulation of SVR4 devices may vary between NetBSD platforms, the SVR4_MAKEDEV script uses the uname(1)
command to determine the architecture the devices nodes are being created for; this can be overridden by setting the MACHINE environment
variable accordingly.
An alternative method is to mount a whole SVR4 partition in /emul/svr4 and then override with other mounts /emul/svr4/etc and /emul/svr4/dev.
BUGS
Many system calls are still not emulated. The streams emulation is incomplete (socketpair does not work yet).
Most SVR4 executables can not handle directory offset cookies > 32 bits. More recent ones, compiled for large file support (Solaris 2.6 and
up) can. With older programs, you will see the message ``svr4_getdents: dir offset too large for emulated program'' when this happens. Cur-
rently, this can only happen on NFS mounted filesystems, mounted from servers that return offsets with information in the upper 32 bits.
These errors should rarely happen, but can be avoided by mounting this filesystem with offset translation enabled. See the -X option to
mount_nfs(8). The -2 option to mount_nfs(8) will also have the desired effect, but is less preferable.
BSD
April 19, 1999 BSD