Creating file systems within a file in a storage technology-abstracted manner

• US 7,614,051 B2
• Filed: 05/01/2004
• Issued: 11/03/2009
• Est. Priority Date: 12/16/2003
• Status: Expired due to Fees

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Rogers, Andrew M., Tonkelowitz, Mark Scott, Glaum, Jeffrey D.
• Primary Examiner(s): Dam; Tuan Q
• Assistant Examiner(s): Dao; Thuy
• Application Number:
  US10/837,150
• Publication Number:
  US 20050132123A1
• Time in Patent Office: 2,012 Days
• Field of Search: None
• US Class Current: 717/175
• CPC Class Codes: G06F 8/63 Image based installation; Cloning; Build to order

Abstract

Described is a system and method used in manufacturing computer devices, in which a single manufacturing image file contains an internal partition and file system layout into which individual operating system component packages are written. The image file is independent of any particular storage technology. To generate the file, a disk image utility tool inputs a memory configuration file and a package-to-partition mapping file to create the partitions/file systems within the image file. The operating system components (package) are written into the partitions. To store (e.g., flash) the image file'"'"'s data on a particular storage device, the image file is post-processed to customize the data for a particular storage device.

Claims

1. In a computing environment, a method of creating a file system within a file in a storage technology abstracted manner so that that file system can be easily applied to varying storage technologies, the method comprising:

accessing packages containing image data to install to a first storage medium, wherein at least some of the packages are operating system image components, and wherein the packages include an update loader component, a kernel component, an operating system files component, and a user data component;

accessing a description of partitions to which the package contents are to be written, the description of the partitions comprising information correlating each package to a particular partition, wherein the description of partitions comprises an Extensible Markup Language (XML) file; and

based on the accessed packages and the description of the partitions, generating an output file to a second storage medium, the output file being an image file and containing a plurality of partitions wherein each partition corresponds to a file system, but not implementing file system logic for a particular storage technology, with the contents of each package stored in one of the plurality of partitions based on the description of the partitions, and wherein the output file comprises;

a first partition, wherein the first partition comprises binary code implementing an update loader;

a second partition, the second partition being a kernel partition, and storing at least one of a random access memory (RAM) image or a read only memory (ROM) image;

a third partition, the third partition being a system partition and comprising operating system files;

a fourth partition, the fourth partition being a user partition specified for user data storage.

2. The method of claim 1 further comprising, accessing a memory configuration file to determine a lay out of the plurality of partitions to be laid out within the output file.

3. The method of claim 1 wherein the second partition comprises a RAM-based image partition, and wherein the RAM-based image partition is located to a unique virtual address range through a fix-up or relocation process based on known address information and known restrictions as to where subsections of an executable file can be placed in the overall virtual address space, to process each executable file and locate the contents at a non-overlapping virtual address space range.

4. The method of claim 1 wherein the second partition comprises a ROM-based image partition, and wherein the ROM-based image partition is has code fixed-up or relocated to execute-in-place on the first storage medium.

5. The method of claim 1 wherein generating the output file comprises writing data to a partition that extends to the end of the file, and adjusting the size of the partition based on the actual amount of data written.

6. The method of claim 5 wherein writing data to a master boot record comprises defining a user store partition.

7. The method of claim 1 wherein generating the output file comprises writing data to the third partition that extends to the end of the file, adding a free space buffer after the end of the data written, and adjusting the size of the third partition based on the actual amount of data written and the free space buffer to enable future updates to the third partition to consume more space than consumed by the data in the current third partition, allowing for growth of subsequent updates.

8. The method of claim 1 further comprising, writing data to a master boot record in the file to define the plurality of partitions contained in the file.

9. The method of claim 1 further comprising, writing additional data to the output file.

10. The method of claim 1 further comprising, executing a post-process to prepare for transferring data from the output file into the first storage medium.

11. The method of claim 10 wherein the first storage medium comprises flash memory in which code therein can be executed in place, and further comprising, accessing a memory configuration file to fix up at least one of the plurality of partitions such that code contained therein will execute in place.

12. The method of claim 1 further comprising, accessing a memory configuration file to determine which sections of the first storage medium are reserved.

13. One or more computer-readable storage media storing computer-executable instructions which when executed perform the method of claim 1.

14. In a computing environment, a method of generating an image for installation to a storage medium of a computing device, the image being generated from a file storing a plurality of partitions in a storage technology abstracted manner allowing the file to be easily applied to variety of storage technologies, the method comprising:

accessing the file that contains a plurality of partitions, wherein the plurality of partitions contained in the file are stored in a storage technology abstracted manner without reference to any particular storage technology, and not implementing file system logic for a particular storage technology, and wherein a description of the file that contains the plurality of partitions is an Extensible Markup Language (XML) file, and wherein each partition contains image data to install to a storage medium and wherein each partition corresponds to a file system, the file comprising;

a first partition, wherein the first partition comprises binary code implementing an update loader;

a second partition, the second partition being a kernel partition, and storing at least one of a RAM image or a ROM image;

a third partition, the third partition being a system partition and comprising operating system files;

a fourth partition, the fourth partition being a user partition specified for user data storage; and

processing the file to introduce any modifications to the plurality of partitions and file system layout as required to convert the plurality of partitions and file system layout from a storage technology abstracted manner to a specific storage technology.

15. The method of claim 14 further comprising, transferring data from the file into the storage medium corresponding to the specific storage technology.

16. One or more computer-readable storage media storing computer-executable instructions which when executed perform the method of claim 15.

17. The method of claim 14 further comprising, accessing a memory configuration file to determine a location of at least one of the partitions within the output file.

18. The method of claim 14 wherein the image data corresponds to packages, and further comprising, generating the file from a partition-to-package mapping file and a memory configuration file.

19. In a computing environment, a computer program product comprising computer readable storage media having stored thereon components for creating a storage technology abstracted file containing partitions corresponding to file systems and for processing the storage technology abstracted file to generate a storage technology specific image file, the components comprising:

a disk image utility process that inputs a partition-to-package mapping file containing partition information and package information, and based on the data in the partition-to-package mapping file, wherein the partition-to-package mapping is an Extensible Markup Language (XML) file outputs an image file using packages identified in the package information, wherein at least some of the packages are operating system image components, and wherein the packages include an update loader component, a kernel component, an operating system files component, and a user data component, the image file comprising a plurality of partitions identified in the partition information, wherein each of the plurality of partitions corresponds to a distinct file system, with the contents of each package stored in one of the partitions based on the description, wherein the data contained in the output image file is maintained in a storage technology abstracted manner, without implementing file system logic for a particular storage technology, so that there is no dependence on any particular storage technology and wherein the output file comprises;

a first partition, wherein the first partition comprises binary code implementing an update loader;

a second partition, the second partition being a kernel partition, and storing at least one of a RAM image or a ROM image;

a third partition, the third partition being a system partition and comprising operating system files;

a fourth partition, the fourth partition being a user partition specified for user data storage; and

a post-process that processes the image file to introduce any modifications to the image as required by a specific storage technology thereby resulting in a storage technology specific image file.

20. The computer program product of claim 19 wherein the disk image utility process further inputs a memory configuration file containing data indicative of how storage for a device is configured.

21. The computer program product of claim 20 wherein the device is configured with memory in which code therein can be executed in place, and wherein the memory configuration file is accessed to fix up at least one of the partitions such that code therein will execute in place.

22. The computer program product of claim 20 wherein the memory configuration file is accessed to determine which sections of device memory are reserved.

23. The computer program product of claim 19 wherein the contents of at least one package corresponds to an operating system component, wherein one of the partitions comprises a system partition, and wherein the disk image utility writes the operating system component to the system partition based on the description.

24. The computer program product of claim 19 wherein the disk image utility writes data to a partition that extends to the end of the file, and adjusts the size of the partition based on the actual amount of data written.

25. The computer program product of claim 19 wherein the disk image utility writes data to the third partition that extends to the end of the file, adding a free space buffer after the end of the data written, and adjusts the size of the third partition based on the actual amount of data written and the free space buffer to enable future updates to the third partition to consume more space than consumed by the data in the current third partition, allowing for growth of subsequent updates.

26. The computer program product of claim 19 wherein the disk image utility writes data to a master boot record in the file to define a partition.

27. The computer program product of claim 26 wherein the disk image utility defines a user store partition by writing data to the master boot record.