US20020103996A1 - Method and system for installing an operating system - Google Patents

Method and system for installing an operating system Download PDF

Info

Publication number
US20020103996A1
US20020103996A1 US09/773,761 US77376101A US2002103996A1 US 20020103996 A1 US20020103996 A1 US 20020103996A1 US 77376101 A US77376101 A US 77376101A US 2002103996 A1 US2002103996 A1 US 2002103996A1
Authority
US
United States
Prior art keywords
computer
operating system
partition
boot
booting
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US09/773,761
Inventor
Joshua LeVasseur
Adam Stone
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Loudcloud Inc
Original Assignee
Individual
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Individual filed Critical Individual
Priority to US09/773,761 priority Critical patent/US20020103996A1/en
Assigned to LOUDCLOUD, INC. reassignment LOUDCLOUD, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: LEVASSEUR, JOSHUA T., STONE, ADAM
Priority to PCT/US2002/002418 priority patent/WO2002061533A2/en
Priority to AU2002237955A priority patent/AU2002237955A1/en
Publication of US20020103996A1 publication Critical patent/US20020103996A1/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/60Software deployment
    • G06F8/61Installation
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/4401Bootstrapping
    • G06F9/4406Loading of operating system
    • G06F9/441Multiboot arrangements, i.e. selecting an operating system to be loaded

Definitions

  • the described technology relates generally to installing an operating system on a computer.
  • a hosting service may provide the infrastructure, both hardware and software, to support the web sites of their customer organizations.
  • the customer organizations need only provide their domain-specific applications, which can be served by the computer system infrastructure of the hosting service.
  • the use of a hosting service allows a customer organization to concentrate its efforts on its domain-specific applications, and allows the hosting service to cost effectively manage the infrastructure needed by multiple customer organizations.
  • FIG. 1 is a block diagram illustrating an example infrastructure that may be provided by a hosting service.
  • the hosting service computer center 100 may include customer systems 110 , 120 , and 130 for different customer organizations.
  • Each customer system may be implemented as a tiered architecture that includes a firewall, a web server, an application server, a database server, and a mass storage device.
  • Each tier may include multiple components (e.g., computers) for providing the functionality of that tier. Additional components can be added to a tier as demand for a customer system increases.
  • the customer system 110 may initially include only two web servers. As traffic to the web site increases, a third web server can be added to the web server tier.
  • the customer systems may include load balancing hardware between each tier to distribute the workload among the components of the next lower tier.
  • the firewalls limit Internet access to only message formats that conform to certain protocols (e.g., HTTP protocol).
  • the web servers receive HTTP request messages, invoke the services of the application servers, and then provide HTTP response messages to the users.
  • the application servers provide domain-specific applications for the customer organizations.
  • the database servers may be conventional database systems with domain-specific data.
  • a hosting service It is important for a hosting service to be able to rapidly add components as the needs of their customer organizations change. For example, if the number of HTTP request messages exceeds the capacity of the web servers of a customer system, then additional web servers need to be added to the customer system. It can, however, be very time-consuming to install the appropriate operating system on the web server that is to be added. If a hosting service supported only one operating system, then each computer (e.g., web server) could be pre-loaded with that operating system. To meet the needs of its customers, a hosting service, however, needs to support more than one operating system. In particular, web sites typically use a Linux-based operating system, such as that provided by Red Hat, Inc., or the NT operating system provided by Microsoft Corporation.
  • FIG. 1 is a block diagram illustrating an example infrastructure that may be provided by a hosting service.
  • FIG. 2 is a block diagram illustrating components of the configuration system.
  • FIG. 3 is a block diagram illustrating the layout of the FAT file system.
  • FIG. 4 is a flow diagram illustrating the processing of the configuration system when a bootable FAT partition can be located after the Linux operating system.
  • FIG. 5 is a flow diagram illustrating the processing of the configuration system when a bootable FAT partition cannot be located after the Linux operating system.
  • the configuration system initially installs a first operating system, such as a Linux-based operating system, on each of the computers. This installation process may require the manual insertion of a floppy disk or CD-ROM into the computer.
  • a first operating system such as a Linux-based operating system
  • the second operating system such as the NT operating system
  • the configuration system directs the installation of the second operating system via a local area network that is connected to an installation server. In this way, the second operating system can be installed on a computer for a customer system without manual intervention after it is determined that the second operating system is to be installed.
  • the configuration system initially installs a Linux-based operating system on the hard drive of each computer, which may require the insertion of a floppy disk or CD-ROM. If a computer with the Linux operating system is to be added to a customer system, then that computer will already have the appropriate operating system installed. If, however, a computer with the NT operating system is to be added to a customer system, then the configuration system installs a Linux-based initiate installation program on the computer.
  • the Linux-based initiate installation program uses the services of the installed Linux-based operating system to create a partition for a file allocation table (“FAT”) file system on the hard drive of the computer.
  • the FAT file system was initially designed for use by the disk operating system (“DOS”) by Microsoft Corporation.
  • the FAT partition includes a boot record (or boot sector) that includes sizing information about the partition boot code.
  • the program then stores in the FAT partition the DOS network driver that is needed to access the installation server via a local area network.
  • the program also stores a DOS-based initiate installation program to initiate the installation process from the installation server.
  • the program sets the computer to boot in accordance with the FAT partition.
  • the program then signals to boot the computer.
  • the computer boots to DOS as indicated by the FAT partition.
  • DOS starts up, it executes the DOS-based initiate installation program, which may be identified in an automatic execution batch file (i.e., “autoexec.bat”).
  • the DOS-based initiate installation program creates a FAT partition for the NT operating system, maps the networks drive of the installation server, and runs the NT installation program from the network drive.
  • the computer is configured to execute the NT operating system.
  • FIG. 2 is a block diagram illustrating components of the configuration system.
  • the computers 210 which are available to be added to a customer system, are connected to the NT installation server 220 via a local area network 230 .
  • the computers 210 may include main memory 211 , a central processing unit 212 , input devices (e.g., keyboard and pointing devices), output devices (e.g., display devices), a network interlace adapter 213 , a hard drive 214 , and a CD-ROM or floppy disk drive 215 .
  • the main memory, hard drive, CD-ROM, and floppy drive are computer-readable media that may contain instructions for implementing the configuration system.
  • the NT installation server 220 includes main memory 221 , a central processing unit 222 , a network interface adapter 223 , a hard drive 224 , and a CD-ROM or floppy disk drive 225 .
  • the computers 210 are initially loaded with the Linux operating system and the Linux-based initiate installation program.
  • the Linux-based program controls creating the FAT partition, loading the DOS network driver into the FAT partition, loading the DOS-based initiate installation program, setting the computer to boot in accordance with the FAT partition, and booting the computer.
  • the computer installs the DOS network driver and starts executing the DOS-based initiate installation program.
  • the DOS-based initiate installation program creates a FAT partition for the NT operating system and directs the installation server to install the NT operating system on the computer.
  • FIG. 3 is a block diagram illustrating the layout of the FAT file system.
  • the FAT file system 300 includes a boot record 301 , file allocation tables 302 , directory entries 303 , and a file storage area 304 .
  • Block 311 illustrates the layout of the boot record.
  • the boot record includes file system sizing information and boot code.
  • the file system sizing information includes the number of bytes per sector, number of sectors per allocation unit, and so on.
  • the boot code is executed when the computer system boots to the FAT partition.
  • Block 312 illustrates the layout of a file allocation table.
  • the file allocation tables include cluster pointers linking the various clusters that comprise a file of the file system.
  • Block 313 illustrates the layout of a directory entry.
  • the directory entries describe the hierarchical organization of the files stored in the file system.
  • the entries include the name of the file, the number of the starting cluster for the file, the file size, and so on.
  • the Linux loader (“LiLo”) controls the setting of the master boot record 314 to point to the boot record of the FAT partition.
  • the master boot record does not include a large enough field to point to a FAT partition that is installed at a location after the installed Linux operating system. In such a case, the configuration system boots the Linux operating system from a RAM disk and then executes the Linux-based initiate installation program that is stored on the RAM disk.
  • FIG. 4 is a flow diagram illustrating the processing of the configuration system when a bootable FAT partition can be located after the Linux operating system.
  • Flow diagram 410 illustrates the initial setup of a computer.
  • the configuration system installs both the Linux operating system on the computer and the Linux-based initiate installation program for performing the processing of blocks 422 - 427 .
  • the processing of blocks 422 - 427 can be performed from any time after the installation of the Linux operating system until the time the NT operating system is to be installed on the computer.
  • blocks 422 - 425 can be performed as soon as the Linux operating system is installed, and the performance of blocks 426 - 427 can be delayed until it is decided that the NT operating system should be installed on the computer.
  • the performance of blocks 422 - 427 can be delayed until it is decided that the NT operating system should be installed on the computer.
  • the configuration system creates a 16-bit FAT partition on the hard drive of the computer.
  • the configuration system stores the boot record in the created FAT partition.
  • the configuration system stores the DOS network drivers needed to access the NT installation server in the FAT partition.
  • the configuration system stores the DOS-based initiate installation program in the FAT partition and sets the automatic execution batch file to execute that program.
  • the configuration system sets the Linux loader to boot to DOS in accordance with the FAT partition.
  • the configuration system reboots the computer.
  • Flow diagram 420 illustrates the processing of the DOS-based initiate installation program.
  • the program creates a FAT partition for the NT operating system.
  • the program maps the network drive of the NT installation server.
  • the program starts the execution of the NT installation program from the network drive.
  • the program boots the computer to boot to the NT operating system as indicated by flow diagram 430 .
  • FIG. 5 is a flow diagram illustrating the processing of the configuration system when a bootable FAT partition cannot be located after the Linux operating system.
  • Flow diagram 510 illustrates the initial setup of the computer.
  • the configuration service installs Linux on the computer.
  • the configuration system sets the Linux loader to boot to RAM disk.
  • the RAM disk is configured to execute the Linux-based initiate installation program.
  • the configuration system boots the computer system.
  • Flow diagram 520 illustrates the processing of the Linux-based initiate installation program.
  • the Linux loader loads the RAM disk, which contains the Linux-based initiate installation program, and then directs the execution of that program.
  • Blocks 522 - 527 operate in a similar manner to blocks 422 - 427 , and the processing then continues at flow diagram 420 .

