Looking at


http://docs.sun.com/app/docs/doc/817...kv6ki7g?a=view

it have an example of removing a package (in this case man pages,
SUNWman) from a jumpstart install, but putting appropiate commands in
the profile.



# profile keywords profile values
# ----------------- -----------------
install_type initial_install
system_type standalone
partitioning default
filesys any 512 swap # specify size of /swap
cluster SUNWCprog
package SUNWman delete
cluster SUNWCacc



When I try this, I get an error during the jumpstart install. Here's my
comoplete profile:


# profile keywords profile values
# ----------------- -----------------
install_type initial_install
system_type standalone
partitioning explicit
filesys c1t0d0s0 10000 /
filesys c1t0d0s1 2048 swap
filesys c1t0d0s7 free /export/home
cluster SUNWCXall
# Delete Infiniband packages, which interfers with GPIB controller.
package SUNWudapltr delete
package SUNWudapltu delete
package SUNWtavor delete
package SUNWrpcib delete
package SUNWipoib delete
package SUNWib delete
package NIpcigpib add
http://www.drkirkby.co.uk/jumpstart/GPIB/ timeout 10



as you can see, I'm trying to delete the packages associated with the
Sun InfiniBand Framework, as the driver they use (called ib), happens to
be the same name National Instruments used in their GPIB driver for
Solaris.


But when I do a jumptstart install, it will not remove the packages -
see messages below.


Executing SolStart preinstall phase...
Executing begin script "install_begin"...
Begin script install_begin execution completed.

Processing profile
- Selecting cluster (SUNWCXall)
WARNING: Cannot deselect required package (SUNWudapltr)
WARNING: Cannot deselect required package (SUNWudapltu)
WARNING: Cannot deselect required package (SUNWtavor)
WARNING: Cannot deselect required package (SUNWrpcib)
WARNING: Cannot deselect required package (SUNWipoib)
WARNING: Cannot deselect required package (SUNWib)
- Selecting all disks
- Configuring boot device
- Configuring / (c1t0d0s0)
- Configuring swap (c1t0d0s1)
- Configuring /export/home (c1t0d0s7)
- Deselecting unmodified disk (c1t1d0)

Verifying disk configuration

Verifying space allocation
- Total software size: 3805.75 Mbytes

Preparing system for Solaris install

Configuring disk (c1t0d0)
- Creating Solaris disk label (VTOC)

Creating and checking UFS file systems
- Creating / (c1t0d0s0)
- Creating /export/home (c1t0d0s7)

Beginning Solaris software installation

Starting software installation


Since I've only got a couple I need to set up with these packages
removed, it is not a big hassle to do it manually, but I'd like to know
the trick to removing them.

