Sponsored Content
Full Discussion: Solaris Installation
Operating Systems Solaris Solaris Installation Post 302305905 by bartus11 on Friday 10th of April 2009 05:39:58 AM
Old 04-10-2009
You may also check /var/sadm/system/admin/CLUSTER file to see what package configuration was used. (To install SUNWCrnet and SUNWCreq only 1st CD is required, to install other clusters you need CDs 1,2,3,4)
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Solaris Installation

Each and every time I tried to install Solaris 8 on my Dell Dimension (Intel P II - 400 MHz processor) the system hangs up. I am not able to load the Operating System at all. The same software works on other PC(different make). If anyone has a solution, please let me know. (6 Replies)
Discussion started by: vpedditi
6 Replies

2. Solaris

Solaris installation

Hi All, Can I install solaris 9 on my desktop P3(750 MHz) machine at home? I have 256MB of RAM and 80Gb hasd disk. Can anyone tell me a proper document/link for installation? Thanks in advance. Malay Maru (1 Reply)
Discussion started by: malaymaru
1 Replies

3. Solaris

installation of Solaris: installation bypasses network config.

hello solaris friends, I've tried installing Sun Solaris 10.0, but everytime it seems to bypass the network config. screen that looks similar to this...here's the url: http://www.hup.hu/old/images/hup/Solaris/Sol10beta7/9.png I'm able to install it all the way through but I get no... (2 Replies)
Discussion started by: cadmiumgreen
2 Replies

4. Solaris

Solaris 10 Installation

Firstly, I'm still new to all the technical of OS. But I'm learning. Hence I am starting to explore Unix via Solaris 10. Today, I backed up all my files and formatted my computer. I only have one physical hard drive of about 250GB. So unpartitioned all my exisiting drives and start my... (5 Replies)
Discussion started by: Xannen
5 Replies

5. Solaris

Solaris Installation

Hi, I want to know as we can install Sun Solaris through hyperterminal,Wheather any other software is coming through which we can install sun solaris (1 Reply)
Discussion started by: manoj.solaris
1 Replies

6. Solaris

new installation Solaris

hi guys im totally new to Solaris - i can use it for some functions (like at work) but installing is a first for me - please dont flame if there are any stupid questions; allright, my set up is a gigabyte motherboard which is supposed to work (BigAdmin - HCL: Gigabyte GA-MA790GP-DS4H ) 4... (5 Replies)
Discussion started by: Landser
5 Replies

7. Solaris

Solaris installation

i want to install solaris 10 in my server ... can u please guide me.. (6 Replies)
Discussion started by: senkerth
6 Replies

8. Solaris

Solaris 10 flash installation - fatal error. Solaris installation program exited.

Not very helpful to say the least. Seems to read the flar file and go through the upgrade and then come up with this error. Any ideas? (1 Reply)
Discussion started by: psychocandy
1 Replies

9. Solaris

Installation of Solaris 10 1/13

Hi, I am doing a fresh installation of Solaris 10 1/13 on an IBM x3550 M3 server (x86). When I begin the installation it shows me failed to mount zfs, I was advised by oracle to ignore that. After the installation has finished and I reboot,I get a host of random errors after that it displays... (1 Reply)
Discussion started by: spirited67
1 Replies
pkgrm(1M)                                                                                                                                pkgrm(1M)

NAME
pkgrm - remove a package from the system SYNOPSIS
pkgrm [-nv] [-a admin] [ [-A | -M] -R root_path] [-V fs_file] [pkginst... | -Y category[,category...]] pkgrm -s spool [pkginst... | -Y category[,category...]] pkgrm will remove a previously installed or partially installed package from the system. A check is made to determine if any other packages depend on the one being removed. If a dependency exists, the action taken is defined in the admin file. The default state for the command is in interactive mode, meaning that prompt messages are given during processing to allow the administra- tor to confirm the actions being taken. Non-interactive mode can be requested with the -n option. The -s option can be used to specify the directory from which spooled packages should be removed. Certain unbundled and third-party packages are no longer entirely compatible with the latest version of pkgrm. These packages require user interaction throughout the removal and not just at the very beginning. To remove these older packages (released prior to Solaris 2.4), set the following environment variable:NONABI_SCRIPTS=TRUE pkgrm permits keyboard interaction throughout the removal as long as this environment variable is set. The following options are supported: -a admin Use the installation administration file, admin, in place of the default admin file. pkgrm first looks in the current work- ing directory for the administration file. If the specified administration file is not in the current working directory, pkgrm looks in the /var/sadm/install/admin directory for the administration file. -A Remove the package files from the client's file system, absolutely. If a file is shared with other packages, the default behavior is to not remove the file from the client's file system. -M Instruct pkgrm not to use the $root_path/etc/vfstab file for determining the client's mount points. This option assumes the mount points are correct on the server and it behaves consistently with Solaris 2.5 and earlier releases. -n Non-interactive mode. If there is a need for interaction, the command will exit. Use of this option requires that at least one package instance be named upon invocation of the command. Certain conditions must exist for a package to be removed non-interactively or a non-restrictive admin file needs to be used. -R root_path Defines the full path name of a directory to use as the root_path. All files, including package system information files, are relocated to a directory tree starting in the specified root_path. Note - The root file system of any non-global zones must not be referenced with the -R option. Doing so might damage the global zone's file system, might compromise the security of the global zone, and might damage the non-global zone's file system. See zones(5). -s spool Remove the specified package(s) from the directory spool. The default directory for spooled packages is /var/sadm/pkg. -v Trace all of the scripts that get executed by pkgrm, located in the pkginst/install directory. This option is used for debugging the procedural and non-procedural scripts. -V fs_file Specify an alternative fs_file to map the client's file systems. Used in situations where the $root_path/etc/vfstab file is non-existent or unreliable. -Y category Remove packages based on the value of the CATEGORY parameter stored in the installed or spooled package's pkginfo(4) file. No package with the CATEGORY value of system can removed from the file system with this option. The following operand is supported: pkginst Specifies the package to be removed. The format pkginst.* can be used to remove all instances of a package. The asterisk character (*) is a special character to some shells and may need to be escaped. In the C-Shell, "*" must be surrounded by single quotes (') or preceded by a backslash (). Example 1: Removing All instances of SUNWjunk From client1 The following example removes all instances of SUNWjunk from client1: example% pkgrm -R /export/root/client1 SUNWjunk* Note the caveat on the use of the -R option in the description of that option, above. The following exit values are returned: 0 Successful completion. 1 Fatal error. 2 Warning. 3 Interruption. 4 Administration. 10 Reboot after removal of all packages. 20 Reboot after removal of this package. See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ pkginfo(1), pkgmk(1), pkgparam(1), pkgproto(1), pkgtrans(1), installf(1M), pkgadd(1M), pkgask(1M), pkgchk(1M), removef(1M), admin(4),pkginfo(4), attributes(5) 6 Apr 2005 pkgrm(1M)
All times are GMT -4. The time now is 08:51 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy