05-18-2006
More info
Sorry, the question was asked to me, "What is the danger associated with not adding " ./ " before a
> >script name when you run it?"
I pretty much know what it means I just don't know what would happen if I don't add it to a command.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi, I have just started a Systems Programming course and am required to write a c shell script as part of it.
I have little to no clue about unix.
The spec states that the script can be run only once on each host by a user, but the script can be run on different hosts by the one user.
... (2 Replies)
Discussion started by: richgi
2 Replies
2. Shell Programming and Scripting
Hello,
I don't know anything about scripting, and I want help on writing a script, which can help me doing my research.
Actually I have some ASCII format files formatted in a way looks like this
6 lines of text that is not important for me
File_header_name_number_1 <--... (1 Reply)
Discussion started by: geoquest
1 Replies
3. Shell Programming and Scripting
I am very new to Unix. I need to write a script that will grep some files, etc. When I write the script, do I need to know what shell I am using? If so, how do I do that? (1 Reply)
Discussion started by: ssmiths001
1 Replies
4. Shell Programming and Scripting
I am currently taking a linux shell scripting class and also a intro to programming class using QBASIC. Will this interfere with how i learn each one? Are they similar in some ways? I already took a unix course based on the commands and it was easy, but now i have to create programs. Also, how... (1 Reply)
Discussion started by: brentdeback
1 Replies
5. AIX
Please help me
1. Please give me the few examples of shell scripts written for AIX
2.I have scripts written on Unix, does that work for AIX, if not what are the changes to be carried out to run the scripts on AIX....
Please help me (4 Replies)
Discussion started by: me_haroon
4 Replies
6. Shell Programming and Scripting
can anyone help me in writing a shell script to visualize how simple commands work and on what logic. For Eg: ls command how it lists out all the files and directories, need to write a simple script based on the commands source code.:D (0 Replies)
Discussion started by: rahul_11d
0 Replies
7. Shell Programming and Scripting
Experts,
I am newbie in shell scripting. I want to write Bash shell scripts corresponding to windows bat files. I have installed cygwin at c:\cygwin and i am trying to crate the sh file using vi editor. i am not able to understand how to use linux/unix convention for the code. following is my... (15 Replies)
Discussion started by: rajuchacha007
15 Replies
8. What is on Your Mind?
Please, I beg you, “Stop!” Yes, stop writing scripts and instead build workflows.
Programmers, Sys-Admins, System Support, I'm talking to you.
Ok, I know in this community I'm going to get some serious backlash for my statements but I truly believe in my statement.
There was a time when... (13 Replies)
Discussion started by: mikemazz
13 Replies
9. Shell Programming and Scripting
Hi,
I wanted to load data from HDFS to HIVE by writing bash script.
Description:
I have written a bash script to validate the data and loaded validated data from local file system to HDFS. Now in the same bash script i wanted to load the data from HDFS to HIVE. How can i do it ? Also how tyhe... (2 Replies)
Discussion started by: shree11
2 Replies
10. Shell Programming and Scripting
Hi,
I have a script file where i'm validatig the input file and storing the validated records on HDFS.
I wanted to load data from HDFS to HBASE using pig script. So for that i have created a HBASE table and written pig script to load data from HDFS to HBASE which is working fine. Now i wanted... (0 Replies)
Discussion started by: shree11
0 Replies
LEARN ABOUT MOJAVE
purity
PURITY(6) Games Manual PURITY(6)
NAME
purity - a general purpose purity test
SYNOPSIS
/usr/games/purity [ flags ] [ testname ]
DESCRIPTION
Purity is an interactive purity test program with a simple, user interface and datafile format. For each test, questions are printed to
the your terminal, and you are prompted for an answer to the current question. At a prompt, these are your choices:
y Answer "yes" to the question.
n Answer "no" to the question.
b Backup one question, if you answered it incorrectly, or someone is watching you take the test, and you don't (or do) want to
admit a different answer.
r Redraw the current question.
q Quit the test, and print the current score.
? Print a help screen for the current prompt.
k Kill a section of the test. This skips all the questions of the test until the next subject heading.
a Toggle answer mode between real answers and obfuscated answers. Real answers print "yes" and "no", while obfuscated answers
are "Maybe" and "maybe". Obfuscated answers are preferred if you are shy, and don't want people to be able to read your
answers over your shoulder as you take the test.
d Toggle dERanGe output.
s Print your current score on the test you are taking.
l Toggle score logging.
At the end of the test, your score is printed out. For most purity tests, lower scores denote more "experience" of the test material.
FLAGS
These are the command line flags for the test.
-a Show real answers (i.e. "yes" and "no") instead of obfuscated ones (i.e. "Maybe" and "maybe") as you answer the questions.
-d PrINt THe tESt in DerANgeD pRInT.
-f Take the test in fast mode. Only the questions are printed, and not any other text blocks, like the introdution, subject
headers, and the conclusion.
-l Take the test without having your score logged.
-p Print the test without prompting for answers. This is useful for making hard copies of the tests without having to edit out
the prompts by hand.
-r Decrypt the test using the Rot 13 algorithm. This is done as a form of "protection", such that if you read a rot13 test and
it offends you, it's your own fault.
-z zoom through more prompts in large text blocks. The default is to prompt the user for more when a screenful of text has been
printed without any user input.
DATAFILE FORMAT
The format of the datafiles is a very simple format, intended such that new tests can quickly and easily be converted to run with the test.
There are four types of text in a purity test datafile. Each type is contained in a bracket type of punctuation. The definitions are as
follows:
the styles of text blocks are:
{ plain text block }
[ subject header ]
( test question )
and < conclusion >
Plain text blocks are printed out character for character.
Subject headers are preceded by their subject numbers, starting at 1, and then printed as text blocks.
Questions are preceded by their numbers, and then prompt the user to answer the question, keeping track of the user's current score.
Conclusions first calculate and print the user's score for the test, then print out the conclusion as a text block.
If you wish to include any of the various bracket punctuation in your text, the backslash ("") character will escape the next character.
To print a question with parentheses, you would use the following format:
(have you ever written a purity test (like this one)?)
the output would be this:
1. have you ever written a purity test (like this one)?
and then it would have asked the user for her/his answer.
For a generic datafile, use the "sample" datafile for the test.
FILES
/var/games/purity.scores the score logfile
/usr/share/games/purity/* test data files
AUTHOR
Eric Lechner, lechner@ucscb.ucsc.edu
18 December 1989 PURITY(6)