1. Open a new terminal to your docker container

You run the docker image as in:
~/Downloads/pcs3746-sistemas-operacionais/1$ ./run.sh
In your ubuntu, do:
docker ps, as in:
~/Downloads/pcs3746-sistemas-operacionais/1$ docker ps
CONTAINER ID        IMAGE                  COMMAND                  CREATED             STATUS              PORTS               NAMES
ded8427efd96        tiagoshibata/pcs3746   "/entrypoint.sh /def…"   5 hours ago         Up 5 hours                              focused_swartz

You may see that we have the docker image tiagoshibata running on a docker container with ID ded8427efd96. It running for 5 hours and it has an image name blessed by docker: focused_swartz.
Now, you may open another terminal and enter again in the docker container.
Do:
~/Downloads/pcs3746-sistemas-operacionais/1$ docker exec -ti focused_swartz bash
Note that you must insert the name given by "docker ps" and not necessarily focused_swartz.

~/Downloads/pcs3746-sistemas-operacionais/1$ docker exec -ti focused_swartz bash
root@ded8427efd96:/# 
root@ded8427efd96:/# su student
To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.

student@ded8427efd96:/$ ps ax
  PID TTY      STAT   TIME COMMAND
    1 pts/0    Ss+    0:00 /bin/bash /entrypoint.sh /default_cmd.sh
    7 pts/0    S+     0:00 su student -c env PATH=/usr/local/sbin:/usr/local/bin
    8 ?        Ss     0:00 /bin/bash /default_cmd.sh
 2616 ?        Sl     0:01 qemu-system-arm -M versatilepb -m 128M -nographic -ke
 2620 pts/1    Ss     0:00 bash
 2630 pts/1    S      0:00 su student
 2631 pts/1    S+     0:00 bash
 2640 pts/2    Ss     0:00 bash
 2650 pts/2    S      0:00 su student
 2651 pts/2    S      0:00 bash
 2658 pts/2    S+     0:00 arm-none-eabi-gdb -ex target remote:1234 /home/studen
 2666 pts/3    Ss     0:00 bash
 2675 pts/3    S      0:00 su student
 2676 pts/3    S      0:00 bash
 2682 pts/3    R+     0:00 ps ax
student@ded8427efd96:/$ 

Now you may see all the processes running on the ubuntu inside your docker image, specially, you may see qemu-system-arm.
That is it! You may create as many terminals to your docker container (an instance of your docker image) as you want.
In the next post, I will show how this new terminal may connect to qemu via gdb.





Comentários

Postar um comentário

Postagens mais visitadas deste blog

Basics on ARM processor

Imagem
I am also teaching "Laboratory of Microprocessors" focusing ARM. I use  ARM Lab Manual  for the first experiences.  I have been asking students to install a tool chain in ubuntu to develop experiments in the simulator provided by arm-...-gdb. Last year, one team made everything as the docker image: https://github.com/EpicEric/gcc-arm.git In order to use it:  git clone https://github.com/EpicEric/gcc-arm.git See README.md  cd gcc-arm/ ./build_docker.sh emacs # any other editor that you prefer; perhaps, you will need sudo,and perhaps gedit suchs as:                sudo ./build_docker.sh gedit docker run --rm -ti -v "$PWD/src":/home/student/src epiceric/gcc-arm Note that your directory $PWD/src is attached to /home/student/src. In this docker image, we have 2 tool-chains: arm-elf and arm-none-eabi. In the first part of the course, we are using arm-elf. We will use arm-none-eabi to deal with the versatille board, emulated by qemu. The environment contai
Leia mais

Assignments - 1

Imagem
My Operating System course has, generally, 4 to 5 assignments corresponding to each chapter of the book: " Operating Systems Design and Implementation, Third Edition ", i.e., 1. Introduction, 2. Processes, 3. Input and Output, 4. Memory and 5. File Systems. For the first assignment, I ask students to implement a simple system call. Generally, I divide the class into 10 teams which are given 10 different tasks. General Instructions to the First Assignment A system call makes a software interrupt. All teams must install docker and Shibata's work, visualize the switch from user to kernel mode following:  http://linux-kernel-lab.blogspot.com.br/2018/04/arm-linux-kernel-on-docker-image-with.html http://linux-kernel-lab.blogspot.com.br/2018/04/first-run.html http://linux-kernel-lab.blogspot.com.br/2018/04/first-init.html http://linux-kernel-lab.blogspot.com.br/2018/04/rebuilding-new-docker-image.html http://linux-kernel-lab.blogspot.com.br/2018/04/creating-new-te
Leia mais

Assignments 2- 2021

Imagem
Phase 2 All teams, please study:  https://linux-kernel-lab.blogspot.com/2018/06/block-and-unblock-process-assignment.html Team 1 - process hierachy Study: -V52: https://www.youtube.com/watch?v=tSnT9SYAb9A Create the system call pid_father() which returns the pid of the father (see task_struct).  Make init creates one child which creates one grandson. Both init and grandson continually prints "init" and father's pid, however, the child process, exits. What happens to the grandson parent? Study the linux source code and show how the kernel changes the grandson's father. Team 2 - signal Study the following code: #include<stdio.h> #include<signal.h> void bypass_sigint(int sig_no) {   printf("divide by zero\n"); } int main() {   int a,b,c;     struct sigaction sa;     memset(&sa, 0, sizeof(sa));     sa.sa_handler = &bypass_sigint;     sigaction(SIGFPE, &sa,NULL);     while (1) {       sleep(1);         printf("do nothing \n &quo
Leia mais