In the latest chapter of my p10/net2/libc.so.4.4 transition...

I have spent upwards of 16 hours of the past 48, with but limited success
to show for.  Thanks to some fairly informative e-mail messages, I do have
my ifconfig and ifsetup calls, and most of my /conf files mostly configured.
I have even so much as been able to mount a few directories on my sister
LINUX machine (still running p9/net1), where I keep my X stuff.

However...

/bin/hostname -Sv still gives <machine name>: no such address

`ps -aux` shows that syslogd takes up 38% of CPU, while rpc.mountd takes 50%.
/usr/adm/syslog.* files composed a 20 MB horror that crashed my login attempts,
and forced me to grab the dusty SLS a1,a2 disks.

/bin/df just does not work with libc.so.4.4, but works fine with libc.so.4.3--
regardless of whether I use p9 or p10.

/bin/mount doesn't not work well with libc.so.4.4.  `mount` does not display
the mount table.

I do not think the DNS stuff has ever worked with my 4.4/p10.

And finally, quite recently (due to a change in configuration, I'm sure), p10
hangs after the lpd attempt, before even giving me a prompt.

I have made an attempt to retain access to my p9 setup.  However when I
try to mount a remote drive with libc.so.4.4, I get the most dreadful 
IOT/trace trap.  To fix this and other net1 incompatiblities, I must switch
back and forth between 4.4 to 4.3, and then with p9 to p10-- 
Calgon take me away.

I do not completely understand the relationship between SysV-type calls,
net2, libc.so.4.4,and the kernel.  I think it would be good thing to know 
about and maybe see in a FAQ.

Enough from me now,
Charles