lecture 3

chapter two


2.1 user operating system interface
there are several ways for users to interface with the operating system. here, we discuss two fundamental approaches. one provides a command-line interface, or command interpreter that allows users to directly enter commands to be performed by the operating system. the other allows users to interface with the operating system via a graphical user interface, or gui

some operating systems include the command interpreter in the kernel. others, such as windows xp and unix, treat the command interpreter as a special program that is running when a job is initiated or when a user first logs on (on interactive systems). on systems with multiple command interpreters to choose from, the interpreters are known as shells. for example, on unix and linux systems, a user may choose among several different shells, including the bourne shell, c shell, bourne-again shell, korn shell, and others. third-party shells and free user-written shells are also available. most shells provide similar functionality, and a user s choice of which shell to use is generally based on personal preference. figure 2.1 shows the bourne shell command interpreter
being used on solaris 10. the main function of the command interpreter is to get and execute the next user-specified command. many of the commands given at this level manipulate files: create, deleting, list, print, copy, execute, and so on. the ms-dos and unix shells operate in this way. these commands can be implemented in two general ways.
in one approach, the command interpreter itself contains the code to execute the command. for example, a command to deleting a file may cause the command interpreter to jump to a section of its code that sets up the parameters and makes the appropriate system call. in this case, the number of commands that can be given determines the size of the command interpreter, since each command requires its own implementing code. an alternative approach -used by unix, among other operating systems -implements most commands through system programs. in this case, the command interpreter does not understand the command in any way it merely uses the command to identify a file to be loaded into memory and executed. thus, the unix command to deleting a file

rm file.txt

would search for a file called rm, load the file into memory, and execute it with the parameter file. txt. the function associated with the rm command would be defined completely by the code in the file rm. in this way, programmers can add new commands to the system easily by creating new files with the proper

figure 2.1: the bourne shell command interpreter in solaris i 0.

names. the command-interpreter program, which can be small, does not have to be changed for new commands to be added.