I basically installed everything in Haiku the way I normally do in BeOS. I then was able to download the source tree of Haiku in about 1 hour on Athlonica64. The new networking in Haiku is… F A S T ! Doing the same thing in BeOS takes over 2 hours!
Anyways, as far as I know, I have the entire source tree. Then I tried “Jam -q haiku.image” and it tells me “Operation not allowed”. Why? Do I need a different version of Jam? Is something not configured properly?
Does someone have instructions for “Getting/building Haiku” from WITHIN Haiku? I’ll even gladly modify DarkWyrm’s “Getting Haiku” docs (for BeOS R5) that I “simplified” and make it specifically address Haiku.
My install of BeOS now can’t remember my NIC card across reboots and I need to remove the “unseen” NIC and then reboot and reconfigure it every time I reboot or start up my system. It’s a real PITA!
I am ready to put BeOS R5 out to pasture for good (BeOS works fine on Athlonica (Athlon XP system) and always sees the NIC, but doesn’t particularly like Athlonica64, as far as remembering the NIC card is actually INSTALLED… otherwise, it works great… albeit a LOT slower than Haiku, as for downloading the source tree) … I just need to be able to build Haiku from within Haiku and it’s a done deal.
I am posting from Haiku r27976 built from within haiku. It took me for ever to download the source … about 2 1/2 hrs on a fast connection. I have been attempting to jam from within haiku for about a year, this is the first time it worked. I first built haiku from within Ubuntu linux adding all the optional packages and installed it on a partition by booting zeta and copying the haiku-image file to a bfs partition then running mountimage to access the files. I then copied all the files to a newly created bfs partition for haiku and ran makebootable and bootman from zeta. I then could boot haiku.
I mounted a separate bfs partition to hold the sources and ran an svn checkout. using the instructions found here
This takes about 2 1/2 hours.
I then ran configure and jam-q
It took about 4 hours to jam the source tree (about five times longer than it takes in Ubuntu.)
I then booted to zeta so I could mount the new haiku.image and copy the files to the haiku partition. I re-booted and WOOT it worked! I am running Haiku that was built from within Haiku. too bad mountimage doesn’t work in Haiku, I would not need Zeta to make haiku boot.
You can compile directly to a partition from within BeOS/Zeta/Haiku by mounting it and using jam -q install-haiku (assuming you’ve edited your UserBuildConfig to tell it what path to install to)…
no need to create an image, mount it, and copy the files manually
I’ve done this several times to another BFS partition, but you currently cannot install over the top of a running Haiku instance (there’s a bug about that somewhere IIRC).
UPDATE: Oh, btw, you can mount a BFS image file directly in Haiku using the mount commandline…no need for a separate tool.
[quote=bbjimmy]I am posting from Haiku r27976 built from within haiku. It took me for ever to download the source … about 2 1/2 hrs on a fast connection. I have been attempting to jam from within haiku for about a year, this is the first time it worked. I first built haiku from within Ubuntu linux adding all the optional packages and installed it on a partition by booting zeta and copying the haiku-image file to a bfs partition then running mountimage to access the files. I then copied all the files to a newly created bfs partition for haiku and ran makebootable and bootman from zeta. I then could boot haiku.
I mounted a separate bfs partition to hold the sources and ran an svn checkout. using the instructions found here
This takes about 2 1/2 hours.
I then ran configure and jam-q
It took about 4 hours to jam the source tree (about five times longer than it takes in Ubuntu.)
I then booted to zeta so I could mount the new haiku.image and copy the files to the haiku partition. I re-booted and WOOT it worked! I am running Haiku that was built from within Haiku. too bad mountimage doesn’t work in Haiku, I would not need Zeta to make haiku boot.
[/quote]
You ain’t seen fast, til you’ve seen what Athlonica can do, using Ubuntu 8.10 (Intrepid Ibex)… 25 min. to download the entire sources and 45 minutes to JAM. And this is the FIRST run. Not later downloads/JAM’s. BeOS, on the exact same system, took about 2 hours to do each. Seriously!
And “Athlonica” is only an Athlon XP 2000+ CPU with 512Mb of RAM, GeForce 2 GTS video card, Intel 10/100 NIC, and a 10Mbit/sec. Cox cable internet connection.
Now, I just want to know exactly how to mount/copy my freshly JAM’d copy of “haiku.image” to the 9.7Gbyte BFS partition I have (when I was using BeOS) on the drive.
You ain’t seen fast, til you’ve seen what Athlonica can do, using Ubuntu 8.10 (Intrepid Ibex)… 25 min. to download the entire sources and 45 minutes to JAM. And this is the FIRST run. Not later downloads/JAM’s. BeOS, on the exact same system, took about 2 hours to do each. Seriously!
And “Athlonica” is only an Athlon XP 2000+ CPU with 512Mb of RAM, GeForce 2 GTS video card, Intel 10/100 NIC, and a 10Mbit/sec. Cox cable internet connection.
Now, I just want to know exactly how to mount/copy my freshly JAM’d copy of “haiku.image” to the 9.7Gbyte BFS partition I have (when I was using BeOS) on the drive.
Instructions specific to Ubuntu are appreciated.
This is similar to my experience using ubuntu Hardy Heron. I was discussing compiling from within Haiku.
