Selective loading of client operating system in a computer network

• US 6,611,915 B1
• Filed: 05/27/1999
• Issued: 08/26/2003
• Est. Priority Date: 05/27/1999
• Status: Expired due to Term

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Wagner, Jonathan Mark, Sullivan, Michael Joseph, Kubik, Joseph
• Primary Examiner(s): HUA, LY
• Application Number:
  US09/321,786
• Time in Patent Office: 1,552 Days
• Field of Search: 713/200, 713/201, 707/1, 707/10, 707/104.1, 707/203, 707/205, 707/206, 709/203, 709/219, 709/220, 709/225, 709/228, 709/217
• US Class Current: 709/211
• CPC Class Codes: G06F 9/4416 Network booting; Remote initial program loading [RIPL]
• CPC Class Codes: Y10S 707/99931 Database or file accessing
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing
• CPC Class Codes: Y10S 707/99953 Recoverability

Abstract

A client station on computer network uses an operating system such as JavaOS which is permanently stored at the server rather than on storage media at the client location. JavaOS is loaded and installed at the client upon bootup of the client. The JavaOS is loaded and installed at the client upon bootup of the client. Once the basic system is booted using local firmware, and the base file systems on the network are enabled, an application can begin running, and when it needs to use a particular class file a request will be made through the file system and will be routed over to a generic file system driver, on the client, which will then determine, using a set of configured information, where this class exists; it will utilize the particular file systems available on to that booted client, whether it be NFS, or TFTP, to determine where the server is and how to retrieve that particular class file. It will go ahead and force that operation to occur and the class file will be retrieved and cached locally on the client to be used by the application. In order to avoid loading unneeded or lesser-used parts of the JavaOS from the server to the client memory at boot time, groups of classes are broken out of the monolithic image of JavaOS, as part of the Java service loader model (JSL). JSL-provided packages allow an URL prefix to be provided as part of a package'"'"'s configuration information. When a class method/data is requested by the loader via the filesystem, if it is not already present, the URL prefix is used to lazily retrieve and cache that file in memory. This allows classes and data files to be delivered as needed, and significantly reduces the amount of data to be retrieved by TFTP by the client at boot time.

Claims

1. A method of loading and installing an operating system at a client connected to a network, comprising the steps of:

at said server, separating said operating system into parts, including a first main part and at least one other part, and assigning each of parts a different identification;

at said client, retrieving and installing said first part of said operating system by requesting said first part to be loaded from said server using a generic file system driver via said network using a first identification; and

at said client, after said first part has been retrieved and installed, then retrieving and installing said at least one other part of said operating system by sending a request to said server via said network using a second identification.

2. A method according to claim 1 wherein said identification of said first part is a URL prefix, and said URL prefix is used in a request to retrieve said first part from said server.

3. A method according to claim 2 wherein said identification of said at least one other part is a URL prefix, and said URL prefix is used by said client in said request to retrieve said at least one other part from said server.

4. A method according to claim 3 wherein said first part of said operating system is loaded from said server upon boot-up of said client.

5. A method according to claim 4 wherein said operating system is JavaOS.

6. A method according to claim 5 wherein said at least one other part of said operating system is loaded from said server to said client as needed rather than at boot-up of said client.

7. A system for loading and installing an operating system at a client connected to a network, comprising:

said operating system at said server being separated into parts, including a first main part and at least one other part, each of parts being assigned a different identification;

at said client, means for retrieving and installing said first part of said operating system by requesting said first part to be loaded from said server via said network using a first identification; and

at said client, means for then retrieving and installing said at least one other part of said operating system using a generic file system driver by sending a request to said server via said network using a second identification, after said first part has been retrieved and installed.

8. A system according to claim 7 wherein said identification of said first part is a URL prefix, and said URL prefix is used in a request to retrieve said first part from said server.

9. A system according to claim 8 wherein said identification of said at least one other part is a URL prefix, and said URL prefix is used by said client in said request to retrieve said at least one other part from said server.

10. A system according to claim 9 wherein said operating system is loadable from said server upon boot-up of said client.

11. A system according to claim 10 wherein said operating system is JavaOS.

12. A system according to claim 11 wherein said at least one other part of said operating system is loaded from said server to said client as needed rather than at boot-up of said client.