Program starting method, device, equipment and medium

Abstract

This application relates to the field of program execution technology, and more particularly to a program startup method, apparatus, device, and medium. In this application, a target file to be run is obtained. Based on the target file, the root directory of the file system of the runtime environment is replaced to obtain a replaced updated file. The updated file includes at least a startup script subfile, a thought information subfile, and a facility information subfile. All updated files are traversed, and files to be run that meet preset conditions are selected. Based on the files to be run, links are generated in the root directory to obtain links to be run. When a startup command is received from the terminal, the program runs according to the links to be run. This application achieves containerized deployment with rapid and isolated program startup by replacing the root directory to construct a virtual environment, structurally encapsulating application components, and dynamically generating runtime links. This allows for analysis of the runtime environment of the file to be run, thereby efficiently controlling the program startup mechanism.

Description

Technical Field

[0001] This application relates to the field of program execution technology, and in particular to a program startup method, apparatus, device and medium. Background Technology

[0002] With the increasing complexity of software applications and the widespread adoption of cloud-native technologies, achieving rapid, reliable, and isolated deployment and operation of applications has become a core challenge in software development and operations. Traditional application startup and deployment methods are gradually revealing their shortcomings when faced with complex dependency environments, multiple version coexistence, and security isolation requirements.

[0003] Currently, most programs are launched via the system package manager or by direct compilation and installation, deploying the application's binaries, libraries, and configuration files to the host machine's global directory. Dependencies are resolved and satisfied system-wide by the package manager. Since different applications may require different versions of the same dependency library, conflicts can easily arise, causing applications to fail to run or the system to become unstable.

[0004] Therefore, how to analyze the runtime environment of executable files in order to efficiently control the program startup mechanism has become an urgent problem to be solved. Summary of the Invention

[0005] In view of this, embodiments of this application provide a program startup method, apparatus, device, and medium to solve the problem of how to analyze the runtime environment of the executable file, thereby efficiently controlling the program startup mechanism.

[0006] In a first aspect, embodiments of this application provide a program initiation method, including:

[0007] Obtain the target file to be run, and replace the root directory of the file system of the running environment according to the target file to obtain the updated file after replacement. The updated file includes at least the startup script sub-file, the thinking information sub-file, and the institute information sub-file.

[0008] Traverse all the updated files, filter out the files to be run that meet the preset conditions, and generate links in the root directory based on the files to be run to obtain the links to be run.

[0009] Upon receiving the startup command from the terminal, the program is executed according to the link to be run.

[0010] Secondly, according to an embodiment of this application, a program initiation device includes:

[0011] The file replacement module is used to obtain the target file to be run, and replace the root directory of the file system of the running environment according to the target file to obtain the updated file after replacement. The updated file includes at least a startup script sub-file, a thinking information sub-file, and a plant information sub-file.

[0012] The link generation module is used to traverse all the updated files, filter out the files to be run that meet the preset conditions, and generate links in the root directory based on the files to be run to obtain the links to be run.

[0013] The execution module is used to run the program according to the link to be run when a start command is received from the terminal.

[0014] Thirdly, embodiments of this application provide a computer device, the computer device including a processor, a memory, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the program startup method as described in the first aspect.

[0015] Fourthly, embodiments of this application provide a computer-readable storage medium storing a computer program that, when executed by a processor, implements the program startup method as described in the first aspect.

[0016] The beneficial effects of the embodiments in this application compared with the prior art are:

[0017] This application obtains the target file to be run, replaces the root directory of the file system of the runtime environment based on the target file, and obtains a replaced updated file. The updated file includes at least a startup script subfile, a thought information subfile, and a plant information subfile. All the updated files are traversed, and files that meet preset conditions are selected to be run. Based on the files to be run, links are generated in the root directory to obtain a link to be run. When a startup command is received from the terminal, the program runs based on the link to be run. This application achieves containerized deployment with fast and isolated program startup by replacing the root directory to build a virtual environment, structurally encapsulating application components, and dynamically generating runtime links. This allows for analysis of the runtime environment of the files to be run, thereby efficiently controlling the program startup mechanism. Attached Figure Description

