|Home||Switchboard||Unix Administration||Red Hat||TCP/IP Networks||Neoliberalism||Toxic Managers|
May the source be with you, but remember the KISS principle ;-)
Bigger doesn't imply better. Bigger often is a sign of obesity, of lost control, of overcomplexity, of cancerous cells
On systems with a PROM version of 1.x or 2.x, the nvalias command might not be available. On these systems, you need to use nvedit to create custom device aliases. nvedit is a line editor that edits the NVRAMRC directly, has a set of editing commands, and operates in a temporary buffer. The following is a sample nvedit session:
ok setenv use-nvramrc? true
Learning nvedit This section is included for information purposes, to show an additional method for modifying the NVRAM. The nvedit line editor will not be on the certification exam.
The system responds with the following:
use-nvramrc? = true ok nvedit 0: devalias disk0 /pci@1f,0/pci@1,1/ide@3/disk@0,0\ 1: <Control-C> ok nvstore ok reset Resetting ...... ok boot disk0
The preceding example uses nvedit to create a permanent device alias named disk0. The example uses Ctrl+C to exit the editor. It also uses the nvstore command to make the change permanent in the NVRAMRC. Then, it issues the reset command to reset the system and then boots the system from disk0 by using the boot disk0 command.
Table 3.10 lists some of the basic commands you can use while in the nvedit line editor.
|Ctrl+A||Moves backward to beginning of the line.|
|Ctrl+B||Moves backward one character.|
|Esc+B||Moves backward one word.|
|Ctrl+C||Exits the script editor, returning to the OpenBoot command interpreter. The temporary buffer is preserved but is not written back to the script. You use nvstore afterward to write it back.|
|Ctrl+D||Erases the next character.|
|Esc+D||Erases from the cursor to the end of the word, storing the erased characters in a save buffer.|
|Ctrl+E||Moves forward to the end of the line.|
|Ctrl+F||Moves forward one character.|
|Esc+F||Moves forward one word.|
|Ctrl+H||Erases the previous character.|
|Esc+H||Erases from the beginning of the word to just before the cursor, storing erased characters in a save buffer.|
|Ctrl+K||Erases from the cursor position to the end of the line, storing the erased characters in a save buffer. If at the end of a line, it joins the next line to the current line (that is, deletes the new line).|
|Ctrl+L||Displays the entire contents of the editing buffer.|
|Ctrl+N||Moves to the next line of the script-editing buffer.|
|Ctrl+O||Inserts a new line at the cursor position and stays on the current line.|
|Ctrl+P||Moves to the previous line of the script-editing buffer.|
|Ctrl+Q||Quotes the next character (that is, allows you to insert control characters).|
|Ctrl+R||Retypes the line.|
|Ctrl+U||Erases the entire line, storing the erased characters in a save buffer.|
|Ctrl+W||Erases from the beginning of the word to just before the cursor, storing erased characters in a save buffer.|
|Ctrl+Y||Inserts the contents of the save buffer before the cursor.|
|Return (Enter)||Inserts a new line at the cursor position and advances to the next line.|
|Delete||Erases the previous character.|
|Backspace||Erases the previous character.|
Anyone who has access to a computer keyboard can access OpenBoot and modify parameters unless you set up the security variables:
|security-mode||Restricts the set of operations that users are allowed to perform at the OpenBoot prompt.|
|security-password||Specifies the firmware security password. (It is never displayed.) You should not set this variable directly; you set it by using password.|
|security-#badlogins||Specifies the number of incorrect security password attempts.|
New password (only first 8 chars are used): <enter password> Retype new password: <enter password>
Setting the OpenBoot Security Mode It is important to remember your security password and to set it before setting the security mode. If you later forget this password, you cannot use your system; you must call your vendor's customer support service to make your machine bootable again.
If you are able to get to a Unix prompt as root, you can use the eeprom command to either change the security-mode parameter to none or reset the security password.
Earlier in this chapter you learned how to change the OpenBoot parameter security-password from the command line.
After you assign a password, you can set the security variables that best fit your environment.
You use security-mode to restrict the use of OpenBoot commands. The syntax for setting security-mode is as follows:
setenv security-mode <value>
|full||Specifies that all OpenBoot commands except go require a password. This security mode is the most restrictive.|
|command||Specifies that all OpenBoot commands except boot and go require a password.|
|none||Specifies that no password is required. This is the default.|
The following example sets the OpenBoot environment so that all commands except boot and go require a password:
setenv security-mode command
With security-mode set to command, a password is not required if you enter the boot command by itself or if you enter the go command. Any other command requires a password, including the boot command with an argument.
The following are examples of when a password might be required when security-mode is set to command:
|ok boot||No password is required.|
|ok go||No password is required.|
|ok boot vmunix||A password is required.|
The system displays a password prompt as follows:
|Password||The password is not echoed as it is typed.|
|ok reset-all||A password is required.|
|Password||Type the password.|
If you enter an incorrect security password, there is a delay of about 10 seconds before the next startup prompt appears. The number of times that an incorrect security password can be typed is stored in the security-#badlogins variable, but you should not change this variable.
Groupthink : Two Party System as Polyarchy : Corruption of Regulators : Bureaucracies : Understanding Micromanagers and Control Freaks : Toxic Managers : Harvard Mafia : Diplomatic Communication : Surviving a Bad Performance Review : Insufficient Retirement Funds as Immanent Problem of Neoliberal Regime : PseudoScience : Who Rules America : Neoliberalism : The Iron Law of Oligarchy : Libertarian Philosophy
War and Peace : Skeptical Finance : John Kenneth Galbraith :Talleyrand : Oscar Wilde : Otto Von Bismarck : Keynes : George Carlin : Skeptics : Propaganda : SE quotes : Language Design and Programming Quotes : Random IT-related quotes : Somerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose Bierce : Bernard Shaw : Mark Twain Quotes
Vol 25, No.12 (December, 2013) Rational Fools vs. Efficient Crooks The efficient markets hypothesis : Political Skeptic Bulletin, 2013 : Unemployment Bulletin, 2010 : Vol 23, No.10 (October, 2011) An observation about corporate security departments : Slightly Skeptical Euromaydan Chronicles, June 2014 : Greenspan legacy bulletin, 2008 : Vol 25, No.10 (October, 2013) Cryptolocker Trojan (Win32/Crilock.A) : Vol 25, No.08 (August, 2013) Cloud providers as intelligence collection hubs : Financial Humor Bulletin, 2010 : Inequality Bulletin, 2009 : Financial Humor Bulletin, 2008 : Copyleft Problems Bulletin, 2004 : Financial Humor Bulletin, 2011 : Energy Bulletin, 2010 : Malware Protection Bulletin, 2010 : Vol 26, No.1 (January, 2013) Object-Oriented Cult : Political Skeptic Bulletin, 2011 : Vol 23, No.11 (November, 2011) Softpanorama classification of sysadmin horror stories : Vol 25, No.05 (May, 2013) Corporate bullshit as a communication method : Vol 25, No.06 (June, 2013) A Note on the Relationship of Brooks Law and Conway Law
Fifty glorious years (1950-2000): the triumph of the US computer engineering : Donald Knuth : TAoCP and its Influence of Computer Science : Richard Stallman : Linus Torvalds : Larry Wall : John K. Ousterhout : CTSS : Multix OS Unix History : Unix shell history : VI editor : History of pipes concept : Solaris : MS DOS : Programming Languages History : PL/1 : Simula 67 : C : History of GCC development : Scripting Languages : Perl history : OS History : Mail : DNS : SSH : CPU Instruction Sets : SPARC systems 1987-2006 : Norton Commander : Norton Utilities : Norton Ghost : Frontpage history : Malware Defense History : GNU Screen : OSS early history
The Peter Principle : Parkinson Law : 1984 : The Mythical Man-Month : How to Solve It by George Polya : The Art of Computer Programming : The Elements of Programming Style : The Unix Haterís Handbook : The Jargon file : The True Believer : Programming Pearls : The Good Soldier Svejk : The Power Elite
Most popular humor pages:
Manifest of the Softpanorama IT Slacker Society : Ten Commandments of the IT Slackers Society : Computer Humor Collection : BSD Logo Story : The Cuckoo's Egg : IT Slang : C++ Humor : ARE YOU A BBS ADDICT? : The Perl Purity Test : Object oriented programmers of all nations : Financial Humor : Financial Humor Bulletin, 2008 : Financial Humor Bulletin, 2010 : The Most Comprehensive Collection of Editor-related Humor : Programming Language Humor : Goldman Sachs related humor : Greenspan humor : C Humor : Scripting Humor : Real Programmers Humor : Web Humor : GPL-related Humor : OFM Humor : Politically Incorrect Humor : IDS Humor : "Linux Sucks" Humor : Russian Musical Humor : Best Russian Programmer Humor : Microsoft plans to buy Catholic Church : Richard Stallman Related Humor : Admin Humor : Perl-related Humor : Linus Torvalds Related humor : PseudoScience Related Humor : Networking Humor : Shell Humor : Financial Humor Bulletin, 2011 : Financial Humor Bulletin, 2012 : Financial Humor Bulletin, 2013 : Java Humor : Software Engineering Humor : Sun Solaris Related Humor : Education Humor : IBM Humor : Assembler-related Humor : VIM Humor : Computer Viruses Humor : Bright tomorrow is rescheduled to a day after tomorrow : Classic Computer Humor
The Last but not Least Technology is dominated by two types of people: those who understand what they do not manage and those who manage what they do not understand ~Archibald Putt. Ph.D
Copyright © 1996-2018 by Dr. Nikolai Bezroukov. www.softpanorama.org was initially created as a service to the (now defunct) UN Sustainable Development Networking Programme (SDNP) in the author free time and without any remuneration. This document is an industrial compilation designed and created exclusively for educational use and is distributed under the Softpanorama Content License. Original materials copyright belong to respective owners. Quotes are made for educational purposes only in compliance with the fair use doctrine.
FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available to advance understanding of computer science, IT technology, economic, scientific, and social issues. We believe this constitutes a 'fair use' of any such copyrighted material as provided by section 107 of the US Copyright Law according to which such material can be distributed without profit exclusively for research and educational purposes.
This is a Spartan WHYFF (We Help You For Free) site written by people for whom English is not a native language. Grammar and spelling errors should be expected. The site contain some broken links as it develops like a living tree...
|You can use PayPal to make a contribution, supporting development of this site and speed up access. In case softpanorama.org is down you can use the at softpanorama.info|
The statements, views and opinions presented on this web page are those of the author (or referenced source) and are not endorsed by, nor do they necessarily reflect, the opinions of the author present and former employers, SDNP or any other organization the author may be associated with. We do not warrant the correctness of the information provided or its fitness for any purpose.
Last modified: September 12, 2017