01-27-2014
Could you sell the Sparc and get an x86 machine instead? Even a slow x86 is going to be faster than running anything in full emulation.
8 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I still haven't got an answer to this question...
Excerpt from My SysAd Blog
A colleague of mine is having a problem with a Sun Fire v1280 server crashing. He tried Googling for the error message in red but hasn't found anything yet. Your insights would be greatly appreciated.
"cannot... (2 Replies)
Discussion started by: esofthub
2 Replies
2. UNIX for Dummies Questions & Answers
Hello all,
I'm lost and can't figure this problem out.
I have a Sun fire 280R running Solaris 8. Everything was working great. I have one drive in bay 1(not 0). But when I reboot the system it trys to open files in /dev/rdsk/c1t1d0s0. Should it have been opeing /dev/rdsk/c1t0d0s0, the... (4 Replies)
Discussion started by: larryase
4 Replies
3. Solaris
Hello,
I hope you can help me. I am new to Sun servers and we have a Sun Fire v440 server in which one power supply failed, we are waiting for new one. But now our server is shutting down constantly. Is there any setting with which we can prevent this behaviour? (1 Reply)
Discussion started by: Tibor
1 Replies
4. Solaris
I am new to Sun.
I brought Sun Fire 280R to practice UNIX. What are the requirements for the monitor/CRT? Will it burn out old non-Sun CRTs? Does it need LCD monitor?
Thanks. (3 Replies)
Discussion started by: bramptonmt
3 Replies
5. Solaris
Dear Team,
I need some expert advice to my problem.
We have a Sun Fire v440 in our customer Place. Server is working fine and no hardware deviations are found except one problem that processors generating too much heat. I have verified and found that the room temperature was 26-27 degree.... (5 Replies)
Discussion started by: sudhansu
5 Replies
6. Hardware
Can be Installed WMware EXSi on Sun Fire 445 sparc?
I need to virtualize VMware EXSi on Sun Fire 445 for implement Windows, I can do? (2 Replies)
Discussion started by: abelop
2 Replies
7. Solaris
I switched on the power to the server. But, the server did not power on i.e., none of the 3 LEDs on the front panel is lighted.
(Power supplies are showing only amber LEDs with "Ready to remove" sign).
I tried to turn on the power supplies via System Controller menu (platform shell), but it... (6 Replies)
Discussion started by: solind
6 Replies
8. Solaris
Hello,
I have purchaced an old SUn fire x2270 server .
I wanted to make ILOM upgrade to the latest version of software :
ILOM 3.0.9.18.a r126592
BIOS vers. 2.09
Server 2.2.3
(10-Aug-2018)
Because my version is very outdated.
But i can't download the updatebecause it's require... (4 Replies)
Discussion started by: LouisLakoute
4 Replies
LEARN ABOUT OSX
svk::command::info
SVK::Command::Info(3) User Contributed Perl Documentation SVK::Command::Info(3)
NAME
SVK::Command::Info - Display information about a file or directory
SYNOPSIS
info [PATH | DEPOTPATH]...
OPTIONS
-R [--recursive] : descend recursively
DESCRIPTION
For example, here's the way to display the info of a checkout path:
% svk info ~/dev/svk
Checkout Path: /Users/gugod/dev/svk
Depot Path: //svk/local
Revision: 447
Last Changed Rev.: 447
Last Changed Date: 2006-11-28
Copied From: /svk/trunk, Rev. 434
Merged From: /svk/trunk, Rev. 445
You can see the result has some basic information: the actual depot path, and current revision. Next are advanced information about copy
and merge source for this depot path.
The result of "svk info //svk/local" is almost the same as above, except for the "Checkout Path:" line is not there, because you are not
referring to a checkout path.
Note that the revision numbers on "Copied From:" and "Merged From:" lines are for the source path (//svk/trunk), not the target path
(//svk/local). The example above state that, //svk/local is copied from the revision 434 of //svk/trunk, and //svk/local was merged from
the revision 445 of //svk/trunk. Hence if you do a "svk log -r 434 //svk/local", svk would tell you that //svk/local does not exist at
revision 434.
So far there is no easy way to tell the actual revision number of //svk/local right after a copy or merge.
If the target is a depot path, or the corresponding depot path of the target checkout path is actually a mirroring path, the output of this
command will look like this:
% svk info //svk/trunk
Depot Path: //svk/trunk
Revision: 447
Last Changed Rev.: 445
Mirrored From: svn://svn.clkao.org/svk, Rev. 1744
So you can see this depot path is mirrored from a remote repository, and so far mirrored up to revision 1744.
perl v5.10.0 2008-08-04 SVK::Command::Info(3)