List of Figures

2.1. SEND and RECEIVE message passing primitives.

2.2. The sender is blocked while the receiver is not ready to receive.

2.3. The receiver is blocked while the message is not being received.

2.4. Giving the name of the MINIX system that will be installed.

2.5. Launching the virtualized MINIX.

2.6. Starting the installation.

2.7. Loading the system from disk.

2.8. We accept defaults, mutatis mutandis.

2.9. MINIX starts from hard disk now.

2.10. Opening the source file kernel/main.c with vi.

2.11. The modification of the function announce() in the kernel/main.c source file.

2.12. The booting of the newly compiled kernel.

2.13. The message from the kernel.

2.14. The first step of managing packages.

2.15.

2.16. Printing out the size of the PCB and the size of the process table.

2.17. Read the size of the PCB and the size of the process table.

2.18. Extending the MINIC PCB.

2.19. Counting massages.

2.20. The kernel process table.

2.21. Connecting a debug function to a function key.

2.22. The beginning of the function uzenetszam_dmp.

2.23. The midst of the function uzenetszam_dmp.

2.24. The end of the function uzenetszam_dmp.

2.25. The prototype of the function uzenetszam_dmp.

2.26. Displaying the IPC matrix.

2.27. List of the non-empty slots from the process table.

2.28. An array to store the „IPC matrix”.

2.29. Incrementing of the appropriate element of the uzenetszam array.

2.30. This is the uzenetszam that we defined in the server layer.

2.31. Usage of the sys_getmatrix system call that will be newly developed.

2.32. Printing the matrix.

2.33. Defining the sys_getmatrix macro.

2.34. The GET_MATRIX macro.

2.35. Supplying the do_getinfo system call.

2.36. Displaying the IPC matrix in the second solution.

3.1. Downloading the kernel sources.

3.2. Making the .config with command make menuconfig.

3.3. Setting the option Kernel .config support.

3.4. Starting the compiling.

3.5. Starting the installation.

3.6. The version of the running kernel.

3.7. The updated GRUB menu.

3.8. The new kernel.

3.9. Switching off the option Enable loadable module support.

3.10. The size of the kernel image.

3.11. The circular doubly linked list of PCBs in Linux.

4.1. Compiling the client and the server.

4.2. Running the client and the server.

4.3. Checking the results.

5.1. The LightFC++ team assembles before kick off using the move command.

5.2. After kick off the players move using the pos command.

5.3. Testing the throw-in: player 11 kicks the ball across the touch line.

5.4. Testing of the throw-in: player 4 starts to move towards the ball.

5.5. Testing the throw-in: player 4 is closer than 30 meters.

5.6. Testing of the throw-in: player 4 has just arrived to the ball.

5.7. Testing of the throw-in: player 4 passes the ball to player 3.

5.8. Testing the throw-in: the ball is moving towards player 3.

5.9. The 4-4-2 formation.

5.10. Corner kick formations.

5.11. Player 3 and player 6 should go to the ball.

5.12. An opposing player gains possession of the ball.

5.13. A portion of the soccerwindow2's log file.

5.14. The Debrecen Round Forest FC++'s team logo in the soccerwindow2 and the rcssmonitor.

6.1. The starting icon of the Seventh Eye.

6.2. The splash screen of the Seventh Eye.

6.3. The main menu of the Seventh Eye.