06-05-2003
Yes, you would have to start from scratch. There is no way to get back to a safe state from the first attempt at the cluster patch when you were not in single user. The second/third attempts would have just totally screwed up the system.
This is something we all learn - if you search the forum for patch and single user, you will find others that have done the same thing. I've done it (after many times of it going just fine it finally bit me). Check out Info Doc 18465 on Sunsolve - here is a small portion of it:
Quote:
Step Two- Avoid More Problems Before Installation
Go to Single User Mode. This avoids so many problems in and of itself, and it the
*FIRST STEP* in the installation stage of ANY patch cluster, kernel, or firmware
patch. Often, people will be in the habit of installing when in multiuser mode, and
claim to have never had problems as a result. I understand that going to
single user mode involves down time for the system, but scheduling down time
for other activities is normal for sys admins, and patch installation should be
included in the mix of things to be done when scheduled downtime is available.
Also, this step is in the README files of every patch and patch cluster I have
spoke of, for good reason. Modifying your live kernel is not a good idea.
8 More Discussions You Might Find Interesting
1. Solaris
Hi there,
maybe one of you knows the software package tool during the installation of solaris 10. You are able to choose an installtion and customize it with pressing F4 ....
a very nice list occurs where you can select packages like apache, ssh and so on ...
Is it possible to start this... (0 Replies)
Discussion started by: drexler76
0 Replies
2. Solaris
Hi,
I want to install man pages package from solaris 10.
Solaris 10 has already been installed on my servor but I have to add the man pages packages. I search for a long time on internet this package but I didn't find a compatible one... So I downloaded Solaris 10 from Sun site to get this... (12 Replies)
Discussion started by: MasterapocA
12 Replies
3. Ubuntu
W: GPG error: http://archive.canonical.com karmic Release: Unknown error executing gpgv
W: GPG error: http://us.archive.ubuntu.com karmic Release: Unknown error executing gpgv
W: GPG error: http://us.archive.ubuntu.com karmic-updates Release: Unknown error executing gpgv
W: GPG error:... (17 Replies)
Discussion started by: CRGreathouse
17 Replies
4. UNIX for Advanced & Expert Users
Friends,
Please let meknow, How we can find the dependancies of .dstream package & .rpm package before installation ?
For AIX, We can use the inutoc . command to create the .toc file for the bff package, What about Solaris & Linux ? (0 Replies)
Discussion started by: yb4779
0 Replies
5. Debian
Hi List,
Recently I was doing some toubleshooting installing a package on a Redhat 6 machine using the the installer script which came with that package and I got an error message telling me that a file was missing indicating that I had to google for the dependancies and install them before this... (2 Replies)
Discussion started by: landossa
2 Replies
6. Emergency UNIX and Linux Support
Hello,
i have installed a package by using the command
sudo rpm -i filepackage.rpm
package filepackage is already installed
when i try to remove it, i get an error saying "is not installed":
sudo rpm -e filepackage.rpm
error: package filepackage is not installed
How can... (4 Replies)
Discussion started by: g_p
4 Replies
7. UNIX for Dummies Questions & Answers
i am not able to install anything from package manager . (2 Replies)
Discussion started by: upvan111
2 Replies
8. UNIX for Advanced & Expert Users
I came across a number of apparent tarballs of OS packages which are in a format which I do not recognize. Does anybody know which packet manager uses this format?
# ls
pkg_cfiles
pkg_data
pkg_data32
pkg_data64
pkg_info
pkg_scripts
pkg_signature
# cat pkg_info
PACKAGE=8.2... (3 Replies)
Discussion started by: fpmurphy
3 Replies
LEARN ABOUT DEBIAN
stg-squash
STG-SQUASH(1) StGit Manual STG-SQUASH(1)
NAME
stg-squash - Squash two or more patches into one
SYNOPSIS
stg squash [options] <patches>
DESCRIPTION
Squash two or more patches, creating one big patch that contains all their changes. In more detail:
1. Pop all the given patches, plus any other patches on top of them.
2. Push the given patches in the order they were given on the command line.
3. Squash the given patches into one big patch.
4. Allow the user to edit the commit message of the new patch interactively.
5. Push the other patches that were popped in step (1).
Conflicts can occur whenever we push a patch; that is, in step (2) and (5). If there are conflicts, the command will stop so that you can
resolve them.
OPTIONS
-n NAME, --name NAME
Name of squashed patch.
-m MESSAGE, --message MESSAGE
Use MESSAGE instead of invoking the editor.
-f FILE, --file FILE
Use the contents of FILE instead of invoking the editor. (If FILE is "-", write to stdout.)
--save-template FILE
Instead of running the command, just write the message template to FILE, and exit. (If FILE is "-", write to stdout.)
When driving StGit from another program, it is often useful to first call a command with --save-template, then let the user edit the
message, and then call the same command with --file.
STGIT
Part of the StGit suite - see linkman:stg[1]
StGit 03/13/2012 STG-SQUASH(1)