Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Creating a simple ID Script
Top Forums UNIX for Beginners Questions & Answers Creating a simple ID Script Post 302984259 by bakunin on Sunday 23rd of October 2016 03:35:35 PM
Old 10-23-2016
Quote:
Originally Posted by kkishore4580
Would I use the same functions in Linux/Ubuntu as I would in Python?
"Linux" (or "Unix", for that matter) is not a programming environment. Unixes (this includes Linux) use certain "shells" (commando processors, if you are proficient with Windoze: think of something similar in function to CMD.EXE, but with the capabilities of PowerShell included from the start).

Most of the shells (and all of the common ones) are not only built for interactive use but also have built-in languages which you can use to write programs ("scripts"). The syntax of these languages are quite similar, but not the same.

Today the overwhelming majority of scripting is done in one of two shells: bash (Bourne Again SHell) and ksh (Korn Shell). Both these languages are based on an older shell (the Bourne shell) and downwards compatible to it, so scripts written in strict Bourne shell code will run in both these shells and produce the same results. There is a newer standard to scripting, POSIX shell, which is based mostly on the Korn shell and both, bash and ksh are able to understand that standard. Both offer (different) features though, which are not part of this standard.

Linux distributions (not Ubuntu) usually come equipped with bash as the default shell, but can easily be changed to use the Korn shell, which is freely available today. Of the commercial Unixes some come with ksh (Solaris, AIX, if i remember correctly HP-Ux), some with Bourne shell (SCO, IRIX, and maybe - i can't remember - Tru64) but can utilize bash (which is also freely available) too.

Understand, that the shell language usually only covers the languages structure: you use system commands like you would use library functions in a high-level language. If you use everything your system offers it is likely that the next (different) system might not understand everything, like if you use the specialities of a certain compiler you may have to change your code if you switch to another compiler. This is why seasoned script programmers stay with the commands and options described in POSIX almost religiously, because this way they are guaranteed that their script runs on other platforms the same way it does so on theirs.

I hope this helps.

bakunin
 

8 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Creating a command history feature in a simple UNIX shell using C

I'm trying to write a history feature to a very simple UNIX shell that will list the last 10 commands used when control-c is pressed. A user can then run a previous command by typing r x, where x is the first letter of the command. I'm having quite a bit of trouble figuring out what I need to do, I... (2 Replies)
Discussion started by: -=Cn=-
2 Replies

2. Shell Programming and Scripting

creating a simple archiving script

Im trying to create a script to archive specified directories into a specified tarball backup file. This is what i want the input to look like ex. save -i '/bin/b*' -i '/bin/ls' -o backup this is what i have #!/bin/bash #save - backup file script unset myInput unset myOutput while... (3 Replies)
Discussion started by: lensmen
3 Replies

3. Shell Programming and Scripting

Creating simple shell program

Hi, I'm new to UNIX shell programming... can anyone help in doing the following : 1) create a text file named "Model File" having following columns : Name Number Physics Chemistry 2) prompt user to n rows enter the name, number, physics ,chemistry 3) display the entire columns and rows... (1 Reply)
Discussion started by: Mayuri P R
1 Replies

4. Programming

Creating a simple Help Desk system in PHP

hi guys i'm new to php,,i'm asked to develop a simple online help desk (where the admin can view the problem an forward it to another one to handle it and so on) or get a ready sytem then modify alil on it but i dont know where to start ir to find any suggestion please? (2 Replies)
Discussion started by: kedah160
2 Replies

5. UNIX for Dummies Questions & Answers

Help with creating a simple program!!

i am new to shell scripting!! i am making this program in bourne shell, that asks the user to input "Hello (their name)" or "question (their name)", any other input, "ERROR" will be outputted. if they input "Hello (name)", i want to out saying Hello (name) but if they input "question (name)", i... (4 Replies)
Discussion started by: bshell_1214
4 Replies

6. Shell Programming and Scripting

how to execute ksh simple shell script without creating .sh file

please help me to execute a simple shell script like for i in `ls echo $i done . i dont want to create a new sh file to execute it. Can i just type and execute it ? because I always this kind of simple for loops . Please help . Thanks (7 Replies)
Discussion started by: Sooraj_Linux
7 Replies

7. Homework & Coursework Questions

Help with creating a simple shell script

Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted! 1. The problem statement, all variables and given/known data: Write a shell script that accepts two arguments. The two arguments are the name of 2 files. • If the arguments... (3 Replies)
Discussion started by: Scripter12345
3 Replies

8. Web Development

Creating a Simple Linux Dashboard with Oracle Jet

Creating a Simple Linux Dashboard with Oracle Jet - Part 1 the Server Side PHP Code Creating a simple Linux dashboard with Oracle Jet is easy and fun. It's simple to create a dashboard to monitor your Linux server using Oracle JET. The sky is the limit with indicators and gauges. ... (7 Replies)
Discussion started by: Neo
7 Replies

LEARN ABOUT HPUX

sh

sh(1)							      General Commands Manual							     sh(1)

NAME

       sh - overview of various system shells

SYNOPSIS

   POSIX Shell
       option] ...  string] [arg ...]

       option] ...  string] [arg ...]

   Korn Shell
       option] ...  string] [arg ...]

       option] ...  string] [arg ...]

   C Shell
       [command_file] [argument_list ...]

   Key Shell
DESCRIPTION

   Remarks
       The POSIX .2 standard requires that, on a POSIX-compliant system, executing the command activates the POSIX shell (located in file on HP-UX
       systems), and executing the command produces an on-line manual entry that displays the syntax of the POSIX shell command-line.

       However, the command has historically been associated with the conventional Bourne shell, which could confuse some users.   To  meet  stan-
       dards  requirements  and also clarify the relationships of the various shells and where they reside on the system, this entry provides com-
       mand-line syntax and a brief description of each shell, and lists the names of the manual entries where each shell is described in  greater
       detail.

       The Bourne shell is removed from the system starting with HP-UX 11i Version 1.5.  Please use the POSIX shell as an alternative.

   Shell Descriptions
       The HP-UX operating system supports the following shells:

	      POSIX-conforming command programming language and command interpreter
			residing  in  file Can execute commands read from a terminal or a file.  This shell conforms to current POSIX standards in
			effect at the time the HP-UX system release was introduced, and is similar to the Korn shell in many respects.	Similar in
			many  respects to the Korn shell, the POSIX shell contains a history mechanism, supports job control, and provides various
			other useful features.

	      Korn-shell command programming language and commands interpreter
			residing in file Can execute commands read from a terminal or a file.  This shell, like the POSIX shell, contains  a  his-
			tory mechanism, supports job control, and provides various other useful features.

	      A command language interpreter
			that incorporates a command history buffer, C-language-like syntax, and job control facilities.

	      Restricted version of the POSIX shell command interpreter.
			Sets  up  a  login  name  and  execution  environment whose capabilities are more controlled (restricted) than normal user
			shells.

	      restricted version of the Korn-shell command interpreter
			Sets up a login name and execution environment whose capabilities  are	more  controlled  (restricted)	than  normal  user
			shells.

	      An extension of the standard Korn Shell
			that uses hierarchical softkey menus and context-sensitive help.

							  +--------------+--------------------+
							  | To obtain:	 |  Use the command:  |
							  +--------------+--------------------+
							  | POSIX Shell  |  /usr/bin/sh ...   |
							  | Korn Shell	 |  /usr/bin/ksh ...  |
							  | C Shell	 |  /usr/bin/csh ...  |
							  | Key Shell	 |  /usr/bin/keysh    |
							  +--------------+--------------------+
       These shells can also be the default invocation, depending on the entry in the file.  See also chsh(1).

WARNINGS

       Many manual entries contain descriptions of shell behavior or describe program or application behavior similar to ``the shell'' with a ref-
       erence to ``see sh(1)''.

SEE ALSO

       For more information on the various individual shells, see:

       keysh(1)       Key Shell description.

       ksh(1)	      Korn Shell description.

       sh-posix(1)    POSIX Shell description.

       csh(1)	      C Shell description.

																	     sh(1)
All times are GMT -4. The time now is 12:28 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy