I've got a really old system we use for call logging. The OS is SCO 3.2
uname -a output
Code:
SCO_SV bts7053 3.2 2 i386
the problem we are having is that its no longer doing its backups. The original problem was the tape drive, which has been replaced twice now. Because the company are currently looking to replace the whole system within the next 6 months we are loathed to replace it again.
What I thought of doing was replacing the current backup script with one to dump to an NFS share on another server, however when i try
Code:
#mount -f nfs 192.168.1.45:/backup/sco /backup2
I get the response
Code:
mount: invalid fs type <nfs>
I have also tried creating an exports file with a listing to try remotely mount the directory i wish to backup but NFS doesn't seem to be installed/available
I'm pretty clued up on linux but limited with Unix so any quick pointers or help would be much appreciated....
Cheers
Last edited by johno12345; 04-25-2007 at 09:38 AM..
I have a machine A NFS mounted on machine B
I am doing a build from machine B on the MFS mounted dir of machine A but I keep getting the following:
NFS server A not responding still trying.
I go to machine A and can log onto machine A and everything seems fine.
How do I go about finding... (6 Replies)
Ok, so I have an nfs mount setup and within it there are symbolic links to other directories and such.
So anyways I created a link to a directory like so
ln -s /var/stuff/more/stuff/here/ stuff/
and i ended up with directory stuff with link 'here' inside.
so i was pieved and decided... (1 Reply)
I am having a really bad day today.
I am trying to get an nfs mount to work. I want to have a mount from machinea:/home going to /home on machineb. I can mount machinea:/home on any mount point EXCEPT /home and see the files. I can not see the files or list the directory (it hangs) when I mount... (17 Replies)
I am trying to set up an OpenSolaris box to be an NFS server.
The OpenSolaris version is 2008.11.
The kernel (uname -a output) is: SunOS minime-28 5.11 snv_101b i86pc i386 i86pc
It is running ZFS but I know nothing about ZFS.
I have an entry in the /etc/dfs/dfstab file:
share -F... (1 Reply)
I'm trying to share some directories with NFS among Debian machines. In order to do so, I installed nfs-common and nfs-kernel-server on the server machine. It seemed that starting portmap daemon lasted a long time and I get the following messages in /var/log/messages:
Jan 30 18:18:03 masternode... (26 Replies)
Hi,
I am trying to move a local directory from a local disk to a nfs disk that has been shared on another file server. I am using this tar command:
tar cf - . | (cd /export/nfsdisk && tar xpf - )
It copies the data okay but the big problem is that is resets the owner:group to 'nobody'. The... (2 Replies)
Hi,
I have two machines (AIX) each on a different VLAN.
Need to mount a filesystem using nfs on the other one.
When I export the nfs file system its a breeze. But when I try to mount it on the other machine the smitty command hangs on "running" and i get an OK from smitty but with this... (6 Replies)
Hi All,
I hoping someone can help me get my NFS working properly. I don't know why I'm having little issues... Overall, NFS is working, therefore, the problem may not be with NFS. I can ssh to remote nodes and view NFS shared directories (/home). Here is the problem, when on a node and I open a... (2 Replies)
Hi all,
i have some doubts in a situation that i fail to get an answer in Google.
I have a solaris 10 nfs server and 5 centos 6.0 nfs clients.
The problem/situation is that in the clients the free memory is "disappearing" along the time (passing to used)..and it gets free if i umount the... (5 Replies)
Hi,
I'm using Solaris 10 and OS/2 warp. There is a share on OS/2 warp which I'm trying to mount on Solaris. I get the following error message
$mount -F nfs -o rw 10.5.170.16:D:\audio /AudioSCRAFT
nfs mount: 10.5.170.16:D:audio: no applicable versions of NFS supportedAny idea how I mount the... (5 Replies)
Discussion started by: maverick_here
5 Replies
LEARN ABOUT NETBSD
compat_ibcs2
COMPAT_IBCS2(8) BSD System Manager's Manual COMPAT_IBCS2(8)NAME
compat_ibcs2 -- setup procedure for running iBCS2 binaries
DESCRIPTION
NetBSD supports running Intel Binary Compatibility Standard 2 (iBCS2) binaries. This only applies to i386 systems for now. Binaries are
supported from SCO UNIX and other systems derived from AT&T System V Release 3 UNIX. iBCS2 support is only well tested using SCO binaries.
XENIX binaries are also supported although not as well tested. SVR4 binaries are supported by the COMPAT_SVR4 option.
iBCS2 supports COFF, ELF, and x.out (XENIX) binary formats. Binaries from SCO OpenServer (version 5.x) are the only ELF binaries that have
been tested. Most programs should work, but not ones that use or depend on:
kernel internal data structures
STREAMS drivers (other than TCP/IP sockets)
local X displays (uses a STREAMS pipe)
virtual 8086 mode
The iBCS2 compatibility feature is active for kernels compiled with the COMPAT_IBCS2 option enabled. If support for iBCS2 ELF executables is
desired, the EXEC_ELF32 option should be enabled in addition to COMPAT_IBCS2.
Many COFF-format programs and most ELF-format programs are dynamically linked. This means that you will also need the shared libraries that
the program depends on. Also, you will need to create a ``shadow root'' directory for iBCS2 binaries on your NetBSD system. This directory
is named /emul/ibcs2. Any file operations done by iBCS2 programs run under NetBSD will look in this directory first. So, if an iBCS2 pro-
gram opens, for example, /etc/passwd, NetBSD will first try to open /emul/ibcs2/etc/passwd, and if that does not exist open the 'real'
/etc/passwd file. It is recommended that you install iBCS2 packages that include configuration files, etc. under /emul/ibcs2, to avoid nam-
ing conflicts with possible NetBSD counterparts. Shared libraries should also be installed in the shadow tree.
Generally, you will need to look for the shared libraries that iBCS2 binaries depend on only the first few times that you install an iBCS2
program on your NetBSD system. After a while, you will have a sufficient set of iBCS2 shared libraries on your system to be able to run
newly imported iBCS2 binaries without any extra work.
Setting up shared libraries
How to get to know which shared libraries iBCS2 binaries need, and where to get them? Depending on the file type of the executable, there are
different possibilities (when following these instructions: you will need to be root on your NetBSD system to do the necessary installation
steps).
COFF binaries You can simply copy all of the available shared libraries since they are fairly small in size. The COFF shared libraries are
typically found in /shlib and can be obtained from the following sources:
SCO UNIX version 3.x (aka ODT)
SCO UNIX version 5.x (aka OpenServer)
SCO UnixWare
Many versions of SVR4.2/x86
After copying the shared libraries, you should have at least the following files on your system:
/emul/ibcs2/shlib/libc_s
/emul/ibcs2/shlib/libnsl_s
/emul/ibcs2/shlib/protlib_s
ELF binaries You can simply copy all of the available shared libraries from the source system or distribution or use ldd(1) to determine
the libraries required by a specific binary.
After copying the shared libraries, you should have at least the following files on your system:
/emul/ibcs2/usr/lib/libc.so.1
/emul/ibcs2/usr/lib/libcrypt.so
/emul/ibcs2/usr/lib/libndbm.so
/emul/ibcs2/usr/lib/libsocket.so.1
If you don't have access to a SCO system, you will need to get the extra files you need from a SCO distribution. As of January 1998, SCO
sells a copy of SCO OpenServer (iBCS2) and/or SCO UnixWare (SVR4) for personal/non-commercial use for only the cost of shipping (about
$20US). The distribution comes on an ISO9660-format CDROM which can be mounted and used to copy the necessary files.
Run the following script to copy the basic set of files from a SCO distribution directory mounted somewhere locally:
/usr/share/examples/emul/ibcs2/ibcs2-setup [directory]
You should now be set up for SCO binaries which only need standard shared libs.
BUGS
The information about SCO distributions may become outdated.
Attempting to a use a nameserver on the local host does not currently work due to an absurd shortcut taken by the iBCS2 network code (remem-
ber that there are no kernel sockets).
16/32/64 bit offsets may not be handled correctly in all cases.
BSD February 8, 1998 BSD