mirror of
https://github.com/LCTT/TranslateProject.git
synced 2025-01-10 22:21:11 +08:00
20140716-2 选题
This commit is contained in:
DeadFire
parent
c38b925454
commit
d9f337a594
@ -0,0 +1,197 @@
|
||||
7 ‘dmesg’ Commands for Troubleshooting and Collecting Information of Linux Systems
|
||||
================================================================================
|
||||
The ‘dmesg‘ command displays the messages from the kernel ring buffer. A system passes multiple runlevel from where we can get lot of information like system architecture, cpu, attached device, RAM etc. When computer boots up, a kernel (core of an operating system) is loaded into memory. During that period number of messages are being displayed where we can see hardware devices detected by kernel.
|
||||
|
||||
|
||||
dmesg Command Examples
|
||||
|
||||
The messages are very important in terms of diagnosing purpose in case of device failure. When we connect or disconnect hardware device on the system, with the help of dmesg command we come to know detected or disconnected information on the fly. The dmesg command is available on most **Linux and Unix** based Operating System.
|
||||
|
||||
Let’s throw some light on most famous tool called ‘dmesg’ command with their practical examples as discussed below. The exact syntax of dmesg as follows.
|
||||
|
||||
# dmseg [options...]
|
||||
|
||||
### 1. List all loaded Drivers in Kernel ###
|
||||
|
||||
We can use text-manipulation tools i.e. ‘**more**‘, ‘**tail**‘, ‘**less**‘ or ‘**grep**‘ with dmesg command. As output of dmesg log won’t fit on a single page, using dmesg with pipe more or less command will display logs in a single page.
|
||||
|
||||
[root@tecmint.com ~]# dmesg | more
|
||||
[root@tecmint.com ~]# dmesg | less
|
||||
|
||||
#### Sample Output ####
|
||||
|
||||
[ 0.000000] Initializing cgroup subsys cpuset
|
||||
[ 0.000000] Initializing cgroup subsys cpu
|
||||
[ 0.000000] Initializing cgroup subsys cpuacct
|
||||
[ 0.000000] Linux version 3.11.0-13-generic (buildd@aatxe) (gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu8) ) #20-Ubuntu SMP Wed Oct 23 17:26:33 UTC 2013
|
||||
(Ubuntu 3.11.0-13.20-generic 3.11.6)
|
||||
[ 0.000000] KERNEL supported cpus:
|
||||
[ 0.000000] Intel GenuineIntel
|
||||
[ 0.000000] AMD AuthenticAMD
|
||||
[ 0.000000] NSC Geode by NSC
|
||||
[ 0.000000] Cyrix CyrixInstead
|
||||
[ 0.000000] Centaur CentaurHauls
|
||||
[ 0.000000] Transmeta GenuineTMx86
|
||||
[ 0.000000] Transmeta TransmetaCPU
|
||||
[ 0.000000] UMC UMC UMC UMC
|
||||
[ 0.000000] e820: BIOS-provided physical RAM map:
|
||||
[ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
|
||||
[ 0.000000] BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved
|
||||
[ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000007dc08bff] usable
|
||||
[ 0.000000] BIOS-e820: [mem 0x000000007dc08c00-0x000000007dc5cbff] ACPI NVS
|
||||
[ 0.000000] BIOS-e820: [mem 0x000000007dc5cc00-0x000000007dc5ebff] ACPI data
|
||||
[ 0.000000] BIOS-e820: [mem 0x000000007dc5ec00-0x000000007fffffff] reserved
|
||||
[ 0.000000] BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
|
||||
[ 0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fed003ff] reserved
|
||||
[ 0.000000] BIOS-e820: [mem 0x00000000fed20000-0x00000000fed9ffff] reserved
|
||||
[ 0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000feefffff] reserved
|
||||
[ 0.000000] BIOS-e820: [mem 0x00000000ffb00000-0x00000000ffffffff] reserved
|
||||
[ 0.000000] NX (Execute Disable) protection: active
|
||||
.....
|
||||
|
||||
### 2. List all Detected Devices ###
|
||||
|
||||
To discover which hard disks has been detected by kernel, you can search for the keyword “**sda**” along with “**grep**” like shown below.
|
||||
|
||||
[root@tecmint.com ~]# dmesg | grep sda
|
||||
|
||||
[ 1.280971] sd 2:0:0:0: [sda] 488281250 512-byte logical blocks: (250 GB/232 GiB)
|
||||
[ 1.281014] sd 2:0:0:0: [sda] Write Protect is off
|
||||
[ 1.281016] sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
|
||||
[ 1.281039] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
|
||||
[ 1.359585] sda: sda1 sda2 < sda5 sda6 sda7 sda8 >
|
||||
[ 1.360052] sd 2:0:0:0: [sda] Attached SCSI disk
|
||||
[ 2.347887] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
|
||||
[ 22.928440] Adding 3905532k swap on /dev/sda6. Priority:-1 extents:1 across:3905532k FS
|
||||
[ 23.950543] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro
|
||||
[ 24.134016] EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (null)
|
||||
[ 24.330762] EXT4-fs (sda7): mounted filesystem with ordered data mode. Opts: (null)
|
||||
[ 24.561015] EXT4-fs (sda8): mounted filesystem with ordered data mode. Opts: (null)
|
||||
|
||||
**NOTE**: The ‘sda’ first SATA hard drive, ‘sdb’ is the second SATA hard drive and so on. Search with ‘hda’ or ‘hdb’ in the case of IDE hard drive.
|
||||
|
||||
### 3. Print Only First 20 Lines of Output ###
|
||||
|
||||
The ‘head’ along with dmesg will show starting lines i.e. ‘dmesg | head -20′ will print only 20 lines from the starting point.
|
||||
|
||||
[root@tecmint.com ~]# dmesg | head -20
|
||||
|
||||
[ 0.000000] Initializing cgroup subsys cpuset
|
||||
[ 0.000000] Initializing cgroup subsys cpu
|
||||
[ 0.000000] Initializing cgroup subsys cpuacct
|
||||
[ 0.000000] Linux version 3.11.0-13-generic (buildd@aatxe) (gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu8) ) #20-Ubuntu SMP Wed Oct 23 17:26:33 UTC 2013 (Ubuntu 3.11.0-13.20-generic 3.11.6)
|
||||
[ 0.000000] KERNEL supported cpus:
|
||||
[ 0.000000] Intel GenuineIntel
|
||||
[ 0.000000] AMD AuthenticAMD
|
||||
[ 0.000000] NSC Geode by NSC
|
||||
[ 0.000000] Cyrix CyrixInstead
|
||||
[ 0.000000] Centaur CentaurHauls
|
||||
[ 0.000000] Transmeta GenuineTMx86
|
||||
[ 0.000000] Transmeta TransmetaCPU
|
||||
[ 0.000000] UMC UMC UMC UMC
|
||||
[ 0.000000] e820: BIOS-provided physical RAM map:
|
||||
[ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
|
||||
[ 0.000000] BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved
|
||||
[ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000007dc08bff] usable
|
||||
[ 0.000000] BIOS-e820: [mem 0x000000007dc08c00-0x000000007dc5cbff] ACPI NVS
|
||||
[ 0.000000] BIOS-e820: [mem 0x000000007dc5cc00-0x000000007dc5ebff] ACPI data
|
||||
[ 0.000000] BIOS-e820: [mem 0x000000007dc5ec00-0x000000007fffffff] reserved
|
||||
|
||||
### 4. Print Only Last 20 Lines of Output ###
|
||||
|
||||
The ‘tail’ along with dmesg command will print only 20 last lines, this is useful in case we insert removable device.
|
||||
|
||||
[root@tecmint.com ~]# dmesg | tail -20
|
||||
|
||||
parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
|
||||
ppdev: user-space parallel port driver
|
||||
EXT4-fs (sda1): mounted filesystem with ordered data mode
|
||||
Adding 2097144k swap on /dev/sda2. Priority:-1 extents:1 across:2097144k
|
||||
readahead-disable-service: delaying service auditd
|
||||
ip_tables: (C) 2000-2006 Netfilter Core Team
|
||||
nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
|
||||
NET: Registered protocol family 10
|
||||
lo: Disabled Privacy Extensions
|
||||
e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
|
||||
Slow work thread pool: Starting up
|
||||
Slow work thread pool: Ready
|
||||
FS-Cache: Loaded
|
||||
CacheFiles: Loaded
|
||||
CacheFiles: Security denies permission to nominate security context: error -95
|
||||
eth0: no IPv6 routers present
|
||||
type=1305 audit(1398268784.593:18630): audit_enabled=0 old=1 auid=4294967295 ses=4294967295 res=1
|
||||
readahead-collector: starting delayed service auditd
|
||||
readahead-collector: sorting
|
||||
readahead-collector: finished
|
||||
|
||||
### 5. Search Detected Device or Particular String ###
|
||||
|
||||
It’s difficult to search particular string due to length of dmesg output. So, filter the lines with are having string like ‘**usb**‘ ‘**dma**‘ ‘**tty**‘ and ‘**memory**‘ etc. The ‘**-i**’ option instruct to [grep command][1] to ignore the case (upper or lower case letters).
|
||||
|
||||
[root@tecmint.com log]# dmesg | grep -i usb
|
||||
[root@tecmint.com log]# dmesg | grep -i dma
|
||||
[root@tecmint.com log]# dmesg | grep -i tty
|
||||
[root@tecmint.com log]# dmesg | grep -i memory
|
||||
|
||||
#### Sample Output ####
|
||||
|
||||
[ 0.000000] Scanning 1 areas for low memory corruption
|
||||
[ 0.000000] initial memory mapped: [mem 0x00000000-0x01ffffff]
|
||||
[ 0.000000] Base memory trampoline at [c009b000] 9b000 size 16384
|
||||
[ 0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
|
||||
[ 0.000000] init_memory_mapping: [mem 0x37800000-0x379fffff]
|
||||
[ 0.000000] init_memory_mapping: [mem 0x34000000-0x377fffff]
|
||||
[ 0.000000] init_memory_mapping: [mem 0x00100000-0x33ffffff]
|
||||
[ 0.000000] init_memory_mapping: [mem 0x37a00000-0x37bfdfff]
|
||||
[ 0.000000] Early memory node ranges
|
||||
[ 0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x000effff]
|
||||
[ 0.000000] PM: Registered nosave memory: [mem 0x000f0000-0x000fffff]
|
||||
[ 0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
|
||||
[ 0.000000] Memory: 2003288K/2059928K available (6352K kernel code, 607K rwdata, 2640K rodata, 880K init, 908K bss, 56640K reserved, 1146920K highmem)
|
||||
[ 0.000000] virtual kernel memory layout:
|
||||
[ 0.004291] Initializing cgroup subsys memory
|
||||
[ 0.004609] Freeing SMP alternatives memory: 28K (c1a3e000 - c1a45000)
|
||||
[ 0.899622] Freeing initrd memory: 23616K (f51d0000 - f68e0000)
|
||||
[ 0.899813] Scanning for low memory corruption every 60 seconds
|
||||
[ 0.946323] agpgart-intel 0000:00:00.0: detected 32768K stolen memory
|
||||
[ 1.360318] Freeing unused kernel memory: 880K (c1962000 - c1a3e000)
|
||||
[ 1.429066] [drm] Memory usable by graphics device = 2048M
|
||||
|
||||
### 6. Clear dmesg Buffer Logs ###
|
||||
|
||||
Yes, we can clear dmesg logs if required with below command. It will clear dmesg ring buffer message logs till you executed the command below. Still you can view logs stored in ‘**/var/log/dmesg**‘ files. If you connect any device will generate dmesg output.
|
||||
|
||||
[root@tecmint.com log]# dmesg -c
|
||||
|
||||
### 7. Monitoring dmesg in Real Time ###
|
||||
|
||||
Some distro allows command ‘tail -f /var/log/dmesg’ as well for real time dmesg monitoring.
|
||||
|
||||
[root@tecmint.com log]# watch "dmesg | tail -20"
|
||||
|
||||
**Conclusion**: The dmesg command is useful as dmesg records all the system changes done or occur in real time. As always you can man dmesg to get more information.
|
||||
|
||||
----------
|
||||
|
||||
|
||||
|
||||
Narad Shrestha
|
||||
|
||||
- [Twitter profile][t]
|
||||
- [Facebook profile][f]
|
||||
- [Google+ profile][g]
|
||||
|
||||
He has over 10 years of rich IT experience which includes various Linux Distros, FOSS and Networking. Narad always believes sharing IT knowledge with others and adopts new technology with ease.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.tecmint.com/dmesg-commands/
|
||||
|
||||
译者：[译者ID](https://github.com/译者ID) 校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[1]:http://www.tecmint.com/12-practical-examples-of-linux-grep-command/
|
||||
[t]:http://twitter.com/@nrdshrestha
|
||||
[f]:http://facebook.com/narad.shrestha.9
|
||||
[g]:http://plus.google.com/104542109955805873615?rel=author
|
||||
@ -0,0 +1,182 @@
|
||||
Install “Android 4.4 KitKat” to Run Favourite Games and Applications in Linux
|
||||
================================================================================
|
||||
**Android (x86)** is a project which aims to port Android system to Intel x86 processors to let users install it easily on any computer, the way they do this is by taking android source code, patching it to work on Intel x86 processors and some laptops and tablets.
|
||||
|
||||
|
||||
Install Android 4.4 KitKat in Linux
|
||||
|
||||
A few days ago, the project released “Android KitKat 4.4 RC2”, and today we will explain how to install it on VirtualBox, there is a problem that the mouse pointer doesn’t work in android in VirtualBox, but you may use this guide to install it beside other systems as a main system and the mouse should work I guess, otherwise we’ll use the keyboard.
|
||||
|
||||
### Step 1: Install VirtualBox in Linux ###
|
||||
|
||||
**1.** VirtualBox is available to install easily via official repositories in most Linux distributions, to install it on Ubuntu run.
|
||||
|
||||
$ sudo apt-get install virtualbox
|
||||
|
||||
For other Linux distributions like **RHEL, CentOS and Fedora**, use the following article to install Virtualbox.
|
||||
|
||||
- [Install VirtualBox in RHEL, CentOS and Fedora][1]
|
||||
|
||||
### Step 2: Download and Install Android 4.4 KitKat in Virtualbox ###
|
||||
|
||||
**2.** This is an easy step, just download **Android 4.4 x86 Kit Kat** file from the [androud Sourceforge.net][2] project.
|
||||
|
||||
**3.** To install **Android 4.4 kitkat** on VirtualBox, you need first to boot from the .iso image that you downloaded, to do so, open **VirtualBox**, Click on new to create a new virtual machine, and choose the settings as follow.
|
||||
|
||||
|
||||
Create New Virtual Machine
|
||||
|
||||
**4.** Then it will ask you to choose a Memory size for the machine, Android 4.4 kitkat needs 1GB of RAM to work perfectly, but I will choose 512MB since I only have 1GB of RAM on my computer.
|
||||
|
||||
|
||||
Set Memory to New Machine
|
||||
|
||||
**5.** Now select “Create a virtual hard drive now” to create a new one.
|
||||
|
||||
|
||||
Create Virtual Hard Drive
|
||||
|
||||
**6.** It will now ask you for the type of the new virtual hard drive, select **VDI**.
|
||||
|
||||
|
||||
Select Hard Drive Type
|
||||
|
||||
|
||||
Select Storage Type
|
||||
|
||||
**7.** Now choose the size of the virtual hard drive, you may choose any size you want, no less than **4GB** so the system can be installed correctly beside any future apps that you want to install.
|
||||
|
||||
|
||||
Set Size for Virtual Drive
|
||||
|
||||
**8.** Now that’s your first virtual machine is created, now to boot from the **.iso** file that you downloaded, select the virtual machine from the list on the left, click on **Settings**, and go for “**storage**”, do as follow and select the **.iso** image of **android 4.4 kitkat RC2**.
|
||||
|
||||
|
||||
Select Android KitKat ISO
|
||||
|
||||
**9.** Click on **OK**, and start the machine to boot the .iso image, choose “**Installation**” to start installing the system on the virtual machine.
|
||||
|
||||
|
||||
Select to Install Android Kit Kat
|
||||
|
||||
**10.** Please select a partition to install Android-x86.
|
||||
|
||||
|
||||
Select Partition Drive
|
||||
|
||||
**11.** Now you will be prompted **cfdisk** which is a partitioning tool that we will use to create a new hard drive, so we can install android 4.4 on it, Click on “**New**”.
|
||||
|
||||
|
||||
Create New Partition
|
||||
|
||||
**12.** Choose “**Primary**” as partition type.
|
||||
|
||||
|
||||
Choose Primary Partition
|
||||
|
||||
**13.** Next, select the size of the partition.
|
||||
|
||||
|
||||
Select Size of Partition
|
||||
|
||||
**14.** Now, we have to make the new hard drive bootable in order to be able to write changes to the disk, click on “**Bootable**” to give the bootable flag to the new partition, you won’t notice any changes in fact but the bootable flag will be given to that partition.
|
||||
|
||||
|
||||
Make Partition Bootable
|
||||
|
||||
**15.** After that, click on “**Write**” to write the changes to the hard drive.
|
||||
|
||||
|
||||
Apply Changes to Partition
|
||||
|
||||
**16.** It will ask you if you are sure, write “**yes**” and click on **Enter**.
|
||||
|
||||
|
||||
Confirm Partition Changes
|
||||
|
||||
**17.** Now that’s our new hard drive is created, now click on **Quit** and you will see something like this, select the partition that you created before in order to install android on it and hit **Enter**.
|
||||
|
||||
|
||||
Choose Partition to Install Android
|
||||
|
||||
**18.** Choose “**ext3**” as a filesystem for the hard drive and format.
|
||||
|
||||
|
||||
Select Ext3 Partition Type
|
||||
|
||||
|
||||
Format Partition
|
||||
|
||||
**19.** You will be asked now if you want to install GRUB bootloader, of course you will select **Yes**, because if you don’t, you won’t be able to boot the new system, so choose “**Yes**” and hit **Enter**.
|
||||
|
||||
|
||||
Install Boot Loader GRUB
|
||||
|
||||
**20.** Finally, you will be asked if you want to make the **/system** partition writeable, choose Yes, it will help in a lot of things later after you install the system.
|
||||
|
||||
|
||||
Make Partition Writeable
|
||||
|
||||
**21.** The installer will start it’s mission… after the installer finishes the job, choose Reboot, in my test, the “Run-Android x86” didn’t work for me, so you have to reboot.
|
||||
|
||||
|
||||
Android Kit Kat Installation
|
||||
|
||||
**22.** Now that’s we installed **Android 4.4 KitKat RC2** on our hard drive, the problem is now that VirtualBox will keep loading the **.iso** image file instead of booting from the virtual hard drive, so to fix this problem, go to **Settings**, under “**storage**” select the **.iso** file and remove it from the booting menu.
|
||||
|
||||
|
||||
Remove Android Kit Kat Image
|
||||
|
||||
**23.** Now you can start the virtual machine with the installed android system.
|
||||
|
||||
|
||||
Start Android Kit Kat System
|
||||
|
||||
|
||||
Android Splash Screen
|
||||
|
||||
**24.** Now you will start a wizard to configure some things before you start using **Android**. You will see a screen like this, Now the problem is, that the Mouse doesn’t work in **android 4.4 KitKat**, that means that we’ll be using our skills in keyboard, first choose the **language** you want using the **Up** and **Down** keys in the keyboard, and to go the next step, hit the **Right** arrow key and click **Enter**.
|
||||
|
||||
|
||||
Android Welcome Screen
|
||||
|
||||
|
||||
Select WiFi Network
|
||||
|
||||
|
||||
Create Android Google Account
|
||||
|
||||
|
||||
Sign in Google Account
|
||||
|
||||
|
||||
Set Date and Time
|
||||
|
||||
|
||||
Enter Your Details
|
||||
|
||||
|
||||
Android 4.4 Kit Kat Home Screen
|
||||
|
||||
Installing **Android x86** will be good for you if you don’t have a smartphone and you want to use the **Play Store** apps easily, have you ever tried to install android x86? What was the results? Do you think that android may become a “**real operation system**” targeting PCs in the feature?
|
||||
|
||||
----------
|
||||
|
||||
|
||||
|
||||
[Hanny Helal][3]
|
||||
|
||||
A Linux & Foss user since 2010, working on many projects in the field of Free Software.
|
||||
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.tecmint.com/install-android-kitkat-in-linux/
|
||||
|
||||
译者：[译者ID](https://github.com/译者ID) 校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[1]:http://www.tecmint.com/install-virtualbox-on-redhat-centos-fedora/
|
||||
[2]:http://sourceforge.net/projects/android-x86/
|
||||
[3]:http://www.tecmint.com/
|
||||
@ -0,0 +1,42 @@
|
||||
Linux FAQs with Answers--How to define PATH environment variable for sudo commands
|
||||
================================================================================
|
||||
> **Question**: I built and installed a program in /usr/local/bin. The program requires root privilege to run. But when I try to run the program with sudo, I get "sudo: XXXXX: command not found" error. Somehow /usr/local/bin is not included in the PATH environment variable. How can I fix this problem?
|
||||
|
||||
When you run a program with sudo, the program is executed with a new, minimum environment for security reasons. That is, not all the environment variables you define are inherited to sudo commands. In case of PATH environment variable, it is reset to a new "default" PATH variable when sudo is used. So if the new default PATH variable does not include the folder where your program is, you will get "command not found" error with sudo.
|
||||
|
||||
To customize the default PATH variable for sudo session, open /etc/sudoers file with a text editor, and look for "secure_path". The value defined in "secure_path" will be used as the default PATH variable when you execute sudo commands.
|
||||
|
||||
So add any necessary path (e.g., /usr/local/bin) to "secure_path", and it will be passed to sudo commands.
|
||||
|
||||
Defaults secure_path = /sbin:/bin:/usr/sbin:/usr/bin:/usr/local/bin
|
||||
|
||||
This change will be effective immediately.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://ask.xmodulo.com/define-path-environment-variable-sudo-commands.html
|
||||
|
||||
译者：[译者ID](https://github.com/译者ID) 校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[1]:
|
||||
[2]:
|
||||
[3]:
|
||||
[4]:
|
||||
[5]:
|
||||
[6]:
|
||||
[7]:
|
||||
[8]:
|
||||
[9]:
|
||||
[10]:
|
||||
[11]:
|
||||
[12]:
|
||||
[13]:
|
||||
[14]:
|
||||
[15]:
|
||||
[16]:
|
||||
[17]:
|
||||
[18]:
|
||||
[19]:
|
||||
[20]:
|
||||
Loading…
Reference in New Issue
Block a user