[0018] To more clearly illustrate the technical solutions in the embodiments of this application, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0019] Figure 1 This is a schematic diagram of an application environment for a program startup method provided in Embodiment 1 of this application;

[0020] Figure 2 This is a flowchart illustrating a program startup method provided in Embodiment 2 of this application;

[0021] Figure 3 This is a flowchart illustrating a program startup method provided in Embodiment 3 of this application;

[0022] Figure 4 This is a flowchart illustrating a program startup method provided in Embodiment 4 of this application;

[0023] Figure 5 This is a flowchart illustrating a program startup method provided in Embodiment 5 of this application;

[0024] Figure 6 This is a schematic diagram of the structure of a program startup device provided in Embodiment Six of this application;

[0025] Figure 7 This is a schematic diagram of the structure of a computer device provided in Embodiment 7 of this application. Detailed Implementation

[0026] In the following description, specific details such as particular system architectures and techniques are set forth for illustrative purposes and not for limitation, in order to provide a thorough understanding of the embodiments of this application. However, those skilled in the art will understand that this application may also be implemented in other embodiments without these specific details. In other instances, detailed descriptions of well-known systems, apparatuses, circuits, and methods have been omitted so as not to obscure the description of this application with unnecessary detail.

[0027] It should be understood that, when used in this application specification and the appended claims, the term "comprising" indicates the presence of the described features, integrals, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or a collection thereof.

[0028] It should also be understood that the term “and / or” as used in this application specification and the appended claims means any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

[0029] As used in this application specification and the appended claims, the term "if" may be interpreted, depending on the context, as "when," "once," "in response to determination," or "in response to detection." Similarly, the phrase "if determined" or "if detected [the described condition or event]" may be interpreted, depending on the context, as meaning "once determined," "in response to determination," "once detected [the described condition or event]," or "in response to detection [the described condition or event]."

[0030] Furthermore, in the description of this application and the appended claims, the terms "first," "second," "third," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0031] References to "one embodiment" or "some embodiments" as described in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0032] It should be understood that the sequence number of each step in the following embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0033] To illustrate the technical solution of this application, specific embodiments are described below.

[0034] The program startup method provided in Embodiment 1 of this application can be applied to, for example, Figure 1 In this application environment, the client and server connect and communicate. Users can provide the conditions, requirements and operation instructions for program startup by operating the client, and the server is used to control the program startup method according to the control instructions sent by the client.

[0035] The client side includes, but is not limited to, PDAs, desktop computers, laptops, ultra-mobile personal computers (UMPCs), netbooks, cloud terminal devices, and personal digital assistants (PDAs). The server side can be a standalone server or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (CDNs), and big data and artificial intelligence platforms.

[0036] See Figure 2 This is a flowchart illustrating a program startup method provided in Embodiment 2 of this application. The above-described program startup method can be applied to... Figure 1 The server-side component.

[0037] like Figure 2 As shown, the program startup method may include the following steps:

[0038] Step S201: Obtain the target file to be run. Based on the target file, replace the root directory of the file system of the running environment to obtain the updated file after replacement. The updated file includes at least a startup script sub-file, a thought information sub-file, and a plant information sub-file.

[0039] Optionally, replacing the root directory of the file system of the runtime environment with the target file to obtain the updated file may include the following steps:

[0040] Based on the target file, determine the file location corresponding to the target file;

[0041] Based on the file location, remove the file information from the file system to obtain the location to be filled;

[0042] The target file is filled into the position to be filled to obtain the replaced updated file.

[0043] Obtaining the target file to be run refers to obtaining all the files required for the program to run. The target file can be a file package or an image layer, such as an image layer in Docker.

[0044] Determining the file location corresponding to the target file involves the system parsing the metadata (such as the manifest or directory tree) of the target file package to understand the expected path of each file within the package. Removing file information from the file system does not mean physically deleting the host file. Instead, it means marking this expected location as blank or writable in the memory data structure prepared for the new file system (such as the underlying directory of a union file system). The resulting location to be filled is a clean directory path prepared in the virtual file system, awaiting the target file to be filled.

