ProHoster > Блог > Gudanarwa > Yadda ake fara amfani da Yanayin mai amfani a cikin Linux

Yadda ake fara amfani da Yanayin mai amfani a cikin Linux

Gabatarwa daga mai fassara: Dangane da tushen shigar da yawa cikin rayuwarmu na nau'ikan kwantena daban-daban, yana iya zama mai ban sha'awa da amfani don gano tare da waɗanne fasahohin duk sun fara sau ɗaya. Wasu daga cikinsu za a iya amfani da su da amfani har yau, amma ba kowa ba ne ke tunawa da irin waɗannan hanyoyin (ko kuma ya san idan ba a kama su ba yayin ci gaba da sauri). Ɗayan irin wannan fasaha shine Linux Mode User. Marubucin na asali ya yi yawa na tono, yana gano wane daga cikin tsoffin abubuwan da ke faruwa har yanzu suna aiki kuma waɗanda ba su yi ba, kuma sun haɗa wani abu kamar umarnin mataki-mataki kan yadda ake samun kanku UML na gida a cikin 2k19. Kuma eh, mun gayyaci marubucin ainihin sakon zuwa Habr Cadey, don haka idan kuna da tambayoyi - tambaya cikin Turanci a cikin sharhi.

Yadda ake fara amfani da Yanayin mai amfani a cikin Linux

Yanayin mai amfani a cikin Linux shine, a haƙiƙa, tashar jiragen ruwa na Linux kernel zuwa kanta. Wannan yanayin yana ba ku damar gudanar da cikakken kernel na Linux azaman tsarin mai amfani kuma masu haɓakawa galibi ke amfani da su don gwada direbobi. Amma wannan yanayin kuma yana da amfani a matsayin kayan aikin keɓewa gabaɗaya, ƙa'idarsa ta yi kama da aikin injina. Wannan yanayin yana ba da ƙarin keɓewa fiye da Docker, amma ƙasa da cikakken injin kama-da-wane kamar KVM ko Akwatin Virtual.

Gabaɗaya, Yanayin Mai amfani na iya zama kamar baƙon kayan aiki mai wahala don amfani, amma har yanzu yana da amfaninsa. Bayan haka, wannan cikakkiyar kwaya ce ta Linux wacce ke gudana daga mai amfani mara amfani. Wannan fasalin yana ba da damar yuwuwar lambar da ba ta da aminci ta gudana ba tare da wata barazana ga na'ura mai masaukin baki ba. Kuma tunda wannan kwaya ce mai cikakken aiki, hanyoyinta sun keɓance daga na'ura mai ɗaukar hoto, wato Ayyukan da ke gudana a cikin Yanayin Mai amfani ba za su ganuwa ga mai watsa shiri ba. Wannan baya kama da kwandon Docker na yau da kullun, wanda a halin da ake ciki na'ura mai watsa shiri koyaushe yana ganin matakai a cikin ma'ajiyar. Dubi wannan yanki na pstree daga ɗaya daga cikin sabar na: 

containerd─┬─containerd-shim─┬─tini─┬─dnsd───19*[{dnsd}]
           │                 │      └─s6-svscan───s6-supervise
           │                 └─10*[{containerd-shim}]
           ├─containerd-shim─┬─tini─┬─aerial───21*[{aerial}]
           │                 │      └─s6-svscan───s6-supervise
           │                 └─10*[{containerd-shim}]
           ├─containerd-shim─┬─tini─┬─s6-svscan───s6-supervise
           │                 │      └─surl
           │                 └─9*[{containerd-shim}]
           ├─containerd-shim─┬─tini─┬─h───13*[{h}]
           │                 │      └─s6-svscan───s6-supervise
           │                 └─10*[{containerd-shim}]
           ├─containerd-shim─┬─goproxy───14*[{goproxy}]
           │                 └─9*[{containerd-shim}]
           └─32*[{containerd}]

Kuma kwatanta wannan zuwa pstree na Linux kernel a Yanayin Mai amfani:

linux─┬─5*[linux]
      └─slirp

Lokacin aiki tare da kwantena Docker, Ina iya gani daga mai masaukin suna sunayen hanyoyin da ke gudana a cikin baƙo. Tare da Yanayin Mai amfani na Linux, wannan ba zai yiwu ba. Me ake nufi? Wannan yana nufin kayan aikin sa ido waɗanda ke gudana ta tsarin tsarin dubawa na Linux kar a gani tafiyar matakai da ke gudana a cikin tsarin baƙo. Amma a wasu yanayi, wannan yanayin zai iya zama takobi mai kaifi biyu.