Abstract

A method and system for selectively installing different operating systems on computers. The configuration system initially installs a first operating system, such as a Linux-based operating system, on each of the computers. This installation process may require the manual insertion of a floppy disk or CD-ROM into the computer. Once the first operating system is installed, the second operating system, such as the NT operating system, can be installed without manual intervention at the computer. The configuration system directs the installation of the second operating system via a local area network that is connected to an installation server.

Description

    TECHNICAL FIELD
  • The described technology relates generally to installing an operating system on a computer. [0001]
  • BACKGROUND
  • Many organizations (e.g., corporations) have found it desirable to provide web sites through which users (e.g., customers) can access the web pages of the organization. These web sites may be used to conduct electronic commerce or to disseminate information about the organization. The goal of many of these organizations is to have as many users as possible visit their web sites. In order to support a large number of visits, these organizations often develop complex computer system infrastructures. These infrastructures may include firewalls, load balancers, web servers, application servers, and so on. As the number of visits increases, additional computers need to be added to the infrastructure. Organizations may find it very expensive and time consuming to design, build, and maintain the necessary computer system infrastructure using their internal information technology group. In addition, there may be a shortage of information technology personnel who are qualified to work on such computer system infrastructures. As a result, these organizations may outsource the management of their web sites to a hosting service. [0002]
  • A hosting service may provide the infrastructure, both hardware and software, to support the web sites of their customer organizations. The customer organizations need only provide their domain-specific applications, which can be served by the computer system infrastructure of the hosting service. The use of a hosting service allows a customer organization to concentrate its efforts on its domain-specific applications, and allows the hosting service to cost effectively manage the infrastructure needed by multiple customer organizations. FIG. 1 is a block diagram illustrating an example infrastructure that may be provided by a hosting service. The hosting [0003] service computer center 100 may include customer systems 110, 120, and 130 for different customer organizations. Each customer system may be implemented as a tiered architecture that includes a firewall, a web server, an application server, a database server, and a mass storage device. Each tier may include multiple components (e.g., computers) for providing the functionality of that tier. Additional components can be added to a tier as demand for a customer system increases. For example, the customer system 110 may initially include only two web servers. As traffic to the web site increases, a third web server can be added to the web server tier. The customer systems may include load balancing hardware between each tier to distribute the workload among the components of the next lower tier. The firewalls limit Internet access to only message formats that conform to certain protocols (e.g., HTTP protocol). The web servers receive HTTP request messages, invoke the services of the application servers, and then provide HTTP response messages to the users. The application servers provide domain-specific applications for the customer organizations. The database servers may be conventional database systems with domain-specific data. One skilled in the art will appreciate that there are many possible variations to the overall architecture of the infrastructure.
  • It is important for a hosting service to be able to rapidly add components as the needs of their customer organizations change. For example, if the number of HTTP request messages exceeds the capacity of the web servers of a customer system, then additional web servers need to be added to the customer system. It can, however, be very time-consuming to install the appropriate operating system on the web server that is to be added. If a hosting service supported only one operating system, then each computer (e.g., web server) could be pre-loaded with that operating system. To meet the needs of its customers, a hosting service, however, needs to support more than one operating system. In particular, web sites typically use a Linux-based operating system, such as that provided by Red Hat, Inc., or the NT operating system provided by Microsoft Corporation. The installation of an operating system on a computer typically requires manual intervention, such as inserting a floppy disk or CD-ROM into the computer. This manual intervention increases the time needed to add computers to a customer system. It would be desirable to have a technique for installing different operating systems quickly and without manual intervention after it is determined which operating system needs to be installed on a computer. [0004]
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • FIG. 1 is a block diagram illustrating an example infrastructure that may be provided by a hosting service. [0005]
  • FIG. 2 is a block diagram illustrating components of the configuration system. [0006]
  • FIG. 3 is a block diagram illustrating the layout of the FAT file system. [0007]
  • FIG. 4 is a flow diagram illustrating the processing of the configuration system when a bootable FAT partition can be located after the Linux operating system. [0008]
  • FIG. 5 is a flow diagram illustrating the processing of the configuration system when a bootable FAT partition cannot be located after the Linux operating system.[0009]
  • DETAILED DESCRIPTION
  • A method and system for selectively installing different operating systems on computers is provided. In one embodiment, the configuration system initially installs a first operating system, such as a Linux-based operating system, on each of the computers. This installation process may require the manual insertion of a floppy disk or CD-ROM into the computer. Once the first operating system is installed, the second operating system, such as the NT operating system, can be installed without manual intervention at the computer. The configuration system directs the installation of the second operating system via a local area network that is connected to an installation server. In this way, the second operating system can be installed on a computer for a customer system without manual intervention after it is determined that the second operating system is to be installed. [0010]
  • The configuration system initially installs a Linux-based operating system on the hard drive of each computer, which may require the insertion of a floppy disk or CD-ROM. If a computer with the Linux operating system is to be added to a customer system, then that computer will already have the appropriate operating system installed. If, however, a computer with the NT operating system is to be added to a customer system, then the configuration system installs a Linux-based initiate installation program on the computer. The Linux-based initiate installation program uses the services of the installed Linux-based operating system to create a partition for a file allocation table (“FAT”) file system on the hard drive of the computer. The FAT file system was initially designed for use by the disk operating system (“DOS”) by Microsoft Corporation. The FAT partition includes a boot record (or boot sector) that includes sizing information about the partition boot code. The program then stores in the FAT partition the DOS network driver that is needed to access the installation server via a local area network. The program also stores a DOS-based initiate installation program to initiate the installation process from the installation server. The program then sets the computer to boot in accordance with the FAT partition. The program then signals to boot the computer. The computer boots to DOS as indicated by the FAT partition. As DOS starts up, it executes the DOS-based initiate installation program, which may be identified in an automatic execution batch file (i.e., “autoexec.bat”). The DOS-based initiate installation program creates a FAT partition for the NT operating system, maps the networks drive of the installation server, and runs the NT installation program from the network drive. Upon completion of the installation, the computer is configured to execute the NT operating system. [0011]
  • FIG. 2 is a block diagram illustrating components of the configuration system. The [0012] computers 210, which are available to be added to a customer system, are connected to the NT installation server 220 via a local area network 230. The computers 210 may include main memory 211, a central processing unit 212, input devices (e.g., keyboard and pointing devices), output devices (e.g., display devices), a network interlace adapter 213, a hard drive 214, and a CD-ROM or floppy disk drive 215. The main memory, hard drive, CD-ROM, and floppy drive are computer-readable media that may contain instructions for implementing the configuration system. Communication channels other than a local area network, such as the Internet, a wide area network, or point-to-point dial-up connections may be used to connect the computers to the NT installation server. The NT installation server 220 includes main memory 221, a central processing unit 222, a network interface adapter 223, a hard drive 224, and a CD-ROM or floppy disk drive 225. The computers 210 are initially loaded with the Linux operating system and the Linux-based initiate installation program. (Alternatively, the loading of the Linux-based initiate installation program can be deferred until it is determined that the NT operating system should be installed on the computer.) The Linux-based program controls creating the FAT partition, loading the DOS network driver into the FAT partition, loading the DOS-based initiate installation program, setting the computer to boot in accordance with the FAT partition, and booting the computer. When booted, the computer installs the DOS network driver and starts executing the DOS-based initiate installation program. The DOS-based initiate installation program creates a FAT partition for the NT operating system and directs the installation server to install the NT operating system on the computer.
  • FIG. 3 is a block diagram illustrating the layout of the FAT file system. The FAT file system [0013] 300 includes a boot record 301, file allocation tables 302, directory entries 303, and a file storage area 304. Block 311 illustrates the layout of the boot record. The boot record includes file system sizing information and boot code. The file system sizing information includes the number of bytes per sector, number of sectors per allocation unit, and so on. The boot code is executed when the computer system boots to the FAT partition. Block 312 illustrates the layout of a file allocation table. The file allocation tables include cluster pointers linking the various clusters that comprise a file of the file system. Block 313 illustrates the layout of a directory entry. The directory entries describe the hierarchical organization of the files stored in the file system. The entries include the name of the file, the number of the starting cluster for the file, the file size, and so on. In one embodiment, the Linux loader (“LiLo”) controls the setting of the master boot record 314 to point to the boot record of the FAT partition. In an alternate embodiment, the master boot record does not include a large enough field to point to a FAT partition that is installed at a location after the installed Linux operating system. In such a case, the configuration system boots the Linux operating system from a RAM disk and then executes the Linux-based initiate installation program that is stored on the RAM disk.
  • FIG. 4 is a flow diagram illustrating the processing of the configuration system when a bootable FAT partition can be located after the Linux operating system. Flow diagram [0014] 410 illustrates the initial setup of a computer. In block 421, the configuration system installs both the Linux operating system on the computer and the Linux-based initiate installation program for performing the processing of blocks 422-427. The processing of blocks 422-427 can be performed from any time after the installation of the Linux operating system until the time the NT operating system is to be installed on the computer. For example, blocks 422-425 can be performed as soon as the Linux operating system is installed, and the performance of blocks 426-427 can be delayed until it is decided that the NT operating system should be installed on the computer. Alternatively, the performance of blocks 422-427 can be delayed until it is decided that the NT operating system should be installed on the computer. In block 422, the configuration system creates a 16-bit FAT partition on the hard drive of the computer. In block 423, the configuration system stores the boot record in the created FAT partition. In block 424, the configuration system stores the DOS network drivers needed to access the NT installation server in the FAT partition. In block 425, the configuration system stores the DOS-based initiate installation program in the FAT partition and sets the automatic execution batch file to execute that program. In block 426, the configuration system sets the Linux loader to boot to DOS in accordance with the FAT partition. In block 427, the configuration system reboots the computer. Once booted, the processing continues at flow diagram 420. Flow diagram 420 illustrates the processing of the DOS-based initiate installation program. In block 421, the program creates a FAT partition for the NT operating system. In block 422, the program maps the network drive of the NT installation server. In block 423, the program starts the execution of the NT installation program from the network drive. Upon completion of the installation, the program boots the computer to boot to the NT operating system as indicated by flow diagram 430.
  • FIG. 5 is a flow diagram illustrating the processing of the configuration system when a bootable FAT partition cannot be located after the Linux operating system. Flow diagram [0015] 510 illustrates the initial setup of the computer. In block 511, the configuration service installs Linux on the computer. In block 512, the configuration system sets the Linux loader to boot to RAM disk. The RAM disk is configured to execute the Linux-based initiate installation program. In block 513, the configuration system boots the computer system. Flow diagram 520 illustrates the processing of the Linux-based initiate installation program. In block 521, the Linux loader loads the RAM disk, which contains the Linux-based initiate installation program, and then directs the execution of that program. Blocks 522-527 operate in a similar manner to blocks 422-427, and the processing then continues at flow diagram 420.
  • Based on the above description, it will be appreciated that although specific embodiments of the configuration system have been described for purposes of illustration, various modifications may be made without deviating from the spirit and scope of the invention. Accordingly, the invention is not limited except by the appended claims. [0016]

