Operating system startup item management method, device, medium and computer program product

Abstract

The present application discloses an operating system startup item management method and device, medium and computer program product, which relates to the field of computer technology. The method includes: scanning the startup devices of a server, dividing multiple startup devices into multiple startup device groups; determining the priority and the number of boot program startup items of multiple startup device groups; and creating boot program startup items for the number of startup devices corresponding to the boot program startup items in each startup device group in order of priority from high to low. The operating system startup item management method provided by the present application creates boot program startup items for the number of startup devices corresponding to the boot program startup items in each startup device group in order of priority from high to low, flexibly sets the startup items of the server according to user needs, avoids the boot program abnormality problem caused by too many startup devices in the traditional BIOS mode, and improves the usability of the server product.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and more specifically, to an operating system startup item management method and device, medium and computer program product. Background Art

[0002] The BIOS (Basic Input Output System) of the X86 architecture includes the Legacy mode and the UEFI (Unified Extensible Firmware Interface) mode. Due to the influence of the X86 architecture design, in the Legacy mode, the system can only allocate 128 KB of address space for the boot program startup item. This fixed address space limitation is limited by the X86 architecture rather than the BIOS itself. When the server product uses the Legacy mode, the device paired with the system will generate a boot program. When a large number of such devices are installed on the server, the system address space required by the boot programs generated by these devices may be larger than 128K, which will cause the boot programs of some devices to execute abnormally, making the server unusable.

[0003] Therefore, how to avoid the problem of abnormal BIOS boot program in traditional mode is a technical problem that needs to be solved by those skilled in the art. Summary of the invention

[0004] The purpose of the present application is to provide an operating system startup item management method, device and equipment, storage medium and computer program product, which avoids the problem of abnormal BIOS boot program in traditional mode.

[0005] To achieve the above purpose, the present application provides an operating system startup item management method, including:

[0006] Scanning the boot devices of the server, and dividing the plurality of the boot devices into a plurality of boot device groups;

[0007] Determining the priorities of the plurality of boot device groups and the number of boot program startup items;

[0008] In descending order of the priorities, boot program startup items are created for the boot devices corresponding to the number of boot program startup items in each of the boot device groups.

[0009] The plurality of boot devices are divided into a plurality of boot device groups, including:

[0010] The plurality of startup devices are divided into a plurality of startup device groups according to connection modes and / or device types of the plurality of startup devices.

[0011] The connection modes include direct connection through interfaces conforming to different protocols and / or connection through different types of storage cards, and the device types include hard disks and / or network cards.

[0012] After the plurality of boot devices are divided into a plurality of boot device groups, the method further includes:

[0013] Displaying a plurality of priority setting options of the boot device groups and a number setting option of boot program startup items in a basic input and output system setting interface;

[0014] The priorities of the plurality of startup device groups and the number of boot program startup items are acquired through an input interface, and the priorities of the plurality of startup device groups and the number of boot program startup items are stored.

[0015] The step of determining the priorities of the plurality of boot device groups and the number of boot program startup items includes:

[0016] The priorities and the number of boot program startup items of the stored multiple startup device groups are obtained.

[0017] After the plurality of boot devices are divided into a plurality of boot device groups, the method further includes:

[0018] During the startup process of the basic input and output system, determining whether the current startup mode is a unified extensible firmware interface mode;

[0019] If not, the step of displaying a plurality of priority setting options of the startup device groups and a boot program startup item quantity setting option in a basic input / output system setting interface is performed.

[0020] After determining whether the current startup mode is the unified extensible firmware interface mode, the method further includes:

[0021] If the current startup mode is the unified extensible firmware interface mode, the priority setting options of the plurality of startup device groups and the boot program startup item quantity setting options in the setting interface are hidden.

[0022] The step of determining whether the current startup mode is the unified extensible firmware interface mode includes:

[0023] The current value of the startup mode variable of the basic input and output system is obtained, and whether the current startup mode is the unified extensible firmware interface mode is determined according to the current value of the startup mode variable.

