How to use sudo – root privilege for a normal user

Sudo works under Linux / Mac OS X and all UNIX like operating systems. /etc/sudoers (config file that defines or list of who can run what) allows you to delegate authority to give certain users or groups of users the ability to run various commands as the superuser(root) or another user without needing the root password. This is useful for delegating roles and permissions to other users without sharing the root password.

This file must be edited with the visudo command as the root user . The sudo command allows users to do tasks on a Linux system as another user.

Read more

How do I use sudo?

Let us take an example here,

If you want to give the user John, access to restart httpd service. First, Login as root user, then use visudo command edit the config file:

# visudo

 

 

Append the following lines to file:

John ALL= /etc/init.d/httpd restart

Save and close file . Now John user can restart httpd service by typing the following command:

$ sudo /etc/init.d/httpd restart

Output:

We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:
#1) Respect the privacy of others.
#2) Think before you type.
#3) With great power comes great responsibility.
Password:
Stopping httpd: [ OK ]
Starting httpd: [ OK ]

The sudo command has logged the attempt to the log file /var/log/secure or /var/log/auth.log file:

# tail -f /var/log/secure

Sample outputs:

Nov 15 06:05:36 localhost sudo: John : TTY=pts/1 ; PWD=/home/John ; USER=root ; COMMAND=/etc/init.d/httpd restart

Before running a command with sudo, users usually supply their password. Once authenticated, and if the /etc/sudoers configuration file permits the user access, the command will be run. sudo logs each command run.
a) If you want to allow John to run various commands:

John ALL=/sbin/halt, /bin/kill, /etc/init.d/httpd

b) Allow user John to restart httpd without any password i.e. as root without authenticating himself:

John ALL= NOPASSWD: /etc/init.d/httpd restart

c) Allow user Alex to run any command from /usr/bin directory:

