Date: Wed, 17 Sep 1997 10:12:11 -0400 From: Robert Withrow <bwithrow@BayNetworks.COM> To: freebsd-stable@freebsd.org Cc: bwithrow@tuva.engeast Subject: Minor problems with upcomming 2.2.5 Message-ID: <199709171412.KAA09701@tuva.engeast.baynetworks.com>
next in thread | raw e-mail | index | archive | help
I have great hopes of deploying FBSD 2.2.5 widely here in this SUNOS shop.
To do this I would need to be able to have people install and run
FBSD essentially ``out of the box''. To date this has not been possible
for any prior version of FBSD due to various problems in the installation
and in the code, stimulated by our environment---the largest problem
areas have been with NFS and AMD, heavily used here.
My testing of the September 14'th releng release is very encouraging.
For one thing, it is the *first* version I have tested that has working
AMD/NFS (for our environment) out-of-the-box!
There are a few problems that I need to solve, and I hope the fixes can
be integrated into the upcomming 2.2.5 release.
1) XFree86-3.3.1 won't install using the sysinstall program, either during
or after the initial installation. I think Jordan is working on this.
2) I need the following patch to be made to rc.network. This is because
*all* of our AMD maps are in NIS. Thus my rc.conf.local has a line like
this:
amd_flags='-c 3600 -l syslog `ypcat -k amd.master`'
NOTE THE "'" quoting? That is *necessary* because NIS is not up at the
time when rc.conf.local is sourced! The patch addes the necessary extra
level of evaluation at the correct time (when AMD is being started and
NIS is already up):
*** rc.network~ Sun Sep 14 08:32:10 1997
--- rc.network Tue Sep 16 15:17:47 1997
***************
*** 186,192 ****
if [ "X${amd_enable}" = X"YES" ]; then
echo -n ' amd'
! amd -p ${amd_flags} > /var/run/amd.pid 2> /dev/null
fi
if [ "X${rwhod_enable}" = X"YES" ]; then
--- 186,192 ----
if [ "X${amd_enable}" = X"YES" ]; then
echo -n ' amd'
! eval amd -p ${amd_flags} > /var/run/amd.pid 2> /dev/null
fi
if [ "X${rwhod_enable}" = X"YES" ]; then
3) AMD uses up all process slots when it starts up in the GENERIC kernel
because, I think, our master map has about 160 mounts, with about 140 of
them being direct mounts. (I know the direct mounts suck, but I can't
change the maps, because I need to interop with the SUNOS systems.) I have
been dealing with this by building a kernel with "maxusers 30" but
it whould be nice not to require the user to do that. I can imagine
a few solutions:
a) Have AMD throttle its process creation at startup.
b) Have GENERIC go out with more process slots.
c) Find a way to have a custom kernel be installed automatically,
instead of GENERIC.
Ideas?
4) I need to have passwd and group have the NIS ditties in them. I don't
know how to cause this to happen at installation time.
5) I need to have other files be replaced at installation time with site
specific ones. I want to have this be automatic. I don't yet know how
to do this..
Thanks for any help you can offer...
--
Robert Withrow -- (+1 508 916 8256)
BWithrow@BayNetworks.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199709171412.KAA09701>