Gabaɗaya, gabaɗayan post ɗin da ke ƙasa tarin bincike ne da yunƙurin ƙoƙarin cimma sakamakon da ake so. Don yin wannan, dole ne in yi amfani da kayan aikin daɗaɗɗen kayan aiki, karanta tushen kernel, yin babban kuskuren lambar da aka rubuta a zamanin da nake har yanzu a makarantar firamare, da kuma tinker tare da Heroku yana ginawa ta amfani da binary na musamman don nemo kayan aikin da nake buƙata. . Duk wannan aikin ya sa mutanen da ke kan IRC dina suka kira ni sihiri. Ina fatan wannan sakon ya zama ingantaccen takaddun shaida ga wani don gwada abu iri ɗaya tare da sabbin kernels da nau'ikan OS.

gyara

Saita Yanayin Mai amfani na Linux ana yin shi ta matakai da yawa:

  • shigar da dogara ga mai watsa shiri;
  • zazzage kernel na Linux;
  • Tsarin ginin kwaya;
  • taro kwaya;
  • shigarwa na binary;
  • daidaita tsarin fayil ɗin baƙo;
  • zaɓi na sigogin ƙaddamar da kwaya;
  • kafa cibiyar sadarwar baƙo;
  • fara baƙo kwaya.

Ina ɗauka cewa idan kun yanke shawarar yin shi da kanku, wataƙila za ku yi duk abin da aka bayyana a cikin wasu tsarin Ubuntu ko Debian. Na yi ƙoƙarin aiwatar da duk abubuwan da ke sama a cikin rarraba da na fi so - Alpine, amma babu abin da ya zo, a fili saboda gaskiyar cewa Linux kernel yana da glibc-isms mai wuyar ɗaure don direbobi a Yanayin Mai amfani. Ina shirin bayar da rahoton wannan zuwa sama bayan na fahimci matsalar.

Shigar da abin dogara akan mai gida

Ubuntu yana buƙatar aƙalla fakiti masu zuwa don gina kernel na Linux ( ɗaukan shigarwa mai tsabta):

- 'build-essential'
- 'flex'
- 'bison'
- 'xz-utils'
- 'wget'
- 'ca-certificates'
- 'bc'
- 'linux-headers'

Kuna iya shigar da su tare da umarni mai zuwa (kamar tushen ko tare da sudo):

apt-get -y install build-essential flex bison xz-utils wget ca-certificates bc 
                   linux-headers-$(uname -r)

Lura cewa gudanar da shirin saitin menu na kernel na Linux zai buƙaci shigarwa libncurses-dev. Da fatan za a tabbatar an shigar da shi tare da umarni mai zuwa (kamar tushen ko tare da sudo):

apt-get -y install libncurses-dev

Zazzagewar kwaya

Yanke shawarar inda zaka zazzage sannan ka gina kwaya. Don wannan aiki, kuna buƙatar ware kusan 1,3 GB na sararin diski, don haka tabbatar cewa kuna da shi.

Bayan zuwa kernel.org kuma sami URL don zazzage sabuwar kwaya mai tsayayye. A lokacin rubuta wannan shine: https://cdn.kernel.org/pub/linux/kernel/v5.x/linux-5.1.16.tar.xz

Zazzage wannan fayil ta amfani da 'wget':

wget https://cdn.kernel.org/pub/linux/kernel/v5.x/linux-5.1.16.tar.xz

Kuma cire shi da 'tar':

tar xJf linux-5.1.16.tar.xz

Yanzu mun shigar da kundin adireshi da aka ƙirƙira lokacin buɗe kayan kwalta:

cd linux-5.1.16

Saitin ginin kwaya

Tsarin ginin kwaya saiti ne Makefiles с da yawa kayan aiki na al'ada da rubutun don sarrafa tsarin aiki. Da farko, buɗe shirin saitin ma'amala:

make ARCH=um menuconfig

Zai gina wani bangare kuma ya nuna maka akwatin maganganu. Lokacin'[Select]', za ku iya daidaitawa ta amfani da Space ko Shigar maɓallan. Kewaya taga, kamar yadda aka saba, tare da kiban maballin "sama" da "ƙasa", kuma zaɓi abubuwa - "hagu" ko "dama".

Ma'anar kallo -> yana nufin cewa kana cikin menu na ƙasa, ana samun dama ta maɓallin Shigar. Hanyar fita a fili ta hanyar '[Exit]'.

Haɗa waɗannan zaɓuɓɓukan a cikin '[Select]' kuma a tabbata suna da ''[*]' kusa da su:

UML-specific Options:
  - Host filesystem
Networking support (enable this to get the submenu to show up):
  - Networking options:
    - TCP/IP Networking
UML Network devices:
  - Virtual network device
  - SLiRP transport

Shi ke nan, za ku iya fita daga wannan taga ta hanyar zaɓar '[Exit]'. Kawai ka tabbata an sa ka ajiye tsarin a ƙarshen kuma zaɓi '[Yes]'.

Ina ba da shawarar ku yi wasa tare da zaɓuɓɓukan ginin kernel bayan karanta wannan post ɗin. Ta hanyar waɗannan gwaje-gwajen, zaku iya koyan abubuwa da yawa dangane da fahimtar aikin injiniyoyi masu ƙarancin ƙima da tasirin tutoci daban-daban akan taron sa.

Gina kwaya

Kwayar Linux babban shiri ne wanda ke yin abubuwa da yawa. Ko da tare da irin wannan ƙaramin tsari akan tsohuwar kayan aiki, yana iya ɗaukar ɗan lokaci kaɗan don ginawa. Don haka gina kernel tare da umarni mai zuwa:

make ARCH=um -j$(nproc)

Don me? Wannan umarnin zai gaya wa maginin mu ya yi amfani da duk abubuwan da ake samu na CPU da zaren a cikin aikin ginin. Tawaga $(nproc) a karshen Gina ya maye gurbin fitar da umarni nproc, wanda wani bangare ne na coreutils a cikin daidaitaccen ginin Ubuntu.

Bayan ɗan lokaci, za a haɗa kernel ɗin mu cikin fayil ɗin da za a iya aiwatarwa ./linux.

Shigar da binary

Tunda Yanayin Mai amfani a cikin Linux yana ƙirƙirar binary na yau da kullun, zaku iya shigar dashi kamar kowane mai amfani. Ga yadda na yi:

mkdir -p ~/bin
cp linux ~/bin/linux

Hakanan yana da kyau a tabbatar da hakan ~/bin yana cikin ku $PATH:

export PATH=$PATH:$HOME/bin

Saita tsarin fayil ɗin baƙo

Ƙirƙiri adireshi don tsarin fayil ɗin baƙo:

mkdir -p $HOME/prefix/uml-demo
cd $HOME/prefix

Bude alpinelinux.org kuma a ciki sashin saukewa sami ainihin hanyar zazzagewa MINI ROOT FILESYSTEM. A lokacin rubuta wannan shine:

http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/x86_64/alpine-minirootfs-3.10.0-x86_64.tar.gz

Zazzage wannan kwal ɗin ta amfani da wget:

wget -O alpine-rootfs.tgz http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/x86_64/alpine-minirootfs-3.10.0-x86_64.tar.gz

Yanzu shigar da tsarin tsarin fayil ɗin baƙo kuma cire tarihin:

cd uml-demo
tar xf ../alpine-rootfs.tgz

Ayyukan da aka bayyana za su haifar da ƙaramin samfurin tsarin fayil. Saboda yanayin tsarin, zai yi matukar wahala a shigar da fakiti ta hanyar mai sarrafa apk na Alpine. Amma wannan FS zai isa ya kimanta ra'ayin gaba ɗaya.

Muna kuma buƙatar kayan aiki tini don hana amfani da ƙwaƙwalwar ajiya aljan tafiyar matakai bakon kwaya. 

wget -O tini https://github.com/krallin/tini/releases/download/v0.18.0/tini-static
chmod +x tini

Ƙirƙirar layin umarni kernel

Kernel na Linux, kamar sauran shirye-shirye, yana da gardamar layin umarni waɗanda za a iya isa ga ta hanyar tantance maɓalli. --help.

Kansa - taimako

linux --help
User Mode Linux v5.1.16
        available at http://user-mode-linux.sourceforge.net/

--showconfig
    Prints the config file that this UML binary was generated from.

