All devices are
represented by files called special files
that are located in/dev
directory. Thus, device files and other files are named and accessed in the
same way. A 'regular file' is just an ordinary data file in the disk. A 'block
special file' represents a device with characteristics similar to a disk (data
transfer in terms of blocks). A 'character special file' represents a device
with characteristics similar to a keyboard (data transfer is by stream of bits
in sequential order).
Showing posts with label UNIX. Show all posts
Showing posts with label UNIX. Show all posts
Wednesday, 6 August 2014
What is 'inode'?
All UNIX files have its
description stored in a structure called 'inode'. The inode contains info about
the file-size, its location, time of last access, time of last modification,
permission and so on. Directories are also represented as files and have an
associated inode. In addition to descriptions about the file, the inode
contains pointers to the data blocks of the file. If the file is large, inode
has indirect pointer to a block of pointers to additional data blocks (this
further aggregates for larger files). A block is typically 8k.
Inode consists of the
following fields:
Ø File owner identifier
Ø File type
Ø File access permissions
Ø File access times
Ø Number of links
Ø File size
Ø Location of the file data
Brief about the directory representation in UNIX
A Unix directory is a file
containing a correspondence between filenames and inodes. A directory is a
special file that the kernel maintains. Only kernel modifies directories, but
processes can read directories. The contents of a directory are a list of
filename and inode number pairs. When new directories are created, kernel makes
two entries named '.' (refers to the directory itself) and '..' (refers to parent
directory).
System call for creating directory is
mkdir (pathname, mode).
What are the Unix system calls for I/O?
Ø open(pathname,flag,mode) - open file
Ø creat(pathname,mode) - create file
Ø close(filedes) - close an open file
Ø read(filedes,buffer,bytes) - read data
from an open file
Ø write(filedes,buffer,bytes) - write
data to an open file
Ø lseek(filedes,offset,from) - position
an open file
Ø dup(filedes) - duplicate an existing
file descriptor
Ø dup2(oldfd,newfd) - duplicate to a
desired file descriptor
Ø fcntl(filedes,cmd,arg) - change
properties of an open file
Ø ioctl(filedes,request,arg) - change
the behaviour of an open file
The difference between
fcntl anf ioctl is that the former is intended for any open file, while the
latter is for device-specific operations.How do you change File Access Permissions?
Every file has following
attributes:
Ø owner's user ID ( 16 bit integer )
Ø owner's group ID ( 16 bit integer )
Ø File access mode word
'r w x -r w x- r w x'
(user permission-group
permission-others permission)
r-read, w-write, x-execute
To change the access mode, we use
chmod(filename,mode).
Example 1:
To change mode of myfile
to 'rw-rw-r--' (ie. read, write permission for user - read,write permission for
group - only read permission for others)
we give the args as:
chmod(myfile,0664) .
Each operation is represented by
discrete values
'r' is 4
'w' is 2
'x' is 1
Therefore, for 'rw' the value is
6(4+2).
Example 2:
To change mode of myfile
to 'rwxr--r--' we give the args as:
chmod(myfile,0744).
What are links and symbolic links in UNIX file system?
A link is a second name
(not a file) for a file. Links can be used to assign more than one name to a
file, but cannot be used to assign a directory more than one name or link
filenames on different computers.
Symbolic link 'is' a file
that only contains the name of another file.Operation on the symbolic link is
directed to the file pointed by the it.Both the limitations of links are
eliminated in symbolic links.
Commands for linking files
are:
Link ln filename1 filename2
Symbolic link ln -s filename1 filename2
What is a FIFO?
FIFO are otherwise called
as 'named pipes'. FIFO (first-in-first-out) is a special file which is said to
be data transient. Once data is read from named pipe, it cannot be read again.
Also, data can be read only in the order written. It is used in interprocess
communication where a process writes to one end of the pipe (producer) and the
other reads from the other end (consumer).
How do you create special files like named pipes and device files?
The system call mknod
creates special files in the following sequence.
1. kernel assigns new inode,
2. sets the file type to indicate that
the file is a pipe, directory or special file,
3. If it is a device file, it makes the
other entries like major, minor device numbers.
For example:
If the device is a disk,
major device number refers to the disk controller and minor device number is
the disk.
Discuss the mount and unmount system calls
The privileged mount
system call is used to attach a file system to a directory of another file
system; the unmount system call detaches a file system. When you mount another
file system on to your directory, you are essentially splicing one directory
tree onto a branch in another directory tree. The first argument to mount call
is the mount point, that is , a directory in the current file naming system.
The second argument is the file system to mount to that point. When you insert
a cdrom to your unix system's drive, the file system in the cdrom automatically
mounts to /dev/cdrom in your system.
How does the inode map to data block of a file?
Inode has 13 block
addresses. The first 10 are direct block addresses of the first 10 data blocks
in the file. The 11th address points to a one-level index block. The 12th
address points to a two-level (double in-direction) index block. The 13th
address points to a three-level(triple in-direction)index block. This provides
a very large maximum file size with efficient access to large files, but also
small files are accessed directly in one disk read.
What is a shell?
A shell is an interactive user interface to an operating system services that allows an user to enter commands as character strings or through a graphical user interface. The shell converts them to system calls to the OS or forks off a process to execute the command. System call results and other information from the OS are presented to the user through an interactive interface. Commonly used shells are sh,csh,ks etc.
Brief about the initial process sequence while the system boots up.
While
booting, special process called the 'swapper' or 'scheduler' is created with
Process-ID 0. The swapper manages memory allocation for processes and
influences CPU allocation. The swapper inturn creates 3 children:
Ø the process
dispatcher,
Ø vhand and
Ø dbflush
with IDs 1,2
and 3 respectively.
This
is done by executing the file /etc/init. Process dispatcher gives birth to the
shell. Unix keeps track of all the processes in an internal data structure
called the Process Table (listing command is ps -el).
What are various IDs associated with a process?
Unix
identifies each process with a unique integer called ProcessID. The process
that executes the request for creation of a process is called the 'parent
process' whose PID is 'Parent Process ID'. Every process is associated with a
particular user called the 'owner' who has privileges over the process. The
identification for the user is 'UserID'. Owner is the user who executes the
process. Process also has 'Effective User ID' which determines the access
privileges for accessing resources like files.
getpid()
-process id
getppid()
-parent process id
getuid()
-user id
geteuid()
-effective user id
Explain fork() system call.
The
`fork()' used to create a new process
from an existing process. The new
process is called the child process, and the existing process is called the
parent. We can tell which is which by
checking the return value from `fork()'.
The parent gets the child's pid returned to him, but the child gets 0
returned to him.
Predict the output of the following program code
main()
{
fork();
printf("Hello
World!");
}
Answer:
Hello
World!Hello World!
Explanation:
The
fork creates a child that is a duplicate of the parent process. The child
begins from the fork().All the statements after the call to fork() will be
executed twice.(once by the parent process and other by child). The statement
before fork() is executed only by the parent process.
Predict the output of the following program code
main()
{
fork();
fork(); fork();
printf("Hello
World!");
}
Answer:
"Hello
World" will be printed 8 times.
Explanation:
2^n
times where n is the number of calls to fork()
List the system calls used for process management:
System calls Description
fork() To create a new
process
exec() To execute a new
program in a process
wait() To wait until a
created process completes its execution
exit() To exit from a
process execution
getpid() To get a process
identifier of the current process
getppid() To get parent process
identifier
nice() To bias the existing
priority of a process
brk() To increase/decrease
the data segment size of a process
How can you get/set an environment variable from a program?
Getting
the value of an environment variable is done by using `getenv()'.
Setting
the value of an environment variable is done by using `putenv()'.
How can a parent and child process communicate?
A parent and child can communicate through any of the normal inter-process communication schemes (pipes, sockets, message queues, shared memory), but also have some special ways to communicate that take advantage of their relationship as a parent and child. One of the most obvious is that the parent can get the exit status of the child.
What is a zombie?
When
a program forks and the child finishes before the parent, the kernel still
keeps some of its information about the child in case the parent might need it
- for example, the parent may need to check the child's exit status. To be able
to get this information, the parent calls `wait()'; In the interval between the
child terminating and the parent calling `wait()', the child is said to be a
`zombie' (If you do `ps', the child will have a `Z' in its status field to
indicate this.)
Subscribe to:
Comments (Atom)