08-07-2019
Thanks hicksd8 for your reply.
You're right, I will use ufsdump for the backup. But i thought I could break mirror in metadevice and then update the vfstab with direct partition device names so that I could boot with physical device (instead of mirror md)?
For updating to u11, what is the best approach? we don't have support subscription for this machine. Could I just apply latest (or the one that matches update-11) recommended patchset to get to the update-11?
Best,
9 More Discussions You Might Find Interesting
1. Solaris
I have Solaris 10 01/06 version on my server, but i wanna update her from my DVD-Disc to 08/07.
How i can do it ? I has try boot from disc, but don't find Upgrade function =(
Please help me anyone! (1 Reply)
Discussion started by: jess_t03
1 Replies
2. Solaris
Hi All,
I've downloaded and extracted openssh4.1 on solaris 10. When I run the install-sh, it replied with "./install-sh: no input file specified". The file is executable and been move to owner root or the rest of the files.
Why is that? Please help.
Thanks in advance,
itik (4 Replies)
Discussion started by: itik
4 Replies
3. Solaris
Hi all,
i am facing a problem. i cant update the 8 to 10. It show me the error cannot mount the root, swap, and other filesystem.
when i run # format in the normal situation, it give me the below result
# format
0. c1t0d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848>
... (12 Replies)
Discussion started by: SmartAntz
12 Replies
4. Solaris
I need to get from Solaris 10 update 2 to update 7, whats the quickest way just apply kernel patch or live upgrade?
If it is just kernel patching can i go straight from update 2 to 7 or do I have to apply each revision level patch i.e. go from update 2 to 3 to 4 etc... (2 Replies)
Discussion started by: mr_crosby
2 Replies
5. Solaris
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)
Discussion started by: uxravi
3 Replies
6. Solaris
Is it possible to "upgrade" Sol10 update 9 to update 10 by booting from the DVD? I had never even tried this until a user asked me to do it, so i tried and it just hung there after the part where it reads the rules.ok file.
Is this even possible to upgrade? or does it have to be a new install.
... (5 Replies)
Discussion started by: BG_JrAdmin
5 Replies
7. Programming
Right I have a MYSQL database with table1 with 3 columns, colA, colB and colC. I want to combine the data in the 3 columns into a 4th column names col_comb. Here's the SQL command that works:
UPDATE table1 SET `col_comb` = CONCAT( `colA` , ' - ', `colB` , ', ', `colC` );
So now I want this... (5 Replies)
Discussion started by: barrydocks
5 Replies
8. Red Hat
Hi
i want to update the BASH because of the "shell shock" vulnerability.
my RedHat 5 is clean install with the default mirror site.
when im running the command: yum update bash
im getting a message saying there is no update. you can see in the attach picture...
what am i doing wrong? is... (4 Replies)
Discussion started by: guy3145
4 Replies
9. Solaris
If anyone has any solid documents on updating Solaris 11.0 to 11.1 please share. I have been spinning my wheels for day now. I got past running the pre-update step. Rebooted the system and trying to continue with update to 11.1 using IPS repo and keeps failing with message that it can't reach... (5 Replies)
Discussion started by: fly3rs
5 Replies
LEARN ABOUT OSX
svk::command::patch
SVK::Command::Patch(3) User Contributed Perl Documentation SVK::Command::Patch(3)
NAME
SVK::Command::Patch - Manage patches
SYNOPSIS
patch --ls [--list]
patch --cat [--view] PATCHNAME
patch --regen [--regenerate] PATCHNAME
patch --up [--update] PATCHNAME
patch --apply PATCHNAME [DEPOTPATH | PATH] [-- MERGEOPTIONS]
patch --rm [--delete] PATCHNAME
OPTIONS
--depot DEPOTNAME : operate on a depot other than the default one
DESCRIPTION
To create a patch, use "commit -P" or "smerge -P". To import a patch that's sent to you by someone else, just drop it into the "patch"
directory in your local svk repository. (That's usually "~/.svk/".)
svk patches are compatible with GNU patch. Extra svk-specific metadata is stored in an encoded chunk at the end of the file.
A patch name of "-" refers to the standard input and output.
INTRODUCTION
"svk patch" command can help out on the situation where you want to maintain your patchset to a given project. It is used under the
situation that you have no direct write access to remote repository, thus "svk push" cannot be used.
Suppose you mirror project "foo" to "//mirror/foo", create a local copy on "//local/foo", and check out to "~/dev/foo". After you've done
some work, you type:
svk commit -m "Add my new feature"
to commit changes from "~/dev/foo" to "//local/foo". If you have commit access to the upstream repository, you can submit your changes
directly like this:
svk push //local/foo
Sometimes, it's useful to send a patch, rather than submit changes directly, either because you don't have permission to commit to the
upstream repository or because you don't think your changes are ready to be committed.
To create a patch containing the differences between "//local/foo" and "//mirror/foo", use this command:
svk push -P Foo //local/foo
The "-P" flag tells svk that you want to create a patch rather than push the changes to the upstream repository. "-P" takes a single flag:
a patch name. It probably makes sense to name it after the feature implemented or bug fixed by the patch. Patch files you generate will be
created in the "patch" subdirectory of your local svk repository.
Over time, other developers will make changes to project "foo". From time to time, you may need to update your patch so that it still
applies cleanly.
First, make sure your local branch is up to date with any changes made upstream:
svk pull //local/foo
Next, update your patch so that it will apply cleanly to the newest version of the upstream repository:
svk patch --update Foo
Finally, regenerate your patch to include other changes you've made on your local branch since you created or last regenerated the patch:
svk patch --regen Foo
To get a list of all patches your svk knows about, run:
svk patch --list
To see the current version of a specific patch, run:
svk patch --view Foo
When you're done with a patch and don't want it hanging around anymore, run:
svk patch --delete Foo
To apply a patch to the repository that someone else has sent you, run:
svk patch --apply - < contributed_feature.patch
perl v5.10.0 2008-08-04 SVK::Command::Patch(3)