1 / 18

Software Installation Using Disk Images

Software Installation Using Disk Images. By: Irena Lanc and Peter Sempolinski. Software Installation . Conventional methods of software installation involve: Downloading the package Unpacking Compiling Managing path and environment variables

elsie
Download Presentation

Software Installation Using Disk Images

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Software Installation Using Disk Images By: Irena Lanc and Peter Sempolinski

  2. Software Installation • Conventional methods of software installation involve: • Downloading the package • Unpacking • Compiling • Managing path and environment variables • This leads to package files being strewn in directories across disk. • How can this system be made more efficient?

  3. Our Idea • Create a disk image of the software package, and mount it as a loop device. Virtual File System Image un-installation script Unionfs Image-installation script X X Loop-mounted Device Loop-mounted Device Loop- mounted Device Loop- mounted Device Underlying ext2 filesystem

  4. Basic Working Prototype

  5. Basic Working Prototype

  6. Basic Working Prototype

  7. Basic Working Prototype

  8. Basic Working Prototype

  9. Basic Working Prototype

  10. Basic Working Prototype

  11. Basic Working Prototype

  12. Basic Working Prototype

  13. Basic Working Prototype

  14. Basic Working Prototype

  15. Basic Working Prototype

  16. Complications • Number of loop devices hard-limited in kernel • Possible to ask for more devices at boot time. However, this greatly slows down the boot sequence when number of devices > 4000. • System accommodates up to 1000 devices comfortably. • A typical system could have between 1000-2000 software packages

  17. Complications • Dependencies • Images created using files from debian packages, but since we’re re-packaging, dependencies not automatically fetched. • Further tools needed to manage dependencies. • Unionfs • Demands careful coordination of merges by the script. • As yet untested in scalability when merging hundreds of packages.

  18. Road Ahead • 1. Add more scripts to manage dependencies, and generally make system easier to use. • 2. Create a test bed to obtain metrics such as program install time, memory/processor usage, and scalability. • 3. Kernel hacking • To get more out of Unionfs/loopback devices, certain aspects could be modified to provide more flexibility and better performance

More Related