General Haiku Discussion

Here you can talk about anything relating to Haiku.

Haiku 2GB .VDI Image

Forum thread started by atri on Mon, 2008-12-15 23:00

All:

(12-15-2008 2:00PM Pacific)
I just built Haiku on OS X 10.5.6 with the latest SVN and made it into a VMWARE Image.

I then used VirtualBox and added a 2GB .VDI drive; formatted the new Virtual Disk, and mounted it then used Tracker to copy over all files from the haiku VMWare image, and issued the makebootable command on it.

After stopping and reconfiguring the VirtualBox to use the new drive, everything worked perfectly and Haiku is running with 512MB RAM, 32MB Video, and 2GB Expanding Disk (networking using Intel tied to my airport) flawlessly.

I decided to zip and upload the expanding .VDI image in case anyone else would like a ready made package to play with and not having to do all the dirty work.
http://www.cranberry.com/Haiku.zip

Thanks.

Nightly images, quick question.

Forum thread started by aKeN on Fri, 2008-12-12 15:07

Hi all,

I have downloaded and tested many times the nightly images of Haiku (both the Vanilla image and the Pre-Alpha one), and my question is:

Normally we can have new images twice a week or even more frequently, but which are the differences between an image and the one of 3 days later??

Is there any place where we can see what changes in those images?

Thanks in advance

How well does Haiku work with Montevina chipset?

Forum thread started by changturkey on Thu, 2008-12-04 21:31

I have a new machine, a Lenovo SL400, that is based off the Montevina chipset. It has the Intel 5100 Wireless chipset.

Spanish translation for Haiku

Forum thread started by aKeN on Wed, 2008-12-03 13:36

Hi all,
I have registrered today but I'm following this forum quite a good moment ago :-)

