Written by arzajac the 15 Apr 08 at 13:41.
Why do we need to reboot after the system is installed?
Whether we are installing from the live or the alternate installer, we have a kernel in memory.
Would it be possible to copy the contents of the ramdisks onto the hard drive, do other clean up tasks and then pivot_root into the new system? If running from the alternate cd, then X would be started...
There are occasions where a user can run the live cd, install some applications and customize the desktop only to have to repeat these steps after the installation has taken place. This would avoid that; the user would not have to repeat the same steps again.
My issue with this is that for me, and a lot of other people, grub stuffs up and wont work, so they cant boot.
For me I need to edit my entries to boot, and manually edit the grub config after (even on 8.04 beta). Skipping a test of grub means that people might spend ages customising, only to discover they cant boot.
This would not increase the chances of the bootloader being improperly installed, nor would it change the way you go about fixing it. It would simply postpone the first time you would actually need to use it.
To rely on a reboot to complete the install is a little sloppy. The only time you should be forced to reboot is when you absolutely need to. For example (and not limited to): upgrading the kernel (and there may come a day when you could do this on-the-fly), upgrading HAL or changing your hardware and need the power to be off.
Is it necessary to reboot to start using a newly installed Ubuntu system?
The main advantage would be the wow effect. Windows XP needed two reboots to install IIRC (don't know about Vista), and the Ubuntu installer is already quite slick as it is. Of course, I admit that after installing is one time when a reboot is reasonable, as you will not yet have any critical services running.