[0024] Before determining the priorities of the plurality of startup device groups and the number of boot program startup items, the method further includes:

[0025] Determining whether the server is powered on for the first time after refreshing the basic input and output system;

[0026] If yes, the number of boot devices included in the plurality of boot device groups is counted respectively.

[0027] The counting of the number of boot devices included in the plurality of boot device groups comprises:

[0028] In the process of counting the number of network card devices, the number of all network ports included in the network card device is taken as the number of the network card device.

[0029] The step of determining the priorities of the plurality of boot device groups and the number of boot program startup items includes:

[0030] If the server is started for the first time after refreshing the basic input and output system, the number of boot program startup items in the startup device group is set to the number of startup devices included in the startup device group.

[0031] The step of determining the priorities of the plurality of boot device groups and the number of boot program startup items includes:

[0032] If the server is not started for the first time after refreshing the basic input and output system, the priorities of the plurality of boot device groups and the number of boot program startup items stored therein are obtained.

[0033] To achieve the above object, the present application provides an operating system startup item management device, comprising:

[0034] A division module, used for scanning the boot devices of the server, and dividing the plurality of the boot devices into a plurality of boot device groups;

[0035] A determination module, used to determine the priorities of the plurality of startup device groups and the number of boot program startup items;

[0036] The creation module is used to create boot program startup items for the corresponding number of boot program startup items in each of the boot device groups in order of the priorities from high to low.

[0037] To achieve the above objectives, the present application provides an electronic device, including:

[0038] Memory for storing computer programs;

[0039] A processor is used to implement the steps of the above-mentioned operating system startup item management method when executing the computer program.

[0040] To achieve the above-mentioned purpose, the present application provides a non-volatile storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps of the above-mentioned operating system startup item management method are implemented.

[0041] To achieve the above objectives, the present application provides a computer program product, including a computer program, which implements the steps of the above operating system startup item management method when executed by a processor.

[0042] From the above scheme, it can be seen that an operating system startup item management method provided by the present application includes: scanning the startup devices of the server, dividing multiple startup devices into multiple startup device groups; determining the priority and the number of boot program startup items of multiple startup device groups; and creating boot program startup items for the corresponding number of boot program startup items in each startup device group in order of the priority from high to low.

[0043] The operating system startup item management method provided by the present application sets the priority of each startup device group and the number of boot program startup items, creates boot program startup items for the corresponding number of boot program startup items in each startup device group in order of priority from high to low, flexibly sets the server startup items according to user needs, avoids the boot program abnormality caused by too many startup devices in the traditional BIOS mode, and improves the usability of the server product. The present application also discloses an operating system startup item management device, an electronic device, a non-volatile storage medium and a computer program product, which can also achieve the above technical effects.

[0044] It should be understood that the foregoing general description and the following detailed description are exemplary only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following is a brief introduction to the drawings required for use in the embodiments or the prior art descriptions. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work. The drawings are used to provide a further understanding of the present disclosure and constitute a part of the specification. Together with the following specific implementation methods, they are used to explain the present disclosure, but do not constitute a limitation to the present disclosure. In the drawings:

[0046] Figure 1 The present invention is a flowchart of a method for managing operating system startup items according to an exemplary embodiment;

[0047] Figure 2 It is a flowchart of another operating system startup item management method according to an exemplary embodiment;

[0048] Figure 3A flowchart of an operating system startup item management method in an application embodiment provided by the present application;

[0049] Figure 4 is a structural diagram of an operating system startup item management device according to an exemplary embodiment;

[0050] Figure 5 The figure is a structural diagram of an electronic device according to an exemplary embodiment. DETAILED DESCRIPTION

[0051] The technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in the field without making creative work are within the scope of protection of the present application. In addition, in the embodiments of the present application, "first", "second", etc. are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0052] The embodiment of the present application discloses a method for managing operating system startup items, which avoids the problem of abnormal BIOS boot program in traditional mode.