Alex ALL = /usr/bin/*

 

 

d) Allow user Alex to run ALL commands:

Alex ALL =(ALL) ALL

e) If you want to allow system admin user to run all commands (add users to a group eg:- unixsa)
Append the following line:

## Allows people in group unixsa to run all commands
 %unixsa ALL=(ALL) ALL

Save and close the file. Finally, add a group called unixsa:

# groupadd unixsa

Add a user called Alex (existing user) to group unixsa:

# usermod -a -G unixsa Alex

Verify group membership:

# id Alex

Sample Outputs:

uid=5001(Alex) gid=5001(Alex) groups=5001(Alex),110(unixsa)

Login as user Alex and to run any command as the root type:

$ sudo /etc/init.d/network restart

f) If database admin user want to run command as oracle

Append the following lines to /etc/sudoers file:

John ALL=(oracle) /u01/app/oracle/product/11.1.0/db_1/bin/dbstart

In this case, it’s that indicating the user John can execute the dbstart command as oracle occurs. When using sudo to assume the role of a user other than root, use the -u option and give the user name as an argument, followed by the command that should be executed.

$ whoami
John

 

$ sudo -u oracle /u01/app/oracle/product/11.1.0/db_1/bin/dbstart

Output:

Password:
 Processing Database instance "TEST": log file /u01/app/oracle...

That’s all, we have tried all the common options for the sudo command. You may have your queries in the comments section.

 

Red Hat Enterprise Linux specification comparison, RHEL 3/4/5/6 and RHEL 7

Let’s have a look at the specification comparison between different recent versions. Here is list of Hardware and software features (from RedHat) in RHEL 3/4/5/6 and the RHEL 7.

RHEL Read more

Specification Version 3 Version 4 Version 5 Version 6 Version 7
Maximum logical CPUs
x86 16 32 32 32 N/A
Itanium 2 8 256 [512] 256 [1024] N/A N/A
x86_64 8 64 [64] 160 [255] 240 [4096] 160 [5120]
POWER 8 64 [128] 128 128 128
System z 64 (z900) 64 (z10 EC) 101 (zEC12) 101 (zEC12) 101 (zEC12)
Maximum memory
x86 64GB 64GB 16GB 16GB N/A
Itanium 2 128GB 2TB 2TB N/A N/A
x86_64 128GB 256GB [1TB] 1TB 6TB [64TB] 3TB [64TB]
POWER 64GB 128GB [1TB] 512GB [1TB] 2TB 2TB
System z 256GB (z900) 1.5TB (z10 EC) 3TB (z196) 3TB (z196) 3TB (z196)
Maximum number of device paths (“sd” devices)
256 256 1,024 8,192 10,000
Required minimums
x86 256MB 256MB 512MB minimum/1 GB/logical CPU recommended 512MB minimum/1 GB/logical CPU recommended N/A
x86_64 256MB 256MB 512MB minimum/1 GB/logical CPU recommended 1GB minimum/1 GB/logical CPU recommended 1GB minimum/1 GB/logical CPU recommended
Itanium 2 512MB 512MB 512MB/1 GB/logical CPU recommended N/A N/A
POWER 512MB 512MB 1GB minimum/2GB recommended 2GB minimum/2GB required per install 2GB minimum/2GB required per install
Minimum diskspace 800MB 800MB 1GB minimum/5GB recommended 1GB minimum/5GB recommended 10GB minimum/20GB recommended
File systems and storage limits
Maximum filesize (Ext3) 2TB 2TB 2TB 2TB 2TB
Maximum file system size (Ext3) 2TB 8TB 16TB 16TB 16TB
Maximum file size (Ext4) 16TB 16TB 16TB
Maximum file system size (Ext4) 16TB [1EB] 16TB [1EB] 50TB [1EB]
Maximum file size (GFS) 2TB 16TB [8EB] 16TB [8EB] N/A N/A
Maximum file system size (GFS) 2TB 16TB [8EB] 16TB [8EB] N/A N/A
Maximum file size (GFS2) 100TB [8EB] 100TB [8EB] 100TB [8EB]
Maximum file system size (GFS2) 100TB [8EB] 100TB [8EB] 100TB [8EB]
Maximum file size (XFS) 100TB [8EB] 100TB [8EB] 500TB [8EB]
Maximum file system size (XFS) 100TB [16EB] 100TB [16EB] 500TB [16EB]
Maximum Boot LUN size (BIOS) 2TB 2TB 2TB
Maximum Boot LUN size (UEFI) N/A 32bit (i686) – 2TB,
64bit – 16TB (tested limit)
50TB
Maximum x86 per-process virtual address space Approx. 4GB Approx. 4GB Approx. 3GB Approx. 3GB N/A
Maximum x86_64 per-process virtual address space 512GB 2TB 128TB 128TB
Kernel and OS features
Kernel foundation Linux 2.4.21 Linux 2.6.9 Linux 2.6.18 2.6.32 – 2.6.34 3.10
Compiler/toolchain GCC 3.2 GCC 3.4 GCC 4.1 GCC 4.4 GCC 4.8.2
Languages supported 10 15 19 22 22
NIAP/CC certified Yes (3+) Yes (4+) Yes (4+) Yes (4+) Under Evaluation (4+)
Common Criteria certified KVM Evaluated Evaluated Under Evaluation
IPv6 Ready Logo Phase 2 Ready Logo Phase 2 Under Evaluation
FIPS certified Yes (7 modules) Yes (8 modules) Under Evaluation (9 modules)
Common Operating Environment (COE) compliant Yes Yes N/A N/A N/A
LSB-compliant Yes – 1.3 Yes – 3 Yes – 3.1 Yes – 4.0 Under Evaluation (4.1)
GB18030 No Yes Yes Yes Yes
Client environment
Desktop GUI Gnome 2.2 Gnome 2.8 Gnome 2.16 Gnome 2.28 Gnome 3.8
Graphics XFree86 X.org X.org 7.1.1 X.org 7.4 X.org 7.7
OpenOffice V1.1 V1.1.2 V2.0.4 V3.2 LibreOffice V4.1.4
Gnome Evolution V1.4 V2.0 V2.8.0 V2.28 V3.8.5
Default browser Mozilla Firefox Firefox 1.5 Firefox 3.6 Firefox 24.5

Structure of Linux

Here we will be discussing the basics of LINUX, starting with the structure of the OS. The Basic components will be the Kernel, Shell and FHS (Filesystem Hierarchy Standard) . Let’s go through these components in detail..

STRUCTURE

The Kernel

Read more

The Kernel is the Heart of an operating system (OS). Kernel manages everything of a Linux OS. It performs tasks that create and maintain the Linux environment.  It is the communication channel between the hardware and shell. The hardware operations are directed by Shell and are passed through to the right hardware by Kernel.

Structure

SHELL

 

 

Simply put, the shell is a program that takes your commands from the keyboard and gives them to the operating system to perform. . It  is the interface between you and Linux . The commands which we issued , which is interpreted and passed on to the kernel for processing.

 

1

 

There are variable types of shells available in Linux. Most Linux varieties use Bourne-Again shell(bash) but support various others: Korn Shell, Bourne shell, C shell, etc. For all intensive purposes you can just stick with bash but I will show you how to change this if you want to. As you advance you can use shells to create scripts to automate tasks, making your daily routine all the more easier

Filesystem Hierarchy Standard

Linux uses the Filesystem Hierarchy Standard (FHS) file system structure, which defines the names, locations, and permissions for many file types and directories.

4

/ – The root directory. Everything in Linux is under root directory. The first stage of Linux filesystem structure.

/bin – Most of the command binary files are under this directory. General commands including ls, man, mv etc… are all under /bin.

/boot – Necessary boot files for Linux are kept under /boot.

 

 

/dev – The device files are located in /dev

/etc – Configuration files are saved under /etc. This directory is just like the control panel for a Windows host.

/home – For all users except the root user, the home directory will be placed in /home. For e.g, /home/beginnersforum.

/media – /media will be used for mounting external storage devices

/mnt – Temporary mounted file systems

/opt — Application programs directory

/sbin — Additional system binaries.

/tmp – As the name indicates, a temporary directory for files.

/usr – The largest directory in Linux. Application files and config files are also kept under here

/var – var stands for variable , that the Variable data on a system. Data that will change as the system is running (Log files, backups, cache, etc.)

/root – Home directory for root as already discussed

This directory structure is everything in Linux.

We can conclude the basic components of Linux here even-though the topic is very deep. More in coming posts. Enjoy reading…!

1 2