Problems with 1.1 AMIX

[David Miller - CATS]

In article <20983 at cbmvax.commodore.com> I wrote:
|In article <1991Apr25.055026.4278 at digibd.com> rhealey at digibd.com (Rob Healey) writes:
|: ...
|:	 4) The berkeley emulation from hell:
|:
|:	    Sigh. I have a bitch of a time with the 386 S5R4's pathetic
|:	    emulation of berkeley routines and I see it infected the 68k
|:	    code as well. I get the feeling the AT&T people who did the
|:	    Berkeley stuff never went within 2000 miles of a functioning
|:	    Berkeley system. B^(. I'll keep this short though.
|:
|:	    1) If /usr/ucb is in your path before /usr/ccs/bin you are SOL.
|:	       gcc won't work and cc produces executables that loath executing.
|:	       The fix is easy, as the man says, if it hurts when you do
|:	       that, then DON'T do that...
|:	    2) The directory functions in the berkely libs, i.e opendir and
|:	       co., don't know squat about symlinks or non-S5 file systems.
|:	       The people doing the ufs patchwork should make sure that the
|:	       regular lib's dir functions grok S5, ufs, NFS, RFS, etc. and
|:	       such and maybe fix the berkeley stuff if they have time. This
|:	       botch is common to all R4's I've seen so it's not C='s fault
|:	       per say.
|:	    3) The whole Berkeley emulation package on all R4's really needs
|:	       to be taken out into a field and shot. Rewriting it from scratch
|:	       would probably take less time than trying to fix the current
|:	       mess. B^(. Again, this is not unique to AMIX, all R4's seem
|:	       to have braindead Berkeley emulation. B^(. Probably AT&T's
|:	       little way to get you to kick the Berzerkeley habit. B^(.
|
|	       I believe that most, if not all of these will be fixed
|	       in version 2.0.

My use of "will" was a bit premature, the BSD stuff will probably be
fixed, but it's too early to tell if it will make it into 2.0 version
of Amiga UNIX.

DavidM