Thiemo Nagel <thiemo.nagel@gmail.com> writes: >>>The only reason I can think of is that it helps prevent accidentially >>>rebooting the computer half way through the install and encountering a >>>strange half-installed system. >> >> Definitely, yes. If for some reason the installation is aborted, there >> is a good chance that the system will at least reboot to the other >> side of a dual-boot instead of leaving things dead. >> >> There are also potential issues here with ordering - the bootloaders >> may depend on quite a lot of packages and/or state in the system being >> installed. > > Well, what I propose is to install the bootloader (and run the > finish.d scripts) after the base system has been installed. Or, in > other words, to postpone tasksel until after bootloader installation > (and finish.d scripts). I don't see how this could result in an > unbootable system as this is basically the same as running the > installation full-cycle without selecting anything in tasksel. Which is liable to be _very_ confusing, and could easily waste a lot of time and/or convince the victim that Debian is an incomprehensible mess. =-=-=- I suppose that could be mitigated if we created a file something like: /target/Instalation-In-Progress as soon as we mount the target system's root, which we'd delete just before unmounting the file system at the end of the install, and then check for that after the first boot and if found pause the boot with a big warning about an incomplete install. The first-boot-install-check script could offer to delete the file if found, and after that, delete itself to keep things tidy. I'm not sure that's a good idea though -- it seems somewhat fragile. Cheers, Phil. -- |)| Philip Hands [+44 (0)20 8530 9560] http://www.hands.com/ |-| HANDS.COM Ltd. http://ftp.uk.debian.org/ |(| 10 Onslow Gardens, South Woodford, London E18 1NE ENGLAND
Attachment:
pgprgTH2eboDB.pgp
Description: PGP signature