Shulou(Shulou.com)06/02 Report--

How to build Linux kernel experimental environment, many novices are not very clear about this, in order to help you solve this problem, the following editor will explain for you in detail, people with this need can come to learn, I hope you can gain something.

Linux kernel experimental environment

Can be built quickly and supports Docker, Qemu, Ubuntu, Mac OSX, Windows, Web

Founded by Wu Zhangjin in 2016-06-19

Comment and reward

1 Project description

The project aims to quickly build a Linux kernel development environment based on Qemu.

Working with documents: README.md

Online experiment

Taixiao experimental head

2 related articles

Rapid Construction of Linux 0.11 Experimental Environment based on Docker

3 5-minute tutorial 3.1 preparation

Take Ubuntu and Qemu as examples. Install Docker CE first for other Linux and Mac OSX systems. For Windows system, please download and install Docker Toolbox first.

If you want to exempt sudo from using linux lab after installing docker, be sure to join the docker user group and restart the system.

$sudo usermod-aG docker $USER

As the docker image file is relatively large, about 1G, please wait patiently when downloading. In addition, in order to improve the download speed, it is recommended to change the mirror library to the local one by configuring docker, and restart the docker service after replacement.

$grep registry-mirror / etc/default/docker

DOCKER_OPTS= "$DOCKER_OPTS-- registry-mirror= https://docker.mirrors.ustc.edu.cn"

$service docker restart

If the docker default network environment conflicts with the local LAN environment address, update the docker network environment and restart the docker service as follows.

$grep bip / etc/default/docker

DOCKER_OPTS= "$DOCKER_OPTS-- bip=10.66.0.10/16"

$service docker restart

If the above changes do not take effect, please modify it in a file such as / lib/systemd/system/docker.service before restarting the docker service.

$grep dockerd / lib/systemd/system/docker.service

ExecStart=/usr/bin/dockerd-H fd://-- bip=10.66.0.10/16-- registry-mirror= https://docker.mirrors.ustc.edu.cn

$service docker restart

If you use Docker Toolbox, because the default default system installed does not provide a desktop, you need to obtain the external network address of the system, that is, the IP address of the eth2 port, and then access it from the external system.

$ifconfig eth2 | grep 'inet addr' | tr-s''| tr':'| cut-d''- f4

192.168.99.100

If you install your own Linux system through Virtualbox, even if you have a desktop, you want to access it from an external system, you can add an eth2 port device by setting 'Network-> Adapter2-> Host-only Adapter'.

It is important to note that the default / root directory in the default system installed through Docker Toolbox is only mounted in memory, and the data will be lost after shutting down the system. Please do not use it to save the experimental data. You can use another directory to store it, such as / mnt/sda1, which is a virtual disk image file attached to Virtualbox. By default, it is 17.9G, which is enough to store common experimental environments.

3.2 working directory

Again, on Linux or Mac systems, you can find a working directory under ~ / Downloads or ~ / Documents and enter, for example:

$cd ~ / Documents

However, if you are using the default system installed by Docker Toolbox, the default working directory of the system is / root, which is only mounted in memory, so all data will be lost after shutting down the system, so you need to change to the / mnt/sda1 mentioned above, which is a disk image of the plug-in, and the data will be saved continuously after shutting down the system.

$cd / mnt/sda1

3.3 download

$git clone https://github.com/tinyclub/cloud-lab.git

$cd cloud-lab & & tools/docker/choose linux-lab

3.4 installation

$tools/docker/run # load the image and pull up a Linux Lab container

3.5 Quick tasting

After executing tools/docker/vnc, you will open a VNC web page, enter the password to log in according to the console prompt, and then open the Linux Lab console of the desktop and execute:

$make boot

An ARM board of versatilepb will be launched by default. To specify a development board, you can use:

$make list # View the list of supported

$make BOARD=malta # choose a MIPS board here: malta

$make boot

3.6 download more source code

$make core-source-j3 # downloads linux-stable, qemu and buildroot at the same time

3.7 configuration

$make root-defconfig # configure the root file system

$make kernel-checkout # check out a specific branch (make sure that the local changes are backed up before doing this)

$make kernel-defconfig # configure the kernel

$make root-menuconfig # manually configure the root file system

$make kernel-menuconfig # manually configure the kernel

3.8 compilation

$make root # compiles the root file system, which is a little slow. You need to download the compiler with sysroot

$make kernel # compiles the kernel using cross-compilers provided by Ubuntu and emdebian.org

3.9 Save all changes

$make save # saves new configurations and newly generated images

$make kconfig-save # Save to boards/BOARD/

$make rconfig-save

$make root-save # Save to prebuilt/

$make kernel-save

3.10 start the new root file system and kernel

You need to turn on boards/BOARD/Makefile to shield the compiled KIMAG and ROOTFS, and the newly compiled rootfs and kernel in the output/ directory will be started:

$vim boards/versatilepb/Makefile

# KIMAGE=$ (PREBUILT_KERNEL) / $(XARCH) / $(BOARD) / $(LINUX) / zImage

# ROOTFS=$ (PREBUILT_ROOTFS) / $(XARCH) / $(CPU) / rootfs.cpio.gz

$make boot

3.11 start the serial port

$make boot gateway 0 # use the combined key: `exit x`, or open another console to execute: `pkill qemu`

3.12 Select Rootfs device

$make boot ROOTDEV=/dev/nfs

$make boot ROOTDEV=/dev/ram

3.13 extension

By adding or modifying boards/BOARD/Makefile, you can flexibly configure information such as the development board, kernel version, and BuildRoot. Through it, you can flexibly create your own specific Linux experimental environment.

$cat boards/versatilepb/Makefile

ARCH=arm

XARCH=$ (ARCH)

CPU=arm926t

MEM=128M

LINUX=2.6.35

NETDEV=smc91c111

SERIAL=ttyAMA0

ROOTDEV=/dev/nfs

ORIIMG=arch/$ (ARCH) / boot/zImage

CCPRE=arm-linux-gnueabi-

KIMAGE=$ (PREBUILT_KERNEL) / $(XARCH) / $(BOARD) / $(LINUX) / zImage

ROOTFS=$ (PREBUILT_ROOTFS) / $(XARCH) / $(CPU) / rootfs.cpio.gz

The default kernel and Buildroot information corresponds to boards/BOARD/linux_$ {LINUX} _ defconfig and boards/BOARD/buildroot_$ {CPU} _ defconfig. If you want to add your own configuration, please note that it is consistent with the CPU and Linux configuration in boards/BOARD/Makefile.

3.14 more usage

The detailed usage will not be wordy here, please check the help by yourself.

$make help

3.15 experimental results

Is it helpful for you to read the above content? If you want to know more about the relevant knowledge or read more related articles, please follow the industry information channel, thank you for your support.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.