Skip to main content

Introduction - Day -1

We will start this training on RHEL7.3
Normally there are 3 ways to interact with any OS-
1. GUI(graphical user interface) - In simple words we can say interacting with OS using mouse. This the same way you are interacting with Windows.
2. CLI(Command line interface) - In this way user can't use mouse because there we don't have any graphics(icons/buttons) so that you can double click and open the things and select etc.
3. API(Application programming interface) - Normal user don't this, it is specially for developers

Here I'll talk about CLI, whatever things you do in GUI, 99% of them you can do from CLI as well. The beauty of CLI is that we can do the things very fastly and also it requires very limited/less resource(compute unit or we can say RAM/CPU etc..).

Let's take an example how CLI is faster than GUI-
Use case: Open 100 terminals - This task can be completed in two way
(A) - GUI(Right Click on home screen and then select open terminal, same thing we have to do 100 times and at the end of this task 100 terminals will be opened). Which is initially OK but I don't like this kind of manual effort. We can do the same thing very smartly and easily with computer speed. May be manually it take 10 minutes but using CLI it can be done within few steps. To understand this in detail, please watch this video....
(B) - CLI

One more use case I want to tell you, whenever we give any input using mouse(double click to open something) in background some program executes by some command and we know very well that executable state of any program is known as process and this process will complete the task which we have give to system.
Let me explain in more simple words, for example lets suppose you have a requirement so that you want to launch #Firefox in your system, so that you will double click on Firefox icon and after few milliseconds Firefox is ready in front of you. But think in another way, what exactly happen in background when you clicked on Firefox icon, if somehow you know that then you can fix below kind issue in case you come across in future
Mouse is not working - then you can run the program manually and launch firefox easily. It is just starting so I am not going into very much technical but this is not a small thing, if you know that program name then you can do lots of things. we will discuss in future.
To explain these things in more easy way I am preparing a video please watch and clear you concept and enjoy the things....For video Click here...

Comments

Popular posts from this blog

error: db5 error(11) from dbenv->open: Resource temporarily unavailable

If rpm command is not working in your system and it is giving an error message( error: db5 error(11) from dbenv->open: Resource temporarily unavailable ). What is the root cause of this issue? How to fix this issue?   just a single command- [root@localhost rpm]# rpm --rebuilddb Detailed error message- [root@localhost rpm]# rpm -q firefox ^Cerror: db5 error(11) from dbenv->open: Resource temporarily unavailable error: cannot open Packages index using db5 - Resource temporarily unavailable (11) error: cannot open Packages database in /var/lib/rpm ^Cerror: db5 error(11) from dbenv->open: Resource temporarily unavailable error: cannot open Packages database in /var/lib/rpm package firefox is not installed [root@localhost rpm]# RPM manage a database in which it store all information related to packages installed in our system. /var/lib/rpm, this is directory where this information is available. [root@localhost rpm]# cd /var/lib/rpm [root@

Failed to get D-Bus connection: Operation not permitted

" Failed to get D-Bus connection: Operation not permitted " - systemctl command is not working in Docker container. If systemctl command is not working in your container and giving subjected error message then simple solution of this error is, create container with -- privileged option and also provide init file full path  /usr/sbin/init [root@server109 ~]# docker container run -dit --privileged --name systemctl_not_working_centos1 centos:7 /usr/sbin/init For detailed explanation and understanding I am writing more about it, please have look below. If we have a daemon based program(httpd, sshd, jenkins, docker etc.) running inside a container and we would like to start/stop or check status of daemon inside docker then it becomes difficult for us to perform such operations , because by default systemctl and service  commands don't work inside docker. Normally we run below commands to check services status in Linux systems. [root@server109 ~]# systemctl status

AWS cloud automation using Terraform

In this post I'll create multiple resources in AWS cloud using Terraform . Terraform is an infrastructure as code( IAC ) software which can do lots of things but it is superb in cloud automation. To use Terraform we have write code in a high-level configuration language known as Hashicorp Configuration Language , optionally we can write code in JSON as well. I'll create below service using Terraform- 1. Create the key-pair and security group which allow inbound traffic on port 80 and 22 2. Launch EC2 instance. 3. To create EC2 instance use same key and security group which created in step 1 4. Launch Volume(EBS) and mount this volume into /var/www/html directory 5. Upload index.php file and an image on GitHub repository 6. Clone GitHub repository into /var/www/html 7. Create S3 bucket, copy images from GitHub repo into it and set permission to public readable 8 Create a CloudFront use S3 bucket(which contains images) and use the CloudFront URL to update code in /var/w