[0053] See also Figure 1 , according to an exemplary embodiment, a flowchart of a method for managing operating system startup items is shown, such as Figure 1 As shown, including:

[0054] S101: Scanning boot devices of a server, and dividing a plurality of the boot devices into a plurality of boot device groups;

[0055] In a specific implementation, the boot devices of the server are scanned, that is, the devices that can generate boot program startup items, and then multiple boot devices are divided into multiple boot device groups, and the same boot device group contains the same type of boot devices.

[0056] As a feasible implementation manner, dividing the plurality of startup devices into a plurality of startup device groups includes: dividing the plurality of startup devices into a plurality of startup device groups according to connection modes and / or device types of the plurality of startup devices.

[0057] In a specific implementation, the boot device group can be divided according to the connection method between the boot device and the server. The connection method can include direct connection through interfaces that comply with different protocols, such as direct connection through SATA (Serial ATA) and direct connection through NVME (Non-Volatile Memory Express). The connection method can also include connection through different types of storage cards, such as connection through RAID (Redundant Array of Independent Disks) card and connection through SAS (Serial Attached SCSI) card.

[0058] In addition, the boot device group may also be divided according to the device type of the boot device, and the device type of the boot device may include a hard disk, a network card, and the like.

[0059] Of course, you can also divide the boot device group according to the connection method between the boot device and the server and the device type. For example, you can divide multiple boot devices into directly connected SATA hard drives, directly connected NVME hard drives, hard drives connected to RAID cards, hard drives connected to SAS cards, network cards, etc.

[0060] S102: Determine the priorities of the plurality of boot device groups and the number of boot program startup items;

[0061] In a specific implementation, the priority of each pre-set boot device group and the number of boot program startup items are determined. The number of boot program startup items of the boot device group is used to describe how many devices in the boot device group can be used as real boot devices at most, and can be set between 0 and the number of devices included in the boot device group. The number of boot program startup items of the boot device group can include the number of directly connected SATA hard disk startup items, the number of directly connected NVME hard disk startup items, the number of hard disk startup items connected to the RAID card, the number of hard disk startup items connected to the SAS card, and the number of network card startup items.

[0062] The priority of the boot device group can include the boot priority of the directly connected SATA hard disk, the boot priority of the directly connected NVME hard disk, the boot priority of the hard disk connected to the RAID card, the boot priority of the hard disk connected to the SAS card, and the boot priority of the network card. The priority can be set according to user needs. For example, the priority order can be set from high to low to be directly connected SATA hard disk, directly connected NVME hard disk, hard disk connected to the RAID card, hard disk connected to the SAS card, and network card.

[0063] Of course, the priority of each startup device group can also be automatically set by the server. The basis for setting the priority order of each startup device group can include any one or a combination of any one of the startup speed, interface transmission speed, device performance, and compatibility. The faster the startup speed and interface transmission speed, the higher the priority of the startup device group; the better the device performance and the higher the compatibility, the higher the priority of the startup device group.

[0064] As a feasible implementation mode, after dividing the plurality of the boot devices into a plurality of boot device groups, it also includes: displaying priority setting options and boot program startup item quantity setting options for the plurality of the boot device groups in the setting interface of the basic input and output system; obtaining the priorities and boot program startup item quantities of the plurality of the boot device groups through the input interface, and storing the priorities and boot program startup item quantities of the plurality of the boot device groups; accordingly, determining the priorities and boot program startup item quantities of the plurality of the boot device groups, including: obtaining the stored priorities and boot program startup item quantities of the plurality of the boot device groups.

[0065] In a specific implementation, the user can adjust the priority order of each boot device group and the number of boot program startup items in each boot device group through the BIOS setting interface. After the user sets it through the input interface (such as keyboard, mouse, etc.), this information will be saved. When the server starts, the system will determine the startup order and the number of boot program startup items based on these stored priorities and the number of startup items.

[0066] S103: creating boot program startup items for the corresponding number of boot program startup items in each of the boot device groups in order of the priorities from high to low.

[0067] In the specific implementation, each boot device group is processed in order from high to low according to the priority order of the boot device group defined by the user in the BIOS settings. For each boot device group, the system will generate boot program startup items for the corresponding number of boot devices in the boot device group according to the number of boot program startup items set by the user. In this way, when the server starts, it will load and execute the boot programs of each device according to this order and number, ensuring that the system can start as the user expects.

[0068] The operating system startup item management method provided in the embodiment of the present application sets the priority of each startup device group and the number of boot program startup items, creates boot program startup items for the corresponding number of boot program startup items in each startup device group in order from high to low priority, flexibly sets the server startup items according to user needs, avoids boot program abnormalities caused by too many startup devices in the traditional BIOS mode, and improves the usability of server products.

[0069] The embodiment of the present application discloses a method for managing operating system startup items. Compared with the previous embodiment, this embodiment further explains and optimizes the technical solution. Specifically:

[0070] See also Figure 2 , a flowchart of another operating system startup item management method according to an exemplary embodiment is shown, such as Figure 2 As shown, including:

[0071] S201: Determine whether the server is powered on for the first time after refreshing the basic input and output system; if so, proceed to S202; if not, proceed to S204;

[0072] In this step, it is checked whether the server is started for the first time after its basic input and output system is updated. If it is the first time to start, then enter S202, if not, then directly enter S204.

[0073] S202: Scanning the boot devices of the server, and dividing the plurality of the boot devices into a plurality of boot device groups;

[0074] S203: Count the number of boot devices included in the plurality of boot device groups respectively, set the number of boot program startup items of the boot device group to the number of boot devices included in the boot device group, and proceed to S204;

[0075] In a specific implementation, if the server is powered on for the first time after refreshing the BIOS, the number of boot devices contained in each boot device group is counted, and the number of boot program startup items of each boot device group is set according to the number.

[0076] As a feasible implementation method, in the process of counting the number of network card devices, the number of all network ports included in the network card device is used as the number of the network card device. In a specific implementation, for a network card device, the number of its network ports is counted, that is, if a network card device contains several network ports, several boot devices are counted.

[0077] S204: During the startup of the basic input and output system, determine whether the current startup mode is the unified extensible firmware interface mode; if so, enter S205; if not, enter S206;

[0078] In this step, during the BIOS startup process, the current startup mode is determined, including the traditional mode and the unified extensible firmware interface mode. If the current startup mode is the traditional mode, enter S206; if the current startup mode is the unified extensible firmware interface mode, enter S205.

[0079] As a feasible implementation, determining whether the current boot mode is the unified extensible firmware interface mode includes: obtaining the current value of the boot mode variable of the basic input and output system, and determining whether the current boot mode is the unified extensible firmware interface mode according to the current value of the boot mode variable. In a specific implementation, the current boot mode can be determined according to the value of the boot mode (bootmode) variable of the BIOS.

[0080] S205: hiding the priority setting options of the plurality of startup device groups and the boot program startup item quantity setting options in the basic input and output system setting interface;

[0081] In this step, if the current boot mode is the Unified Extensible Firmware Interface mode, the boot device group priority setting option and the boot program startup item quantity setting option in the BIOS setup interface are hidden, because the UEFI mode may have its own boot management method.

[0082] S206: displaying priority setting options of the plurality of startup device groups and boot program startup item quantity setting options in the basic input and output system setting interface, acquiring priorities of the plurality of startup device groups and boot program startup item quantities through an input interface, and storing priorities of the plurality of startup device groups and boot program startup item quantities;

[0083] In this step, if the current boot mode is the traditional mode, the priority setting options of the boot device group and the boot program startup item quantity setting options are displayed in the BIOS setup interface, and the user is allowed to set them through the input interface and then save these settings.

[0084] S207: Obtain priorities and numbers of boot program startup items of the plurality of startup device groups, and create boot program startup items for the corresponding number of boot program startup items in each startup device group in descending order of the priorities.

[0085] In this step, the system creates boot items for the corresponding number of boot devices in each boot device group according to the priority and number of boot program boot items set by the user, ensuring that the devices are loaded in priority order during startup.

[0086] It can be seen that this embodiment flexibly sets the server startup items according to user needs, avoids the boot program abnormality problem caused by too many startup devices in the traditional BIOS mode, and improves the usability of the server product.

[0087] An application example provided by the present application is described below. Figure 3 As shown, the following steps are included:

[0088] S2_1: The boot device, i.e., the device that can generate the boot program startup item, is divided into a directly connected SATA hard disk, a directly connected NVME hard disk, a hard disk connected to a RAID card, a hard disk connected to a SAS card, and a network card according to the connection mode.

[0089] S2_2: Create boot program startup item number options for each type of startup device in the BIOS setup interface, specifically the number of directly connected SATA hard disk startup items, the number of directly connected NVME hard disk startup items, the number of RAID card startup items, the number of SAS card startup items, and the number of network card startup items, which are used to set the maximum number of devices of this type that can be used as startup devices. These options can be set between 0 and the number of devices of the type.

[0090] S2_3: Create a priority setting option for each type of boot device in the BIOS setup interface, specifically the boot priority of the direct-connected SATA hard disk, the boot priority of the direct-connected NVME hard disk, the boot priority of the RAID card, the boot priority of the SAS card, and the boot priority of the network card. The default value of the priority can be set according to user needs. The priority order set in this embodiment is from high to low: direct-connected SATA hard disk, direct-connected NVME hard disk, RAID card, SAS card, and network card.

[0091] S2_4: During the BIOS startup process, determine whether the current startup mode is the traditional mode or the UEFI mode.

[0092] S2_5: If the boot mode is UEFI mode, the number of boot program startup items and priority setting options for each type of boot device are hidden in the BIOS interface, and the solution is exited.

[0093] S2_6: If the boot mode is the traditional mode, the number of boot program startup items and priority setting options for each type of boot device are displayed in the BIOS interface.

[0094] S2_7: Traverse all boot devices, group them according to directly connected SATA hard disks, directly connected NVME hard disks, hard disks connected to RAID cards, hard disks connected to SAS cards, and network cards, and count the number of devices in each group. In particular, each network card is counted according to the number of network ports.

[0095] S2_8: Determine whether it is the first boot after refreshing the BIOS; if so, enter S2_9; if not, enter S2_10;

[0096] S2_9: Set the default number of startup items in each group to the number counted by the corresponding device.

[0097] S2_10: Read the value of the boot program startup item number option of each boot device group preset in BIOS.

[0098] S2_11: Read the priority of each boot device group preset in BIOS.

[0099] S2_12: creating boot program startup items for the devices in each startup device group in sequence according to the priority and the number of boot program startup items preset in the group.

[0100] For the interface design of BIOS, the boot device, i.e., the device that can generate the boot program startup item, is divided into the following types according to the connection method, including but not limited to directly connected SATA hard disk, directly connected NVME hard disk, hard disk connected by RAID card, hard disk connected by SAS card, network card, etc. In the BIOS setup interface, a boot program startup item number option is created for each type of boot device to set the maximum number of devices of this type that can be used as boot devices. These options can be set between 0 and the number of devices of the said type. The number of startup items in each group is set to the number of devices of the said type when the computer is turned on for the first time. In the BIOS setup interface, a priority setting option is created for each type of boot device to set the priority of creating boot program startup items for this type of device. The default value of the priority can be set according to user needs. The boot program startup item number option and priority setting option for each type of boot device are only displayed in the traditional BIOS setup interface and are only effective in the traditional BIOS mode. They are not effective in the UEFI BIOS mode.

[0101] An operating system startup item management device provided in an embodiment of the present application is introduced below. The operating system startup item management device described below and the operating system startup item management method described above can be referenced to each other.

[0102] See also Figure 4 , according to an exemplary embodiment, a structural diagram of an operating system startup item management device is shown, such as Figure 4 As shown, including:

[0103] A division module 401 is used to scan the boot devices of the server and divide the plurality of the boot devices into a plurality of boot device groups;

[0104] A determination module 402 is used to determine the priorities of the plurality of boot device groups and the number of boot program startup items;

[0105] The creation module 403 is used to create boot program startup items for the corresponding number of boot program startup items in each of the boot device groups in order of the priorities from high to low.

[0106] The operating system startup item management device provided in the embodiment of the present application sets the priority of each startup device group and the number of boot program startup items, creates boot program startup items for the corresponding number of boot program startup items in each startup device group in order of priority from high to low, flexibly sets the server startup items according to user needs, avoids boot program abnormalities caused by too many startup devices in the traditional BIOS mode, and improves the usability of server products.

[0107] Based on the above embodiment, as a preferred implementation, the division module 401 is specifically used to: divide the multiple startup devices into multiple startup device groups according to the connection mode and / or device type of the multiple startup devices.

[0108] Based on the above embodiments, as a preferred implementation mode, the connection mode includes direct connection through interfaces conforming to different protocols and / or connection through different types of storage cards, and the device type includes a hard disk and / or a network card.

[0109] Based on the above embodiment, as a preferred implementation, it also includes:

[0110] A display module, used for displaying the priority setting options of the plurality of boot device groups and the boot program startup item quantity setting options in the basic input and output system setting interface;

[0111] The storage module is used to obtain the priorities of the plurality of startup device groups and the number of boot program startup items through the input interface, and store the priorities of the plurality of startup device groups and the number of boot program startup items.

[0112] Based on the above embodiment, as a preferred implementation, the determining module 402 is specifically used to: obtain the priorities of the plurality of boot device groups and the number of boot program startup items stored.

[0113] Based on the above embodiment, as a preferred implementation, it also includes:

[0114] A first judgment module is used to judge whether the current startup mode is the unified extensible firmware interface mode during the startup process of the basic input and output system; if so, start the workflow of the hidden module; if not, start the workflow of the display module;

[0115] The hiding module is used to hide the priority setting options of the plurality of startup device groups and the boot program startup item quantity setting options in the setting interface.

[0116] Based on the above embodiment, as a preferred implementation mode, the first judgment module is specifically used to: obtain the current value of the startup mode variable of the basic input and output system, and judge whether the current startup mode is the unified extensible firmware interface mode according to the current value of the startup mode variable.

[0117] Based on the above embodiment, as a preferred implementation, it also includes:

[0118] The second judgment module is used to judge whether the server is turned on for the first time after refreshing the basic input and output system; if so, start the work flow of the statistical module;

[0119] The counting module is used to count the number of startup devices included in the plurality of startup device groups respectively.

[0120] Based on the above embodiment, as a preferred implementation mode, the statistical module is specifically used for: in the process of counting the number of network card devices, taking the number of all network ports included in the network card device as the number of the network card device.

[0121] Based on the above embodiment, as a preferred implementation, the determination module 402 is specifically used for: if the server is turned on for the first time after refreshing the basic input and output system, the number of boot program startup items in the startup device group is set to the number of startup devices included in the startup device group.

[0122] Based on the above embodiment, as a preferred implementation, the determination module 402 is specifically used for: if the server is not started for the first time after refreshing the basic input and output system, obtaining the priorities of the plurality of boot device groups and the number of boot program startup items stored.

[0123] Regarding the device in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.

[0124] Based on the hardware implementation of the above program module, and in order to implement the method of the embodiment of the present application, the embodiment of the present application also provides an electronic device, Figure 5 FIG. 1 is a structural diagram of an electronic device according to an exemplary embodiment. Figure 5 As shown, the electronic equipment includes:

[0125] Communication interface 1, capable of exchanging information with other devices such as network devices;

[0126] The processor 2 is connected to the communication interface 1 to implement information exchange with other devices, and is used to execute the operating system startup item management method provided by one or more technical solutions when running a computer program. The computer program is stored in the memory 3.

[0127] Of course, in actual application, the various components in the electronic device are coupled together through the bus system 4. It can be understood that the bus system 4 is used to realize the connection and communication between these components. In addition to the data bus, the bus system 4 also includes a power bus, a control bus and a status signal bus. However, for the sake of clarity, Figure 5 Various buses are labeled as bus system 4.

[0128] The memory 3 in the embodiment of the present application is used to store various types of data to support the operation of the electronic device. Examples of such data include: any computer program used to operate on the electronic device.

[0129] It can be understood that the memory 3 can be a volatile memory or a non-volatile memory, and can also include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a magnetic random access memory (FRAM), a flash memory, a magnetic surface memory, an optical disc, or a compact disc read-only memory (CD-ROM); the magnetic surface memory can be a disk memory or a tape memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), synchronous static random access memory (SSRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM, SyncLink Dynamic Random Access Memory), and direct RAMbus random access memory (DRRAM, Direct Rambus Random Access Memory).The memory 3 described in the embodiments of the present application is intended to include but is not limited to these and any other suitable types of memories.

[0130] The method disclosed in the above embodiment of the present application can be applied to the processor 2, or implemented by the processor 2. The processor 2 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the hardware integrated logic circuit in the processor 2 or the instruction in the form of software. The above processor 2 may be a general-purpose processor, a DSP, or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The processor 2 can implement or execute the methods, steps and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor or any conventional processor, etc. In combination with the steps of the method disclosed in the embodiment of the present application, it can be directly embodied as a hardware decoding processor to execute, or it can be executed by a combination of hardware and software modules in the decoding processor. The software module may be located in a storage medium, which is located in the memory 3, and the processor 2 reads the program in the memory 3 and completes the steps of the above method in combination with its hardware.

[0131] When the processor 2 executes the program, the corresponding processes in the various methods of the embodiments of the present application are implemented, which will not be repeated here for the sake of brevity.

[0132] In an exemplary embodiment, the embodiment of the present application further provides a non-volatile storage medium storing a computer program, which can be executed by the processor 2 to complete the steps of the aforementioned method.

[0133] In an exemplary embodiment, the present application also provides a computer program product, including a computer program, which is executed by the processor 2 to complete the steps of the aforementioned method.

[0134] A person of ordinary skill in the art can understand that all or part of the steps of implementing the above-mentioned method embodiment can be completed by hardware related to computer program instructions, and the aforementioned computer program can be stored in a non-volatile storage medium. When the computer program is executed, it executes the steps of the above-mentioned method embodiment. Alternatively, if the above-mentioned integrated unit of the present application is implemented in the form of a software function module and sold or used as an independent product, it can also be stored in a non-volatile storage medium. Based on this understanding, the technical solution of the embodiment of the present application can be essentially or partly embodied in the form of a software product, which is stored in a non-volatile storage medium and includes a number of instructions for an electronic device (which can be a personal computer, a server, a network device, etc.) to execute all or part of the methods described in each embodiment of the present application.

[0135] The above description is only a specific implementation manner of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application.

Claims

