


What type of file is a picture in Linux?
Pictures in Linux are ordinary file types. Linux has seven file types: ordinary file types, directory files, block device files, character devices, etc.; among them, the characteristic of ordinary file types is that they do not contain structural information with file system information. Files that are usually exposed to users, such as graphics Files, data files, sound files, etc. all belong to this file type.
#The operating environment of this tutorial: linux5.9.8 system, Dell G3 computer.
Pictures in Linux are ordinary file types. Documents in doc, ppt, zip, jpg, jpeg, gif, bmp, png and other formats under windows are all ordinary files under Linux.
Linux has seven file types:
1, Common file type
The most commonly used type of file, Its characteristic is that it does not contain structural information of file system information. Usually files that users come into contact with, such as graphic files, data files, document files and sound files, all belong to this type of file. This type of file can be divided into plain text files according to its internal structure ( ASCII), binary files (binary), data format files (data), and various compressed files.
Plain text file (ASCII): This is the most common file type in Unix systems. It is called a plain text file because the content can be read directly, such as Numbers, letters, etc. Setting files almost always belong to this file type. For example, use the command "cat ~/.bashrc" to see the contents of the file (cat reads the contents of the file).
Binary file: The system actually only recognizes and can execute binary files. Executable files in Linux (scripts, text batch files are not included) are in this format. For example, the command cat is a binary file.
Data format files (data): Some programs will read files in certain formats during operation. Those files in specific formats can be called data files. ). For example, when a user logs in, Linux will record the login data in the /var/log/wtmp file. This file is a data file that can be read out through the last command. But when using cat, garbled characters will be read. Because it is a file in a special format.
2. Directory file
is the directory, which can be entered using the # cd command. The first attribute is [d], for example [drwxrwxrwx]
3. Block device file
Block device file: It is an interface device that stores data for system access. In simple terms, it is harddisk. For example, the code of hard disk No. 1 is /dev/hda1 and other files. The first attribute is [b]
4. Character device
Character device file: the interface device of the serial port, such as keyboard, mouse, etc. The first attribute is [c]
5. Socket file
This type of file is usually used in network data connections. A program can be started to listen for client requests, and the client can communicate data through the socket. The first attribute is [s]. This file type is most commonly seen in the /var/run directory.
6. Pipe file
FIFO is also a special file type. The main purpose is to solve errors caused by multiple programs accessing a file at the same time. FIFO is the abbreviation of first-in-first-out. The first attribute is [p]
7, and the link file
is similar to the shortcut under Windows. The first attribute is [l], for example [lrwxrwxrwx]
Extended knowledge: three ways to view file types
1, ls-l/ls-ld Or ll [ls-l — view the file ls-ld — view the path ll ---- same as ls -l]
ll anaconda-ks.cfg //看第一个字符 -rw-------. 1 root root 2460 6月 1 23:37 anaconda-ks.cfg [root@localhost log]# ls -ld /etc drwxr-xr-x. 81 root root 4096 Jan 29 03:25 /etc
2, file command
[root@localhost data]# file a.txt a.txt: ASCII text
3, stat command
[root@localhost data]# stat a.txt //查看文件的详细属性(其中包括文件时间属性) File: `a.txt' Size: 3 Blocks: 8 IO Block: 4096 regular file Device: 803h/2051d Inode: 544365 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2018-01-28 20:56:01.965885036 +0800 Modify: 2018-01-28 20:55:27.181876154 +0800 Change: 2018-01-28 20:55:27.181876154 +0800
Related recommendations: "Linux Video Tutorial"
The above is the detailed content of What type of file is a picture in Linux?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



The key differences between CentOS and Ubuntu are: origin (CentOS originates from Red Hat, for enterprises; Ubuntu originates from Debian, for individuals), package management (CentOS uses yum, focusing on stability; Ubuntu uses apt, for high update frequency), support cycle (CentOS provides 10 years of support, Ubuntu provides 5 years of LTS support), community support (CentOS focuses on stability, Ubuntu provides a wide range of tutorials and documents), uses (CentOS is biased towards servers, Ubuntu is suitable for servers and desktops), other differences include installation simplicity (CentOS is thin)

CentOS has been discontinued, alternatives include: 1. Rocky Linux (best compatibility); 2. AlmaLinux (compatible with CentOS); 3. Ubuntu Server (configuration required); 4. Red Hat Enterprise Linux (commercial version, paid license); 5. Oracle Linux (compatible with CentOS and RHEL). When migrating, considerations are: compatibility, availability, support, cost, and community support.

CentOS installation steps: Download the ISO image and burn bootable media; boot and select the installation source; select the language and keyboard layout; configure the network; partition the hard disk; set the system clock; create the root user; select the software package; start the installation; restart and boot from the hard disk after the installation is completed.

How to use Docker Desktop? Docker Desktop is a tool for running Docker containers on local machines. The steps to use include: 1. Install Docker Desktop; 2. Start Docker Desktop; 3. Create Docker image (using Dockerfile); 4. Build Docker image (using docker build); 5. Run Docker container (using docker run).

Docker uses Linux kernel features to provide an efficient and isolated application running environment. Its working principle is as follows: 1. The mirror is used as a read-only template, which contains everything you need to run the application; 2. The Union File System (UnionFS) stacks multiple file systems, only storing the differences, saving space and speeding up; 3. The daemon manages the mirrors and containers, and the client uses them for interaction; 4. Namespaces and cgroups implement container isolation and resource limitations; 5. Multiple network modes support container interconnection. Only by understanding these core concepts can you better utilize Docker.

VS Code system requirements: Operating system: Windows 10 and above, macOS 10.12 and above, Linux distribution processor: minimum 1.6 GHz, recommended 2.0 GHz and above memory: minimum 512 MB, recommended 4 GB and above storage space: minimum 250 MB, recommended 1 GB and above other requirements: stable network connection, Xorg/Wayland (Linux)

Docker process viewing method: 1. Docker CLI command: docker ps; 2. Systemd CLI command: systemctl status docker; 3. Docker Compose CLI command: docker-compose ps; 4. Process Explorer (Windows); 5. /proc directory (Linux).

Troubleshooting steps for failed Docker image build: Check Dockerfile syntax and dependency version. Check if the build context contains the required source code and dependencies. View the build log for error details. Use the --target option to build a hierarchical phase to identify failure points. Make sure to use the latest version of Docker engine. Build the image with --t [image-name]:debug mode to debug the problem. Check disk space and make sure it is sufficient. Disable SELinux to prevent interference with the build process. Ask community platforms for help, provide Dockerfiles and build log descriptions for more specific suggestions.
