updating Haiku alpha to the latest nighly build

Forum thread started by farvardin on Sun, 2010-01-24 07:58

Hello,

I have installed Haiku alpha since its release, and I'd like to have an updated version, by using a nightly buid without deleting my /home and all the extra apps I've already installed.

Is there a best way to do this, or do I have to save everything, install Haiku again, and restore my saves?

‹ How do I get the "Anyboot" image onto my USB device? Where does grapics driver go? ›

Comments

Re: updating Haiku alpha to the latest nighly build

by cipri - 2010-01-24 12:38

You don't have to do anything. Just install the nightly build on the same partition again, your files will still be there (if you don't manually format the partion).

Re: updating Haiku alpha to the latest nighly build

by farvardin - 2010-01-24 16:44

thank you, it worked as you described.

Advices to people who may want to do the same:

- be aware all gcc2 applications will no longer work (including old beos software)
- you'd better keep an archive of a working gcc4 browser at hand, because for example Bezilla won't work anymore (gcc2). I could download a working version from haiku-files thanks to the Arora browser from TiltOS projet (box -i arora). Bezilla is much more stable though.
- the BeZilla compiled 3 days ago won't load (missing libnet.so) until you create a symbolic link from libnetwork.so to libnet.so from the folder /boot/system/lib

Re: updating Haiku alpha to the latest nighly build

by hey68you - 2010-01-25 14:53
cipri wrote:

You don't have to do anything. Just install the nightly build on the same partition again, your files will still be there (if you don't manually format the partion).

Can you please provide more details about this:

What I tried and I got an error using last night's nightly image running a R1 installed on a partition:
1) mount the image from the terminal using the 

mountvolume

command.
2) Use the installer and choose the to install on the existing and running Haiku boot volume
3) Press ok on the warnings

Then I think I got an IO error Alert box. ( I could try again if you want to know the exact error).

Thanks,
hey68you

Re: updating Haiku alpha to the latest nighly build

by tonestone57 - 2010-01-25 18:24

yes, please provide more information so we know exactly how you went about doing this. I would like to know and so would others that read this thread. Thanks.

Re: updating Haiku alpha to the latest nighly build

by richienyhus - 2010-01-25 22:04
hey68you wrote:

Use the installer and choose the to install on the existing and running Haiku boot volume

Would it not make more sense to install from a running nightly USB volume onto a non-running hard drive boot volume?

Re: updating Haiku alpha to the latest nighly build

by farvardin - 2010-01-26 02:55

I don't think it's possible to upgrade from the running alpha1 system.

I simply downloaded the latest nightly build, burned this iso on a cdrw, ran this cd and installed it on my current haiku partition.

Re: updating Haiku alpha to the latest nighly build

by hey68you - 2010-04-28 14:09

Guess what !

This overwriting method finally worked for me without have to burn a CD or write to a USB stick:

Steps:

  • 1) Burned a CD iso image of r36263 (from around April 15, 2010).
  • 2) Installed it to a cleaned BFS partition (no R1 artifacts).
  • 3) Used it for a couple of weeks (you can skip this step).
  • 4) Downloaded raw nightly image .zip of (haiku-r1a2-rc-r36511-x86gcc2hybrid-raw.zip)
  • 5) Extracted the haiku-alpha.image file to /boot
  • 6) Using the CD of older r36263, reboot into Desktop (not into Installer)
  • 7) Mount (both read+write) the boot disk of version r36263 that's installed on the partition (from step 2)
  • 8) Within this disk, mount newer haiku-alpha.image that you extracted in step 5 by just double-clicking the file in Tracker.
  • 9) Run the installer from the newly mounted Haiku virtual drive (found at /Haiku/system/apps/Installer
  • 10) Choose install from virtual drive
  • 11) Choose install to existing old r36263 real partition from step 2
  • 12) Choose "install anyway" button when it tells you there's already an installation there.

It sounds more complicated than it was :)

But now after reboot it's updated to r36511.

Great work to all core devs and contributors!