UBfusion
January 19th, 2007, 01:30 AM
Bare with me, I just want to express how satisfying is to manage installing Feisty Desktop (alternate installs ok) for the first time ever from an iso!
I can proudly report that at least in VMware the python script bugs that I and several testers were experiencing in Herd2 and later builds gone in build 20071118. However there's a small formatting error that needs to be addressed. Instructions follow:
1. Create a new VM guest with the usual settings. Set the iso as boot CD.
2. When feisty boots, the installer will pass all the screens and ask to partition the disk.
3. Choose to partition the whole disk and proceed. The process will hang at 15% and the the VM will freeze totally. Shutdown the VM.
4. Reboot the VM and in Bios setup choose to boot first from the CD (i.e. the iso). Save settings and reboot.
5. Feisty live will start again. If at this point you try to reinstall, try the manual partitioning. You will see that the correct partitions were created indeed but they were not formatted properly. This is why the installation hangs. (I have seen many similar bugs in launchpad)
6. Now open a terminal and format the partitions manually using sudo mkfs.ext3 /dev/sda1 and sudo mkswap /dev/sda5
7. Go to the installer screen and press "back" to restart the partitioning process and choose manual partitioning. You will then see that the installer correctly identifies the mount points.
8. Proceed with the installation, installation will successfully complete!!!
9. Press "Restart now". (In case Feisty has frozen, just power down the VM). When the Bios screen appears, power the VM down and in the VM menu change the settings to replace the feisty iso with a normal cd drive (so that the VM won't boot from the CD again).
10. Feisty will boot gloriously with "crash report" and "available updates" notifications.
FEISTY IS UP and running :D
Clicking the crash report notification icon will lead to the reporter's crashing. My feeling is that this does not need a bug report (see below).
There will be ~18 updates available. Install them and restart feisty. No more crash report icon! Apparently the gtk libs included in the updates did their magic.
Conclusion: In previous builds I had tried manual formatting but it didn't work. In my opinion 20070118 is a major step forward in the development of feisty daily builds. When the partitioning process is fully debugged my feeling is that the desktop x64 will be ready for thorough testing, possibly leading to Herd3.
Well done development team! Tomorrow I'll install on a real new HDD.
I can proudly report that at least in VMware the python script bugs that I and several testers were experiencing in Herd2 and later builds gone in build 20071118. However there's a small formatting error that needs to be addressed. Instructions follow:
1. Create a new VM guest with the usual settings. Set the iso as boot CD.
2. When feisty boots, the installer will pass all the screens and ask to partition the disk.
3. Choose to partition the whole disk and proceed. The process will hang at 15% and the the VM will freeze totally. Shutdown the VM.
4. Reboot the VM and in Bios setup choose to boot first from the CD (i.e. the iso). Save settings and reboot.
5. Feisty live will start again. If at this point you try to reinstall, try the manual partitioning. You will see that the correct partitions were created indeed but they were not formatted properly. This is why the installation hangs. (I have seen many similar bugs in launchpad)
6. Now open a terminal and format the partitions manually using sudo mkfs.ext3 /dev/sda1 and sudo mkswap /dev/sda5
7. Go to the installer screen and press "back" to restart the partitioning process and choose manual partitioning. You will then see that the installer correctly identifies the mount points.
8. Proceed with the installation, installation will successfully complete!!!
9. Press "Restart now". (In case Feisty has frozen, just power down the VM). When the Bios screen appears, power the VM down and in the VM menu change the settings to replace the feisty iso with a normal cd drive (so that the VM won't boot from the CD again).
10. Feisty will boot gloriously with "crash report" and "available updates" notifications.
FEISTY IS UP and running :D
Clicking the crash report notification icon will lead to the reporter's crashing. My feeling is that this does not need a bug report (see below).
There will be ~18 updates available. Install them and restart feisty. No more crash report icon! Apparently the gtk libs included in the updates did their magic.
Conclusion: In previous builds I had tried manual formatting but it didn't work. In my opinion 20070118 is a major step forward in the development of feisty daily builds. When the partitioning process is fully debugged my feeling is that the desktop x64 will be ready for thorough testing, possibly leading to Herd3.
Well done development team! Tomorrow I'll install on a real new HDD.