Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 12 Oct 1995 12:30:19 -0500
From:      "Eric L. Hernes" <erich@lodgenet.com>
To:        se@zpr.uni-koeln.de (Stefan Esser)
Cc:        Eric Siegerman <erics@now.com>, current@FreeBSD.ORG
Subject:   Re: cvs commit: src/sys/i386/ibcs2 ibcs2_ioctl.h ibcs2_ipc.h  ibcs2_isc_syscall.h ibcs2_isc_sysent.c ... 
Message-ID:  <199510121730.MAA08152@jake.lodgenet.com>
In-Reply-To: Your message of "Thu, 12 Oct 1995 13:56:38 BST." <199510121256.AA10533@Sysiphos> 

next in thread | previous in thread | raw e-mail | index | archive | help
> On Oct 11, 20:07, Eric Siegerman wrote:
> } Subject: Re: cvs commit: src/sys/i386/ibcs2 ibcs2_ioctl.h ibcs2_ipc.h ibcs
> } On Oct 10, Stefan Esser wrote:
> } > [...] if just a single 
> } > directory is searched (e.g. /compat/ibcs2/lib) a mount of a System V 
> } > /usr file system on /compat/ibcs2 would not be much use. There were 
> } > other directories that contain shared libraries under 386/ix at least
> } > (I never had to work on a SCO system)
> } 
> } FYI, Xenix 2.3.4 has a shared library in /shlib/libc_s.
> 
> Thanks for the information!
> 
> It seems to strengthen my point, that 
> mounting a System V file system under 
> /compat/ibcs2 and using its bin and lib
> directories will not work in general ...

I do more work than I care to admit on SCO.
I've used Xenix, Sco Unix, and now the OpenServer5 crap.

Just as a matter of interest, how would you propose mounting
a Xenix filesystem?  Xenix doesn't have nfs, and FBSD doesn't support
Xenix (or SysV for that matter) filesystems.  You could possibly
mount a Xenix filesystem on an SCO Unix box and then nfs from there,
but if you already have an SCO machine, why do you need iBCS?

> 
> We'll need to play tricks (e.g. with 
> symlinks) to make the shared libraries 
> appear at the place where the emulation 
> code looks for them, and then I'd rather 
> choose a file system, that is suitable to 
> take a copy of those libs, in case I need
> to install them ...


I believe that BSDi traps all system calls which deal with
filenames (particularily open, maybe only open) and re-maps some of
them to the sco-filesystem layout (eg /usr/spool -> /varr/spool)
I would expect the system calls to already be trapped.
I don't know how the old SysV shared lib scheme works, for
example who loads the library etc...

> 
> Regards, STefan
> 

eric.
--
erich@lodgenet.com
erich@rrnet.com




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199510121730.MAA08152>