> >1)
> >Does anyone have a profile which prevents packages from being
> >installed in /usr/dt, mounts /usr/dt from a server, and sets
> >up CDE as the default login interface.
> Where is the problem? Just exclude all packages for /usr/dt from the
> list of packages to install. I even installed some packeges (the
> Answerbooks) in /ab/dt. /ab is a large disk on the server containung
> all Answerbooks installed.
Yes, I know what to do conceptually. The devil's in the details.
Here's the section from the profile:
#SEC Clusters destined for /usr/dt
cluster SUNWCdtusr delete
cluster SUNWCdtrun delete
cluster SUNWCdtdev delete
#SEC Another package destined for /usr/dt
package SUNWdtcor delete
However, this package, SUNWdtcor cannot be deselected:
/usr/sbin/install.d/pfinstall -D -c /tmp/install SS5_1.05gb.prof > !
SS5_1.05gb.prof.test.out
WARNING: Cannot deselect required package (SUNWdtcor)
WARNING: SUNWxildh depends on SUNWxilrl, which is not selected
WARNING: SUNWxilow depends on SUNWxilrl, which is not selected
WARNING: SUNWxwplt depends on SUNWxilrl, which is not selected
WARNING: SUNWab2m depends on SUNWdtbas, which is not selected
WARNING: SUNWolrte depends on SUNWxilrl, which is not selected
WARNING: SUNWoldst depends on SUNWdtdmn, which is not selected
WARNING: SUNWoldte depends on SUNWdtdmn, which is not selected
WARNING: SUNWolimt depends on SUNWxilrl, which is not selected
WARNING: SUNWsregu depends on SUNWdthj, which is not selected
WARNING: SUNWsregu depends on SUNWdtdte, which is not selected
WARNING: SUNWsregu depends on SUNWdtlog, which is not selected
But if it's left in, it writes to /usr/dt:
#grep SUNWdtcor /var/sadm/install/contents
/usr/dt d none 0775 root bin SUNWdtcor SUNWab2m:base SUNWdtdte SUNWdticn
SUNWdtdst SUNWdthj:base SUNWdtim SUNWdtwm SUNWspl SUNWsregu
/usr/dt/bin d none 0775 root bin SUNWdtcor SUNWmfrun SUNWdtbas
SUNWab2m:base SUNWdtdte SUNWdtdmn SUNWdtdst SUNWdthe SUNWdthj:base
SUNWdtim SUNWdtrme SUNWdtwm SUNWsregu
/usr/dt/bin/rpc.ttdbserver=/usr/openwin/bin/rpc.ttdbserver s none
SUNWdtcor
/usr/dt/bin/rpc.ttdbserverd=/usr/openwin/bin/rpc.ttdbserverd s none
SUNWdtcor
/usr/dt/bin/tt_type_comp=/usr/openwin/bin/tt_type_comp s none SUNWdtcor
/usr/dt/bin/ttce2xdr=/usr/openwin/bin/ttce2xdr s none SUNWdtcor
/usr/dt/bin/ttcp=/usr/openwin/bin/ttcp s none SUNWdtcor
/usr/dt/bin/ttdbck=/usr/openwin/bin/ttdbck s none SUNWdtcor
/usr/dt/bin/ttmv=/usr/openwin/bin/ttmv s none SUNWdtcor
/usr/dt/bin/ttrm=/usr/openwin/bin/ttrm s none SUNWdtcor
/usr/dt/bin/ttrmdir=/usr/openwin/bin/ttrmdir s none SUNWdtcor
/usr/dt/bin/ttsession=/usr/openwin/bin/ttsession s none SUNWdtcor
/usr/dt/bin/ttsnoop=/usr/openwin/bin/ttsnoop s none SUNWdtcor
/usr/dt/bin/tttar=/usr/openwin/bin/tttar s none SUNWdtcor
/usr/dt/bin/tttrace=/usr/openwin/bin/tttrace s none SUNWdtcor
/usr/dt/lib d none 0775 root bin SUNWdtcor SUNWmfrun SUNWdtbas SUNWdtdte
SUNWdtdst SUNWdthe SUNWdtim SUNWdtwm SUNWspl SUNWsregu
/usr/dt/lib/libpam.so=/usr/lib/libpam.so s none SUNWdtcor
/usr/dt/lib/libpam.so.1=/usr/lib/libpam.so.1 s none SUNWdtcor
/usr/dt/lib/libtt.so=/usr/openwin/lib/libtt.so.2 s none SUNWdtcor
/usr/dt/lib/libtt.so.2=/usr/openwin/lib/libtt.so.2 s none SUNWdtcor
/usr/dt/lib/security d none 0775 root bin SUNWdtcor
/usr/dt/lib/security/pam_unix.so=/usr/lib/security/pam_unix.so s none
SUNWdtcor
/usr/dt/lib/security/pam_unix.so.1=/usr/lib/security/pam_unix.so.1 s
none SUNWdtcor
/usr/dt/share d none 0775 root bin SUNWdtcor SUNWmfrun SUNWdtdte
SUNWdticn SUNWdtdst SUNWdthj:docs SUNWdtwm
/usr/dt/share/include d none 0775 root bin SUNWdtcor SUNWmfrun SUNWdtdte
/usr/dt/share/include/Tt d none 0775 root bin SUNWdtcor
/usr/dt/share/include/Tt/tt_c.h=/usr/openwin/share/include/desktop/tt_c.h
s none SUNWdtcor
/usr/dt/share/include/Tt/tttk.h=/usr/openwin/share/include/desktop/tttk.h
s none SUNWdtcor
Quote:> To have CDE as the default login, you only have to install
> /etc/init.d/dtlogin and make the links /etc/rc0.d/K10dtlogin,
> /etc/rc2.d/S99dtlogin and /etc/rc1.d/K10dtlogin.
Presumably, by using:
/usr/dt/bin/dtconfig -inetd
/usr/dt/bin/dtconfig -e
So that entails mounting server:/usr/dt after preventing
everything from installing into /usr/dt on the client, right?
If you've done this, please provide an example.
Quote:> >2) >Is there a way to run the nisclient script from a profile without
> >it being interactive, so that NIS+ client can be initialized?
> >/usr/lib/nis/nisclient -v -h server -a IP -d domain
> All you need to be a NISPLUS client is to have a valit NIS_COLD_START
> file in /var/nis. You can copy your current NIS_COLD_START from your
> server into your jumpstart directory and include some code to copy it
> to /var/nis on the new system during install.
Thats all there is to it?
> 73, Mario
> --
> Institut fuer Robotik und Prozessinformatik der TU Braunschweig
> Hamburger Strasse 267, 38114 Braunschweig, Germany
--
Scott E. Chapal____________________________________________________
Database & Network Manager 912.734.4706
J.W. Jones Ecological Research Center FAX:912.734.6650
by