[0045] The system places or maps the files in the target file package to the virtual directory structure prepared in the previous step, according to the expected paths determined in the first step. This ultimately forms a new, complete file system view. After this process, the root directory seen by the program about to run is this newly constructed environment containing all the necessary files. This environment includes at least the startup script subfile (i.e., the program's entry point), the program's configuration, parameters, and status subfiles, and the library files, runtime environment, and underlying system components that the program depends on.

[0046] Step S202: Traverse all the updated files, filter out the files to be run that meet the preset conditions, and generate links in the root directory according to the files to be run to obtain the links to be run.

[0047] Optionally, the step of traversing all the updated files and filtering out the files to be run that meet the preset conditions may include the following steps:

[0048] Filter all the aforementioned startup script sub-files;

[0049] If the data type in the startup script sub-file is a preset data type to be displayed, then the target file corresponding to the startup script sub-file is determined to be the file to be run.

[0050] The process involves traversing all the updated files generated in step S201. Filtering involves identifying a specific subset of these files, termed "files to be run," based on a set of rules (preset conditions). Links to these files are created in the root directory based on their locations. This allows the program to access the actual files stored deep within the directory simply by accessing the links in the root directory upon startup. This is similar to creating shortcuts on a computer desktop; the program doesn't need to know which complex, deeply nested folder the software is installed in, but simply clicks the desktop shortcut. All the aforementioned startup script sub-files are filtered; the system focuses solely on script files, regardless of images, configuration files, or other data, as only script files typically possess the capability to be executed. The system opens these script files and checks their data type tags. Data types can be understood as file metadata or parameters defined within the script. A comparison rule (whether it matches the preset data type to be displayed) is applied. Once a script is selected, the system ultimately determines the target file corresponding to that script (either the script itself or the main program the script points to) as the file to be run.

[0051] Step S203: Upon receiving the start command from the terminal, the program is executed according to the link to be run.

[0052] Receiving the startup command signifies that the system is in a standby state, listening for input signals from the terminal. This command acts as a trigger, marking the official start of the program's lifecycle. The terminal can refer to the user interface (CLI / GUI input), remote control interface, or system call entry point. The system does not directly search for the original executable files scattered throughout the file system; instead, it calls the link to be run generated in step S202. Path mapping means that the link to be run logically points to a specific location in the root directory reconstructed in step S201. The system parses the link to obtain the target file path or memory address it points to. Based on the path parsed from the link, the system loads the corresponding "file to be run" (i.e., a startup script or executable program that meets preset conditions). The system transfers control to the loaded program, executing its internally defined logic code, thereby completing the program's startup and initialization process and putting it into the running state.

[0053] This application obtains the target file to be run, replaces the root directory of the file system of the runtime environment based on the target file, and obtains a replaced updated file. The updated file includes at least a startup script subfile, a thought information subfile, and a plant information subfile. All the updated files are traversed, and files that meet preset conditions are selected to be run. Based on the files to be run, links are generated in the root directory to obtain a link to be run. When a startup command is received from the terminal, the program runs based on the link to be run. This application achieves containerized deployment with fast and isolated program startup by replacing the root directory to build a virtual environment, structurally encapsulating application components, and dynamically generating runtime links. This allows for analysis of the runtime environment of the files to be run, thereby efficiently controlling the program startup mechanism.

[0054] See Figure 3 This is a flowchart illustrating a program startup method provided in Embodiment 3 of this application. Figure 3 As shown, step S202, which involves generating a link in the root directory based on the file to be run, to obtain the link to be run, may include the following steps:

[0055] Step S301: Generate a file access path based on the file to be run;

[0056] Step S302: Based on the file access path, generate a link for the root directory to obtain the link to be run.

[0057] The system extracts the file access path from the metadata or storage attributes of the file to be run. The file access path refers to an absolute path or a relative path relative to the root directory of the file system.

[0058] The access path must conform to the operating system's file system specification (such as the POSIX standard or Windows path format) to ensure that the path string can be correctly parsed and addressed by the operating system. Only after the exact storage address of the target file is determined can an index file pointing to that address be created subsequently.

[0059] In step S201, the system reconstructs a new link entity under the "root directory," using the file access path obtained in step S301 as the target address. The link file itself is located in the root directory (entry level), while the data entity it points to is located in the deeper file system structure. The resulting link object is the link to be executed. This link to be executed serves as the unified entry point for program startup, encapsulating the complex storage details of the underlying files.

[0060] In this embodiment, the complex target file in the deep directory can be indirectly loaded by simply accessing a simple link in the root directory through the subsequent startup instruction, thereby achieving decoupling of the runtime environment and standardization of the access path.

[0061] See Figure 4 This is a flowchart illustrating a program startup method provided in Embodiment 4 of this application. Figure 4 As shown, after completing the program execution based on the link to be executed in step S203, the following steps may also be included:

[0062] Step S401: Obtain the running interface of the program, and set the position of the auxiliary screen according to the running interface;

[0063] Step S402: Set virtual keys according to the position of the auxiliary screen, and set corresponding information display content according to the virtual keys.

[0064] The process of acquiring the runtime interface refers to the process by which the system extracts renderable interface objects or window handles from the graphical user interface (GUI) framework after the program starts. This runtime interface serves as the visual output carrier of the program logic. The system detects the existence of an extended display (a second screen, virtual screen, or a designated display area, i.e., an "auxiliary screen"). Based on preset rules (such as maximizing, left-aligning, right-aligning, or specific coordinates), the acquired program runtime window is positioned and rendered onto the designated area of ​​the "auxiliary screen." This step creates dynamic interactive elements within the interface context of the auxiliary screen and functionalizes them. In specific areas of the program interface deployed to the auxiliary screen (such as edges, corners, or fixed layout positions), the system dynamically generates virtual interactive controls. These "virtual keys" are software-level buttons, touch areas, or hot zones, not physical buttons.

[0065] Setting the corresponding information display content for each created virtual key involves binding its interaction logic. Specifically, this means defining what content the system should display when a user clicks or triggers the virtual key. For example, displaying the program's running status, log information, popping up auxiliary control panels, menus, or toolsets, or switching to display specific data views or dashboards.

[0066] In this embodiment of the application, post-processing operations such as automated interface layout and dynamic interactive interface expansion are performed on the multi-screen display environment after the program runs, aiming to improve user experience and operational efficiency.

[0067] See Figure 5 This is a flowchart illustrating a program startup method provided in Embodiment 5 of this application. Figure 5 As shown, after completing the program execution based on the link to be executed in step S203, the following steps may also be included:

[0068] Step S501: Obtain the running device for the program, and determine the storage space based on the running device.

[0069] Step S502: Use a preset external expansion to expand the storage space to obtain an expanded space.

[0070] Optionally, the extended space is divided according to a preset format to obtain a partitioned space;

[0071] Based on the partitioned space, the target files are stored to obtain a file repository.

[0072] Specifically, obtaining the running device refers to the system calling the device interface to identify the physical or virtual device on which the current program instance is running, as well as obtaining the device's unique identifier, hardware configuration information, or platform type.

[0073] Determining storage space refers to the system locating the basic storage area on the device allocated to this program or related purpose based on identified device information. Storage space is a root directory, partition path, or mount point that serves as the base address for subsequent storage operations.

[0074] Using preset external expansion refers to the system calling external storage resources to expand according to pre-configured policies, including but not limited to mounting new physical disks or storage volumes, allocating additional cloud storage blocks or object storage space, and expanding the capacity of virtual disks (such as VMDK, VHD).

[0075] Extending the storage space refers to the system logically or physically integrating new externally mounted or allocated storage resources with the "storage space" determined in step S501. After integration, the effective storage address space available to the program increases, forming a larger, unified "extended space". According to a predefined file system layout or partitioning scheme (such as a specific directory structure, storage pool partitioning, or LVM logical volume layout), the "extended space" is further subdivided into multiple logically independent sub-regions, called "partitioned spaces". Storing target files refers to storing data files that need to be persistently saved (which may be data generated during program execution, configuration files, or files involved in steps S201-S202) into specific "partitioned spaces" according to certain rules (such as by type, by time, or by functional module).

[0076] The resulting file repository refers to a structured, scalable, dedicated file storage area that, after the above organization, is used to systematically manage all program-related files.

[0077] This application embodiment aims to achieve elastic expansion of storage capacity and orderly organization of storage content through a dynamic storage resource allocation and structured data management mechanism during program execution, so as to meet the massive or structured data storage needs that may be generated during program execution.

[0078] Corresponding to the program startup method in the above embodiments, Figure 6 This paper shows a structural block diagram of a program startup device provided in Embodiment Six of this application. The program startup device can be applied to... Figure 1 For ease of explanation, only the parts of the server-side diagram relevant to the embodiments of this application are shown.

[0079] See Figure 6 The program initiation device includes:

[0080] The file replacement module 61 is used to obtain the target file to be run, and replace the root directory of the file system of the running environment according to the target file to obtain the updated file after replacement. The updated file includes at least the startup script sub-file, the thinking information sub-file, and the institute information sub-file.

[0081] The link generation module 62 is used to traverse all the updated files, filter the files to be run that meet the preset conditions, and generate links in the root directory according to the files to be run to obtain the links to be run.

[0082] The running module 63 is used to run the program according to the link to be run when a start command is received from the terminal.

[0083] Optionally, the file replacement module 61 includes:

[0084] The location determination unit is used to determine the file location corresponding to the target file based on the target file;

[0085] The fill-in unit is used to remove file information from the file system based on the file position to obtain the fill-in position;

[0086] A fill unit is used to fill the target file into the position to be filled, so as to obtain the replaced updated file.

[0087] Optionally, the link generation module 62 includes:

[0088] The filtering unit is used to filter all the startup script sub-files. If the data type in the startup script sub-file is a preset data type to be displayed, then the target file corresponding to the startup script sub-file is determined to be the file to be run.

[0089] Optionally, the link generation module 62 includes:

[0090] The path generation unit is used to generate a file access path based on the file to be run;

[0091] The link to be run determination unit is used to generate links in the root directory based on the file access path to obtain the link to be run.

[0092] Optionally, the program initiation device includes:

[0093] The auxiliary screen setting module is used to obtain the running interface of the program and set the position of the auxiliary screen according to the running interface.

[0094] The display confirmation module is used to set virtual keys according to the position of the auxiliary screen, and to set the corresponding information display content according to the virtual keys.

[0095] Optionally, the program initiation device includes:

[0096] A storage space determination module is used to obtain the running device of the program and determine the storage space based on the running device;

[0097] The space expansion module is used to expand the storage space using a preset external expansion method to obtain expanded space.

[0098] Optionally, the program initiation device includes:

[0099] The space partitioning module is used to partition the extended space according to a preset format to obtain the partitioned space;

[0100] The storage module is used to store the target files according to the partitioned space to obtain a file storage repository.

[0101] It should be noted that the information interaction and execution process between the above modules, units, and sub-units are based on the same concept as the method embodiments of this application. For details on their specific functions and technical effects, please refer to the method embodiments section, and they will not be repeated here.

[0102] Figure 7 This is a schematic diagram of the structure of a computer device provided in Embodiment Seven of this application. Figure 7 As shown, the computer device of this embodiment includes: at least one processor ( Figure 7 Only one is shown in the diagram), a memory, and a computer program stored in the memory and executable on at least one processor. When the processor executes the computer program, it implements the steps of any of the above-described program startup methods or program startup method embodiments.

[0103] This computer device may include, but is not limited to, a processor and memory. Those skilled in the art will understand that...Figure 7 The examples of computer devices are merely examples and do not constitute a limitation on computer devices. Computer devices may include more or fewer components than shown in the illustration, or combinations of certain components, or different components, such as network interfaces, displays, and input devices.

[0104] The processor referred to can be a CPU, but it can also be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor can be a microprocessor or any conventional processor.

[0105] Memory includes readable storage media, internal memory, etc., wherein internal memory can be the RAM of a computer device, providing an environment for the operation of the operating system and computer-readable instructions stored in the readable storage media. The readable storage media can be the hard drive of a computer device, or in other embodiments, it can be an external storage device of the computer device, such as a plug-in hard drive, Smart Media Card (SMC), Secure Digital (SD) card, or Flash Card. Furthermore, memory can include both internal storage units and external storage devices of the computer device. Memory is used to store the operating system, applications, bootloader, data, and other programs, such as program code for computer programs. Memory can also be used to temporarily store data that has been output or will be output.

[0106] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is used as an example. In practical applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiments can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit. Furthermore, the specific names of the functional units and modules are only for easy differentiation and are not intended to limit the scope of protection of this application. The specific working process of the units and modules in the above device can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here. If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments of this application can be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the above method embodiments. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. A computer-readable medium can include at least: any entity or device capable of carrying computer program code, a recording medium, a computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signals, telecommunication signals, and software distribution media. Examples include USB flash drives, portable hard drives, magnetic disks, or optical disks. In some jurisdictions, according to legislation and patent practice, computer-readable media cannot be electrical carrier signals or telecommunication signals.

[0107] The implementation of all or part of the processes in the methods of the above embodiments can also be accomplished by a computer program product. When the computer program product is run on a computer device, it enables the computer device to execute the steps in the above method embodiments.

[0108] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0109] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0110] In the embodiments provided in this application, it should be understood that the disclosed apparatus / computer devices and methods can be implemented in other ways. For example, the apparatus / computer device embodiments described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0111] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0112] The above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be included within the protection scope of this application.

