From owner-freebsd-current Thu Oct 12 10:25:48 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA22129 for current-outgoing; Thu, 12 Oct 1995 10:25:48 -0700 Received: from spot.lodgenet.com (lodgenet.iw.net [204.157.148.88]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id KAA22045 for ; Thu, 12 Oct 1995 10:23:48 -0700 Received: from jake.lodgenet.com (jake.lodgenet.com [204.124.120.30]) by spot.lodgenet.com (8.6.12/8.6.12) with ESMTP id MAA22543; Thu, 12 Oct 1995 12:23:17 -0500 Received: from localhost (localhost [127.0.0.1]) by jake.lodgenet.com (8.6.12/8.6.12) with SMTP id MAA08152; Thu, 12 Oct 1995 12:30:20 -0500 Message-Id: <199510121730.MAA08152@jake.lodgenet.com> X-Authentication-Warning: jake.lodgenet.com: Host localhost didn't use HELO protocol X-Mailer: exmh version 1.6.2 7/18/95 To: se@zpr.uni-koeln.de (Stefan Esser) cc: Eric Siegerman , 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 ... In-reply-to: Your message of "Thu, 12 Oct 1995 13:56:38 BST." <199510121256.AA10533@Sysiphos> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 12 Oct 1995 12:30:19 -0500 From: "Eric L. Hernes" Sender: owner-current@FreeBSD.ORG Precedence: bulk > 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