iomem=<name>,<file>
    Configure <file> as an IO memory region named <name>.

mem=<Amount of desired ram>
    This controls how much "physical" memory the kernel allocates
    for the system. The size is specified as a number followed by
    one of 'k', 'K', 'm', 'M', which have the obvious meanings.
    This is not related to the amount of memory in the host.  It can
    be more, and the excess, if it's ever used, will just be swapped out.
        Example: mem=64M

--help
    Prints this message.

debug
    this flag is not needed to run gdb on UML in skas mode

root=<file containing the root fs>
    This is actually used by the generic kernel in exactly the same
    way as in any other kernel. If you configure a number of block
    devices and want to boot off something other than ubd0, you
    would use something like:
        root=/dev/ubd5

--version
    Prints the version number of the kernel.

umid=<name>
    This is used to assign a unique identity to this UML machine and
    is used for naming the pid file and management console socket.

con[0-9]*=<channel description>
    Attach a console or serial line to a host channel.  See
    http://user-mode-linux.sourceforge.net/old/input.html for a complete
    description of this switch.

eth[0-9]+=<transport>,<options>
    Configure a network device.
    
aio=2.4
    This is used to force UML to use 2.4-style AIO even when 2.6 AIO is
    available.  2.4 AIO is a single thread that handles one request at a
    time, synchronously.  2.6 AIO is a thread which uses the 2.6 AIO
    interface to handle an arbitrary number of pending requests.  2.6 AIO
    is not available in tt mode, on 2.4 hosts, or when UML is built with
    /usr/include/linux/aio_abi.h not available.  Many distributions don't
    include aio_abi.h, so you will need to copy it from a kernel tree to
    your /usr/include/linux in order to build an AIO-capable UML

nosysemu
    Turns off syscall emulation patch for ptrace (SYSEMU).
    SYSEMU is a performance-patch introduced by Laurent Vivier. It changes
    behaviour of ptrace() and helps reduce host context switch rates.
    To make it work, you need a kernel patch for your host, too.
    See http://perso.wanadoo.fr/laurent.vivier/UML/ for further
    information.

uml_dir=<directory>
    The location to place the pid and umid files.

quiet
    Turns off information messages during boot.

hostfs=<root dir>,<flags>,...
    This is used to set hostfs parameters.  The root directory argument
    is used to confine all hostfs mounts to within the specified directory
    tree on the host.  If this isn't specified, then a user inside UML can
    mount anything on the host that's accessible to the user that's running
    it.
    The only flag currently supported is 'append', which specifies that all
    files opened by hostfs will be opened in append mode.

Wannan rukunin yana haskaka mahimman sigogin ƙaddamarwa. Bari mu gudanar da kernel tare da mafi ƙarancin zaɓin da ake buƙata:

linux 
  root=/dev/root 
  rootfstype=hostfs 
  rootflags=$HOME/prefix/uml-demo 
  rw 
  mem=64M 
  init=/bin/sh

Layukan da ke sama suna gaya wa kernel ɗinmu mai zuwa:

  • A ɗauka tushen tsarin fayil ɗin na'urar karya ce /dev/root.
  • Zaɓi runduna a matsayin direban tsarin fayil ɗin tushen.
  • Dutsen tsarin fayil ɗin baƙo da muka ƙirƙira akan tushen na'urar.
  • Kuma eh, a yanayin karanta-rubutu.
  • Yi amfani da 64 MB na RAM kawai (zaka iya amfani da ƙasa da yawa dangane da abin da kuke shirin yi, amma 64 MB yana kama da mafi kyawun adadin).
  • Kwayar tana farawa ta atomatik /bin/sh yadda init-tsari.

Gudun wannan umarni kuma yakamata ku sami wani abu kamar haka:

Ƙarin takardar

Core dump limits :
        soft - 0
        hard - NONE