Claims

1. A program startup method, characterized in that, include: Obtain the target file to be run, and replace the root directory of the file system of the running environment according to the target file to obtain the updated file after replacement. The updated file includes at least the startup script sub-file, the thinking information sub-file, and the institute information sub-file. Traverse all the updated files, filter out the files to be run that meet the preset conditions, and generate links in the root directory based on the files to be run to obtain the links to be run. Upon receiving the startup command from the terminal, the program is executed according to the link to be run.

2. The program startup method according to claim 1, characterized in that, The step of replacing the root directory of the file system of the runtime environment based on the target file to obtain the updated file includes: Based on the target file, determine the file location corresponding to the target file; Based on the file location, remove the file information from the file system to obtain the location to be filled; The target file is filled into the position to be filled to obtain the replaced updated file.

3. The program startup method according to claim 1, characterized in that, The step of traversing all the updated files and filtering for files to be run that meet preset conditions includes: All the startup script sub-files are filtered. If the data type in the startup script sub-file is a preset data type to be displayed, then the target file corresponding to the startup script sub-file is determined to be the file to be run.

4. The program startup method according to claim 1, characterized in that, The step of generating a link in the root directory based on the file to be run, to obtain the link to be run, includes: Generate a file access path based on the file to be run; Based on the file access path, a link is generated for the root directory to obtain the link to be run.

5. The program startup method according to claim 1, characterized in that, After the program is executed based on the link to be run, the process further includes: Obtain the running interface of the program, and set the position of the auxiliary screen according to the running interface; Based on the location of the auxiliary screen, set virtual keys, and based on the virtual keys, set the corresponding information display content.

6. The program startup method according to claim 1, characterized in that, After the program is executed based on the link to be run, the process further includes: Obtain the device on which the program runs, and determine the storage space based on the device on which the program runs; The storage space is expanded using a preset external expansion method to obtain an expanded space.

7. The program startup method according to claim 6, characterized in that, The process of expanding the storage space using a preset external expansion method, after obtaining the expanded space, further includes: The extended space is divided according to a preset format to obtain a partitioned space; Based on the partitioned space, the target files are stored to obtain a file repository.

8. A program initiation device, characterized in that, include: The file replacement module is used to obtain the target file to be run, and replace the root directory of the file system of the running environment according to the target file to obtain the updated file after replacement. The updated file includes at least a startup script sub-file, a thinking information sub-file, and a plant information sub-file. The link generation module is used to traverse all the updated files, filter out the files to be run that meet the preset conditions, and generate links in the root directory based on the files to be run to obtain the links to be run. The execution module is used to run the program according to the link to be run when a start command is received from the terminal.

9. A computer device, characterized in that, The computer device includes a processor, a memory, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the program startup method as described in any one of claims 1 to 7.

10. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by the processor, it implements the program startup method as described in any one of claims 1 to 7.

Images