On Mar 21, 1:34 pm, Dave <f...@coo.com> wrote:
> Looking at
>
> http://docs.sun.com/app/docs/doc/817...kv6ki7g?a=view
>
> it have an example of removing a package (in this case man pages,
> SUNWman) from a jumpstart install, but putting appropiate commands in
> the profile.
>
> # profile keywords profile values
> # ----------------- -----------------
> install_type initial_install
> system_type standalone
> partitioning default
> filesys any 512 swap # specify size of /swap
> cluster SUNWCprog
> package SUNWman delete
> cluster SUNWCacc
>
> When I try this, I get an error during the jumpstart install. Here's my
> comoplete profile:
>
> # profile keywords profile values
> # ----------------- -----------------
> install_type initial_install
> system_type standalone
> partitioning explicit
> filesys c1t0d0s0 10000 /
> filesys c1t0d0s1 2048 swap
> filesys c1t0d0s7 free /export/home
> cluster SUNWCXall
> # Delete Infiniband packages, which interfers with GPIB controller.
> package SUNWudapltr delete
> package SUNWudapltu delete
> package SUNWtavor delete
> package SUNWrpcib delete
> package SUNWipoib delete
> package SUNWib delete
> package NIpcigpib addhttp://www.drkirkby.co.uk/jumpstart/GPIB/timeout 10
>
> as you can see, I'm trying to delete the packages associated with the
> Sun InfiniBand Framework, as the driver they use (called ib), happens to
> be the same name National Instruments used in their GPIB driver for
> Solaris.
>
> But when I do a jumptstart install, it will not remove the packages -
> see messages below.
>
> Executing SolStart preinstall phase...
> Executing begin script "install_begin"...
> Begin script install_begin execution completed.
>
> Processing profile
> - Selecting cluster (SUNWCXall)
> WARNING: Cannot deselect required package (SUNWudapltr)
> WARNING: Cannot deselect required package (SUNWudapltu)
> WARNING: Cannot deselect required package (SUNWtavor)
> WARNING: Cannot deselect required package (SUNWrpcib)
> WARNING: Cannot deselect required package (SUNWipoib)
> WARNING: Cannot deselect required package (SUNWib)
> - Selecting all disks
> - Configuring boot device
> - Configuring / (c1t0d0s0)
> - Configuring swap (c1t0d0s1)
> - Configuring /export/home (c1t0d0s7)
> - Deselecting unmodified disk (c1t1d0)
>
> Verifying disk configuration
>
> Verifying space allocation
> - Total software size: 3805.75 Mbytes
>
> Preparing system for Solaris install
>
> Configuring disk (c1t0d0)
> - Creating Solaris disk label (VTOC)
>
> Creating and checking UFS file systems
> - Creating / (c1t0d0s0)
> - Creating /export/home (c1t0d0s7)
>
> Beginning Solaris software installation
>
> Starting software installation
>
> Since I've only got a couple I need to set up with these packages
> removed, it is not a big hassle to do it manually, but I'd like to know
> the trick to removing them.

hmmm.. not sure.


but you could setup a post install .sh script and add a couple of
pkgrm lines in there to remove those packages.

Dave <foo@coo.com> wrote:
> Processing profile
> - Selecting cluster (SUNWCXall)
> WARNING: Cannot deselect required package (SUNWudapltr)
> WARNING: Cannot deselect required package (SUNWudapltu)
> WARNING: Cannot deselect required package (SUNWtavor)
> WARNING: Cannot deselect required package (SUNWrpcib)
> WARNING: Cannot deselect required package (SUNWipoib)
> WARNING: Cannot deselect required package (SUNWib)

If the packages are part of the core metacluster, they cannot be
deselected.

Either modify the .clustertoc file so they're not, or run a finish
script to remove them explicitly. The second option is more
maintainable.

If you remove them at finish time, make sure you have an "admin" file
that doesn't require interaction and that you use -n.

Good luck!

--
Darren Dunham ddunham@taos.com
Senior Technical Consultant TAOS http://www.taos.com/
Got some Dr Pepper? San Francisco, CA bay area
< This line left intentionally blank to confuse you. >

Darren Dunham wrote:

> If the packages are part of the core metacluster, they cannot be
> deselected.
>
> Either modify the .clustertoc file so they're not, or run a finish
> script to remove them explicitly. The second option is more
> maintainable.
>
> If you remove them at finish time, make sure you have an "admin" file
> that doesn't require interaction and that you use -n.
>
> Good luck!
>



Where do I put the admin file? In the same directory as the post-install
script on the jumpstart server? I have several files in /usr/local/config


# ls /usr/local/config
postinstall preinstall profile rules rules.ok sysidcfg


The /usr/local/config/postinstall would I assume have something like

pkgrm -n -a ????? SUNWudapltr SUNWudapltu SUNWtavor SUNWrpcib SUNWipoib
SUNWib SUNWudapltr SUNWudapltu SUNWtavor SUNWrpcib SUNWipoib SUNWhermon
SUNWarbel SUNWrds SUNWib


(There's a few more than I said earlier, as I now realise Sun have a few
more packages which depend on SUNWib, which is the one that presents me
problems.)