Checking that ptrace can change system call numbers...OK
Checking syscall emulation patch for ptrace...OK
Checking advanced syscall emulation patch for ptrace...OK
Checking environment variables for a tempdir...none found
Checking if /dev/shm is on tmpfs...OK
Checking PROT_EXEC mmap in /dev/shm...OK
Adding 32137216 bytes to physical memory to account for exec-shield gap
Linux version 5.1.16 (cadey@kahless) (gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)) #30 Sun Jul 7 18:57:19 UTC 2019
Built 1 zonelists, mobility grouping on.  Total pages: 23898
Kernel command line: root=/dev/root rootflags=/home/cadey/dl/uml/alpine rootfstype=hostfs rw mem=64M init=/bin/sh
Dentry cache hash table entries: 16384 (order: 5, 131072 bytes)
Inode-cache hash table entries: 8192 (order: 4, 65536 bytes)
Memory: 59584K/96920K available (2692K kernel code, 708K rwdata, 588K rodata, 104K init, 244K bss, 37336K reserved, 0K cma-reserved)
SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
NR_IRQS: 15
clocksource: timer: mask: 0xffffffffffffffff max_cycles: 0x1cd42e205, max_idle_ns: 881590404426 ns
Calibrating delay loop... 7479.29 BogoMIPS (lpj=37396480)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 512 (order: 0, 4096 bytes)
Checking that host ptys support output SIGIO...Yes
Checking that host ptys support SIGIO on close...No, enabling workaround
devtmpfs: initialized
random: get_random_bytes called from setup_net+0x48/0x1e0 with crng_init=0
Using 2.6 host AIO
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
futex hash table entries: 256 (order: 0, 6144 bytes)
NET: Registered protocol family 16
clocksource: Switched to clocksource timer
NET: Registered protocol family 2
tcp_listen_portaddr_hash hash table entries: 256 (order: 0, 4096 bytes)
TCP established hash table entries: 1024 (order: 1, 8192 bytes)
TCP bind hash table entries: 1024 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 1024 bind 1024)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
console [stderr0] disabled
mconsole (version 2) initialized on /home/cadey/.uml/tEwIjm/mconsole
Checking host MADV_REMOVE support...OK
workingset: timestamp_bits=62 max_order=14 bucket_order=0
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
io scheduler noop registered (default)
io scheduler bfq registered
loop: module loaded
NET: Registered protocol family 17
Initialized stdio console driver
Using a channel type which is configured out of UML
setup_one_line failed for device 1 : Configuration failed
Using a channel type which is configured out of UML
setup_one_line failed for device 2 : Configuration failed
Using a channel type which is configured out of UML
setup_one_line failed for device 3 : Configuration failed
Using a channel type which is configured out of UML
setup_one_line failed for device 4 : Configuration failed
Using a channel type which is configured out of UML
setup_one_line failed for device 5 : Configuration failed
Using a channel type which is configured out of UML
setup_one_line failed for device 6 : Configuration failed
Using a channel type which is configured out of UML
setup_one_line failed for device 7 : Configuration failed
Using a channel type which is configured out of UML
setup_one_line failed for device 8 : Configuration failed
Using a channel type which is configured out of UML
setup_one_line failed for device 9 : Configuration failed
Using a channel type which is configured out of UML
setup_one_line failed for device 10 : Configuration failed
Using a channel type which is configured out of UML
setup_one_line failed for device 11 : Configuration failed
Using a channel type which is configured out of UML
setup_one_line failed for device 12 : Configuration failed
Using a channel type which is configured out of UML
setup_one_line failed for device 13 : Configuration failed
Using a channel type which is configured out of UML
setup_one_line failed for device 14 : Configuration failed
Using a channel type which is configured out of UML
setup_one_line failed for device 15 : Configuration failed
Console initialized on /dev/tty0
console [tty0] enabled
console [mc-1] enabled
Failed to initialize ubd device 0 :Couldn't determine size of device's file
VFS: Mounted root (hostfs filesystem) on device 0:11.
devtmpfs: mounted
This architecture does not have kernel memory protection.
Run /bin/sh as init process
/bin/sh: can't access tty; job control turned off
random: fast init done
/ #

Abubuwan da ke sama za su ba mu tsarin baƙo a kalla, ba tare da abubuwa kamar /proc ko sanya sunan mai masauki. Misali, gwada umarni masu zuwa:

- uname -av
- cat /proc/self/pid
- hostname

Don fita daga baƙo, rubuta exit ko danna control-d. Wannan zai kashe harsashi da fargabar kwaya:

/ # exit
Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000000
fish: “./linux root=/dev/root rootflag…” terminated by signal SIGABRT (Abort)

Mun sami wannan fargabar kwaya saboda Linux kernel yana tunanin tsarin farawa koyaushe yana gudana. Idan ba tare da shi ba, tsarin ba zai iya yin aiki ba kuma ya rushe. Amma tun da wannan tsari ne na mai amfani, abin da aka samu yana aika kansa zuwa ga SIGABRT, wanda ke haifar da fitarwa.

