other application processes.3,/LINUXRC responsible for the system after the start of the configuration(1) It is like a house built after not directly live, but also to decorate the same; the operating system can not be used directly after startup, to configure.(2) Application layer configuration after operating system startup (usually called runtime configuration, English shorthand etc) is to make our operating system more convenient to use, more suitable for my personal hobby or practicality.4
require calibration screenConfiguring Wired Networks# ifconfig eth0 192.168.17.150 netmask 255.255.255.0 up#route add default GW 192.168.17.254 dev eth0#/system/busybox/sbin/ifconfig Querying the current IP configuration of the Development Board#/system/busybox/sbin/route Query Routing tablePut all the setup commands into the script file Linuxre (depending on the situation), to ensure that each boot can au
Cluster-dns analytic application in the cluster? Create namespaceKubectl create-f Kube-system.yaml? Create ReplicationcontrollerKubectl create-f Skydns-rc.yaml? Create serviceKubectl create-f Skydns-service.yamlDelete is to replace "create" in the above three commands with "delete"6. View the startup status of the Dns-pod[[email protected] k8s-master dns]# kubectl get pod--namespace=kube-systemNAME Ready STATUS Restartskube-dns-v11-ey14j 4/4 Running 8 1d7. View the information for the service d
X86 platform based on the grub2+busybo+linux-2.6.36 making Linux systemFirst, download the kernel source code, GRUB2 source code, and BusyBox Source:
Download GRUB2 Source code
ftp://ftp.gnu.org/gnu/grub/to find the desired version, here to choose grub-1.99.tar.gz
Download BusyBox Source code
http://www.busybox.net/downloads/to find the desired version, here to choose
1. Re-production and file system startup or the following error occurred
[ 1.955000] Request_module:runaway loop modprobe binfmt-464c
//This error is due to the fact that the cross-compilation tool
configuration BusyBox is not configured Found in configuration busybox setting->build options->
write prefix in cross compile arm-none-linux-gnueabi-
[ 1.965000] Failed to EXECUTE/LINUXRC (error-8). Att
Android phone can be WiFi internet, this is good. But when there is no WiFi, how to go on Ah, 3G---> Limited traffic, watching video is not cost-effective! Here I summarize several methods for your reference.Method One: USB cable, mobile phone wired internet1, connect the phone via USB cable to the computer, check the "settings, wireless and network binding and portable hotspot--USB binding" option, the computer will appear the virtual network card,To facilitate the resolution, the virtual netwo
specific applications. For applications such as industrial control that do not need to update control programs frequently, it is sufficient to select a read-only file system such as caramfs, in addition, the cramfs compression rate is as high as 50%, which can greatly save our storage space. However, for applications that need to store data such as data collection, read-only file systems cannot meet the needs of application systems, we can choose a readable file system like jffs or yaffs. Howev
1. Cross-compile busybox
Version: busybox-1.22.0.tar.bz2
Modify makefile to add a cross-compiler path
Arch? = Arm
Cross_compile? =/Opt/arm-2009q1/bin/ARM-None-Linux-gnueabi-
Configure busybox
Build options --->
[*] Build busybox as a static binary (no shared libs)
General configuration --->
[*] Don't use/usr
Linux
devices in the/dev directory during system device initialization (that is, after the system is started, the/dev directory contains the device files of various devices, which can be used directly ). In addition, it can also automatically delete the corresponding device file nodes under/dev after the device is uninstalled (this is useful for some hot swapping devices and is automatically created when plugged in, is automatically deleted when unplugging ). Another advantage is that when writing a
Directory
1. Write in front
2.devmem use
3. Application Layer
4. Kernel Layer
1. Write in frontRecently, when debugging, you need to access physical memory at the user level, and the application layer can use the devmem tool to access the physical address. View the source code, is actually the /dev/mem operation, through the mmap can map the physical address to the virtual address of the user space, completes the reading and writing to the device register in the user sp
be e.g.BusyBox and/or other applications and/or libraries.
host > mkdir mnthost > gunzip ramdisk.gzhost > mount -o loop ramdisk mnt/host > ... copy stuff you want to have in ramdisk to mnt...host > umount mnthost > gzip -v9 ramdisk
The resulting ramdisk.gz is now ready for usage. Note its size is smaller than Count> Cause of compression.
Note: Don't forget to create/copy some basic/dev/xxx nodes to ramdisk.
Note: If BusyBox or applications in ramdisk
, saving the use of the/sbin/arp program. Secondly, in an embedded system, the user is no longer a general PCUsers can simplify the program interface, help online, and even simplify program functions. Busybox [2]It is a representative set of tool programs. It provides common UNIX functions such as file tools, Shell, text processing, and compression programs with a single small program. Table4. List busybox
ARM-Linux transplantation (III)-init process Startup Process Analysis
K-style
Reprinted please indicate from Hengyang Normal College 08 electric 2 k-style http://blog.csdn.net/ayangke,QQ:843308498 mailbox: yangkeemail@qq.com
We usually use busybox to build the necessary applications for the root file system. Busybox determines the operation to be performed by passing in parameters. When the INIT process s
: ......
4: os.writeBytes("exit\n");
5: os.flush();
From the code above, we can see that the su program must be run first. In fact, the root secrets are all in the SU program, the android root permission Cracking Analysis describes that the default su program of the Android system can run only root and shell, which is safe. If you remove this restriction, it is root cracking!
Next, we will analyze how the program obtains the root permission. If you are familiar with the Linux su command, y
root file system found/# MountMount: No/proc/mounts/# Mount-T proc/procMount: mounting proc on/proc failed: no such file or directoryTherefore, the corresponding directory must be created in the RCS./# Mount-Mount: mounting none on/dev/SHM failed: no such file or directoryMount: mounting none on/dev/PTS failed: no such file or directoryCause Analysis: fstab is mounted in a forward manner, and SHM and PTS under/dev are overwritten when mounted to the/dev directory. Therefore, it is best to manua
execute the above process. Most other tool kits (including busybox) call this command "switch_root ".-------------------------------------------------------------------------------Populating initramfsBy default, the 2.6 kernel always generates a gzipped cpio document, which is linked with the kernel. This document is blank by default. The size of this document in x86 environment is 134 bytes.The config_initramfs_source configuration parameter specifi
parameters, this is because the/sbin/init initialization script is started by default. (The linuxrc file generated after compilation and installation of busybox is the symbol file pointing to/bin/busybox. Delete it and rewrite the script by yourself ). This method is not used in my file system, so you do not need to set init =/linuxrc.
The Busybox init process
The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion;
products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the
content of the page makes you feel confusing, please write us an email, we will handle the problem
within 5 days after receiving your email.
If you find any instances of plagiarism from the community, please send an email to:
info-contact@alibabacloud.com
and provide relevant evidence. A staff member will contact you within 5 working days.