Not sure exactly how to handle the admin file issue.

Dave wrote:

> pkgrm -n -a ????? SUNWudapltr SUNWudapltu SUNWtavor SUNWrpcib SUNWipoib
> SUNWib SUNWudapltr SUNWudapltu SUNWtavor SUNWrpcib SUNWipoib SUNWhermon
> SUNWarbel SUNWrds SUNWib

Em, I've copied the same onces twice there! I think the following is
what I need to remove.

pkgrm -n -a admin SUNWudapltr SUNWudapltu SUNWtavor SUNWrpcib SUNWipoib
SUNWhermon SUNWarbel SUNWrds SUNWib

but I'm not sure where to put the admin file. I assume it has to be
copied to the client, or perhaps the fact the directory is shared, it
can be accessed via NFS.

Yours, a bit confused....

On Mar 21, 4:35 pm, Dave <f...@coo.com> wrote:
> Darren Dunham wrote:
> > If the packages are part of the core metacluster, they cannot be
> > deselected.
>
> > Either modify the .clustertoc file so they're not, or run a finish
> > script to remove them explicitly. The second option is more
> > maintainable.
>
> > If you remove them at finish time, make sure you have an "admin" file
> > that doesn't require interaction and that you use -n.
>
> > Good luck!
>
> Where do I put the admin file? In the same directory as the post-install
> script on the jumpstart server? I have several files in /usr/local/config
>
> # ls /usr/local/config
> postinstall preinstall profile rules rules.ok sysidcfg
>
> The /usr/local/config/postinstall would I assume have something like
>
> pkgrm -n -a ????? SUNWudapltr SUNWudapltu SUNWtavor SUNWrpcib SUNWipoib
> SUNWib SUNWudapltr SUNWudapltu SUNWtavor SUNWrpcib SUNWipoib SUNWhermon
> SUNWarbel SUNWrds SUNWib
>
> (There's a few more than I said earlier, as I now realise Sun have a few
> more packages which depend on SUNWib, which is the one that presents me
> problems.)
>
> Not sure exactly how to handle the admin file issue.

This is a little ungly, but you don't have to mess with admin files...

PKGLIST="pkg \
pkg \
pkg"

for PKG in $PKGLIST
do
while true ; do echo "y" ; done | pkgrm ${PKG} -R /a
done

On Mar 21, 5:10 pm, ITguy <southa...@gmail.com> wrote:
> On Mar 21, 4:35 pm, Dave <f...@coo.com> wrote:
>
>
>
> > Darren Dunham wrote:
> > > If the packages are part of the core metacluster, they cannot be
> > > deselected.
>
> > > Either modify the .clustertoc file so they're not, or run a finish
> > > script to remove them explicitly. The second option is more
> > > maintainable.
>
> > > If you remove them at finish time, make sure you have an "admin" file
> > > that doesn't require interaction and that you use -n.
>
> > > Good luck!
>
> > Where do I put the admin file? In the same directory as the post-install
> > script on the jumpstart server? I have several files in /usr/local/config
>
> > # ls /usr/local/config
> > postinstall preinstall profile rules rules.ok sysidcfg
>
> > The /usr/local/config/postinstall would I assume have something like
>
> > pkgrm -n -a ????? SUNWudapltr SUNWudapltu SUNWtavor SUNWrpcib SUNWipoib
> > SUNWib SUNWudapltr SUNWudapltu SUNWtavor SUNWrpcib SUNWipoib SUNWhermon
> > SUNWarbel SUNWrds SUNWib
>
> > (There's a few more than I said earlier, as I now realise Sun have a few
> > more packages which depend on SUNWib, which is the one that presents me
> > problems.)
>
> > Not sure exactly how to handle the admin file issue.
>
> This is a little ungly, but you don't have to mess with admin files...
>
> PKGLIST="pkg \
> pkg \
> pkg"
>
> for PKG in $PKGLIST
> do
> while true ; do echo "y" ; done | pkgrm ${PKG} -R /a

while true ; do echo "y" | pkgrm ${PKG} -R /a ; done

Victor
> done

On Mar 21, 5:18 pm, victorfeng1...@yahoo.com wrote:
> On Mar 21, 5:10 pm, ITguy <southa...@gmail.com> wrote:
>
>
>
> > On Mar 21, 4:35 pm, Dave <f...@coo.com> wrote:
>
> > > Darren Dunham wrote:
> > > > If the packages are part of the core metacluster, they cannot be
> > > > deselected.
>
> > > > Either modify the .clustertoc file so they're not, or run a finish
> > > > script to remove them explicitly. The second option is more
> > > > maintainable.
>
> > > > If you remove them at finish time, make sure you have an "admin" file
> > > > that doesn't require interaction and that you use -n.
>
> > > > Good luck!
>
> > > Where do I put the admin file? In the same directory as the post-install
> > > script on the jumpstart server? I have several files in /usr/local/config
>
> > > # ls /usr/local/config
> > > postinstall preinstall profile rules rules.ok sysidcfg
>
> > > The /usr/local/config/postinstall would I assume have something like
>
> > > pkgrm -n -a ????? SUNWudapltr SUNWudapltu SUNWtavor SUNWrpcib SUNWipoib
> > > SUNWib SUNWudapltr SUNWudapltu SUNWtavor SUNWrpcib SUNWipoib SUNWhermon
> > > SUNWarbel SUNWrds SUNWib
>
> > > (There's a few more than I said earlier, as I now realise Sun have a few
> > > more packages which depend on SUNWib, which is the one that presents me
> > > problems.)
>
> > > Not sure exactly how to handle the admin file issue.
>
> > This is a little ungly, but you don't have to mess with admin files...
>
> > PKGLIST="pkg \
> > pkg \
> > pkg"
>
> > for PKG in $PKGLIST
> > do
> > while true ; do echo "y" ; done | pkgrm ${PKG} -R /a
>
> while true ; do echo "y" | pkgrm ${PKG} -R /a ; done

I take my last post back.

Victor
>
> Victor
>
> > done

ITguy wrote:

>> Not sure exactly how to handle the admin file issue.
>
> This is a little ungly, but you don't have to mess with admin files...
>
> PKGLIST="pkg \
> pkg \
> pkg"
>
> for PKG in $PKGLIST
> do
> while true ; do echo "y" ; done | pkgrm ${PKG} -R /a
> done


I'm not over keen on a "yes" response to everything, as I could come
unstuck. For example, I thought I had all the packages that depended on
SUNWib, but Sun have added a few more in update 4 of Solaris 10.

Hence whilst I'd like things to be removed with no interaction if
possible, I would like some interaction in the case of a problem.

I'm thinking the file might need to be refered to as


I've got a feeling the following might work, if the admin file is where
the rules, sysidcfg, pre and post install scripts are

pkgrm -n -a /tmp/install_config/admin SUNWudapltr SUNWudapltu SUNWtavor
SUNWrpcib SUNWipoib SUNWhermon SUNWarbel SUNWrds SUNWib


Just in the process of trying that.

Dave <foo@coo.com> wrote:
> pkgrm -n -a admin SUNWudapltr SUNWudapltu SUNWtavor SUNWrpcib SUNWipoib
> SUNWhermon SUNWarbel SUNWrds SUNWib
>
> but I'm not sure where to put the admin file. I assume it has to be
> copied to the client, or perhaps the fact the directory is shared, it
> can be accessed via NFS.

Wherever you want that is visible to the pkgrm. The INSTALL_CONFIG
directory with your profile and start/finish directories is available.
(I think that mounts on /tmp/install_config from memory....)

--
Darren Dunham ddunham@taos.com
Senior Technical Consultant TAOS http://www.taos.com/
Got some Dr Pepper? San Francisco, CA bay area
< This line left intentionally blank to confuse you. >