Saitin hanyar sadarwar baƙo

Kuma a nan ne abubuwa suka fara tafiya ba daidai ba. Hanyar sadarwa a cikin Yanayin Mai amfani Linux shine inda gaba ɗaya ra'ayi na iyakance "yanayin mai amfani" ya fara raguwa. Bayan haka, yawanci a matakin tsarin, cibiyar sadarwar tana iyakance mai gata hanyoyin aiwatarwa don dukkanmu dalilai masu fahimta.

Lura. per .: za ku iya karanta ƙarin game da zaɓuɓɓuka daban-daban don aiki tare da hanyar sadarwa a UML a nan.

Tafiya zuwa Slirp

Koyaya, akwai wani tsohon kuma kusan kayan aiki mara tallafi da ake kira zamewa, wanda Linux Yanayin Mai amfani zai iya hulɗa tare da hanyar sadarwa. Yana aiki sosai kamar tari na TCP/IP mai amfani kuma baya buƙatar kowane izini na tsarin aiki. Wannan kayan aiki ya kasance aka sake shi a shekarar 1995, kuma sabon sabuntawa yana kwanan wata 2006. Slirp ya tsufa sosai. A lokacin ba tare da tallafi da sabuntawa ba, masu tarawa sun yi nisa wanda yanzu wannan kayan aikin za a iya kwatanta shi azaman kode rube.

Don haka bari mu zazzage Slirp daga wuraren ajiyar Ubuntu kuma muyi ƙoƙarin gudanar da shi:

sudo apt-get install slirp
/usr/bin/slirp
Slirp v1.0.17 (BETA)

Copyright (c) 1995,1996 Danny Gasparovski and others.
All rights reserved.
This program is copyrighted, free software.
Please read the file COPYRIGHT that came with the Slirp
package for the terms and conditions of the copyright.

IP address of Slirp host: 127.0.0.1
IP address of your DNS(s): 1.1.1.1, 10.77.0.7
Your address is 10.0.2.15
(or anything else you want)

Type five zeroes (0) to exit.

[autodetect SLIP/CSLIP, MTU 1500, MRU 1500, 115200 baud]

SLiRP Ready ...
fish: “/usr/bin/slirp” terminated by signal SIGSEGV (Address boundary error)

Ya Allah. Bari mu shigar da Slirp's debugger mu ga ko za mu iya gano abin da ke faruwa a nan:

sudo apt-get install gdb slirp-dbgsym
gdb /usr/bin/slirp
GNU gdb (Ubuntu 8.1-0ubuntu3) 8.1.0.20180409-git
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/slirp...Reading symbols from /usr/lib/debug/.build-id/c6/2e75b69581a1ad85f72ac32c0d7af913d4861f.debug...done.
done.
(gdb) run
Starting program: /usr/bin/slirp
Slirp v1.0.17 (BETA)

Copyright (c) 1995,1996 Danny Gasparovski and others.
All rights reserved.
This program is copyrighted, free software.
Please read the file COPYRIGHT that came with the Slirp
package for the terms and conditions of the copyright.

IP address of Slirp host: 127.0.0.1
IP address of your DNS(s): 1.1.1.1, 10.77.0.7
Your address is 10.0.2.15
(or anything else you want)

Type five zeroes (0) to exit.

[autodetect SLIP/CSLIP, MTU 1500, MRU 1500, 115200 baud]

SLiRP Ready ...

Program received signal SIGSEGV, Segmentation fault.
                                                    ip_slowtimo () at ip_input.c:457
457     ip_input.c: No such file or directory.

Kuskuren ya mamaye mu wannan layin. Bari mu kalli takin, watakila wani abu zai taimake mu a can:

(gdb) bt full
#0  ip_slowtimo () at ip_input.c:457
        fp = 0x55784a40
#1  0x000055555556a57c in main_loop () at ./main.c:980
        so = <optimized out>
        so_next = <optimized out>
        timeout = {tv_sec = 0, tv_usec = 0}
        ret = 0
        nfds = 0
        ttyp = <optimized out>
        ttyp2 = <optimized out>
        best_time = <optimized out>
        tmp_time = <optimized out>
#2  0x000055555555b116 in main (argc=1, argv=0x7fffffffdc58) at ./main.c:95
No locals.

Anan mun ga cewa hadarin yana faruwa a lokacin babban madauki lokacin da slirp yayi ƙoƙarin bincika lokacin ƙarewa. A wannan lokacin, dole ne in daina ƙoƙarin yin kuskure. Amma bari mu ga ko Slirp ya gina daga nau'ikan ayyuka. Na sake zazzage tarihin kai tsaye daga rukunin yanar gizon Sourceforge, domin jan wani abu daga can ta hanyar layin umarni yana da zafi:

cd ~/dl
wget https://xena.greedo.xeserv.us/files/slirp-1.0.16.tar.gz
tar xf slirp-1.0.16.tar.gz
cd slirp-1.0.16/src
./configure --prefix=$HOME/prefix/slirp
make

Anan muna ganin faɗakarwa game da ayyukan ginanniyar da ba a bayyana ba, wato, game da rashin iya haɗa fayil ɗin binary da ya haifar. Ya bayyana cewa tsakanin 2006 zuwa wannan batu, gcc ya daina samar da alamomin da aka yi amfani da su a cikin ayyukan ginanniyar fayilolin da aka haɗa. Bari mu yi kokarin maye gurbin keyword inline akan sharhi mara komai kuma duba sakamakon:

vi slirp.h
:6
a
<enter>
#define inline /**/
<escape>
:wq
make

A'a. Wannan kuma baya aiki. Har yanzu ba a iya samun alamomin waɗannan ayyukan.

A wannan lokacin, na daina na fara kallon Github Heroku gina fakiti. Ra'ayina shine wasu kunshin ginin Heroku zasu ƙunshi binaries da nake buƙata. A ƙarshe, binciken ya jagorance ni a nan. Na zazzage na kwashe uml.tar.gz kuma ya sami wadannan:

total 6136
-rwxr-xr-x 1 cadey cadey   79744 Dec 10  2017 ifconfig*
-rwxr-xr-x 1 cadey cadey     373 Dec 13  2017 init*
-rwxr-xr-x 1 cadey cadey  149688 Dec 10  2017 insmod*
-rwxr-xr-x 1 cadey cadey   66600 Dec 10  2017 route*
-rwxr-xr-x 1 cadey cadey  181056 Jun 26  2015 slirp*
-rwxr-xr-x 1 cadey cadey 5786592 Dec 15  2017 uml*
-rwxr-xr-x 1 cadey cadey     211 Dec 13  2017 uml_run*

Wannan shi ne slirp binary! Yana aiki?

./slirp
Slirp v1.0.17 (BETA) FULL_BOLT

Copyright (c) 1995,1996 Danny Gasparovski and others.
All rights reserved.
This program is copyrighted, free software.
Please read the file COPYRIGHT that came with the Slirp
package for the terms and conditions of the copyright.

IP address of Slirp host: 127.0.0.1
IP address of your DNS(s): 1.1.1.1, 10.77.0.7
Your address is 10.0.2.15
(or anything else you want)

Type five zeroes (0) to exit.

[autodetect SLIP/CSLIP, MTU 1500, MRU 1500]

SLiRP Ready ...

Ba ya rushe - don haka ya kamata ya yi aiki! Bari mu dasa wannan binary a ciki ~/bin/slirp:

cp slirp ~/bin/slirp

Idan mahaliccin kunshin ya cire shi, I yayi madubi.

Tsarin hanyar sadarwa

Yanzu bari mu saita hanyar sadarwa a kan kwaya ta baƙonmu. Sabunta zaɓuɓɓukan ƙaddamarwa:

linux 
  root=/dev/root 
  rootfstype=hostfs 
  rootflags=$HOME/prefix/uml-demo 
  rw 
  mem=64M 
  eth0=slirp,,$HOME/bin/slirp 
  init=/bin/sh

Yanzu bari mu kunna hanyar sadarwa:

mount -t proc proc proc/
mount -t sysfs sys sys/

ifconfig eth0 10.0.2.14 netmask 255.255.255.240 broadcast 10.0.2.15
route add default gw 10.0.2.2

Na farko guda biyu umarni umarni /proc и /sys wajibi ne don aiki ifconfig, wanda ke saita hanyar sadarwa don sadarwa tare da Slirp. Tawaga route saita tebirin kwaya don tilasta duk zirga-zirgar da za a aika ta hanyar Slirp. Bari mu duba wannan tare da tambayar DNS:

nslookup google.com 8.8.8.8
Server:    8.8.8.8
Address 1: 8.8.8.8 dns.google

Name:      google.com
Address 1: 172.217.12.206 lga25s63-in-f14.1e100.net
Address 2: 2607:f8b0:4006:81b::200e lga25s63-in-x0e.1e100.net

Yana aiki!

Lura ta .: A bayyane yake, an rubuta ainihin sakon akan tebur tare da katin sadarwar waya, ko wani tsari wanda baya buƙatar ƙarin direbobi. A kwamfutar tafi-da-gidanka mai WiFi 8265 daga Intel, kuskure yana faruwa lokacin haɓaka hanyar sadarwa

/ # ifconfig eth0 10.0.2.14 netmask 255.255.255.240 broadcast 10.0.2.15
slirp_tramp failed - errno = 2
ifconfig: ioctl 0x8914 failed: No such file or directory
/ #

A bayyane yake, kernel ba zai iya sadarwa tare da direban katin sadarwar ba. Ƙoƙarin tattara firmware a cikin kernel, rashin alheri, bai gyara yanayin ba. A lokacin bugawa, ba a iya samun mafita a cikin wannan tsarin ba. A kan mafi sauƙin saiti (misali, a cikin Virtualbox), ƙirar tana tashi daidai.

Bari mu sarrafa ta atomatik tare da rubutun harsashi mai zuwa:

#!/bin/sh
# init.sh

mount -t proc proc proc/
mount -t sysfs sys sys/
ifconfig eth0 10.0.2.14 netmask 255.255.255.240 broadcast 10.0.2.15
route add default gw 10.0.2.2

echo "networking set up"

exec /tini /bin/sh

Kuma yi alama da shi mai aiwatarwa:

chmod +x init.sh

Sannan za mu yi canje-canje ga layin umarni na kernel:

linux 
  root=/dev/root 
  rootfstype=hostfs 
  rootflags=$HOME/prefix/uml-demo 
  rw 
  mem=64M 
  eth0=slirp,,$HOME/bin/slirp 
  init=/init.sh

Kuma bari mu maimaita:

SLiRP Ready ...
networking set up
/bin/sh: can't access tty; job control turned off

nslookup google.com 8.8.8.8
Server:    8.8.8.8
Address 1: 8.8.8.8 dns.google

Name:      google.com
Address 1: 172.217.12.206 lga25s63-in-f14.1e100.net
Address 2: 2607:f8b0:4004:800::200e iad30s09-in-x0e.1e100.net

Cibiyar sadarwa ta tabbata!

docker file

Don sauƙaƙa muku bincika duk waɗannan, na tattara Dockerfile, wanda ke sarrafa yawancin matakan da aka kwatanta kuma ya kamata ya ba ku tsarin aiki. Ina kuma da preconfigured kwaya, wanda ke da duk abin da aka bayyana a cikin post. Amma yana da mahimmanci a fahimci cewa a nan na zayyana mafi ƙarancin saiti kawai.

Ina fatan wannan sakon ya taimaka muku fahimtar yadda ake haɓaka kwaya baƙo. Ya zama wani nau'i na dodo, amma an ƙirƙiri littafin a matsayin cikakken jagora kan gini, shigarwa da daidaita Yanayin Mai amfani a cikin Linux ƙarƙashin nau'ikan tsarin aiki na wannan dangi na zamani. Matakai na gaba yakamata su haɗa da shigar da sabis da sauran software da ke cikin tsarin baƙo. Tunda hotunan kwantena na Docker kawai ƙwallo ne na jama'a, yakamata ku iya fitar da hoton ta hanyar docker export, sa'an nan kuma ƙayyade hanyar shigarwa a tushen tsarin fayil ɗin kernel na baƙo. To, sannan aiwatar da rubutun harsashi.

Godiya ta musamman ga Rkeene daga #lobsters akan Freenode. Ba tare da taimakonsa na gyara Slirp ba, da ban kai ga wannan nisa ba. Ban san yadda tsarin Slackware ɗin sa ke aiki daidai da slirp ba, amma tsarin Ubuntu da Alpine na ba su karɓi slirp ba kuma binary Rkene ya ba ni shawara. Amma ya ishe ni cewa aƙalla wani abu ya yi mini aiki.

source: www.habr.com

Add a comment