09-22-2010
Changing back the OBP from the RSC
Hi everyone new to Solaris 10 and Linix and am having problems changing back the OBP from RSC ( Remote System Control).
I bought a SunFire 280R Server a month or two ago, installed Solaris 10 on to it. Have been trying to setup correct settings and came across a guide on Oracle website which reads:
To display current and default values of specific OpenBoot configuration variable, specify the "printenv" commandand the varible name at the ok prompt. ie: ok printenv diag-switch?
diag-switch? = false (This being the default value).
I some how changed this value to True...
And changed the setenv diag-level from (min) to Max.
In doing this I have lost the ok prompt on startup and want to get it back from the remote system control. Can't find a command prompt to run new commands to get the ok prompt back.
Can anyone out there please help me with this problem?....
Cheers
Arjay
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Has anyone had a message after attempting a telnet to an RSC server of:
"Console session already in use." I'm attempting to access this server to setup a user account, and I'm having some problems. Does anyone have an
idea or suggestion on how to proceed? (0 Replies)
Discussion started by: mr-synapse
0 Replies
2. Solaris
Hello, today i'm comment in /etc/vfstab fs /usr and my server load in SingleUser without anything commands :(
How i can enter to OBP from # ? or ILOM ?
I'm try CTRL+BREAK (F5) , CTRL+ALT+BREAK (F5) and #. but it's don't help me :(((( (5 Replies)
Discussion started by: jess_t03
5 Replies
3. Solaris
Hello experts...
In OBP(OK prompt)... How can i know whole command if i know part of a command?
Thanks in advance... (2 Replies)
Discussion started by: younus_syed
2 Replies
4. Solaris
Hi All,
Please send the configuration for RSC in solaris.
Thanks and Regards, (3 Replies)
Discussion started by: lbreddy
3 Replies
5. Solaris
Dear All,
Can any body help me how to configure the RSC in solaris9.
Thanks and Regards, (1 Reply)
Discussion started by: lbreddy
1 Replies
6. Solaris
Hi All
I have done a reboot for SUN Solaris 8 ( model SUNFIRE 280R)
but i havent got the OK prompt i only got the following:
RSC2 POST - Version 10-18-2000 0.7
Dual Port Memory Test, PASSED.
TTY External - Internal Loopback Test
TTY External - Internal Loopback Test, PASSED.
... (3 Replies)
Discussion started by: alaa75
3 Replies
7. Solaris
Hi All, ;)
I have configured rsc hosted on Sun-Fire-V490.
But I am not able to telnet this machine
Packages installed :
#pkginfo -l | grep SUNWrsc
PKGINST: SUNWrsc
PKGINST: SUNWrscd
PKGINST: SUNWrscj
I rebooted system but still I' not able to take rsc.
I am not... (3 Replies)
Discussion started by: tuxian
3 Replies
8. Solaris
Does anyone know where to get these on Oracle's support site or elsewhere? (7 Replies)
Discussion started by: LittleLebowski
7 Replies
9. UNIX for Dummies Questions & Answers
Hi Gurus,
I am totally confused :wall: . I have some questions regarding OBP,EEPROMand NVRAM, BIOS.
What actually are these how do they function and interact on a Sparc based solaris system.
What is ok> ?
What is system Firmware ?
How does the system startup?
Trying to google... (8 Replies)
Discussion started by: rama krishna
8 Replies
10. Solaris
I have a disk failure in a V280, the support tech asked for explorer output and rsc information
sc>showsc
rsc>environment
rsc>loghistory
rsc>consolehistory
rsc>version -v
since RSC is not a secure connection, I am not comfortable with providing this information for a disk... (2 Replies)
Discussion started by: baumer11
2 Replies
LEARN ABOUT DEBIAN
git-mergetool
GIT-MERGETOOL(1) Git Manual GIT-MERGETOOL(1)
NAME
git-mergetool - Run merge conflict resolution tools to resolve merge conflicts
SYNOPSIS
git mergetool [--tool=<tool>] [-y|--no-prompt|--prompt] [<file>...]
DESCRIPTION
Use git mergetool to run one of several merge utilities to resolve merge conflicts. It is typically run after git merge.
If one or more <file> parameters are given, the merge tool program will be run to resolve differences on each file (skipping those without
conflicts). Specifying a directory will include all unresolved files in that path. If no <file> names are specified, git mergetool will run
the merge tool program on every file with merge conflicts.
OPTIONS
-t <tool>, --tool=<tool>
Use the merge resolution program specified by <tool>. Valid merge tools are: araxis, bc3, diffuse, ecmerge, emerge, gvimdiff, kdiff3,
meld, opendiff, p4merge, tkdiff, tortoisemerge, vimdiff and xxdiff.
If a merge resolution program is not specified, git mergetool will use the configuration variable merge.tool. If the configuration
variable merge.tool is not set, git mergetool will pick a suitable default.
You can explicitly provide a full path to the tool by setting the configuration variable mergetool.<tool>.path. For example, you can
configure the absolute path to kdiff3 by setting mergetool.kdiff3.path. Otherwise, git mergetool assumes the tool is available in PATH.
Instead of running one of the known merge tool programs, git mergetool can be customized to run an alternative program by specifying
the command line to invoke in a configuration variable mergetool.<tool>.cmd.
When git mergetool is invoked with this tool (either through the -t or --tool option or the merge.tool configuration variable) the
configured command line will be invoked with $BASE set to the name of a temporary file containing the common base for the merge, if
available; $LOCAL set to the name of a temporary file containing the contents of the file on the current branch; $REMOTE set to the
name of a temporary file containing the contents of the file to be merged, and $MERGED set to the name of the file to which the merge
tool should write the result of the merge resolution.
If the custom merge tool correctly indicates the success of a merge resolution with its exit code, then the configuration variable
mergetool.<tool>.trustExitCode can be set to true. Otherwise, git mergetool will prompt the user to indicate the success of the
resolution after the custom tool has exited.
-y, --no-prompt
Don't prompt before each invocation of the merge resolution program.
--prompt
Prompt before each invocation of the merge resolution program. This is the default behaviour; the option is provided to override any
configuration settings.
TEMPORARY FILES
git mergetool creates *.orig backup files while resolving merges. These are safe to remove once a file has been merged and its git
mergetool session has completed.
Setting the mergetool.keepBackup configuration variable to false causes git mergetool to automatically remove the backup as files are
successfully merged.
GIT
Part of the git(1) suite
Git 1.7.10.4 11/24/2012 GIT-MERGETOOL(1)