LAB_0 operating system experiment preparation (full)

I. Introduction to the experiment

Experimental purpose:

  share picture

knowledge reserve:

span>

  share picture

2. Related downloads

1. Download the mirror file

This image file is of VDI type, and can only be downloaded with visualbox

   link: https://pan .baidu.com/s/1L7WX6ju49DYC6ZS_wNxGkQ < /span>
   extraction code: y397

   Description: This image file is based on Ubuntu encapsulated by the teacher almost everything needed for the experiment

2, visualbox download

   download address: span>

  http://www.virtualbox.org/wiki/Downloads

< p>   download step reference:

  https://jingyan.baidu.com/article/425e69e61f267bbe15fc1621.html

3. Installation

  share picture  

  share picture

   just click to create.

three, related content

(1) About the experimental environment

< p>  Open the terminal

  share picture

After    is opened, it looks like this

  share picture

 Check the instructions given by the teacher, the instruction file is README.md

share picture

see the specific content for yourself .

(2) specific operations

①View and modify the code

software understand

cd enter/ moocos/ucore_lab/labcodes/lab1 is behind this directory

you can use understand to view< /p>

Just enter understand directly


understand cracking:

However, this understanding cannot be used. You need to purchase the product or enter the license

Don’t worry, the license is ready for you here

I forgot to take the screenshot, respectfully Please understand.

Select Enter License Code

select again Add Eval or SDL

then enter 19878CBBFB13

the mailbox can be omitted, click OK


②Compiled code

The same is cd After entering the directory /moocos/ucore_lab/labcodes/lab1,

Enter make,

[~/moocos/ucore_lab/labcodes_answer]
moocos-> cd lab1_result
[~/moocos/ucore_lab/labcodes_answer /lab1_result]
moocos-> make
+ cc kern/init/init.c
+ cc kern/libs/ readline.c
+ cc kern/libs/stdio.c
+ cc kern/debug/kdebug.c
+ cc kern/debug/kmonitor.c
+ cc kern/debug/panic.c
+ cc kern/ driver/clock.c
+ cc kern/driver/console.c
+ cc kern/driver/intr.c
+ cc kern/driver/picirq.c
+ cc kern/trap/trap.c< br>+ cc kern/trap/trapentry.S
+ cc kern/trap/vectors.S
+ cc kern/mm/pmm.c
+ cc libs/printfmt.c
+ cc libs/string.c
+ ld bin/kernel
+ cc boot/bootasm.S
+ cc boot/bootmain.c
+ cc tools/sign.c
+ ld bin /bootblock
‘obj/bootblock.out’ size: 488 bytes
build 512 bytes boot sector:’bin/bootblock’ success!
10000+0 records in
10000+0 records out
5120000 bytes (5.1 MB) copied, 0.0776545 s, 65.9 MB/s
1+0 records in
1+0 records out
512 bytes (512 B) copied, 9.8909e-05 s, 5.2 MB/s
146+1 records in
146+1 records out< /span>
74923 bytes (75 kB) copied, 0.00031777 s, 236 MB/s
[~/moocos/ucore_lab/labcodes_answer/lab1_result]

Enter make qEBMU

In hardware simulation Run the program in the environment

share picture

③Check and score

In this integrated environment, there is an evaluation function

input: make grade

share pictures

At this point, you should have a general understanding of the operating system experiment. & Understand some basic operations of Linux.


The operating system class has entered the experimental stage, and I was confused when I first pondered it , Took a lot of detours. I spent a lot of time trying to set up the experimental environment by myself, but failed. However, trying to use the experimental environment given by the teacher is very smooth, and I hope it can help students who see my blog. Welcome everyone to leave a message in the comment area!

Leave a Comment

Your email address will not be published.