Claims (39)

1. A method in a computer for booting a computer, the method comprising:
installing a Linux-based operating system on a hard drive of the computer;
creating a FAT partition on the hard drive using services of the installed Linux-based operating system, the FAT partition having a boot record and an initiate installation program;
setting the computer to boot in accordance with the boot record of the FAT partition; and
booting the computer wherein the computer boots in accordance with the boot record of the FAT partition and executes the initiate installation program.
2. The method of claim 1 wherein the boot record controls the booting to DOS.
3. The method of claim 2 including storing a network device driver in the FAT partition so that the initiate installation program can access a network device.
4. The method of claim 3 wherein the initiate installation program creates a partition for an NT operating system and controls the installation of the NT operating system from the network device onto the hard drive.
5. The method of claim 4 including upon installation of the NT operating system booting the computer wherein the computer boots to the installed NT operating system.
6. The method of claim 1 wherein the creating of the FAT partition, setting of the computer to boot, and the booting of the computer occur after identifying that the NT operating system is to be installed on the computer.
7. The method of claim 1 wherein the setting of the computer to boot in accordance with the boot record of the FAT partition occurs after identifying that the NT operating system is to be installed on the computer.
8. A method for installing an NT operating system on a computer with a different operating system currently installed on the computer, the method comprising:
creating a FAT partition on the computer, the FAT partition having a boot record for booting to DOS, having a network device driver, and having a DOS-based initiate installation program;
setting the computer to boot to DOS in accordance with the boot record of the created FAT partition; and
booting the computer wherein the computer boots to DOS in accordance with the boot record and the DOS-based initiate installation program uses the network device driver to initiate installation of the NT operating system from a network device onto the computer.
9. The method of claim 8 including after installing the NT operating system booting the computer wherein the computer boots to the NT operating system.
10. The method of claim 8 wherein the creating occurs before and the setting and booting occur after identifying that the NT operating system is to be installed on the computer.
11. The method of claim 8 wherein the creating occurs after identifying that the NT operating system is to be installed on the computer.
12. The method of claim 8 wherein the DOS-based initiate installation program creates a partition for the NT operating system.
13. The method of claim 8 wherein the different operating system is a Linux-based operating system.
14. The method of claim 8 including before creating the FAT partition setting the computer to boot in accordance with a RAM disk, the RAM disk having a Linux-based initiate installation program.
15. A method for selectively installing different operating systems on computers, the method comprising:
installing a first operating system on each of the computers;
using services of the first operating system,
creating a file system partition on a storage device of the computers, the file system partition having information for installing the second operating system on the computer; and
upon receiving an indication that the second operating system is to be installed on a computer,
setting the computer to boot in accordance with the created file system partition; and
booting the computer wherein the computer boots in accordance with the created file system partition and installs the second operating system on the computer using the information of the file system partition.
16. The method of claim 15 wherein the file system partition is a FAT partition.
17. The method of claim 15 wherein the first operating system is a Linux-based operating system and the second operating system is an NT operating system.
18. The method of claim 15 wherein the file system partition is created upon receiving the indication that the second operating system is to be installed on the computer.
19. The method of claim 15 wherein the second operating system is installed from a network device.
20. The method of claim 15 wherein the created file system partition includes a network device driver for accessing a network device from which the second operating system is to be installed.
21. An apparatus for selectively installing different operating systems on computers, each computer installed with a first operating system, comprising:
means for creating a file system partition on the computers, the file system partition having information for installing the second operating system on the computer;
means for setting the computer to boot in accordance with the created file system partition; and
means for booting the computer wherein the computer boots in accordance with the created file system partition and installs the second operating system on the computer in accordance with the information of the file system partition.
22. The apparatus of claim 21 wherein the file system partition is a FAT partition.
23. The apparatus of claim 21 wherein the first operating system is a Linux-based operating system and the second operating system is an NT operating system.
24. The apparatus of claim 21 wherein the file system partition is created upon receiving an indication that the second operating system is to be installed on the computer.
25. The apparatus of claim 21 wherein the second operating system is installed from a network device.
26. The apparatus of claim 21 wherein the created file system partition includes a network device driver for accessing a network device from which the second operating system is to be installed.
27. The apparatus of claim 21 including means for booting the computer system from a RAM disk that provides means for creating a file system partition, means for setting the computer to boot in accordance with created file system partition, and means for booting the computer.
28. A computer-readable medium including instructions for controlling a computer installed with a Linux-based operating system to install an NT operating system by a method comprising:
creating a FAT partition on the computer, the FAT partition having a boot record for booting to DOS, having a network device driver, and having a DOS-based initiate installation program;
setting the computer to boot to DOS in accordance with the boot record of the FAT partition; and
booting the computer wherein the computer boots to DOS in accordance with the boot record and the DOS-based initiate installation program uses the network device driver to install the NT operating system from a network device onto the computer.
29. The computer-readable medium of claim 28 including after installing the NT operating system onto the computer booting the computer wherein the computer boots to the NT operating system.
30. The computer-readable medium of claim 28 wherein the setting and booting occur after identifying that the NT operating system is to be installed on the computer.
31. The computer-readable medium of claim 28 wherein the creating occurs after identifying that the NT operating system is to be installed on the computer.
32. The computer-readable medium of claim 28 wherein the DOS-based initiate installation program creates a partition for the NT operating system.
33. The computer-readable medium of claim 28 including before creating the FAT partition setting the computer to boot in accordance with a RAM disk, the RAM disk having instructions for controlling the creating of the FAT partition and setting of the computer to boot to DOS.
34. A method of selectively installing different operating systems on computers, the method comprising:
installing a first operating system on the computers; and
upon receiving an indication that a computer is to be configured with a second operating system,
setting the computer to boot in accordance with a file system partition, the file system partition having information for installing the second operating system on the computer, the second operating system being installed from a network device; and
booting the computer to effect the installation of the second operating system from the network onto the computer.
35. The method of claim 34 wherein the first operating system is a Linux-based operating system and the second operating system is the NT operating system.
36. The method of claim 34 wherein the file system partition is a FAT-based partition.
37. The method of claim 34 wherein the file system partition includes a boot record for booting to DOS and a program for initiating the installation of the second operating system.
38. The method of claim 34 including before setting the computer to boot in accordance with the file system partition, booting the computer to RAM disk that controls setting the computer to boot in accordance with the file system partition.
39. The method of claim 34 including after installing the first operating system, creating the file system partition.
US09/773,761 2001-01-31 2001-01-31 Method and system for installing an operating system Abandoned US20020103996A1 (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
US09/773,761 US20020103996A1 (en) 2001-01-31 2001-01-31 Method and system for installing an operating system
PCT/US2002/002418 WO2002061533A2 (en) 2001-01-31 2002-01-29 Method and system for installing an operating system
AU2002237955A AU2002237955A1 (en) 2001-01-31 2002-01-29 Method and system for installing an operating system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US09/773,761 US20020103996A1 (en) 2001-01-31 2001-01-31 Method and system for installing an operating system

Publications (1)

Publication Number Publication Date
US20020103996A1 true US20020103996A1 (en) 2002-08-01

Family

ID=25099231

Family Applications (1)

Application Number Title Priority Date Filing Date
US09/773,761 Abandoned US20020103996A1 (en) 2001-01-31 2001-01-31 Method and system for installing an operating system

Country Status (3)

Country Link
US (1) US20020103996A1 (en)
AU (1) AU2002237955A1 (en)
WO (1) WO2002061533A2 (en)

Cited By (45)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040243997A1 (en) * 2003-05-29 2004-12-02 Sun Microsystems, Inc. Method, system, and program for installing program components on a computer
US20050198484A1 (en) * 2003-12-18 2005-09-08 Cepulis Darren J. Configuring settings of a computer system to be compatible with an operating system
US20060031425A1 (en) * 2004-06-07 2006-02-09 Northrop Grumman Corporation Method for imaging computer systems
US20060195672A1 (en) * 2003-02-20 2006-08-31 Matsushita Electric Industrial Co., Ltd. Information recording medium and region management method thereof
EP1703383A1 (en) * 2005-03-18 2006-09-20 Research In Motion Limited Electronic device having an alterable configuration and methods of manufacturing and configuring the device
US20060229769A1 (en) * 2005-04-08 2006-10-12 Caterpillar Inc. Control system and method
US20060229854A1 (en) * 2005-04-08 2006-10-12 Caterpillar Inc. Computer system architecture for probabilistic modeling
US20060229852A1 (en) * 2005-04-08 2006-10-12 Caterpillar Inc. Zeta statistic process method and system
US20060230097A1 (en) * 2005-04-08 2006-10-12 Caterpillar Inc. Process model monitoring method and system
US20060229753A1 (en) * 2005-04-08 2006-10-12 Caterpillar Inc. Probabilistic modeling system for product design
US20070061144A1 (en) * 2005-08-30 2007-03-15 Caterpillar Inc. Batch statistics process model method and system
US20070118487A1 (en) * 2005-11-18 2007-05-24 Caterpillar Inc. Product cost modeling method and system
US20070179769A1 (en) * 2005-10-25 2007-08-02 Caterpillar Inc. Medical risk stratifying method and system
US20070180490A1 (en) * 2004-05-20 2007-08-02 Renzi Silvio J System and method for policy management
US20070203810A1 (en) * 2006-02-13 2007-08-30 Caterpillar Inc. Supply chain modeling method and system
US20080021681A1 (en) * 2005-04-08 2008-01-24 Caterpillar Inc. Process modeling and optimization method and system
US20080040714A1 (en) * 2006-08-14 2008-02-14 Caterpillar Inc. Method and system for automatic computer and user migration
US20080154459A1 (en) * 2006-12-21 2008-06-26 Caterpillar Inc. Method and system for intelligent maintenance
US20080183449A1 (en) * 2007-01-31 2008-07-31 Caterpillar Inc. Machine parameter tuning method and system
CN100414500C (en) * 2004-06-15 2008-08-27 华为技术有限公司 Outputting method of starting information for embedded computer system
US20090037153A1 (en) * 2007-07-30 2009-02-05 Caterpillar Inc. Product design optimization method and system
US7499842B2 (en) 2005-11-18 2009-03-03 Caterpillar Inc. Process model based virtual sensor and method
US20090063087A1 (en) * 2007-08-31 2009-03-05 Caterpillar Inc. Virtual sensor based control system and method
US7505949B2 (en) 2006-01-31 2009-03-17 Caterpillar Inc. Process model error correction method and system
US20090112334A1 (en) * 2007-10-31 2009-04-30 Grichnik Anthony J Fixed-point virtual sensor control system and method
US20090119065A1 (en) * 2007-11-02 2009-05-07 Caterpillar Inc. Virtual sensor network (VSN) system and method
US20090132216A1 (en) * 2005-04-08 2009-05-21 Caterpillar Inc. Asymmetric random scatter process for probabilistic modeling system for product design
US20090158027A1 (en) * 2005-03-18 2009-06-18 Research In Motion Limited Electronic device having an alterable configuration and methods of manufacturing and configuring the same
US20100050025A1 (en) * 2008-08-20 2010-02-25 Caterpillar Inc. Virtual sensor network (VSN) based control system and method
US7787969B2 (en) 2007-06-15 2010-08-31 Caterpillar Inc Virtual sensor system and method
US20100250202A1 (en) * 2005-04-08 2010-09-30 Grichnik Anthony J Symmetric random scatter process for probabilistic modeling system for product design
US7831416B2 (en) 2007-07-17 2010-11-09 Caterpillar Inc Probabilistic modeling system for product design
US8036764B2 (en) 2007-11-02 2011-10-11 Caterpillar Inc. Virtual sensor network (VSN) system and method
US8086640B2 (en) 2008-05-30 2011-12-27 Caterpillar Inc. System and method for improving data coverage in modeling systems
US8478506B2 (en) 2006-09-29 2013-07-02 Caterpillar Inc. Virtual sensor based engine control system and method
US8615766B2 (en) 2012-05-01 2013-12-24 Concurix Corporation Hybrid operating system
US8793004B2 (en) 2011-06-15 2014-07-29 Caterpillar Inc. Virtual sensor system and method for generating output parameters
US8806478B2 (en) 2012-10-02 2014-08-12 Nextbit Systems, Inc. Customizing operating system based on detected carrier
US8875127B2 (en) 2012-10-02 2014-10-28 Nextbit Systems Inc. Operating system customization
US9038060B2 (en) * 2012-10-02 2015-05-19 Nextbit Systems Inc. Automatically installing operating system specific to a detected network
WO2017082570A1 (en) * 2015-11-11 2017-05-18 삼성전자 주식회사 Electronic device and method for controlling same
WO2020081899A1 (en) * 2018-10-19 2020-04-23 Veriblock, Inc. Systems, methods, and storage media for using the otherwise-unutilized storage space on a storage device
US20210200543A1 (en) * 2019-12-31 2021-07-01 Proton World International N.V. Embedded system
US11624156B2 (en) 2013-12-09 2023-04-11 The Procter & Gamble Company Fibrous structures including an active agent and having a graphic printed thereon
US11720358B2 (en) 2019-12-31 2023-08-08 Proton World International N.V. Embedded system

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6282711B1 (en) * 1999-08-10 2001-08-28 Hewlett-Packard Company Method for more efficiently installing software components from a remote server source
US6351850B1 (en) * 1997-11-14 2002-02-26 Frank Van Gilluwe Computer operating system installation
US6591376B1 (en) * 2000-03-02 2003-07-08 Hewlett-Packard Development Company, L.P. Method and system for failsafe recovery and upgrade of an embedded operating system

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6330653B1 (en) * 1998-05-01 2001-12-11 Powerquest Corporation Manipulation of virtual and live computer storage device partitions
US6377958B1 (en) * 1998-07-15 2002-04-23 Powerquest Corporation File system conversion

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6351850B1 (en) * 1997-11-14 2002-02-26 Frank Van Gilluwe Computer operating system installation
US6282711B1 (en) * 1999-08-10 2001-08-28 Hewlett-Packard Company Method for more efficiently installing software components from a remote server source
US6591376B1 (en) * 2000-03-02 2003-07-08 Hewlett-Packard Development Company, L.P. Method and system for failsafe recovery and upgrade of an embedded operating system

Cited By (68)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7653796B2 (en) * 2003-02-20 2010-01-26 Panasonic Corporation Information recording medium and region management method for a plurality of recording regions each managed by independent file system
US20060195672A1 (en) * 2003-02-20 2006-08-31 Matsushita Electric Industrial Co., Ltd. Information recording medium and region management method thereof
US20040243997A1 (en) * 2003-05-29 2004-12-02 Sun Microsystems, Inc. Method, system, and program for installing program components on a computer
US20050198484A1 (en) * 2003-12-18 2005-09-08 Cepulis Darren J. Configuring settings of a computer system to be compatible with an operating system
US7383429B2 (en) 2003-12-18 2008-06-03 Hewlett-Packard Development Company, L.P. Configuring settings of a computer system to be compatible with an operating system
US20070180490A1 (en) * 2004-05-20 2007-08-02 Renzi Silvio J System and method for policy management
US20060031425A1 (en) * 2004-06-07 2006-02-09 Northrop Grumman Corporation Method for imaging computer systems
CN100414500C (en) * 2004-06-15 2008-08-27 华为技术有限公司 Outputting method of starting information for embedded computer system
EP1703383A1 (en) * 2005-03-18 2006-09-20 Research In Motion Limited Electronic device having an alterable configuration and methods of manufacturing and configuring the device
US20090158027A1 (en) * 2005-03-18 2009-06-18 Research In Motion Limited Electronic device having an alterable configuration and methods of manufacturing and configuring the same
US8156316B2 (en) 2005-03-18 2012-04-10 Research In Motion Limited Electronic device having an alterable configuration and methods of manufacturing and configuring the same
US8364942B2 (en) 2005-03-18 2013-01-29 Research In Motion Limited Electronic device having an alterable configuration and methods of manufacturing and configuring the same
US8583907B2 (en) 2005-03-18 2013-11-12 Blackberry Limited Electronic device having an alterable configuration and methods of manufacturing and configuring the same
US20060230097A1 (en) * 2005-04-08 2006-10-12 Caterpillar Inc. Process model monitoring method and system
US7877239B2 (en) 2005-04-08 2011-01-25 Caterpillar Inc Symmetric random scatter process for probabilistic modeling system for product design
US20080021681A1 (en) * 2005-04-08 2008-01-24 Caterpillar Inc. Process modeling and optimization method and system
US7565333B2 (en) 2005-04-08 2009-07-21 Caterpillar Inc. Control system and method
US20060229769A1 (en) * 2005-04-08 2006-10-12 Caterpillar Inc. Control system and method
US8364610B2 (en) 2005-04-08 2013-01-29 Caterpillar Inc. Process modeling and optimization method and system
US20060229753A1 (en) * 2005-04-08 2006-10-12 Caterpillar Inc. Probabilistic modeling system for product design
US20060229854A1 (en) * 2005-04-08 2006-10-12 Caterpillar Inc. Computer system architecture for probabilistic modeling
US20090132216A1 (en) * 2005-04-08 2009-05-21 Caterpillar Inc. Asymmetric random scatter process for probabilistic modeling system for product design
US8209156B2 (en) 2005-04-08 2012-06-26 Caterpillar Inc. Asymmetric random scatter process for probabilistic modeling system for product design
US20100250202A1 (en) * 2005-04-08 2010-09-30 Grichnik Anthony J Symmetric random scatter process for probabilistic modeling system for product design
US20060229852A1 (en) * 2005-04-08 2006-10-12 Caterpillar Inc. Zeta statistic process method and system
US20070061144A1 (en) * 2005-08-30 2007-03-15 Caterpillar Inc. Batch statistics process model method and system
US7487134B2 (en) 2005-10-25 2009-02-03 Caterpillar Inc. Medical risk stratifying method and system
US7584166B2 (en) 2005-10-25 2009-09-01 Caterpillar Inc. Expert knowledge combination process based medical risk stratifying method and system
US20070179769A1 (en) * 2005-10-25 2007-08-02 Caterpillar Inc. Medical risk stratifying method and system
US7499842B2 (en) 2005-11-18 2009-03-03 Caterpillar Inc. Process model based virtual sensor and method
US20070118487A1 (en) * 2005-11-18 2007-05-24 Caterpillar Inc. Product cost modeling method and system
US7505949B2 (en) 2006-01-31 2009-03-17 Caterpillar Inc. Process model error correction method and system
US20070203810A1 (en) * 2006-02-13 2007-08-30 Caterpillar Inc. Supply chain modeling method and system
US20080040714A1 (en) * 2006-08-14 2008-02-14 Caterpillar Inc. Method and system for automatic computer and user migration
US8387038B2 (en) 2006-08-14 2013-02-26 Caterpillar Inc. Method and system for automatic computer and user migration
US8478506B2 (en) 2006-09-29 2013-07-02 Caterpillar Inc. Virtual sensor based engine control system and method
US20080154459A1 (en) * 2006-12-21 2008-06-26 Caterpillar Inc. Method and system for intelligent maintenance
US7483774B2 (en) 2006-12-21 2009-01-27 Caterpillar Inc. Method and system for intelligent maintenance
US20080183449A1 (en) * 2007-01-31 2008-07-31 Caterpillar Inc. Machine parameter tuning method and system
US7787969B2 (en) 2007-06-15 2010-08-31 Caterpillar Inc Virtual sensor system and method
US7831416B2 (en) 2007-07-17 2010-11-09 Caterpillar Inc Probabilistic modeling system for product design
US20090037153A1 (en) * 2007-07-30 2009-02-05 Caterpillar Inc. Product design optimization method and system
US7788070B2 (en) 2007-07-30 2010-08-31 Caterpillar Inc. Product design optimization method and system
US20090063087A1 (en) * 2007-08-31 2009-03-05 Caterpillar Inc. Virtual sensor based control system and method
US7542879B2 (en) 2007-08-31 2009-06-02 Caterpillar Inc. Virtual sensor based control system and method
US7593804B2 (en) 2007-10-31 2009-09-22 Caterpillar Inc. Fixed-point virtual sensor control system and method
US20090112334A1 (en) * 2007-10-31 2009-04-30 Grichnik Anthony J Fixed-point virtual sensor control system and method
US8036764B2 (en) 2007-11-02 2011-10-11 Caterpillar Inc. Virtual sensor network (VSN) system and method
US8224468B2 (en) 2007-11-02 2012-07-17 Caterpillar Inc. Calibration certificate for virtual sensor network (VSN)
US20090119065A1 (en) * 2007-11-02 2009-05-07 Caterpillar Inc. Virtual sensor network (VSN) system and method
US8086640B2 (en) 2008-05-30 2011-12-27 Caterpillar Inc. System and method for improving data coverage in modeling systems
US7917333B2 (en) 2008-08-20 2011-03-29 Caterpillar Inc. Virtual sensor network (VSN) based control system and method
US20100050025A1 (en) * 2008-08-20 2010-02-25 Caterpillar Inc. Virtual sensor network (VSN) based control system and method
US8793004B2 (en) 2011-06-15 2014-07-29 Caterpillar Inc. Virtual sensor system and method for generating output parameters
US8615766B2 (en) 2012-05-01 2013-12-24 Concurix Corporation Hybrid operating system
US10346481B2 (en) 2012-10-02 2019-07-09 Razer (Asia-Pacific) Pte. Ltd. Customizing operating system based on detected carrier
US8875127B2 (en) 2012-10-02 2014-10-28 Nextbit Systems Inc. Operating system customization
US9038060B2 (en) * 2012-10-02 2015-05-19 Nextbit Systems Inc. Automatically installing operating system specific to a detected network
US9398063B2 (en) 2012-10-02 2016-07-19 Nextbit Systems Inc. Customizing distribution of an operating system based on detected network carrier by retrieving differences between the distributed operating system and an operating system currently installed on a computing device
US8806478B2 (en) 2012-10-02 2014-08-12 Nextbit Systems, Inc. Customizing operating system based on detected carrier
US11624156B2 (en) 2013-12-09 2023-04-11 The Procter & Gamble Company Fibrous structures including an active agent and having a graphic printed thereon
WO2017082570A1 (en) * 2015-11-11 2017-05-18 삼성전자 주식회사 Electronic device and method for controlling same
US10846100B2 (en) 2015-11-11 2020-11-24 Samsung Electronics Co., Ltd. Electronic device and method for controlling same
WO2020081899A1 (en) * 2018-10-19 2020-04-23 Veriblock, Inc. Systems, methods, and storage media for using the otherwise-unutilized storage space on a storage device
US11409451B2 (en) 2018-10-19 2022-08-09 Veriblock, Inc. Systems, methods, and storage media for using the otherwise-unutilized storage space on a storage device
US20210200543A1 (en) * 2019-12-31 2021-07-01 Proton World International N.V. Embedded system
US11714643B2 (en) * 2019-12-31 2023-08-01 Proton World International N.V. Embedded system
US11720358B2 (en) 2019-12-31 2023-08-08 Proton World International N.V. Embedded system

Also Published As

Publication number Publication date
WO2002061533A2 (en) 2002-08-08
WO2002061533A3 (en) 2003-09-25
AU2002237955A1 (en) 2002-08-12

Similar Documents

Publication Publication Date Title
US20020103996A1 (en) Method and system for installing an operating system
US8880864B2 (en) Parallelizing multiple boot images with virtual machines
US9547624B2 (en) Computer system and configuration management method therefor
US5859969A (en) Remote installation system and method
JP4242420B2 (en) Resource sharing independent of OS on many computing platforms
RU2421785C2 (en) Automated control of device drivers
US5872968A (en) Data processing network with boot process using multiple servers
JP4797636B2 (en) Complex information platform apparatus and information processing apparatus configuration method thereof
US8612553B2 (en) Method and system for dynamically purposing a computing device
US20040255286A1 (en) Method for distributed update of firmware across a clustered platform infrastructure
US8250183B1 (en) System and method for pre-installing of virtual server files
US20030097422A1 (en) System and method for provisioning software
EP0613274A2 (en) Socket structure for concurrent multiple protocol access
US7203700B1 (en) Online instance addition and deletion in a multi-instance computer system
US8412901B2 (en) Making automated use of data volume copy service targets
US7912919B2 (en) Common storage in scalable computer systems
US7668938B1 (en) Method and system for dynamically purposing a computing device
JP2009509255A (en) Configuration of remote data processing system
US6687819B1 (en) System, apparatus and method for supporting multiple file systems in boot code
US20020138665A1 (en) Binding of processes in network systems
US20060293877A1 (en) Method and apparatus for uni-lingual workflow usage in multi-lingual data center environments
US20080126772A1 (en) System and Method for Abstracting Computer Disk Image Cloning Capabilities from Bootable Media
Cisco Updating the Mainframe Application Software
Cisco Updating the Mainframe Application Software
Cisco Updating the Mainframe Application Software

Legal Events

Date Code Title Description
AS Assignment

Owner name: LOUDCLOUD, INC., CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:LEVASSEUR, JOSHUA T.;STONE, ADAM;REEL/FRAME:012109/0834

Effective date: 20010809

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION