Author Topic: Interesting Installer - Review on Ars Technica  (Read 2029 times)


  • Member
  • *
  • Posts: 28
    • OpenTrack - 2d video tracking software
Interesting Installer - Review on Ars Technica
« on: October 21, 2010, 06:11:37 am »
Hey folks,

I just read a review on Ars Technica about the changes to Ubuntu's installer with their latest version (10.10):

While I love our current installer (have now put the latest/greatest on two desktops and a laptop without issue, the last upgrade taking only about an hour to complete), this new Ubuntu installer does something that's kind of cool: it multitasks by doing some of the configuration things while files are being copied. 

So I wonder how possible it would be to set up the root and user accounts, choose GRUB or LILO, choose network settings, location/time zone and the works while the packages are being copied into place.  I realize that this opens a can of worms with respect to fixing something that's not broken and that our installer really is just fine (it's as good as it has ever been), but perhaps this is something we could consider, time allowed.

Thanks for a great VL 6.0 SOHO Deluxe Edition.
Tim Niiler


  • Administrator
  • Vectorian
  • *****
  • Posts: 3498
Re: Interesting Installer - Review on Ars Technica
« Reply #1 on: October 21, 2010, 06:38:18 am »
I guess if you re-think the process of an installation, it's not technically ipossible.

You see, ubuntu is a live cd, this means that the tools needed to do the configuration are available at all times, even before packages are copied. In our case, we have our tools needed in the initrd that we use to boot into the live system and then use these to execute the install process.

But, if you're working with a live cd, there is really no reason to wait until the files are copied to perform the configuration. This is why they ask for user names, passwords, localization settings, etc before any packages are copied into the system. These values must be kept somewhere and must execute during the install process.

Example: Bootloader.
In a live system, you should have the tools needed to configure the bootloader. They normally hide these settings by defaulting to /dev/[hs]da, but they have the grub commands available to begin with, so they can easily just run `grub-install /dev/[hs]da` and when the installation copletes, just run `update-grub` to update the OS listings.

It's certainly not impossible, and given multi-threaded and multi-processor processing, not even that complicated.

So, "how come we dont have this in our installer?" you ask
The VL GUI installer is written in Gambas2, which was probably not the best choice, but seemed easy enough at the time.
Definitely something we can do and not only match, but beat it. ;)