I started using BeOS Personal Edition in the 90s, then I discovered the Developpers Edition (which I modified a lot to my liking)... afterwards I stopped my relationship with BeOS for a big time :-( I still read about it and tried Zeta... but not very enthusiastically.

For all this years I have been following the progress of BeOS -> OpenBeOS -> Haiku and even try some images within VirtualBox.

Now I'm thinking about come back to this wonderful world of BeOS that I never fully left, and one of the things I would like to start with is helping the community.

One of the things I modified in my customized version of BeOS was the language, I found a way (or any application) to translate all the menus, so everything on my system was in Spanish... but now I really don't remember how I did it or the tool I used. I would like to start doing that but in a way that I can be useful for the community, and I ask you how to do it, and how I can help!!

Thanks all, I will be waiting your answers :-D

aKeN

copyright issues

Forum thread started by apprentice on Mon, 2008-12-01 16:52

I'm sorry if this question has been answered before, but I'm just concerned of this project's future.

Since Haiku copies it's API&ABI (among other things) straight from BeOS isn't it possible that the same firm that made Be bankrupt or the company now in possession of Be's intellectual property might someday have an issue with Haiku.

When it comes to Microsoft, they have never wanted to monopolize the market, they want to be the only player around. When BeOS was ported from PPC to Intel architecture Microsoft noticed that they had a rival and the rival even (to be totally honest) had a far better product for the desktop market than Microsoft or even Apple (at the time) had. Microsoft has been trying to kill linux since the late 90's and considering the amount of people using linux at the time that seemed like a bit of an over reaction. They have finally - albeit - silently admitted that they can't kill linux since it's an ideology. Haiku on the other hand will be a serious alternative to linux/windows in ~4 years and undoubtedly Microsoft or some other company will try to attack it at some point.

I guess this issue has been resolved already, but I would appreciate if someone would shed some light on this matter and explain to a business illiterate person if this concern is in vain.

[Resolved] Booting to Haiku from Grub only works when Haiku installed in a Primary partition?

Forum thread started by paulfxh on Thu, 2008-11-27 18:35

I have a spare primary partition on my Asus EeePC 901 20 GB where I installed a Haiku raw image (downloaded to Ubuntu and dd'ed it over to the "haiku" partition).
Then I made it bootable by running "makebootable" from within Ubuntu.
As has been well documented recently, this works perfectly.
However, I then decided to go a step further and take out that primary partition, create an extended partition in its place and put two logical partitions within the extended.
Now I copied the haiku-alpha.image over to one of the logicals and made it bootable as usual. Everything fine up to now so I made the appropriate changes to the Grub boot menu for the new location of Haiku. So now the Grub entry for Haiku looked like this:

##Haiku
title   Haiku-alpha 25-11-2008
rootnoverify (hd1,4)
makeactive
chainloader +1

Then I tried to boot Haiku and got

Quote:

Error 12: Invalid device requested

After much totally fruitless messing around, I re-created the primary partition I had deleted and re-installed Haiku as before.
Once again, it booted fine.
So, it seems I can't get Haiku to boot from a logical partition.
Anybody know why or how to get around this?

How to get, JAM, and install Haiku in Ubuntu 8.10 (Intrepid Ibex)

Forum thread started by Luposian on Mon, 2008-11-24 04:44

“How to Get and JAM and Install Haiku in Ubuntu 8.10 (Intrepid Ibex)”
Written by Luposian (Nov. 23, 2008)
Version 1.0

*Thanks go out to Ryan Leavengood and Fredrik Ekdahl (as well as to the various people who commented to both original posts) for helping make it possible to write up this “all in one place” manual. My own struggles to get where I finally got to, are now “simplified” for one and all, so that others needn't go through what I had to, to get here.

The battle was mine. The reward is yours. Enjoy.

------

These instructions assume you have/use a computer that you have been using BeOS (first partition) and Haiku (second partition) on previously. Having two partitions on your drive is also a requirement (leave a previous install of Haiku or Senryu on the second partition (i.e. when you install Ubuntu 8.10, don't mess with the second partition! Ubuntu won't know what the second partition is (“unknown”), but that doesn't matter.)). And, as I have thus only installed Haiku, via Ubuntu 8.10, on an UDMA133 ATA drive, it is assumed your system is similarly equipped.

Ready to begin? Great! Let's go!

Bring up the Terminal (it's in Application → Accessories).

Type: sudo apt-get install subversion autoconf automake texinfo flex bison gawk build-essential

Type in your System password and hit [Enter]. Ubuntu will download/install various files.

When you see the Terminal prompt again, type:

mkdir develop
cd develop
mkdir haiku
cd haiku
svn checkout svn://svn.berlios.de/haiku/buildtools/trunk buildtools

The last command will download the the Haiku build tools.

When the Terminal prompt reappears, type:

cd buildtools/jam
make
sudo ./jam0 install
cd ../..

Use the same password you used before, when it asks. Now, to get the Haiku source tree! At the Terminal prompt, type:

svn checkout http://svn.berlios.de/svnroot/repos/haiku/haiku/trunk trunk

On my system (AMD Athlon XP 2000+, 512Mbytes RAM, Intel 10/100 NIC, nVidia GeForce 2 GTS, 20Gb UDMA133 ATA drive), with a 10Mbit/sec. Cox Cable Internet connection (Ethernet), the entire Haiku source tree was downloaded in 25 minutes. Oddly enough, in BeOS, on this same system, it takes about 2 hours! So, whatever time it takes for you, in BeOS, expect it to take a lot LESS time (just under ¼ the time, in my case), in Ubuntu 8.10! Naturally, future downloads (updates) won't take as long.

Now, to build the cross-compiler tools! At the Terminal prompt, type:

cd ~/develop/haiku/trunk
./configure --build-cross-tools ../buildtools/

My efforts to build the GCC4 tools failed, for some reason, so until whatever caused my attempts to fail are no longer an issue, just use the above command (which builds the GCC 2.95 tools), which worked fine for me.

When the Terminal prompt reappears, to build an image of Haiku, just type:

jam -q haiku-image

This took only 45 minutes on my system, in Ubuntu 8.10, but BeOS takes about 2 hours on this task as well. So, expect MUCH faster JAM times as well.

Ok, everything went smooth as silk and you've got a copy of haiku.image in /generated, right? Now what? Gotta get the image over to that second partition, right? Well, not quite so fast... let's get GRUB all set up and happy, first, shall we?

At the Terminal prompt, type:

sudo gedit /boot/grub/menu.lst

Type the same password... again! Sudo gets you places you can't get, otherwise, but it's kinda a pain to have to keep typing in the system password each time. Oh, well...

You should now see the contents of the menu.lst file. You only want to change a few areas and not mess with the rest.

In the menu.lst file, you will see some lines that look like this:

title Windows...
root (hd0,5)
chainloader +1

Uncomment those three lines (remove the # symbol on each line) to “activate” them and then make sure they look like this:

title Haiku
rootnoverify (hd0,1)
chainloader +1

Now, go to the “timeout 5” line and change it to “timeout 10” (this gives you a little more time to decide which OS you want to boot into).

Comment out (add a # symbol in front of) “hiddenmenu”. This will then allow you to SEE the OS menu!

Go to “Pretty colours” and uncomment the line below it (if you want a color menu, otherwise ignore it)

Ok, now click on the Save menu option in gedit and the GRUB menu is now changed.

Close all the windows and reboot. When the GRUB menu pops up, just sit back and wait til it times out. The topmost OS in the menu will be loaded by default (the menu is displayed in alphabetical order), so Haiku/Senryu will be the OS that loads when it times out.

Did it come up? It should have. If your second partition is shown as ”/dev/sda2” in Partition Editor, then it should work, unless you don't have Haiku/Senryu on that second partition. This “test bootup” allows you to see that the GRUB menu works as expected, and loads the previous OS from your second partition, before you actually JAM Haiku over to the second partition.

Now, for the final move... JAM'ing Haiku onto that partition.

Reboot and select the Ubuntu OS option just under Haiku. You're now back in Ubuntu 8.10.

Go to “UserBuildConfig.sample” and open 'er up in gedit. You will see four lines:

# Install Haiku on device /dev/sda57. Be sure you know what you're doing!
HAIKU_IMAGE_DIR = /dev ;
HAIKU_IMAGE_NAME = sda2 ;
#HAIKU_DONT_CLEAR_IMAGE = 1 ;

Uncomment the two lines in the middle (as shown) and make sure they match the above example. Save it. Now, just rename the file to “UserBuildConfig” (drop “.sample” from the filename) and you're ready to go!

In Terminal, get to Haiku's /trunk directory and type:

jam -q

Hey, wait a second... it didn't work! Why? I dunno, but it doesn't. But you HAVE to do it the wrong way first, for some reason. No worries, though... it'll work this next time (it did for me). Type:

sudo jam -q

Aw, man... sudo AGAIN? Type the password... one...more... time. :-)

And, BINGO! It works like a charm! Or at least it should... it did for me.

Reboot your computer and watch your latest revision of Haiku come up.

Enjoy!

Luposian

Syndicate content