mirror of
https://review.haiku-os.org/haiku
synced 2025-01-31 18:56:49 +01:00
2ac748daf1
that an error can be propagated back to vm_soft_fault(). * Added boolean restart reference parameter to fault_find_page() which is set to true whenever a condition is it encountered that requires to start fault_find_page() from the very beginning. fault_get_page() checks the flag and executes fault_find_page() in a loop, now. * Removed the panic()s+TODOs in fault_find_page() when a cache became busy. The restart feature is used in this case. * fault_find_page(): If after the loop we haven't found a page yet, and after locking the right cache one turned up, we restart the function, too, thus avoiding double insertion of a page into a cache. * Fixed potential dead-lock in fault_get_page(): After inserting a clean page into a cache other than the top cache (read fault on copy-on-write area not backed by a file (e.g. the heap)) the dummy page was removed from the to be locked top cache while we still held a lock for the lower cache, thus inverting the locking direction required by the cache locking policy (top -> bottom). * fault_get_page(): In case of a write access and a readable page found in a lower cache, vm_cache_remove_consumer() could have replaced our dummy page with a real page from a collapsed lower cache while we had unlocked both caches. We didn't check for this condition and always inserted our freshly allocated page, thus potentially inserting a duplicate page into the top cache. We do the check now and discard our page, when another page turned up. Fixes bug #1359. * fault_get_page(), same if block: Removed unused case for removal of the dummy page from a non-top cache. We only ever insert it into the top cache and it should not be moved to another cache. Added an assert. git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@21841 a95241bf-73f2-0310-859d-f6bbb57e9c96
Building on BeOS ================ For building on BeOS you need the development tools from: http://haiku-os.org/downloads Please always use the most recent versions. They are required to build Haiku. Building on a non-BeOS platform =============================== Please read the file 'ReadMe.cross-compile' before continuing. It describes how to build the cross-compilation tools and configure the build system for building Haiku. After following the instructions you can directly continue with the section Building. Configuring on BeOS =================== Open a Terminal and change to your Haiku trunk folder. To configure the build you can run configure like this: ./configure --target=TARGET Where "TARGET" is the target platform that the compiled code should run on: * haiku (default) * r5 * bone * dano (also for Zeta) The configure script generates a file named "BuildConfig" in the "build" directory. As long as configure is not modified (!), there is no need to call it again. That is for re-building you only need to invoke jam (see below). If you don't update the source tree very frequently, you may want to execute 'configure' after each update just to be on the safe side. Building ======== Haiku can be built in either of two ways, as disk image file (e.g. for use with emulators) or as installation in a directory. Image File ---------- jam -q haiku-image This generates an image file named 'haiku.image' in your output directory under 'generated/'. VMware Image File ----------------- jam -q haiku-vmware-image This generates an image file named 'haiku.vmdk' in your output directory under 'generated/'. Directory Installation ---------------------- HAIKU_INSTALL_DIR=/Haiku jam -q install-haiku Installs all Haiku components into the volume mounted at "/Haiku" and automatically marks it as bootable. To create a partition in the first place use DriveSetup and initialize it to BFS. Note that installing Haiku in a directory only works as expected under BeOS, but it is not yet supported under Linux and other non-BeOS platforms. Building Components ------------------- If you don't want to build the complete Haiku, but only a certain app/driver/etc. you can specify it as argument to jam, e.g.: jam Pulse Alternatively, you can 'cd' to the directory of the component you want to build and run 'jam' from there. You can also force rebuilding of a component by using the "-a" parameter: jam -a Pulse Running ======= Generally there are two ways of running Haiku. On real hardware using a partition and on emulated hardware using an emulator like Bochs or QEmu. On Real Hardware ---------------- If you have installed Haiku to its own partition you can include this partition in your bootmanager and try to boot Haiku like any other OS you have installed. To include a new partition in the BeOS bootmanager run this in a Terminal: bootman On Emulated Hardware -------------------- For emulated hardware you should build disk image (see above). How to setup this image depends on your emulater. A tutorial for Bochs on BeOS is below. If you use QEmu, you can usually just provide the path to the image as command line argument to the "qemu" executable. Bochs ----- Version 2.2 of Bochs for BeOS (BeBochs) can be downloaded from BeBits: http://www.bebits.com/app/3324 The package installs to: /boot/apps/BeBochs2.2 You have to set up a configuration for Bochs. You should edit the ".bochsrc" to include the following: ata0-master: type=disk, path="/path/to/haiku.image", cylinders=122, heads=16, spt=63 boot: disk Now you can start Bochs: $ cd /boot/apps/BeBochs2.2 $ ./bochs Answer with RETURN and with some patience you will see Haiku booting. If booting into the graphical evironment fails you can try to hit "space" at the very beginning of the boot process. The Haiku bootloader should then come up and you can select some safe mode options. Docbook documentation ===================== Our documentation can be found in 'src/documentation/'. You can build it by running 'jam' in that folder. The results will be stored in the 'generated/' folder.