09-28-2006
Still supported in what context? Sun is still creating patches for it if that's what you mean.
4 More Discussions You Might Find Interesting
1. Solaris
I have compiled my application on Solaris 10 with following description
SunOS ldg1 5.10 Generic_138888-03 sun4v sparc SUNW,Sun-Blade-T6320
The compiler is Sun C++ 5.9 SunOS_sparc Patch 124863-01 2007/07/25
But when installing the application on Solaris 9
SunOS odcarch02 5.9... (2 Replies)
Discussion started by: ash_bit2k2
2 Replies
2. Solaris
Hi,
I am unable to login into my terminal hosting Solaris 10 and get the below error message
"Server refused to allocate pty
ld.so.1: sh: fatal: libc.so.1: open failed: No such file or directory "
Is there anyways i can get into my machine and what kind of changes are required to be... (7 Replies)
Discussion started by: sankasu
7 Replies
3. Solaris
Need a procedure document to do "root disk mirroring in solaris volume manager for solaris 10". I hope some one will help me asap. I need to do it production environment.
Let me know if you need any deatils on this.
Thanks,
Rama (1 Reply)
Discussion started by: ramareddi16
1 Replies
4. Solaris
Hi Gurus
I am not able to find the patching procedure for solaris 10 ( sol10 u11) to latest patchset with sun cluster having failover zones so that same I should follow.
Take an instance, there are sol1 and sol2 nodes and having two failover zones like sozone1-rg and sozone2-rg and currently... (1 Reply)
Discussion started by: nick101
1 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)