To upgrade to "update 10" you should use Solaris installation DVD and Live Upgrade. Using pachset isn't really upgrading, as it doesn't introduce any new features, it is just patching existing stuff. Can you post output of
Hi all
I wish to undo the mirroring for root and update the Solaris version from 8 to 10. Since i am lack of knowledge and experience on this, hope you all can help me double check the step and correct me.
Existing disk groups details
root@leo # vxdg list
NAME STATE ID... (3 Replies)
Hi all
I had update a server from Solaris 8 to Solaris 10
is it the HBA driver still need to reinstall?
since i can get the driver info as below:
root@sgerpdev # fcinfo hba-port
HBA Port WWN: 21000003ba9b58a3
OS Device Name: /dev/cfg/c1
Manufacturer: QLogic Corp.
... (1 Reply)
Hi All,
I have this fix for AIX (5300-06-06-0811) and i need to install it.
How can i do this?
What are the prerequisites for this fix?
Thanks (1 Reply)
Any one know of a way to do a yum -install and draw the argument of what to install from a text file?
I have a huge list of rpms that I have to install on a bunch of machines and I would like to run one script that goes to each machine and installs all rpms in the list I have. (2 Replies)
I want to update my solaris 10 server which is currently on update 3 stage.
A new application require it to be on update 6.
What is the best way to make it update 6.
should i just install the patch or should i go for the liveupgrade??
thanks for you help in advance (3 Replies)
I am trying to build a Sun Ultra 10 with solaris 10. This computer is one of a collection that was donated to the non-profic company I work for. All media was wiped before I recieved them, so I am starting from stratch.
I downloaded the Solaris 10 ISO and burned a DVD. The computer came with a... (4 Replies)
Hello.
An update of TL from TL7 to TL8 is ending with errors :
Requisite Failures
------------------
SELECTED FILESETS: The following is a list of filesets that you asked to
install. They cannot be installed until all of their requisite filesets
are also installed. See subsequent... (4 Replies)
Hello all,
Relative AIX novice here: I'm trying to clarify the naming of AIX install vs. update media, and how best to name my lpp_sources on my NIM server.
An example:
I have two sets of DVDs from IBM (ordered via Entitled Software Support) sitting in front of me for 7100-03-04. One set... (1 Reply)
Some hackers found a security hole in macOS High Sierra and tweeted it to the world before telling Apple about the problem. You can see the details from PC Magazine's daily news here: Apple Releases Fix for MacOS High Sierra 'Root' Bug. The original story this morning was published before a patch... (6 Replies)
Discussion started by: Don Cragun
6 Replies
LEARN ABOUT SUNOS
lurename
lurename(1M) System Administration Commands lurename(1M)NAME
lurename - change the name of a boot environment
SYNOPSIS
/usr/sbin/lurename -e BE_name -n new_name [-l error_log] [-o outfile] [-X]
DESCRIPTION
The lurename command is part of a suite of commands that make up the Live Upgrade feature of the Solaris operating environment. See
live_upgrade(5) for a description of the Live Upgrade feature.
The lurename command renames the boot environment (BE) BE_name to new_name.
The string new_name must not exceed 30 characters in length and must consist only of alphanumeric characters and other ASCII characters
that are not special to the Unix shell. See the "Quoting" section of sh(1). The BE name can contain only single-byte, 8-bit characters. It
cannot contain whitespace characters. Also, new_name must be unique on the system.
A BE must have the status "complete" before you rename it. Use lustatus(1M) to determine a BE's status. Also, you cannot rename a BE that
has file systems mounted with lumount(1M) or mount(1M).
Renaming a BE is often useful when you upgrade the BE from one Solaris release to another. For example, following an operating system
upgrade, you might rename the BE solaris7 to solaris8.
The lurename command requires root privileges.
OPTIONS
The lurename command has the options listed below.
-e BE_name Name of the BE whose name you want to change.
-l error_log Error and status messages are sent to error_log, in addition to where they are sent in your current environment.
-n new_name New name of the BE. new_name must be unique on a given system.
-o outfile All command output is sent to outfile, in addition to where it is sent in your current environment.
-X Enable XML output. Characteristics of XML are defined in DTD, in /usr/share/lib/xml/dtd/lu_cli.dtd.<num>, where
<num> is the version number of the DTD file.
EXIT STATUS
The following exit values are returned:
0 Successful completion.
>0 An error occurred.
FILES
/etc/lutab
list of BEs on the system
/usr/share/lib/xml/dtd/lu_cli.dtd.<num>
Live Upgrade DTD (see -X option)
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWluu |
+-----------------------------+-----------------------------+
SEE ALSO lu(1M), luactivate(1M), lucancel(1M), lucompare(1M), lucreate(1M), lucurr(1M), ludelete(1M), ludesc(1M), lufslist(1M), lumake(1M),
lumount(1M), lustatus(1M), luupgrade(1M), lutab(4), attributes(5), live_upgrade(5)SunOS 5.10 24 Jan 2002 lurename(1M)