Method for integrating Linux kernel and application software packages and generating installation file list based on CML2 computer language

• US 7,367,013 B2
• Filed: 05/28/2003
• Issued: 04/29/2008
• Est. Priority Date: 12/23/2002
• Status: Expired due to Fees

• Current Assignee: Electronics and Telecommunications Research Institute
• Original Assignee: Electronics and Telecommunications Research Institute
• Inventors: Kang, Woochul, Yun, Hee-Chul, Jung, Young Joon, Kim, Sun Ja, Kim, Heung-Nam
• Primary Examiner(s): Vo; Ted T.
• Application Number:
  US10/445,824
• Publication Number:
  US 20040123286A1
• Time in Patent Office: 1,798 Days
• Field of Search: 717168-178, 717106-107
• US Class Current: 717/106
• CPC Class Codes: G06F 8/60 Software deployment

Abstract

A Linux kernel and an application software package are integrally installed at a target computer by using a CML2. Setup options of the application S/W package to be installed at the target computer are described in an option information file. The option information file of the application S/W package is converted into a CML2 rule file and the CML2 rule file of the application S/W package is then integrated with a CML2 rule file of the Linux kernel, thereby realizing integrated configuration of the Linux kernel and the application S/W package and preparing an environment where dependency rules between the Linux kernel and the application S/W package can be described. Since every option in the option information file has a file list and these file lists are stored in a file list table, an installation file list that describes files finally installed at the target computer can be easily generated.

Claims

1. A method for integrating a computer operating system kernel and application software (S/W) packages and generating an installation file list based on a configuration menu language for the operating system kernel, the method comprising:

(a) generating an option information file for each application S/W package, recording a plurality of setup options in the option information file and identifying each setup option from others;

(b) converting the option information file into a first configuration menu language rule file and storing the first configuration menu language rule file;

(c) adding a dependency rule of the setup option to the first configuration menu language rule file if there exists the setup option having the dependency rule;

(d) integrating the first configuration menu language rule file and a second configuration menu language rule file of the computer operating system kernel to obtain an integrated configuration menu language rule file and storing the integrated configuration menu language-rule file; and

(e) generating the installation file list by compiling the integrated configuration menu language rule file.

2. The method of claim 1, wherein each setup option of the application S/W package has a ‘

short help’

, a ‘

long help’

, a ‘

file list’

, a ‘

dependency rule’ and

a ‘

group attribute’

information in the step (a).

3. The method of claim 2, wherein each setup option always has the ‘

short help’ and

the ‘

long help’ and

optionally has the ‘

file list’

, the ‘

dependency rule’ and

the ‘

group attribute’

information.

4. The method of claim 1, wherein the step (c) includes the steps of:

(c1) changing a menu name ‘

main’

of a highest-level menu in the second configuration menu language rule file of the computer operating system software kernel to a unique name;

(c2) opening a template file of the integrated configuration menu language rule file;

(c3) inserting a ‘

source’

sentence and the name of the second configuration menu language rule file to the template file;

(c4) inserting the convened name of the highest-level menu ‘

main’

in the computer operating system software kernel to the template file;

(c5) inserting the ‘

source’

sentence and the name of the first configuration menu language rule file to the template file;

(c6) inserting a symbol which has been produced by converting the highest-level setup option of the application S/W package in the option information file into the first configuration menu language rule file to the template file; and

(c7) storing the template file as the integrated configuration menu language rule file.

5. The method of claim 1, wherein the step (d) includes the steps of:

(d1) opening a list of selected options and selecting an option from the list;

(d2) determining whether the selected option exists in the file list table;

(d3) recording a file list for the selected option in the installation file list if the selected option exists in the file list table; and

(d4) performing the steps (g1) to (g3) for all the selected options.

6. A method for integrating a computer operating system kernel and application software (S/W) packages and generating an installation file list based on a configuration menu language for the operating system kernel, the method comprising:

a) generating an option information file for each application S/W package, recording a plurality of setup options in the option information file and identifying each setup option from others;

(b) converting the option information file into a first configuration menu language rule file and storing the first configuration menu language rule file, wherein converting the option information file includes the sub-steps of;

(b1) inserting a ‘

name’

, a ‘

short help’

, and a ‘

long help’

of each setup option into a ‘

symbols’

section of the first configuration menu language rule file;

(b2) adding the ‘

name’

, the ‘

short help’

, and the ‘

long help’

of each setup option to a ‘

menus’

section of the first configuration menu language rule file;

(b3) adding a symbol and a menu to a ‘

menu item’

of the first configuration menu language rule file;

(b4) adding a dependency rule of the setup option to the first configuration menu language rule file if there exists the setup option having the dependency rule; and

(b5) storing a file list of each setup option in a file list table, wherein the step (b1) is skipped if the setup option has a group attribute while the steps (b2), (b3) are skipped if the setup option does not have the group attribute;

(c) integrating the first configuration menu language rule file and a second configuration menu language rule file of the computer operating system kernel to obtain an integrated configuration menu language rule file and storing the integrated configuration menu language rule file; and

(d) generating the installation file list by compiling the integrated configuration menu language rule file.

7. The method of claim 6, wherein the step (b1) includes the steps of:

(b11) converting the name of the setup option into a sole symbol name in the first configuration menu language rule file at a time of generating the first configuration menu language rule file, adding the symbol name to the ‘

symbols’

section and inserting the ‘

short help’

of the option next to the symbol name;

(b12) inserting a ‘

text’

sentence next to the ‘

short help’

; and

(b13) adding the ‘

long help’

at a next line of the symbol name.

8. The method of claim 6, wherein the step (b2) includes the steps of:

(b21) converting the name of the setup option into a sole menu name in the first configuration menu language rule file at a time of generating the first configuration menu language rule file, adding the menu name to the ‘

menus’

section and inserting the ‘

short help’

next to the menu name;

(b22) inserting a ‘

text’

sentence next to the ‘

short help’

; and

(b23) adding the ‘

long help’

to a next line of the menu name.

9. The method of claim 6, wherein the step (b3) includes the steps of:

(b31) searching for a menu item of a higher-level option in a direct line at a time of generating the first configuration menu language rule file;

(b32) determining whether the higher-level option has a group attribute; and

(b33) inserting the symbol name, a mark ‘

{’

, the menu name, and a mark ‘

}’

sequentially to the menu item if the higher-level option does not have the group attribute and inserting the menu name to the ‘

menu item’

if the higher-level option has the group attribute.

10. The method of claim 7, wherein the step (b3) includes the steps of:

(b31) searching for a menu item of a higher-level option in a direct line at a time of generating the first configuration menu language rule file;

(b32) determining whether the higher-level option has a group attribute; and

(b33) inserting the symbol name, a mark ‘

{’

, the menu name, and a mark ‘

}’

sequentially to the menu item if the higher-level option does not have the group attribute and inserting the menu name to the ‘

menu item’

if the higher-level option has the group attribute.

11. The method of claim 8, wherein the step (b3) includes the steps of:

(b31) searching for a menu item of a higher-level option in a direct line at a time of generating the first configuration menu language rule file;

(b32) determining whether the higher-level option has a group attribute; and

(b33) inserting the symbol name, a mark ‘

{’

, the menu name, and a mark ‘

}’

sequentially to the menu item if the higher-level option does not have the group attribute and inserting the menu name to the ‘

menu item’

if the higher-level option has the group attribute.

12. The method of claim 6, wherein the dependency rule of the setup option is inserted to a ‘

dependency’

section of the first configuration menu language rule file in the step (b4).

13. The method of claim 6, wherein the step (b5) includes the steps of:

(b51) determining whether the setup option has the file list; and

(b52) storing the symbol name of the setup option and the file list in the file list table if the setup option has the file list.