1. A method for managing operating system startup items, characterized in that: include: Scanning the boot devices of the server, and dividing the plurality of the boot devices into a plurality of boot device groups; If the current startup mode of the basic input and output system is the traditional mode, determining the priorities of the plurality of startup device groups and the number of boot program startup items; The priorities of the plurality of startup device groups and the number of boot program startup items are preset according to user requirements, and the setting range of the number of boot program startup items of the startup device group is 0 to the number of devices included in the startup device group; Creating boot program startup items for target startup devices in each of the startup device groups in order of priority from high to low; The number of target startup devices is the number of boot program startup items corresponding to the startup device group; The plurality of boot devices are divided into a plurality of boot device groups, including: Dividing the plurality of boot devices into a plurality of boot device groups according to connection modes and / or device types of the plurality of boot devices; the connection modes include direct connection through interfaces conforming to different protocols and / or connection through different types of memory cards; and the device types include hard disks and / or network cards; In the process of counting the number of network card devices, the number of all network ports included in the network card device is taken as the number of the network card device. If a network card device includes several network ports, several boot devices are counted.

2. The operating system startup item management method according to claim 1, characterized in that: After dividing the plurality of the boot devices into a plurality of boot device groups, the method further includes: Displaying a plurality of priority setting options of the boot device groups and a number setting option of boot program startup items in a basic input and output system setting interface; The priorities of the plurality of startup device groups and the number of boot program startup items are acquired through an input interface, and the priorities of the plurality of startup device groups and the number of boot program startup items are stored.

3. The operating system startup item management method according to claim 2, characterized in that: Determining the priorities of the plurality of boot device groups and the number of boot program startup items includes: The priorities and the number of boot program startup items of the stored multiple startup device groups are obtained.

4. The operating system startup item management method according to claim 2, characterized in that: After dividing the plurality of the boot devices into a plurality of boot device groups, the method further includes: During the startup process of the basic input and output system, determining whether the current startup mode is a unified extensible firmware interface mode; If not, the step of displaying a plurality of priority setting options of the startup device groups and a boot program startup item quantity setting option in a basic input / output system setting interface is performed.

5. The operating system startup item management method according to claim 4, characterized in that: After determining whether the current boot mode is the unified extensible firmware interface mode, the method further includes: If the current startup mode is the unified extensible firmware interface mode, the priority setting options of the plurality of startup device groups and the boot program startup item quantity setting options in the setting interface are hidden.

6. The operating system startup item management method according to claim 4, characterized in that: Determine whether the current boot mode is the Unified Extensible Firmware Interface mode, including: The current value of the startup mode variable of the basic input and output system is obtained, and whether the current startup mode is the unified extensible firmware interface mode is determined according to the current value of the startup mode variable.

7. The operating system startup item management method according to claim 2, characterized in that: Before determining the priorities of the plurality of boot device groups and the number of boot program startup items, the method further includes: Determining whether the server is powered on for the first time after refreshing the basic input and output system; If yes, the number of boot devices included in the plurality of boot device groups is counted respectively.

8. The operating system startup item management method according to claim 7, characterized in that: Counting the number of boot devices included in the plurality of boot device groups respectively includes: In the process of counting the number of network card devices, the number of all network ports included in the network card device is taken as the number of the network card device.

9. The operating system startup item management method according to claim 7, characterized in that: Determining the priorities of the plurality of boot device groups and the number of boot program startup items includes: If the server is started for the first time after refreshing the basic input and output system, the number of boot program startup items in the startup device group is set to the number of startup devices included in the startup device group.

10. The operating system startup item management method according to claim 7, characterized in that: Determining the priorities of the plurality of boot device groups and the number of boot program startup items includes: If the server is not started for the first time after refreshing the basic input and output system, the priorities of the plurality of boot device groups and the number of boot program startup items stored therein are obtained.

11. An electronic device, characterized in that: include: Memory for storing computer programs; A processor, configured to implement the steps of the operating system startup item management method as claimed in any one of claims 1 to 10 when executing the computer program.

12. A non-volatile storage medium, characterized in that: The non-volatile storage medium stores a computer program, and when the computer program is executed, the steps of the operating system startup item management method according to any one of claims 1 to 10 are implemented.

13. A computer program product, characterized in that It comprises a computer program, which, when executed, implements the steps of the operating system startup item management method according to any one of claims 1 to 10.

Images