Sponsored Content
Full Discussion: upgrade solaris 8 to 10
Operating Systems Solaris upgrade solaris 8 to 10 Post 302214460 by bankai on Monday 14th of July 2008 06:57:51 AM
Old 07-14-2008
I would really avoid doing an upgrade like this unless you absolutely HAVE to. The differences between solaris 8 and 10 are quite extensive.

Might be best to wipe clean and start again.
 

3 More Discussions You Might Find Interesting

1. Solaris

Solaris 9 to Solaris 10 upgrade on Sun Fire 3800

Hello there! I have Sun Fire 3800 with very old Solaris 9 and I need to perform upgrade to concurrent Solaris 10 version, preserving current OS configuration. I supose to make it using Live Upgrade, but according to Solaris Live Upgrade Software: Minimum Patch Requirements page, I need to... (5 Replies)
Discussion started by: Sapfeer
5 Replies

2. Solaris

Solaris Upgrade

Hi, Gurus. Need help: then I try to install same software on solaris, I catch this message: WARNING: Shared package SUNWjaf must be upgraded to version 8.1. WARNING: Shared package SUNWjato must be upgraded to version 2.1.4. WARNING: Shared package SUNWjmail must be upgraded to version 8.1.... (7 Replies)
Discussion started by: burdock
7 Replies

3. Solaris

Upgrade Solaris 11.1 to Solaris 11.2 beta?

Ive googled a bit, but could not find out how to upgrade to Solaris 11.2 beta, using the IPS package manager. Does anyone know how to do it? (4 Replies)
Discussion started by: kebabbert
4 Replies
WIPE(1) 							     LAM TOOLS								   WIPE(1)

NAME
wipe - Shutdown LAM. SYNTAX
wipe [-bdhv] [-n <#>] [<bhost>] OPTIONS
-b Assume local and remote shell are the same. This means that only one remote shell invocation is used to each node. If -b is not used, two remote shell invocations are used to each node. -d Turn on debugging mode. This implies -v. -h Print the command help menu. -v Be verbose. -n <#> Wipe only the first <#> nodes. DESCRIPTION
This command has been deprecated in favor of the lamhalt command. wipe should only be necessary if lamhalt fails and is unable to clean up the LAM run-time environment properly. The wipe tool terminates the LAM software on each of the machines specified in the boot schema, <bhost>. wipe is the topology tool that terminates LAM on the UNIX(tm) nodes of a multicomputer system. It invokes tkill(1) on each machine. See tkill(1) for a description of how LAM is terminated on each node. The <bhost> file is a LAM boot schema written in the host file syntax. CPU counts in the boot schema are ignored by wipe. See bhost(5). Instead of the command line, a boot schema can be specified in the LAMBHOST environment variable. Otherwise a default file, bhost.def, is used. LAM searches for <bhost> first in the local directory and then in the installation directory under etc/. wipe does not quit if a particular remote node cannot be reached or if tkill(1) fails on any node. A message is printed if either of these failures occur, in which case the user should investigate the cause of failure and, if necessary, terminate LAM by manually executing tkill(1) on the problem node(s). In extreme cases, the user may have to terminate individual LAM processes with kill(1). wipe will terminate after a limited number of nodes if the -n option is given. This is mainly intended for use by lamboot(1), which invokes wipe when a boot does not successfully complete. EXAMPLES
wipe -v mynodes Shutdown LAM on the machines described in the boot schema, mynodes. Report about important steps as they are done. FILES
$LAMHOME/etc/lam-bhost.def default boot schema file SEE ALSO
recon(1), lamboot(1), tkill(1), bhost(5), lam-helpfile(5) LAM 6.5.8 November, 2002 WIPE(1)
All times are GMT -4. The time now is 04:25 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy