09-19-2012
Hmmmm! M5000 ??
More questions I'm afraid.....
What version of firmware is on the box? (I'm thinking many patch operations can fall over due to out-of-date firmware.)
What is the QLogic card exactly? (I'm thinking do you need patch 125166-10 to make it work?)
What is the Emulex card exactly? (I'm thinking to you need patch 120222-26 to make it work?)
Which card is the library connected to anyway?
I'm not convinced we know enough to pass judgement yet.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I picked up this library but I cannot get the device to actuate.
How do I make this work with Solaris 7? (2 Replies)
Discussion started by: n9ninchd
2 Replies
2. HP-UX
Hi All,
Hoping that you'll be able to help out on - I've a problem occuring in our backups that's driving me up the wall.
I've got an HP-UX Visualise 6500 as below:
================================
root # uname -a
HP-UX <NAME> B.11.00 A 9000/785 2005956095 two-user license... (2 Replies)
Discussion started by: geralex
2 Replies
3. AIX
Hello every body, I have one tape library 3583 but I can't install this some body have ben installed??
when I tray to install it, the output is the next:
Method error (/etc/methods/cfgAtape):
0514-022 The specified connection is not valid.
some Idea??
thanks
greetings (5 Replies)
Discussion started by: xanatos
5 Replies
4. AIX
I am having my 14 Aix 5.3 servers on bladecenters connected with my Tape Library.
I had a backup scheduled on tape library but after taking backup successfully,
Now,
Question 1:-
I wanted to restore backup but tape library could not recognize the tape and I get I/O error in TSM. I think it... (0 Replies)
Discussion started by: Shrek
0 Replies
5. Solaris
Hi all ,
Anybody has an installation manual for Sun StorageTek C4 tape library . i am trying to do the installation on a Sun Fire V245 .
Thanks a million
cheers
ppass (4 Replies)
Discussion started by: ppass
4 Replies
6. Solaris
Env:
Server : Sparc Ultra-80
OS: Solaris 10
Direct SCSI connection to Library. Terminator connected at the Tape End.
Problem: Unable to see any device file related to Robotic /dev/rsst0.
Unable to see any device file /dev/rmt.
------------
Messages while the machine boots
sst0: No... (3 Replies)
Discussion started by: amqstam
3 Replies
7. Solaris
Hello,
i am trying to get following configuration up running, but get no access to the library roboter.
Server: SunOS 5.10 Generic_138889-03 i86pc i386 i86pc
DELL TL-2000: 1 Tape: IBM ULT3580-HH4 and Robot: 3573-TL,
connected via ISCSI Bridge (build into the TL)
... (1 Reply)
Discussion started by: austin73
1 Replies
8. Solaris
I am a solaris noob. I have a SPARC enterprise T5120 server which i am trying to connect 1 StorEdge 3300 and 1 StorageWorks MSL2024 tape library. Each device is connecting to 1 pci card on the server. I can see the array when i run the format command but i can't seem to detect the tape library.
... (2 Replies)
Discussion started by: M_Owen
2 Replies
9. Solaris
Hi,
Our environment is SUN Solaris. We have purchased HP EML 103e tape library. Can you please let me know do I need to install any Driver of newly added Tape Library to see from the Solaris Host? or how can i see the tape library from my Solaris hosts.
Thanks,
Hassan (0 Replies)
Discussion started by: M_Hassan
0 Replies
10. 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 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)